CefPrefixEntry |
|
SEQUENCE |
|
|
|
|
cefPrefixType |
InetAddressType |
|
|
cefPrefixAddr |
InetAddress |
|
|
cefPrefixLen |
InetAddressPrefixLength |
|
|
cefPrefixForwardingInfo |
SnmpAdminString |
|
|
cefPrefixPkts |
Counter32 |
|
|
cefPrefixHCPkts |
Counter64 |
|
|
cefPrefixBytes |
Counter32 |
|
|
cefPrefixHCBytes |
Counter64 |
|
|
cefPrefixInternalNRPkts |
Counter32 |
|
|
cefPrefixInternalNRHCPkts |
Counter64 |
|
|
cefPrefixInternalNRBytes |
Counter32 |
|
|
cefPrefixInternalNRHCBytes |
Counter64 |
|
|
cefPrefixExternalNRPkts |
Counter32 |
|
|
cefPrefixExternalNRHCPkts |
Counter64 |
|
|
cefPrefixExternalNRBytes |
Counter32 |
|
|
cefPrefixExternalNRHCBytes |
Counter64 |
|
CefFESelectionEntry |
|
SEQUENCE |
|
|
|
|
cefFESelectionName |
SnmpAdminString |
|
|
cefFESelectionId |
Integer32 |
|
|
cefFESelectionSpecial |
CefForwardingElementSpecialType |
|
|
cefFESelectionLabels |
CefMplsLabelList |
|
|
cefFESelectionAdjLinkType |
CefAdjLinkType |
|
|
cefFESelectionAdjInterface |
InterfaceIndexOrZero |
|
|
cefFESelectionAdjNextHopAddrType |
InetAddressType |
|
|
cefFESelectionAdjNextHopAddr |
InetAddress |
|
|
cefFESelectionAdjConnId |
Unsigned32 |
|
|
cefFESelectionVrfName |
MplsVpnId |
|
|
cefFESelectionWeight |
Unsigned32 |
|
CefCfgEntry |
|
SEQUENCE |
|
|
|
|
cefCfgAdminState |
CefAdminStatus |
|
|
cefCfgOperState |
CefOperStatus |
|
|
cefCfgDistributionAdminState |
CefAdminStatus |
|
|
cefCfgDistributionOperState |
CefOperStatus |
|
|
cefCfgAccountingMap |
BITS |
|
|
cefCfgLoadSharingAlgorithm |
INTEGER |
|
|
cefCfgLoadSharingID |
Unsigned32 |
|
|
cefCfgTrafficStatsLoadInterval |
Unsigned32 |
|
|
cefCfgTrafficStatsUpdateRate |
Unsigned32 |
|
CefIntEntry |
|
SEQUENCE |
|
|
|
|
cefIntSwitchingState |
INTEGER |
|
|
cefIntLoadSharing |
INTEGER |
|
|
cefIntNonrecursiveAccouting |
INTEGER |
|
CefCCGlobalEntry |
|
SEQUENCE |
|
|
|
|
cefCCGlobalAutoRepairEnabled |
TruthValue |
|
|
cefCCGlobalAutoRepairDelay |
Unsigned32 |
|
|
cefCCGlobalAutoRepairHoldDown |
Unsigned32 |
|
|
cefCCGlobalErrorMsgEnabled |
TruthValue |
|
|
cefCCGlobalFullScanAction |
CefCCAction |
|
|
cefCCGlobalFullScanStatus |
CefCCStatus |
|
CefInconsistencyRecordEntry |
|
SEQUENCE |
|
|
|
|
cefInconsistencyRecId |
Integer32 |
|
|
cefInconsistencyPrefixType |
InetAddressType |
|
|
cefInconsistencyPrefixAddr |
InetAddress |
|
|
cefInconsistencyPrefixLen |
InetAddressPrefixLength |
|
|
cefInconsistencyVrfName |
MplsVpnId |
|
|
cefInconsistencyCCType |
CefCCType |
|
|
cefInconsistencyEntity |
EntPhysicalIndexOrZero |
|
|
cefInconsistencyReason |
INTEGER |
|
ciscoCefMIB |
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
+---------------+ points +--------------+
| | | | a set +----> | | | | |
|---------------| of FE | |--------------|
| | | | Selection | | | | | |
|---------------| Entries | |--------------|
| | | |------------+ | |<----+
|---------------| |--------------| |
| | +--------------| | | | | |
+---------------+ | +--------------+ |
| |
points to an |
adjacency entry |
| |
| cefAdjTable |
| +---------------+ may point |
+->| | | | to a set |
|---------------| of FE |
| | | | Selection |
|---------------| Entries |
| | | |----------------+
|---------------|
| |
+---------------+
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. |
MODULE-IDENTITY |
|
|
|
cefFIBSummaryEntry |
1.3.6.1.4.1.9.9.492.1.1.1.1.1 |
If CEF is enabled on the Managed device,
each entry contains the FIB summary related
attributes for the managed entity.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefFIBSummaryEntry |
|
|
cefPrefixEntry |
1.3.6.1.4.1.9.9.492.1.1.2.1 |
If CEF is enabled on the Managed device,
each entry contains the forwarding
prefix attributes.
CEF prefix based non-recursive stats are maintained
in internal and external buckets (depending upon the
value of cefIntNonrecursiveAccouting object in the
CefIntEntry).
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefPrefixEntry |
|
|
cefLMPrefixEntry |
1.3.6.1.4.1.9.9.492.1.1.4.1 |
If CEF is enabled on the managed device, then each
entry represents a longest Match Prefix request.
A management station wishing to get the longest
Match prefix for a given destination address
should create the associate instance of the
row status. The row status should be set to
active(1) to initiate the request. Note that
this entire procedure may be initiated via a
single set request which specifies a row status
of createAndGo(4).
Once the request completes, the management station
should retrieve the values of the objects of
interest, and should then delete the entry. In order
to prevent old entries from clogging the table,
entries will be aged out, but an entry will never be
deleted within 5 minutes of completion.
Entries are lost after an agent restart.
I.e. to find out the longest prefix match for
destination address of A.B.C.D on entity whose
entityPhysicalIndex is 1, the Management station
will create an entry in cefLMPrefixTable with
cefLMPrefixRowStatus.1(entPhysicalIndex).1(ipv4).A.B.C.D
set to createAndGo(4). Management Station may query the
value of objects cefLMPrefix and cefLMPrefixLen
to find out the corresponding prefix entry from the
cefPrefixTable once the value of cefLMPrefixState
is set to matchFound(2).
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF.
|
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefLMPrefixEntry |
|
|
cefPathEntry |
1.3.6.1.4.1.9.9.492.1.1.5.1 |
If CEF is enabled on the Managed device,
each entry contain a CEF prefix path.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefPathEntry |
|
|
cefAdjSummaryEntry |
1.3.6.1.4.1.9.9.492.1.2.1.1.1 |
If CEF is enabled on the Managed device,
each entry contains the CEF Adjacency
summary related attributes for the
Managed entity. A row exists for
each adjacency link type.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefAdjSummaryEntry |
|
|
cefAdjEntry |
1.3.6.1.4.1.9.9.492.1.2.2.1 |
If CEF is enabled on the Managed device,
each entry contains the adjacency
attributes. Adjacency entries may exist
for all the interfaces on which packets
can be switched out of the device.
The interface is instantiated by ifIndex.
Therefore, the interface index must have been
assigned, according to the applicable procedures,
before it can be meaningfully used.
Generally, this means that the interface must exist.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefAdjEntry |
|
|
cefFESelectionEntry |
1.3.6.1.4.1.9.9.492.1.3.1.1 |
If CEF is enabled on the Managed device,
each entry contain a CEF forwarding element
selection list.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefFESelectionEntry |
|
|
cefCfgEntry |
1.3.6.1.4.1.9.9.492.1.4.1.1 |
If the Managed device supports CEF,
each entry contains the CEF config
parameter for the managed entity.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefCfgEntry |
|
|
cefResourceEntry |
1.3.6.1.4.1.9.9.492.1.4.2.1 |
If the Managed device supports CEF,
each entry contains the CEF Resource
parameters for the managed entity.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefResourceEntry |
|
|
cefIntEntry |
1.3.6.1.4.1.9.9.492.1.5.1.1 |
If CEF is enabled on the Managed device,
each entry contains the CEF attributes
associated with an interface.
The interface is instantiated by ifIndex.
Therefore, the interface index must have been
assigned, according to the applicable procedures,
before it can be meaningfully used.
Generally, this means that the interface must exist.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefIntEntry |
|
|
cefPeerEntry |
1.3.6.1.4.1.9.9.492.1.6.1.1 |
If CEF is enabled on the Managed device,
each entry contains the CEF related attributes
associated with a CEF peer entity.
entPhysicalIndex and entPeerPhysicalIndex are
also indexes for this table which represents
entities of 'module' entPhysicalClass which are
capable of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefPeerEntry |
|
|
cefPeerFIBEntry |
1.3.6.1.4.1.9.9.492.1.6.2.1 |
If CEF is enabled on the Managed device,
each entry contains the CEF FIB State
associated a CEF peer entity.
entPhysicalIndex and entPeerPhysicalIndex are
also indexes for this table which represents
entities of 'module' entPhysicalClass which are
capable of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefPeerFIBEntry |
|
|
cefStatsPrefixLenEntry |
1.3.6.1.4.1.9.9.492.1.8.1.1 |
If CEF is enabled on the Managed device
and if CEF accounting is set to enable
prefix length based accounting (value of
cefCfgAccountingMap object in the
cefCfgEntry is set to enable 'prefixLength'
accounting), each entry contains the traffic
statistics for a prefix length.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefStatsPrefixLenEntry |
|
|
cefSwitchingStatsEntry |
1.3.6.1.4.1.9.9.492.1.8.2.1 |
If CEF is enabled on the Managed device,
each entry specifies the switching stats.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device.
entPhysicalIndex is also an index for this
table which represents entities of
'module' entPhysicalClass which are capable
of running CEF. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefSwitchingStatsEntry |
|
|
cefCCGlobalEntry |
1.3.6.1.4.1.9.9.492.1.7.1.1 |
If the managed device supports CEF,
each entry contains the global consistency
checker parameter for the managed device.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefCCGlobalEntry |
|
|
cefCCTypeEntry |
1.3.6.1.4.1.9.9.492.1.7.2.1 |
If the managed device supports CEF,
each entry contains the consistency
checker statistics for a consistency
checker type.
A row may exist for each IP version type
(v4 and v6) depending upon the IP version
supported on the device. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefCCTypeEntry |
|
|
cefInconsistencyRecordEntry |
1.3.6.1.4.1.9.9.492.1.7.3.1 |
If the managed device supports CEF,
each entry contains the inconsistency
record. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
CefInconsistencyRecordEntry |
|
|
cefNotifThrottlingInterval |
1.3.6.1.4.1.9.9.492.1.9.4 |
This object controls the generation of the
cefInconsistencyDetection notification.
If this object has a value of zero,
then the throttle control is disabled.
If this object has a non-zero value, then the agent
must not generate more than one
cefInconsistencyDetection 'notification-event' in the
indicated period, where a 'notification-event' is the
transmission of a single trap
or inform PDU to a list of notification destinations.
If additional inconsistency is detected within the
throttling period, then notification-events
for these inconsistencies should be suppressed by the agent
until the current throttling period expires. At the end of a
throttling period, one notification-event should be generated
if any inconsistency was detected since the start of the
throttling period. In such a case, another throttling period
is started right away.
An NMS should periodically poll cefInconsistencyRecordTable
to detect any missed cefInconsistencyDetection
notification-events, e.g., due to throttling or transmission
loss.
If cefNotifThrottlingInterval notification generation
is enabled, the suggested default throttling period is
60 seconds, but generation of the cefInconsistencyDetection
notification should be disabled by default.
If the agent is capable of storing non-volatile
configuration, then the value of this object must be
restored after a re-initialization of the management
system.
The actual transmission of notifications is controlled
via the MIB modules in RFC 3413. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0 | 1..3600 |
|