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.
Parsed from file CISCO-CEF-MIB.mib
Module: CISCO-CEF-MIB
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.
Parsed from file CISCO-CEF-MIB.my.txt
Company: None
Module: CISCO-CEF-MIB
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.
ciscoCefMIB MODULE-IDENTITY LAST-UPDATED "200601300000Z" ORGANIZATION "Cisco System, Inc." CONTACT-INFO "Postal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "200601300000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 492 }
ciscoCefMIB OBJECT IDENTIFIER ::= { ciscoMgmt 492 }
Vendor: Cisco
Module: CISCO-CEF-MIB
[Automatically extracted from oidview.com]
ciscoCefMIB MODULE-IDENTITY LAST-UPDATED "200601300000Z" ORGANIZATION "Cisco System, Inc." CONTACT-INFO "Postal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "200601300000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 492 }
ciscoCefMIB MODULE-IDENTITY LAST-UPDATED "200601300000Z" ORGANIZATION "Cisco System, Inc." CONTACT-INFO "Postal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "200601300000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 492 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.492.0 | ciscoCefMIBNotifs | 4 | 4 | None |
| 1.3.6.1.4.1.9.9.492.1 | ciscoCefMIBObjects | 9 | 177 | None |
| 1.3.6.1.4.1.9.9.492.2 | ciscoCefMIBConform | 2 | 8 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.443 | ciscoCommonMgmtMIB | 3 | 37 | MIB module for integrating different elements of managing a device. For example, different device access methods like SNMP, CLI, … |
| 1.3.6.1.4.1.9.9.445 | ciscoQinqVlanMIB | 3 | 25 | This MIB defines configuration and monitoring capabilities relating to 802.1QinQ interfaces. QinQ interfaces are capable of term… |
| 1.3.6.1.4.1.9.9.447 | ciscoScsiFlowMIB | 3 | 99 | A SCSI Flow is described as a SCSI Initiator SCSI Target combination. This MIB is used to configure and monitor SCSI Flows. Gloss… |
| 1.3.6.1.4.1.9.9.448 | ciscoSsmProvMIB | 2 | 26 | This MIB is used to provision features on a Data Path Processor (DPP) of a Storage Service Module (SSM). A DPP is assigned to a c… |
| 1.3.6.1.4.1.9.9.449 | ciscoEigrpMIB | 3 | 103 | Enhanced Interior Gateway Protocol (EIGRP) is a Cisco proprietary distance vector routing protocol. It is based on the Diffusin… |
| 1.3.6.1.4.1.9.9.450 | ciscoCableAdmCtrlMIB | 3 | 123 | This MIB module defines the managed objects enabling the management of Cable Modem Termination System (CMTS) admission control. CM… |
| 1.3.6.1.4.1.9.9.451 | ciscoIpUrpfMIB | 3 | 47 | Unicast Reverse Path Forwarding (URPF) is a function that checks the validity of the source address of IP packets received on an … |
| 1.3.6.1.4.1.9.9.454 | ciscoDot11LbsMIB | 3 | 23 | This MIB module supports network management for Location Based Services on IEEE 802.11 wireless LAN devices. Location Based Serv… |
| 1.3.6.1.4.1.9.9.455 | ciscoImageTc | 0 | 0 | This MIB module defines the textual conventions used in the enhanced image MIB. Glossary: Base Image Essential part of the operatin… |
| 1.3.6.1.4.1.9.9.456 | ciscoDot11WidsMIB | 3 | 50 | This MIB is intended to be implemented on the following IOS based network entities for the purpose of providing network managemen… |
| 1.3.6.1.4.1.9.9.457 | ciscoWdsIdsMIB | 2 | 18 | This MIB is intended to be implemented on all IOS based network entities that provide Wireless Domain Services, for the purpose o… |
| 1.3.6.1.4.1.9.9.458 | ciscoApplianceRedundancyMIB | 3 | 47 | This mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management applia… |
| 1.3.6.1.4.1.9.9.459 | ciscoBitsClockMIB | 3 | 21 | This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to… |
| 1.3.6.1.4.1.9.9.460 | ciscoTpcMIB | 3 | 24 | The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved … |
| 1.3.6.1.4.1.9.9.461 | ciscoEtherCfmMIB | 3 | 39 | This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-e… |
| 1.3.6.1.4.1.9.9.463 | ciscoSanTapMIB | 3 | 30 | MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that p… |
| 1.3.6.1.4.1.9.9.466 | ciscoEthernetAccessMIB | 2 | 20 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge dev… |
| 1.3.6.1.4.1.9.9.467 | ciscoCryptoAcceleratorMIB | 3 | 107 | The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implem… |
| 1.3.6.1.4.1.9.9.468 | ciscoContextMappingMIB | 2 | 35 | A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple… |
| 1.3.6.1.4.1.9.9.470 | ciscoEnhancedSlbMIB | 3 | 106 | The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB exten… |
| 1.3.6.1.4.1.9.9.471 | ciscoFlexLinksMIB | 3 | 36 | This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2… |
| 1.3.6.1.4.1.9.9.472 | ciscoModuleVirtualizationMIB | 3 | 35 | This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical devi… |
| 1.3.6.1.4.1.9.9.473 | ciscoCcaMIB | 3 | 200 | The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for appl… |
| 1.3.6.1.4.1.9.9.474 | ciscoFilterGroupMIB | 3 | 55 | The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other proto… |
| 1.3.6.1.4.1.9.9.479 | ciscoCableWidebandMIB | 3 | 77 | This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS). Wideband DOCSIS… |
| 1.3.6.1.4.1.9.9.480 | ciscoL4L7moduleResourceLimitMIB | 4 | 100 | The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in … |
| 1.3.6.1.4.1.9.9.482 | ciscoInterfaceTopNExtMIB | 3 | 16 | This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces. |
| 1.3.6.1.4.1.9.9.483 | ciscoIpRanBackHaulMIB | 3 | 248 | This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM en… |
| 1.3.6.1.4.1.9.9.484 | ciscoNacNadMIB | 3 | 157 | This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system. End… |
| 1.3.6.1.4.1.9.9.485 | ciscoRttMonTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and CISCO-RTTMON-ICMP-MIB, but they are not … |
| 1.3.6.1.4.1.9.9.486 | ciscoRttMonIcmpMIB | 3 | 7 | An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such a… |
| 1.3.6.1.4.1.9.9.487 | ciscoRttMonRtpMIB | 3 | 8 | An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provi… |
| 1.3.6.1.4.1.9.9.488 | ciscoFirewallTc | 0 | 0 | This MIB module defines textual conventions that are commonly used in modeling management information pertaining to configuration… |
| 1.3.6.1.4.1.9.9.490 | ciscoNetintMIB | 3 | 11 | This MIB module is for Network Interrupt information on Cisco device. |
| 1.3.6.1.4.1.9.9.491 | ciscoUnifiedFirewallMIB | 3 | 235 | Overview of Cisco Firewall MIB ============================== This MIB Module models status and performance statistics pertaining … |
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.508 | ciscoSlbHealthMonMIB | 3 | 62 | An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB, ciscoVoiceLmrMIB | 3 | 176 | This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes … |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 50 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 61 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.524 | ciscoLwappQosMIB | 3 | 119 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.525 | ciscoLwappTsmMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| ... | ||||