CISCO-FC-ROUTE-MIB: View SNMP OID List / Download MIB

The MIB module for configuring and displaying FC (Fibre Channel) Route Information.

The value of sysUpTime at the most recent time when a conceptual row was created, modified, or deleted in fcRouteTable. If no change has occurred since the last restart of the management system, then the value of this object is 0.

The value of route preference.Route preference is the value used to select one route over other when more than one route to the same destination is learned from different protocols, peers, or static routes from end-users. The preference value is an arbitrary assigned value used to determine the order of routes to the same destination in a single routing database(RIB). The active route is chosen by the lowest preference value.

The action to perform a consistency check of fcRouteTable. none (1) - no action verify (2) - perform verify action Writing verify(2) does a consistency check of the fcRouteTable with either one of the following: - with routeTable in the persistent database if the fcRouteVerifyType value is pss(1) - with forwarding information base software tables on the module specified by fcRouteVerifyModule, if the fcRouteVerifyType value is fibShadow(2). - with forwarding information base hardware tables on the module specified by fcRouteVerifyModule if the fcRouteVerifyType value is fibHardware(3). This verify action is performed on the fcRouteTable for the VSAN specified by fcRouteVerifyVsanID and for the route entries of the type specified by fcRouteVerifyRouteType. The result is shown by fcRouteVerifyResult. If a verify, due to a previous action performed, is in progress in the agent, then setting the fcRouteVerifyAction to verify(2) again will fail. No verification is performed if the value is set to none(1). When read, this object always has the value 'none(1)'. Enumeration: 'verify': 2, 'none': 1.

The value used by fcRouteVerifyAction to perform the consistency check of fcRouteTable with: - route table in persistent database if value is pss(1) - forwarding information base software tables if value is fibShadow(2) - forwarding information base hardware tables if value is fibHardware(3). Enumeration: 'pss': 1, 'fibHardware': 3, 'fibShadow': 2.

This value identifies a particular line card module according to that module's value of entPhysicalIndex in the entPhysicalTable of the ENTITY-MIB (RFC 2737). The forwarding information base present on this module is checked for consistency with the fcRouteTable. The value of this object is relevant only if fcRouteVerifyType is either fibShadow(2) or fibHardware(3).

The value specifies the VSAN id. The fcRouteTable entries and the entries in the table specified by fcRouteVerifyType is checked for consistency for the same VSAN id specified by this object.

The value used by fcRouteVerifyAction to perform the consistency check of fcRouteTable. If the value is unicast(1) then only unicast entries in fcRouteTable and the entries in the table specified by fcRouteVerifyType are checked. If value is multicast(2) then only multicast entries in fcRouteTable and the entries in the table specified by fcRouteVerifyType are checked. If value is label(3) then only label entries in fcRouteTable and the entries in the table specified by fcRouteVerifyType are checked. Enumeration: 'unicast': 1, 'multicast': 2, 'label': 3.

The object displays the details of the first inconsistency that occured from the check. If the check passes successfully then this will be a zero-length string.

This object is used to facilitate the verify action performed using 'fcRouteVerifyAction' by multiple managers. The procedure to perform the action by the NMS is as follows: 1. Retrieve the value of fcRouteVerifyLock. 2. Set the value of fcRouteVerifyLock to the retrieved value, and in the same PDU provide the following values: fcRouteVerifyAction to 'verify(2)' fcRouteVerifyType,fcRouteVerifyVsanID, fcRouteVerifyRouteType and fcRouteVerifyModule. Note, fcRouteVerifyModule is relevent only if fcRouteVerifyType is either 'fibShadow(2)' or fibHardware(3). 3. If the set fails repeat steps 1-2. 4. Retrieve the value of fcRouteVerifyLock and fcRouteVerifyResult in the same pdu. 5. If 'fcRouteVerifyLock' value is not one greater than the retrieved value of 'fcRouteVerifyLock' in step-1 than repeat steps 1-4.

