rfc-4625

Fibre Channel Routing Information MIB

C. DeSanti, K. McCloghrie, S. Kode, S. Gai
date2006-09 streamIETF areaops wgimss statusPROPOSED STANDARD pages22 canonicalhttps://www.rfc-editor.org/rfc/rfc4625 doi10.17487/RFC4625
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 routing within a Fibre Channel fabric, which is independent of the usage of a particular routing protocol. [STANDARDS-TRACK]

Extracted elements (25)

design-rationale §5.3

All Fabric-related information is indexed by an arbitrary integer 'Fabric Index' so that the same MIB structure applies uniformly whether a switch operates on a single physical Fabric (index=1) or within multiple Virtual Fabrics (FC-SW-4). This avoids separate table definitions for virtual vs. physical environments.

routing

design-rationale §5.5

The unusually large ten-object INDEX for t11FcRouteTable was chosen so that management applications can query routes based on attributes (destination, source, interface, protocol) without reading every row—mirroring the design of ipCidrRouteTable and inetCidrRouteTable. Despite the count, the resulting OIDs are shorter than those of inetCidrRouteTable.

routing, snmp

design-rationale §4

This MIB is intentionally protocol-independent: it captures routing table state usable regardless of whether FSPF or another routing protocol populates the table. Protocol-specific management objects (e.g., FSPF parameters) are left to RFC 4626.

routing

interoperability-note §6

In a fabric conformant to FC-SW-3 only one Fabric can exist in a physical infrastructure, so t11FcRouteFabricIndex is always 1. In FC-SW-4 environments, the index distinguishes multiple Virtual Fabrics operating within the same physical infrastructure.

routing

interoperability-note §4

The MIB imports fcmInstanceIndex and fcmSwitchIndex from FC-MGMT-MIB (RFC 4044) and T11FabricIndex from T11-TC-MIB (RFC 4439); implementations must support those base MIBs. It complements—but does not replace—the FSPF-specific MIB in RFC 4626.

routing, snmp

normative-requirement §9 RECOMMENDED

Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; SNMPv3 with cryptographic security enabled is RECOMMENDED instead, with operators responsible for configuring access controls to restrict GET/SET to authorized principals.

security, snmp

normative-requirement §9 RECOMMENDED

Implementors are RECOMMENDED to support the SNMPv3 framework including full cryptographic mechanisms for authentication and privacy when deploying this MIB module.

security, snmp

normative-requirement §6 MUST NOT

Only rows for which t11FcRouteProto has the value 'netmgmt' (static/management-configured routes) can be deleted via SNMP by setting t11FcRouteRowStatus to 'destroy'.

routing, snmp

protocol-element §6

t11FcRouteIfDown controls what happens to a route when its output interface becomes operationally down: retain(2) keeps the entry in the table, remove(1) deletes it. Default is retain(2).

routing

protocol-element §6

t11FcRouteInInterface (InterfaceIndexOrZero) optionally constrains route matching to frames received on a specific local FC interface. A value of zero means any ingress interface matches.

routing

protocol-element §6

t11FcRouteMetric (Unsigned32, range 0..65536) holds the routing metric for a route entry; its interpretation is dependent on t11FcRouteProto.

routing

protocol-element §6

t11FcRouteOutInterface (InterfaceIndex) identifies the local FC interface through which the next hop of the route is reached; it is a mandatory index component of every route entry.

routing

protocol-element §6

t11FcRouteProto is an INTEGER index component that identifies how a route was learned: other(1), local(2), netmgmt(3) for static/management-configured routes, or fspf(4) for FSPF-derived routes.

routing

protocol-element §6

t11FcRouteType distinguishes local(1) routes—where the next FC port is the final destination—from remote(2) routes where it is not. Default value is local(1).

routing

protocol-element §6

The T11-FC-ROUTE-MIB module (OID mib-2 144) defines managed objects for displaying and configuring Fibre Channel routing table information independent of any particular routing protocol such as FSPF.

routing, snmp, yang

protocol-element §6

The t11FcRouteCompliance MODULE-COMPLIANCE statement mandates the t11FcRouteGroup and permits read-only MIN-ACCESS for t11FcRouteIfDown, t11FcRouteDomainId, t11FcRouteMetric, t11FcRouteType, t11FcRouteStorageType, and t11FcRouteRowStatus, meaning write access to these objects is optional for conformant implementations.

routing, snmp

protocol-element §6

The t11FcRouteFabricTable provides per-Fabric routing metadata indexed by fcmInstanceIndex, fcmSwitchIndex, and t11FcRouteFabricIndex. It contains t11FcRouteFabricLastChange, a TimeStamp reflecting the most recent creation, modification, or deletion of any route in that Fabric.

routing

protocol-element §5.5

The t11FcRouteTable INDEX comprises ten components: fcmInstanceIndex, fcmSwitchIndex, t11FcRouteFabricIndex, t11FcRouteDestAddrId, t11FcRouteDestMask, t11FcRouteSrcAddrId, t11FcRouteSrcMask, t11FcRouteInInterface, t11FcRouteProto, and t11FcRouteOutInterface. All are integers or 3-octet strings, yielding at most 22 appended OID sub-identifiers per instance.

routing, snmp

protocol-element §6

The t11FcRouteTable is the central Fibre Channel routing table for locally managed switches, listing all configured and computed routes across all Fabrics. Route lookup compares a received frame's D_ID (logical-ANDed with t11FcRouteDestMask) against t11FcRouteDestAddrId, and similarly for S_ID and optional ingress interface.

routing

registry §8

IANA assigned OID mib-2 144 to the T11-FC-ROUTE-MIB module under the standard MIB-2 subtree.

registry, snmp

security-consideration §9

The read-write/read-create objects t11FcRouteDomainId, t11FcRouteMetric, t11FcRouteType, t11FcRouteIfDown, and t11FcRouteRowStatus allow creating, modifying, or deleting routes; unauthorized SET operations could alter network topology or performance, enabling an attacker to degrade other users.

security, routing, snmp

security-consideration §9

The readable object t11FcRouteLastChangeTime (the time of the last routing table change) is also considered sensitive and should have its GET and NOTIFY access controlled; its values should potentially be encrypted when transmitted via SNMP.

security, snmp

wire-format §6

t11FcRouteDestAddrId is a 3-octet FcAddressIdOrZero field (SIZE 3) representing the destination Fibre Channel Address Identifier of a route; a zero-length value is not permitted.

routing

wire-format §6

t11FcRouteDestMask is a 3-octet mask logical-ANDed with a destination FC Address ID before comparison. Allowed values are 255.255.255, 255.255.0, or 255.0.0; FSPF-generated routes always use 255.0.0 (Domain_ID level). The zero-length value equals 0.0.0.

routing

wire-format §6

t11FcRouteSrcAddrId and t11FcRouteSrcMask are FcAddressIdOrZero fields for source-address-based route matching. When both are 0.0.0, the route matches all source addresses. Allowed mask values are 255.255.255, 255.255.0, 255.0.0, or 0.0.0.

routing