Fibre Channel Fabric Configuration Server MIB
Extracted elements (26)
Notification flow control (suppression counters, end-of-interval notifications) is not applied to the three notifications in this MIB because they are triggered by control-plane events rather than data-plane events, making it impractical to bound their frequency and making the extra complexity unwarranted.
OS LUN Map Entry information (part of a Platform in FC-GS-5) is intentionally excluded from this MIB; instead, it is available via the scsiLunMapGroup in SCSI-MIB (RFC 4455) to avoid duplication and keep MIB scope focused.
The T11FcListIndex / T11FcListIndexPointerOrZero pattern is used to represent multi-valued attributes (management address lists, attached port name lists, node name lists) as separate tables pointed to by index, avoiding variable-length embedded sequences within a single row.
When a device is connected to a single physical Fabric without virtual Fabrics, the Fabric Index (T11FabricIndex) always has the value 1. Multiple physical or virtual Fabrics each receive a distinct index value per FC-SW-4.
When fcmSwitchIndex and t11FcsFabricIndex both appear in an INDEX clause, fcmSwitchIndex is listed first to simplify management queries about all Fabrics connected to a single switch.
It is RECOMMENDED that implementors support the SNMPv3 framework including full cryptographic mechanisms for authentication and privacy. Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; SNMPv3 with cryptographic security SHOULD be deployed instead.
Setting t11FcsFabricDiscoveryStart to 'start' MUST be rejected if a discovery is already/still in progress on any Fabrics in the specified range.
Values written to objects in t11FcsFabricDiscoveryTable are NOT retained over agent reboots, while values written to objects in t11FcsNotifyControlTable SHOULD be persistent/retained over agent reboots.
Write access to t11FcsDiscoveryStatus is constrained: if write is supported, the only writable value is 'localOnly' (WRITE-SYNTAX INTEGER { localOnly(3) }); write access is not required by the compliance statement.
t11FcsFabricDiscoveryTable (indexed by fcmInstanceIndex, fcmSwitchIndex) provides per-switch discovery control with four objects: t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh (T11FabricIndex bounding the Fabric range), t11FcsFabricDiscoveryStart (write 'start' to trigger; reads always return 'noOp'), and t11FcsFabricDiscoveryTimeOut (Unsigned32, 300–86400 seconds, default 900). Values in this table are not retained over agent reboots.
t11FcsIeTable (indexed by fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex, t11FcsIeName) stores discovered Interconnect Element data including WWN (t11FcsIeName, 8 or 16 bytes), type (T11FcIeType: unknown/other/switch/hub/bridge), Domain ID, Management ID, Fabric_Name, logical name, management address list pointer, and info list. By default only local IE name, type, and Domain ID are maintained; full data requires a triggered discovery cycle.
t11FcsMgmtAddrListTable holds management addresses as URLString values, indexed by fcmInstanceIndex, fcmSwitchIndex, t11FcsMgmtAddrListIndex, and t11FcsMgmtAddrIndex. It is shared between IE (t11FcsIeMgmtAddrListIndex) and Platform (t11FcsPlatformMgmtAddrListIndex) references via the T11FcListIndexPointerOrZero indirection pattern.
t11FcsPlatformTable (indexed by fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex, t11FcsPlatformIndex) stores 16 attributes per platform including name, type (4 bytes), node name list pointer, management address list pointer, vendor ID (12 bytes), product ID (20 bytes), product revision, description, label, location, system ID, cluster ID, cluster management addresses, and FC-4 types (32-byte bitmask).
t11FcsPortTable (indexed by fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex, t11FcsIeName, t11FcsPortName) stores per-port attributes: Port_Name (WWN, 8 or 16 bytes), port type (FcPortType), TX type (T11FcPortTxType, 13 values including 10G variants), module type (0–255), physical port number (4-byte unrestricted vendor field), attached port name list pointer, state, speed capabilities (2 bytes), operating speed (2 bytes), and zoning enforcement status (12 bytes).
T11FcsRejectReasonExplanation is a textual convention enumerating 26 reject reason codes (e.g., invNameIdForIEOrPort, ieListNotAvailable, domainIdNotAvailable, platformNameAlreadyExists, resourceUnavailable, attributesMissing) used to qualify an 'unable to perform command request' reject reason code from the FCS.
t11FcsStatsTable provides seven Counter32 objects per (switch, Fabric) pair: t11FcsInGetReqs, t11FcsOutGetReqs, t11FcsInRegReqs, t11FcsOutRegReqs, t11FcsInDeregReqs, t11FcsOutDeregReqs, and t11FcsRejects. All counters have no discontinuities other than sysUpTime=0 resets.
The MIB module is organized into six groups: t11FcsDiscoveredConfigGroup (topology data), t11FcsDiscoveryStatusGroup (discovery monitoring), t11FcsDiscoveryControlGroup (triggering discovery), t11FcsStatisticsGroup (counters), t11FcsNotificationGroup (three notifications), and t11FcsNotificationInfoGroup (notification control and info objects).
Three SNMP notifications are defined: t11FcsRqRejectNotification (FCS rejects a request; carries t11FamLocalSwitchWwn, reason code, reason explanation, vendor code), t11FcsDiscoveryCompleteNotify (discovery range completed; carries t11FcsFabricDiscoveryRangeLow), and t11FcsMgmtAddrChangeNotify (IE management address changed; carries t11FcsMgmtAddrChangeFabricIndex and t11FcsMgmtAddrChangeIeName).
IANA assigned OID 162 under the mib-2 subtree to the T11-FC-FABRIC-CONFIG-SERVER-MIB module (object identifier { mib-2 162 }).
The ability to invalidate discovered topology (by writing 'localOnly' to t11FcsDiscoveryStatus) may allow an attacker to hide the presence of unauthorized equipment on the network.
The read-write objects t11FcsFabricDiscoveryRangeLow, t11FcsFabricDiscoveryRangeHigh, t11FcsFabricDiscoveryTimeOut, t11FcsFabricDiscoveryStart, and t11FcsDiscoveryStatus allow an attacker to trigger, abort, or invalidate topology discovery; the three NotifyEnable objects allow suppression of operational notifications. SET operations in a non-secure environment can have a negative effect on network operations.
The topology tables (t11FcsIeTable, t11FcsMgmtAddrListTable, t11FcsPortTable, t11FcsAttachPortNameListTable, t11FcsPlatformTable, t11FcsNodeNameListTable) and t11FcsStatsTable expose sensitive network topology and operational data; even GET and NOTIFY access should be controlled and values SHOULD be encrypted when transmitted via SNMP.
t11FcsDiscoveryStatus models three states: 'localOnly' (initial, only local data present), 'inProgress' (discovery triggered via t11FcsFabricDiscoveryStart), and 'completed' (discovery done, data cached for at least t11FcsFabricDiscoveryTimeOut seconds). After the timeout expires the state may revert to 'localOnly'. Writing 'localOnly' via SNMP immediately discards cached data and aborts any in-progress discovery.
t11FcsAttachPortName is a 12-byte OCTET STRING: bytes 1–8 contain the attached port's WWN, bytes 9–10 are reserved, byte 11 is Port flags, and byte 12 is Port type, as specified in FC-GS-5 section 6.2.3.3.6.
t11FcsIeInfoList (0–252 bytes) encodes null-terminated substrings in order: vendor name, model name/number, release code/level, followed by zero or more vendor-specific substrings, each terminated by a 0x00 byte.
t11FcsPortSpeedCapab and t11FcsPortOperSpeed are each 2-byte OCTET STRINGs encoded as specified in FC-GS-5; t11FcsPortZoningEnfStatus is a 12-byte OCTET STRING; t11FcsPlatformType is a 4-byte OCTET STRING encoding platform type bits; t11FcsPlatformFC4Types is a 32-byte OCTET STRING bit mask for supported FC-4 types.