The local system's Fibre Channel Routing table. This table lists all the routes that is configured/ calculated at the local system. Traffic through the TL-Port (translation port) uses the R-CTL field in the FC protocol header. During forwarding, this R-CTL field is part of the the value looked-up in the route table for matching. The value of the object fcRoutePreference is used to select one route over other when more than one route to the same destination is learned from different protocols, peers, or static routes from end-users. Only the entries configured by the user, which are fcRouteProto of type netmgmt(3), can be deleted by the user.

Each entry contains a route to a particular destination in a particular VSAN via a particular output interface, and learned in a particular manner.

The destination FC-ID of this route.

Indicate the mask to be logical-ANDed with the destination address Id before being compared to the value in the fcRouteDestAddrId field. This can only be 255.255.255 or 255.255.0 or 255.0.0 .

The routing mechanism via which this route was learned. other(1) - not specified local(2) - local interface netmgmt(3)- static route The following are all dynamic routing protocols fspf(4) - Fibre Shortest Path First mpls(5) - Multiple Protocol Label Switching. multicast(6) - multicast routes. Enumeration: 'netmgmt': 3, 'multicast': 6, 'mpls': 5, 'other': 1, 'fspf': 4, 'local': 2.

The ifIndex value, which identifies the local interface through which the next hop of this route should be reached. If the interface type is TL-Port then R-CTL field in the FC protocol header is also used for look-up in the route table during forwarding. Only interfaces of type Fibre Channel and Port Channel are allowed.

The domain ID of next hop switch. However this object, when read, could have a value zero if value of fcRouteProto is 'local'.

The routing metric for this route. The use of this object is dependent on fcRouteProto used.

The type of route. local(1): refers to a route for which the next hop is the final destination; remote(2): refers to a route for which the next hop is not the final destination. This object is not relevent for multicast and broadcast route entries. Enumeration: 'remote': 2, 'local': 1.

The value if true(1), indicates the route is not to be removed from the relevant Forwarding information base even if the port is operationally 'down'. If false(2), the route is removed from the relevant Forwarding information base (FIB) if the port is operationally 'down'. This object is not relevent for multicast and broadcast route entries.

The status of this conceptual row.

The table to configure and show the ingress traffic counters on physical components (e.g., Linecards). The user has the option of configuring counters depending on the bits selected for the object fcRouteFlowType. If the user selects only vsanId(0) bit for all the entries, then no more than 1024 entries can be created. If the user selects all the 4 bits, vsanId(0), destId(1), srcId(2), port(3), for some entries, then additional entries can be created, up to a maximum of 2048 entries. For statistics collection R-CTL is not part of the the value looked-up in the route table, so the counters are updated immaterial of R-CTL field.

Each entry provides information on the ingress traffic counters at the physical component indicated by entPhysicalIndex. Entries can only be created for physical components, e.g.,line cards, which support this type of ingress traffic counters.

The index of this entry.

The matching criteria by which flows are selected to be included in the traffic which is instrumented by the ingress traffic counters. For each bit which is set, the corresponding object must be configured by the network manager when creating an entry. vsanId(0) represents object fcRouteFlowVsanId, destId(1) represents fcRouteFlowDestId, srcId(2) represents fcRouteFlowSrcId, port(3) represents fcRouteFlowPort.It is optional to provide fcRouteFlowMask. If fcRouteFlowMask is not provided then the default value 255.255.255 is used. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'. Bits: 'vsanId': 0, 'srcId': 2, 'destId': 1, 'port': 3.

The id of VSAN. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'.

The destination fibre channel address id. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'.

The source fibre channel address id. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'.

The mask for source and destination fibre channel address id. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'.

The physical ingress port to which this counter applies. This object cannot be modified while the corresponding value of fcRouteFlowRowStatus is equal to 'active'.

The number of received frames for the flow created by the network manager.

The number of received frame bytes for the flow created by the network manager.

The timestamp indicating the time the row was created or modified.

The status of this conceptual row.

The compliance statement for entities which implement the fc Route mib.

The compliance statement for entities which implement the fc Route mib.

A collection of objects giving route information.

A collection of objects for displaying and configuring route's.

A collection of objects for displaying and configuring ingress traffic flow counters.