rfc-4626

MIB for Fibre Channel's Fabric Shortest Path First (FSPF) Protocol

C. DeSanti, V. Gaonkar, K. McCloghrie, S. Gai
date2006-09 streamIETF areaops wgimss statusPROPOSED STANDARD pages36 canonicalhttps://www.rfc-editor.org/rfc/rfc4626 doi10.17487/RFC4626
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to the Fibre Channel network's Fabric Shortest Path First (FSPF) routing protocol. [STANDARDS-TRACK]

Extracted elements (25)

design-rationale §5.3

In tables indexed by both fcmSwitchIndex and t11FspfFabricIndex, fcmSwitchIndex is listed first to simplify NMS queries for all Fabrics connected to a single switch.

routing, snmp

design-rationale §5.3

The MIB uses a Fabric Index (T11FabricIndex) rather than physical infrastructure identifiers so that the same table structure works uniformly whether operating on a single physical Fabric or multiple Virtual Fabrics; a non-virtual environment always uses index value 1.

routing

design-rationale §6

The T11FspfLastCreationTime textual convention records the sysUpTime when a row was last created, enabling management applications to detect that a row was deleted and re-created between reads, which would otherwise cause an undetectable discontinuity in counter data.

routing, snmp

interoperability-note §6

The t11FspfIfHelloInterval value must be the same at both ends of a link in a Fabric; similarly, t11FspfIfDeadInterval must be greater than the HELLO interval on the same interface.

routing

normative-requirement §9 NOT RECOMMENDED

Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; instead SNMPv3 with cryptographic security SHOULD be deployed.

security, snmp

normative-requirement §9 RECOMMENDED

It is RECOMMENDED that implementors support the full SNMPv3 framework including cryptographic mechanisms for authentication and privacy when implementing this MIB module.

security, snmp

protocol-element §6

t11FspfAdminStatus and t11FspfIfAdminStatus allow enabling (up) or disabling (down) FSPF per-Fabric and per-interface respectively. When FSPF is disabled fabric-wide, it provides no routes to the T11-FC-ROUTE-MIB.

routing

protocol-element §6

t11FspfIfHelloInterval (default 20 seconds) sets the periodic HELLO message interval on an interface; t11FspfIfDeadInterval (default 80 seconds) sets the maximum time without a HELLO before the interface is assumed broken. Both values must be identical at both ends of a link.

routing

protocol-element §6

t11FspfIfLinkCostFactor is an administrative factor (default 100, range 1–65535) used in the link cost formula: Link Cost = (factor/100) * (1.0625e12 / ifSpeed), allowing operators to influence FSPF path selection per interface.

routing

protocol-element §6

t11FspfIfRetransmitInterval (default 5 seconds) specifies the time after which an unacknowledged LSR is retransmitted on an interface in a Fabric.

routing

protocol-element §6

T11FspfLinkType defines FSPF link types: value 1 is Point-to-Point, values 240–255 are vendor-specific, and all others are reserved.

routing

protocol-element §6

t11FspfLsRefreshTime (read-only, default 30 minutes) specifies the interval between transmission of refresh LSRs; t11FspfMaxAge (read-only, default 60 minutes) specifies the maximum age an LSR is retained before removal from the topology database.

routing

protocol-element §6

T11FspfLsrType defines two FC-SW-4 LSR types: type 01 (Switch Link Record) and type 02 (Obsolete); values 240–255 are vendor-specific and all others are reserved.

routing

protocol-element §6

t11FspfMinLsArrival defines the minimum time (in milliseconds, default 1000) after accepting a Link State Record before accepting another update of the same LSR on the same Fabric; LSR updates arriving sooner are discarded.

routing

protocol-element §6

t11FspfMinLsInterval defines the minimum time (in milliseconds, default 5000) after a switch sends an LSR before it will send another update of the same LSR on the same Fabric.

routing

protocol-element §6

The T11-FC-FSPF-MIB module is assigned OID { mib-2 143 } and provides managed objects for monitoring and configuring the FSPF routing protocol in Fibre Channel switches, organized into four groups: t11FspfGeneralGroup, t11FspfIfGroup, t11FspfDatabaseGroup, and t11FspfNotificationGroup.

routing, snmp, registry

protocol-element §6

The t11FspfIfTable provides per-interface FSPF parameters and statistics indexed by fcmInstanceIndex, fcmSwitchIndex, t11FspfFabricIndex, and t11FspfIfIndex. Rows are auto-created when an E_Port becomes non-isolated and auto-deleted when an E_Port becomes isolated with all default parameter values.

routing, snmp

protocol-element §6

The t11FspfLinkTable contains per-link information within LSRs, including neighbor domain ID, source and destination E_Port indices, link type (T11FspfLinkType), and link cost. It is indexed by domain ID, LSR type, and an arbitrary link index.

routing

protocol-element §6

The t11FspfLsrTable holds the topology database of all current LSRs, indexed by domain ID and LSR type. Key fields include t11FspfLsrAge (seconds since insertion), t11FspfLsrIncarnationNumber (monotonically increasing; highest value is most recent), and t11FspfLsrCheckSum.

routing

protocol-element §6

The t11FspfNbrStateChangNotify notification is generated when the FSPF neighbor state machine transitions to a terminal state—either progressing to Full or regressing to Init or Down—carrying ifIndex, domain IDs, new state, and previous state.

routing, snmp

protocol-element §6

The t11FspfTable provides per-Fabric FSPF parameters and statistics indexed by fcmInstanceIndex, fcmSwitchIndex, and t11FspfFabricIndex. Entries are created and removed automatically as Virtual Fabrics are created or deleted.

routing, snmp

registry §8

IANA assigned OID { mib-2 143 } for the T11-FC-FSPF-MIB module as part of the IANA Considerations for this RFC.

registry, snmp

security-consideration §9

Readable objects including t11FspfTable, t11FspfIfTable, t11FspfLsrTable, and t11FspfLinkTable expose topology information that may be sensitive; GET and NOTIFY access should be controlled and values encrypted in transit via SNMP.

security, routing, snmp

security-consideration §9

Several read-write MIB objects are sensitive: t11FspfMinLsArrival, t11FspfMinLsInterval, t11FspfIfHelloInterval, t11FspfIfDeadInterval, and t11FspfIfRetransmitInterval can alter FSPF responsiveness; t11FspfAdminStatus and t11FspfIfAdminStatus can disable dynamic routing; t11FspfIfLinkCostFactor can alter link selection; t11FspfSetToDefault can nullify configuration.

security, routing, snmp

state-machine §6

The T11FspfInterfaceState textual convention defines the FSPF Neighbor Finite State Machine with six states: down(1), init(2), dbExchange(3), dbAckwait(4), dbWait(5), and full(6). The notification t11FspfNbrStateChangNotify fires on transitions to terminal states (Full or Down/Init regression).

routing