Home/Catalog/CISCO-CEF-MIB

CISCO-CEF-MIB

AI MIB Summary

The CISCO-CEF-MIB enables monitoring and management of Cisco Express Forwarding (CEF) data structures, specifically the Forwarding Information Base (FIB), adjacency tables, and forwarding element chains, on Cisco routers supporting distributed CEF architectures. It provides visibility into packet forwarding paths, load-balancing configurations, and consistency checks between Routing Processor and line card databases through specific counters for prefix entries and forwarding element operations.

Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound to the outbound interface. CEF uses two sets of data structures or tables, which it stores in router memory: Forwarding information base (FIB) - Describes a database of information used to make forwarding decisions. It is conceptually similar to a routing table or route-cache, although its implementation is different. Adjacency - Two nodes in the network are said to be adjacent if they can reach each other via a single hop across a link layer. CEF path is a valid route to reach to a destination IP prefix. Multiple paths may exist out of a router to the same destination prefix. CEF Load balancing capability share the traffic to the destination IP prefix over all the active paths. After obtaining the prefix in the CEF table with the longest match, output forwarding follows the chain of forwarding elements. Forwarding element (FE) may process the packet, forward the packet, drop or punt the packet or it may also pass the packet to the next forwarding element in the chain for further processing. Forwarding Elements are of various types but this MIB only represents the forwarding elements of adjacency and label types. Hence a forwarding element chain will be represented as a list of labels and adjacency. The adjacency may point to a forwarding element list again, if it is not the last forwarding element in this chain. For the simplest IP forwarding case, the prefix entry will point at an adjacency forwarding element. The IP adjacency processing function will apply the output features, add the encapsulation (performing any required fixups), and may send the packet out. If loadbalancing is configured, the prefix entry will point to lists of forwarding elements. One of these lists will be selected to forward the packet. Each forwarding element list dictates which of a set of possible packet transformations to apply on the way to the same neighbour. The following diagram represents relationship between three of the core tables in this MIB module. cefPrefixTable cefFESelectionTable ++ | | | | a set +> | | | | | || | | | | Selection | | | | | | || | | | |+ | |<+ || | | | + ++ | | | points to an | adjacency entry | | | | cefAdjTable | | + +->| | | | to a set | | | | | | Selection | | | | | |+ | | | + Some of the Cisco series routers (e.g. 7500 & 12000) support distributed CEF (dCEF), in which the line cards (LCs) make the packet forwarding decisions using locally stored copies of the same Forwarding information base (FIB) and adjacency tables as the Routing Processor (RP). Inter-Process Communication (IPC) is the protocol used by routers that support distributed packet forwarding. CEF updates are encoded as external Data Representation (XDR) information elements inside IPC messages. This MIB reflects the distributed nature of CEF, e.g. CEF has different instances running on the RP and the line cards. There may be instances of inconsistency between the CEF forwarding databases(i.e between CEF forwarding database on line cards and the CEF forwarding database on the RP). CEF consistency checkers (CC) detects this inconsistency. When two databases are compared by a consistency checker, a set of records from the first (master) database is looked up in the second (slave). There are two types of consistency checkers, active and passive. Active consistency checkers are invoked in response to some stimulus, i.e. when a packet cannot be forwarded because the prefix is not in the forwarding table or in response to a Management Station request. Passive consistency checkers operate in the background, scanning portions of the databases on a periodic basis. The full-scan checkers are active consistency checkers which are invoked in response to a Management Station Request. If 64-bit counter objects in this MIB are supported, then their associated 32-bit counter objects must also be supported. The 32-bit counters will report the low 32-bits of the associated 64-bit counter count (e.g., cefPrefixPkts will report the least significant 32 bits of cefPrefixHCPkts). The same rule should be applied for the 64-bit gauge objects and their assocaited 32-bit gauge objects. If 64-bit counters in this MIB are not supported, then an agent MUST NOT instantiate the corresponding objects with an incorrect value; rather, it MUST respond with the appropriate error/exception condition (e.g., noSuchInstance or noSuchName). Counters related to CEF accounting (e.g., cefPrefixPkts) MUST NOT be instantiated if the corresponding accounting method has been disabled. This MIB allows configuration and monitoring of CEF related objects.
Main OID:
ciscoCefMIB.1.3.6.1.4.1.9.9.492
178
Objects
Active
Status
12
Dependencies

