Fibre Channel Registered State Change Notification (RSCN) MIB
Extracted elements (21)
No per-Event-Qualifier counters are defined for Event Qualifier value '0001'b ('Changed Name Server Object') because these RSCNs are already counted by t11NsInRscns and t11NsOutRscns in RFC 4438, avoiding duplication.
Notifications in this MIB are generated by control-plane events (SCR/RSCN/SW_RSCN rejections) that cannot start a chain reaction, so the extra complexity of flow-controlling these notifications is not warranted; no suppression counters or end-of-interval notifications are defined.
When both fcmSwitchIndex and t11FcRscnFabricIndex appear in the same INDEX clause, fcmSwitchIndex is listed first to simplify management protocol queries concerning all Fabrics to which a single switch is connected.
Whether operating on a Physical Fabric or within a Virtual Fabric, RSCN operation is identical; the Fabric Index is always 1 in single-fabric environments, providing backward compatibility with non-Virtual-Fabric deployments.
Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; instead SNMPv3 with cryptographic security enabled is RECOMMENDED.
Implementors are RECOMMENDED to consider the SNMPv3 security features including full support for SNMPv3 cryptographic mechanisms for authentication and privacy.
The compliance statement requires t11FcRscnRegistrationGroup, t11FcRscnNotifyControlGroup, and t11FcRscnNotifyGroup as mandatory groups; t11FcRscnStatsGroup is mandatory only for systems that count such events.
Values written to t11FcRscnIlsRejectNotifyEnable and t11FcRscnElsRejectNotifyEnable SHOULD be retained over agent reboots.
Write access to t11FcRscnIlsRejectNotifyEnable and t11FcRscnElsRejectNotifyEnable is not required for compliance; MIN-ACCESS read-only is permitted.
Per-Event-Qualifier RSCN counters track: Unspecified ('0000'b), Changed Port Attribute ('0002'b), Changed Service Object ('0003'b), Changed Switch Configuration ('0004'b), and Removed Object ('0005'b), both inbound and outbound.
t11FcRscnElsRejectReqNotify is an SNMP notification generated when a switch rejects an SCR or RSCN (ELS-level); it carries the rejected request string, source WWN, reason code, explanation, and vendor code.
t11FcRscnIlsRejectReqNotify is an SNMP notification generated when a switch rejects an SW_RSCN (ILS-level inter-switch); it carries the same varbinds as t11FcRscnElsRejectReqNotify.
The t11FcRscnFabricIndex (T11FabricIndex syntax) uniquely identifies a particular Fabric within a physical infrastructure; its value is always 1 for single-fabric deployments without Virtual Fabrics.
The t11FcRscnNotifyControlTable provides per-Fabric notification control, storing the binary content (up to 255 octets) of the most recently rejected SCR/RSCN/SW_RSCN, its source WWN, reason code, reason code explanation, and vendor-specific code.
The t11FcRscnRegTable enumerates Nx_Ports that have registered to receive RSCNs on all Fabrics configured on one or more Fibre Channel switches, indexed by fcmInstanceIndex, fcmSwitchIndex, t11FcRscnFabricIndex, and t11FcRscnRegFcId.
The t11FcRscnRegType object is a BITS field indicating the type of RSCN registration desired: 'fromFabricController' (bit 0) for events detected by the Fabric Controller, and 'fromNxPort' (bit 1) for events detected by the affected Nx_Port.
The t11FcRscnStatsTable provides RSCN-related statistics per switch per Fabric, including counters for SCRs received/rejected, RSCNs sent/received/rejected, SW_RSCNs sent/received/rejected, and per-Event-Qualifier RSCN counts.
IANA assigned OID mib-2 161 for the T11-FC-RSCN-MIB module. The MIB is rooted at this OID and defines the t11FcRscnMIB MODULE-IDENTITY.
Readable objects including t11FcRscnRegTable (registered Nx_Ports), t11FcRscnStatsTable (RSCN statistics), and t11FcRscnNotifyControlTable (rejection details including WWNs and payloads) may be sensitive and should have GET/NOTIFY access controlled, with encryption recommended for values sent over the network.
SNMP versions prior to SNMPv3 lack adequate security; even on a network secured by IPsec, they provide no per-principal access control for GET/SET operations on MIB objects.
The read-write objects t11FcRscnIlsRejectNotifyEnable and t11FcRscnElsRejectNotifyEnable are sensitive: misconfiguration can cause unwanted notifications to be generated or wanted notifications to be suppressed, impacting network management visibility.