Imported Objects

Objects

178 total
Object Name
ciscoCefMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.492
ciscoCefMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.0
cefResourceFailure
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.492.0.1
cefPeerStateChange
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.492.0.2
cefPeerFIBStateChange
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.492.0.3
cefInconsistencyDetection
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.492.0.4
ciscoCefMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1
cefFIB
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.1
cefFIBSummary
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.1.1
cefFIBSummaryTable
SEQUENCE OF CefFIBSummaryEntry
.1.3.6.1.4.1.9.9.492.1.1.1.1
cefFIBSummaryEntry
CefFIBSummaryEntry
.1.3.6.1.4.1.9.9.492.1.1.1.1.1
cefFIBIpVersion
CefIpVersion (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.1.1.1.1.1
cefFIBSummaryFwdPrefixesro
Unsigned32
.1.3.6.1.4.1.9.9.492.1.1.1.1.1.2
cefPrefixTable
SEQUENCE OF CefPrefixEntry
.1.3.6.1.4.1.9.9.492.1.1.2
cefPrefixEntry
CefPrefixEntry
.1.3.6.1.4.1.9.9.492.1.1.2.1
cefPrefixType
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.2.1.1
cefPrefixAddr
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.2.1.2
cefPrefixLen
InetAddressPrefixLength (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.2.1.3
cefPrefixForwardingInforo
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.492.1.1.2.1.4
cefPrefixPktsro
Counter32 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.5
cefPrefixHCPktsro
Counter64 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.6
cefPrefixBytesro
Counter32 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.7
cefPrefixHCBytesro
Counter64 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.8
cefPrefixInternalNRPktsro
Counter32 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.9
cefPrefixInternalNRHCPktsro
Counter64 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.10
cefPrefixInternalNRBytesro
Counter32 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.11
cefPrefixInternalNRHCBytesro
Counter64 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.12
cefPrefixExternalNRPktsro
Counter32 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.13
cefPrefixExternalNRHCPktsro
Counter64 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.1.2.1.14
cefPrefixExternalNRBytesro
Counter32 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.15
cefPrefixExternalNRHCBytesro
Counter64 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.1.2.1.16
cefLMPrefixSpinLockrw
TestAndIncr (SNMPv2-TC)
.1.3.6.1.4.1.9.9.492.1.1.3
cefLMPrefixTable
SEQUENCE OF CefLMPrefixEntry
.1.3.6.1.4.1.9.9.492.1.1.4
cefLMPrefixEntry
CefLMPrefixEntry
.1.3.6.1.4.1.9.9.492.1.1.4.1
cefLMPrefixDestAddrType
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.4.1.1
cefLMPrefixDestAddr
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.4.1.2
cefLMPrefixStatero
CefPrefixSearchState (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.1.4.1.3
cefLMPrefixAddrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.4.1.4
cefLMPrefixLenro
InetAddressPrefixLength (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.4.1.5
cefLMPrefixRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.492.1.1.4.1.6
cefPathTable
SEQUENCE OF CefPathEntry
.1.3.6.1.4.1.9.9.492.1.1.5
cefPathEntry
CefPathEntry
.1.3.6.1.4.1.9.9.492.1.1.5.1
cefPathId
Integer32
.1.3.6.1.4.1.9.9.492.1.1.5.1.1
cefPathTypero
CefPathType (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.1.5.1.2
cefPathInterfacero
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.9.9.492.1.1.5.1.3
cefPathNextHopAddrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.1.5.1.4
cefPathRecurseVrfNamero
MplsVpnId (MPLS-VPN-MIB)
.1.3.6.1.4.1.9.9.492.1.1.5.1.5
cefAdj
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.2
cefAdjSummary
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.2.1
cefAdjSummaryTable
SEQUENCE OF CefAdjSummaryEntry
.1.3.6.1.4.1.9.9.492.1.2.1.1
cefAdjSummaryEntry
CefAdjSummaryEntry
.1.3.6.1.4.1.9.9.492.1.2.1.1.1
cefAdjSummaryLinkType
CefAdjLinkType (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.2.1.1.1.1
cefAdjSummaryCompletero
Unsigned32
.1.3.6.1.4.1.9.9.492.1.2.1.1.1.2
cefAdjSummaryIncompletero
Unsigned32
.1.3.6.1.4.1.9.9.492.1.2.1.1.1.3
cefAdjSummaryFixupro
Unsigned32
.1.3.6.1.4.1.9.9.492.1.2.1.1.1.4
cefAdjSummaryRedirectro
Unsigned32
.1.3.6.1.4.1.9.9.492.1.2.1.1.1.5
cefAdjTable
SEQUENCE OF CefAdjEntry
.1.3.6.1.4.1.9.9.492.1.2.2
cefAdjEntry
CefAdjEntry
.1.3.6.1.4.1.9.9.492.1.2.2.1
cefAdjNextHopAddrType
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.2.2.1.1
cefAdjNextHopAddr
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.2.2.1.2
cefAdjConnId
Unsigned32(0 | 1..4294967295)
.1.3.6.1.4.1.9.9.492.1.2.2.1.3
cefAdjSourcero
CefAdjacencySource (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.2.2.1.4
cefAdjEncapro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.492.1.2.2.1.5
cefAdjFixupro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.492.1.2.2.1.6
cefAdjMTUro
Unsigned32
.1.3.6.1.4.1.9.9.492.1.2.2.1.7
cefAdjForwardingInforo
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.492.1.2.2.1.8
cefAdjPktsro
Counter32 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.2.2.1.9
cefAdjHCPktsro
Counter64 UNITS "packets"
.1.3.6.1.4.1.9.9.492.1.2.2.1.10
cefAdjBytesro
Counter32 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.2.2.1.11
cefAdjHCBytesro
Counter64 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.2.2.1.12
cefFE
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.3
cefFESelectionTable
SEQUENCE OF CefFESelectionEntry
.1.3.6.1.4.1.9.9.492.1.3.1
cefFESelectionEntry
CefFESelectionEntry
.1.3.6.1.4.1.9.9.492.1.3.1.1
cefFESelectionName
SnmpAdminString
.1.3.6.1.4.1.9.9.492.1.3.1.1.1
cefFESelectionId
Integer32
.1.3.6.1.4.1.9.9.492.1.3.1.1.2
cefFESelectionSpecialro
CefForwardingElementSpecialType (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.3.1.1.3
cefFESelectionLabelsro
CefMplsLabelList (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.3.1.1.4
cefFESelectionAdjLinkTypero
CefAdjLinkType (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.3.1.1.5
cefFESelectionAdjInterfacero
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.9.9.492.1.3.1.1.6
cefFESelectionAdjNextHopAddrTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.3.1.1.7
cefFESelectionAdjNextHopAddrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.492.1.3.1.1.8
cefFESelectionAdjConnIdro
Unsigned32(0 | 1..4294967295)
.1.3.6.1.4.1.9.9.492.1.3.1.1.9
cefFESelectionVrfNamero
MplsVpnId (MPLS-VPN-MIB)
.1.3.6.1.4.1.9.9.492.1.3.1.1.10
cefFESelectionWeightro
Unsigned32(0 | 1..4294967295)
.1.3.6.1.4.1.9.9.492.1.3.1.1.11
cefGlobal
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.492.1.4
cefCfgTable
SEQUENCE OF CefCfgEntry
.1.3.6.1.4.1.9.9.492.1.4.1
cefCfgEntry
CefCfgEntry
.1.3.6.1.4.1.9.9.492.1.4.1.1
cefCfgAdminStaterw
CefAdminStatus (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.4.1.1.1
cefCfgOperStatero
CefOperStatus (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.4.1.1.2
cefCfgDistributionAdminStaterw
CefAdminStatus (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.4.1.1.3
cefCfgDistributionOperStatero
CefOperStatus (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.4.1.1.4
cefCfgAccountingMaprw
Bits
.1.3.6.1.4.1.9.9.492.1.4.1.1.5
cefCfgLoadSharingAlgorithmrw
Enumeration
.1.3.6.1.4.1.9.9.492.1.4.1.1.6
cefCfgLoadSharingIDrw
Unsigned32(0 | 1..4294967295)
.1.3.6.1.4.1.9.9.492.1.4.1.1.7
cefCfgTrafficStatsLoadIntervalrw
Unsigned32 UNITS "seconds"
.1.3.6.1.4.1.9.9.492.1.4.1.1.8
cefCfgTrafficStatsUpdateRaterw
Unsigned32(0 | 1..65535) UNITS "seconds"
.1.3.6.1.4.1.9.9.492.1.4.1.1.9
cefResourceTable
SEQUENCE OF CefResourceEntry
.1.3.6.1.4.1.9.9.492.1.4.2
cefResourceEntry
CefResourceEntry
.1.3.6.1.4.1.9.9.492.1.4.2.1
cefResourceMemoryUsedro
Gauge32 UNITS "bytes"
.1.3.6.1.4.1.9.9.492.1.4.2.1.1
cefResourceFailureReasonro
CefFailureReason (CISCO-CEF-TC)
.1.3.6.1.4.1.9.9.492.1.4.2.1.2
Showing 100 of 178 OID objects

CISCO-CEF-MIB Technical Reference Overview

The CISCO-CEF-MIB SNMP MIB module published by Cisco defines 178 managed OID objects, including 123 scalar/column metrics, 17 SNMP tables, and 4 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.492. Key tabular structures include cefFIBSummaryTable, cefPrefixTable, cefLMPrefixTable, cefPathTable, cefAdjSummaryTable, cefAdjTable. Monitored SNMP traps/notifications include cefResourceFailure, cefPeerStateChange, cefPeerFIBStateChange, cefInconsistencyDetection.

Key OID Definitions in CISCO-CEF-MIB

ciscoCefMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.492

Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound to the outbound interface. CEF uses two sets of data structures or tables, which it stores in router memory: Forwarding information base (FIB) - Describes a database of information used to make forwarding decisions. It is conceptually similar to a routing table or route-cache, although its implementation is different. Adjacency - Two nodes in the network are said to be adjacent if they can reach each other via a single hop across a link layer. CEF path is a valid route to reach to a destination IP prefix. Multiple paths may exist out of a router to the same destination prefix. CEF Load balancing capability share the traffic to the destination IP prefix over all the active paths. After obtaining the prefix in the CEF table with the longest match, output forwarding follows the chain of forwarding elements. Forwarding element (FE) may process the packet, forward the packet, drop or punt the packet or it may also pass the packet to the next forwarding element in the chain for further processing. Forwarding Elements are of various types but this MIB only represents the forwarding elements of adjacency and label types. Hence a forwarding element chain will be represented as a list of labels and adjacency. The adjacency may point to a forwarding element list again, if it is not the last forwarding element in this chain. For the simplest IP forwarding case, the prefix entry will point at an adjacency forwarding element. The IP adjacency processing function will apply the output features, add the encapsulation (performing any required fixups), and may send the packet out. If loadbalancing is configured, the prefix entry will point to lists of forwarding elements. One of these lists will be selected to forward the packet. Each forwarding element list dictates which of a set of possible packet transformations to apply on the way to the same neighbour. The following diagram represents relationship between three of the core tables in this MIB module. cefPrefixTable cefFESelectionTable ++ | | | | a set +> | | | | | || | | | | Selection | | | | | | || | | | |+ | |<+ || | | | + ++ | | | points to an | adjacency entry | | | | cefAdjTable | | + +->| | | | to a set | | | | | | Selection | | | | | |+ | | | + Some of the Cisco series routers (e.g. 7500 & 12000) support distributed CEF (dCEF), in which the line cards (LCs) make the packet forwarding decisions using locally stored copies of the same Forwarding information base (FIB) and adjacency tables as the Routing Processor (RP). Inter-Process Communication (IPC) is the protocol used by routers that support distributed packet forwarding. CEF updates are encoded as external Data Representation (XDR) information elements inside IPC messages. This MIB reflects the distributed nature of CEF, e.g. CEF has different instances running on the RP and the line cards. There may be instances of inconsistency between the CEF forwarding databases(i.e between CEF forwarding database on line cards and the CEF forwarding database on the RP). CEF consistency checkers (CC) detects this inconsistency. When two databases are compared by a consistency checker, a set of records from the first (master) database is looked up in the second (slave). There are two types of consistency checkers, active and passive. Active consistency checkers are invoked in response to some stimulus, i.e. when a packet cannot be forwarded because the prefix is not in the forwarding table or in response to a Management Station request. Passive consistency checkers operate in the background, scanning portions of the databases on a periodic basis. The full-scan checkers are active consistency checkers which are invoked in response to a Management Station Request. If 64-bit counter objects in this MIB are supported, then their associated 32-bit counter objects must also be supported. The 32-bit counters will report the low 32-bits of the associated 64-bit counter count (e.g., cefPrefixPkts will report the least significant 32 bits of cefPrefixHCPkts). The same rule should be applied for the 64-bit gauge objects and their assocaited 32-bit gauge objects. If 64-bit counters in this MIB are not supported, then an agent MUST NOT instantiate the corresponding objects with an incorrect value; rather, it MUST respond with the appropriate error/exception condition (e.g., noSuchInstance or noSuchName). Counters related to CEF accounting (e.g., cefPrefixPkts) MUST NOT be instantiated if the corresponding accounting method has been disabled. This MIB allows configuration and monitoring of CEF related objects.

cefFIBSummaryTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.1.1.1

This table contains the summary information for the cefPrefixTable.

cefPrefixTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.1.2

A list of CEF forwarding prefixes.

cefLMPrefixTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.1.4

A table of Longest Match Prefix Query requests. Generator application should utilize the cefLMPrefixSpinLock to try to avoid collisions. See DESCRIPTION clause of cefLMPrefixSpinLock.

cefPathTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.1.5

CEF prefix path is a valid route to reach to a destination IP prefix. Multiple paths may exist out of a router to the same destination prefix. This table specify lists of CEF paths.

cefAdjSummaryTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.2.1.1

This table contains the summary information for the cefAdjTable.

cefAdjTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.2.2

A list of CEF adjacencies.

cefFESelectionTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.3.1

A list of forwarding element selection entries.

cefCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.4.1

This table contains global config parameter of CEF on the Managed device.

cefResourceTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.4.2

This table contains global resource information of CEF on the Managed device.

cefIntTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.5.1

This Table contains interface specific information of CEF on the Managed device.

cefPeerTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.6.1

Entity acting as RP (Routing Processor) keeps the CEF states for the line card entities and communicates with the line card entities using XDR. This Table contains the CEF information related to peer entities on the managed device.

cefPeerFIBTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.6.2

Entity acting as RP (Routing Processor) keep the CEF FIB states for the line card entities and communicate with the line card entities using XDR. This Table contains the CEF FIB State related to peer entities on the managed device.

cefStatsPrefixLenTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.8.1

This table specifies the CEF stats based on the Prefix Length.

cefSwitchingStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.8.2

This table specifies the CEF switch stats.

cefCCGlobalTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.7.1

This table contains CEF consistency checker (CC) global parameters for the managed device.

cefCCTypeTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.7.2

This table contains CEF consistency checker types specific parameters on the managed device. All detected inconsistency are signaled to the Management Station via cefInconsistencyDetection notification.

cefInconsistencyRecordTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.492.1.7.3

This table contains CEF inconsistency records.

cefResourceFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.492.0.1

A cefResourceFailure notification is generated when CEF resource failure on the managed entity is detected. The reason for this failure is indicated by cefResourcefFailureReason.

cefPeerStateChangeNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.492.0.2

A cefPeerStateChange notification is generated if change in cefPeerOperState is detected for the peer entity.

cefPeerFIBStateChangeNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.492.0.3

A cefPeerFIBStateChange notification is generated if change in cefPeerFIBOperState is detected for the peer entity.

cefInconsistencyDetectionNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.492.0.4

A cefInconsistencyDetection notification is generated when CEF consistency checkers detects an inconsistent prefix in one of the CEF forwarding databases. Note that the generation of cefInconsistencyDetection notifications is throttled by the agent, as specified by the 'cefNotifThrottlingInterval' object.

cefLMPrefixSpinLockTestAndIncrread-write
.1.3.6.1.4.1.9.9.492.1.1.3

An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating Longest Match Prefix Entries in cefLMPrefixTable. When creating a new longest prefix match entry, the value of cefLMPrefixSpinLock should be retrieved. The destination address should be determined to be unique by the SNMP Command Generator application by consulting the cefLMPrefixTable. Finally, the longest prefix entry may be created (Set), including the advisory lock. If another SNMP Command Generator application has altered the longest prefix entry in the meantime, then the spin lock's value will have changed, and so this creation will fail because it will specify the wrong value for the spin lock. Since this is an advisory lock, the use of this lock is not enforced, but not using this lock may lead to conflict with the another SNMP command responder application which may also be acting on the cefLMPrefixTable.

entLastInconsistencyDetectTimeTimeStampread-only
.1.3.6.1.4.1.9.9.492.1.7.4

The value of sysUpTime at the time an inconsistency is detecetd.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→