CISCO-IF-EXTENSION-MIB
AI MIB Summary
The CISCO-IF-EXTENSION-MIB extends the standard IF-MIB on Cisco IOS and NX-OS devices to expose vendor-specific interface attributes, including physical layer details, optical module diagnostics, and interface administrative states not defined in RFC 2863. This module supersedes the deprecated OLD-CISCO-INTERFACES-MIB to provide granular visibility into interface operational parameters for comprehensive network monitoring and troubleshooting.
A MIB module for extending the IF-MIB (RFC2863) to add objects which provide additional information about interfaces not available in other MIBS. This MIB replaces the OLD-CISCO-INTERFACES-MIB.
Main OID:
ciscoIfExtensionMIB.1.3.6.1.4.1.9.9.276
68
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
68 total| Object Name |
|---|
ciscoIfExtensionMIBA MIB module for extending the IF-MIB (RFC2863)
to add objects which provide additional information
about interfaces not available in other MIBS.
This MIB replaces the OLD-CISCO-INTERFACES-MIB. MODULE-IDENTITY .1.3.6.1.4.1.9.9.276 |
ciscoIfExtensionMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.0 |
cieLinkDownA cisco specific linkDown notification
signifies that the SNMP entity, acting in an
agent role, has detected that the ifOperStatus
object for one of its communication links is
about to enter the down state from some other
state (but not from the notPresent state).
The varbinds for this notification indicate the
interface information of the communication
link. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.276.0.1 |
cieLinkUpA cisco specific linkUp trap signifies that
the SNMP entity, acting in an agent role, has
detected that the ifOperStatus object for one
of its communication links left the down state
and transitioned into some other state (but not
into the notPresent state). The varbinds for
this notification indicate the interface
information of the communication link. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.276.0.2 |
ciscoIfExtensionMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1 |
ciscoIfExtensionStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.1 |
cieIfPacketStatsTableThis table contains interface packet
statistics which are not available in
IF-MIB(RFC2863).
As an example, some interfaces to which
objects in this table are applicable are
as follows :
o Ethernet
o FastEthernet
o ATM
o BRI
o Sonet
o GigabitEthernet
Some objects defined in this table may be
applicable to physical interfaces only.
As a result, this table may be sparse for
some logical interfaces. SEQUENCE OF CieIfPacketStatsEntry .1.3.6.1.4.1.9.9.276.1.1.1 |
cieIfPacketStatsEntryAn entry into the cieIfPacketStatsTable. CieIfPacketStatsEntry .1.3.6.1.4.1.9.9.276.1.1.1.1 |
cieIfLastInTimeThis object represents the elapsed time in
milliseconds since last protocol input
packet was received.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.276.1.1.1.1.1 |
cieIfLastOutTimeThis object represents the elapsed time in
milliseconds since last protocol output
packet was transmitted.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.276.1.1.1.1.2 |
cieIfLastOutHangTimeThis object represents the elapsed time in
milliseconds since last protocol output
packet could not be successfully transmitted.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.276.1.1.1.1.3 |
cieIfInRuntsErrsThe number of packets input on a particular
physical interface which were dropped as
they were smaller than the minimum allowable
physical media limit.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.4 |
cieIfInGiantsErrsThe number of input packets on a particular
physical interface which were dropped as
they were larger than the ifMtu (largest
permitted size of a packet which can be
sent/received on an interface).
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.5 |
cieIfInFramingErrsThe number of input packets on a physical
interface which were misaligned or had
framing errors. This happens when the
format of the incoming packet on a physical
interface is incorrect.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.6 |
cieIfInOverrunErrsThe number of input packets which arrived
on a particular physical interface which
were too quick for the hardware to receive
and hence the receiver ran out of buffers.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.7 |
cieIfInIgnoredThe number of input packets which were simply
ignored by this physical interface due to
insufficient resources to handle the incoming
packets.
For example, this could indicate that the input
receive buffers are not available or that the
receiver lost a packet.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.8 |
cieIfInAbortErrsNumber of input packets which were dropped
because the receiver aborted.
Examples of this could be when an abort
sequence aborted the input frame or when
there is a collision in an ethernet segment.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.9 |
cieIfInputQueueDropsThe number of input packets which were
dropped.
Some reasons why this object could be
incremented are:
o Input queue is full.
o Errors at the receiver hardware
while receiving the packet.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.10 |
cieIfOutputQueueDropsThis object indicates the number of output
packets dropped by the interface even though
no error had been detected to prevent them
being transmitted.
The packet could be dropped for many reasons,
which could range from the interface being
down to errors in the format of the packet.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfPacketDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.1.1.11 |
cieIfPacketDiscontinuityTimeThe value of sysUpTime on the most recent
occasion at which this interface's counters
suffered a discontinuity.
If no such discontinuities have occurred
since the last re-initialization of the
local management subsystem, then this
object contains a value of zero.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.276.1.1.1.1.12 |
cieIfInterfaceTableThis table contains objects which provide
more information about interface
properties not available in IF-MIB
(RFC 2863).
Some objects defined in this table may be
applicable to physical interfaces only.
As a result, this table may be sparse for
logical interfaces. SEQUENCE OF CieIfInterfaceEntry .1.3.6.1.4.1.9.9.276.1.1.2 |
cieIfInterfaceEntryAn entry into the cieIfInterfaceTable. CieIfInterfaceEntry .1.3.6.1.4.1.9.9.276.1.1.2.1 |
cieIfResetCountThe number of times the interface was
internally reset and brought up.
Some of the actions which can cause this
counter to increment are :
o Bringing an interface up using the
interface CLI command.
o Clearing the interface with the exec
CLI command.
o Bringing the interface up via SNMP.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfInterfaceDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.2.1.1 |
cieIfKeepAliveEnabledA keepalive is a small, layer-2 message
that is transmitted by a network device
to let directly-connected network devices
know of its presence.
This object returns 'true' if keepalives
are enabled on this interface. If keepalives
are not enabled, 'false' is returned.
Setting this object to TRUE or FALSE enables
or disables (respectively) keepalive on this
interface.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.276.1.1.2.1.2 |
cieIfStateChangeReasonThis object displays a human-readable
textual string which describes the
cause of the last state change of the
interface.
Examples of the values this object
can take are:
o 'Lost Carrier'
o 'administratively down'
o 'up'
o 'down'ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.276.1.1.2.1.3 |
cieIfCarrierTransitionCountNumber of times interface saw the carrier
signal transition.
For example, if a T1 line is unplugged,
then framer will detect the loss of signal
(LOS) on the line and will count it as a
transition.
Discontinuities in the value of this variable
can occur at re-initialization of the
management system, and at other times as
indicated by the values of
cieIfInterfaceDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.276.1.1.2.1.4 |
cieIfInterfaceDiscontinuityTimeThe value of sysUpTime on the most recent
occasion at which this interface's counters
suffered a discontinuity.
If no such discontinuities have occurred
since the last re-initialization of the
local management subsystem, then this
object contains a value of zero.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.276.1.1.2.1.5 |
cieIfDhcpModeThe DHCP mode configured by the
administrator.
If 'true' the DHCP is enabled. In which
case an IP address is requested in DHCP.
This is in addition to any that are
configured by the administrator in
'ciiIPAddressTable' or 'ciiIPIfAddressTable'
in CISCO-IP-IF-MIB.
If 'false' the DHCP is disabled. In which
case all IP addresses are configured by the
administrator in 'ciiIPAddressTable' or
'ciiIPIfAddressTable'.
For interfaces, for which DHCP cannot be or
is not supported, then this object has the
value 'false'.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.276.1.1.2.1.6 |
cieIfMtuThe MTU configured by the administrator.
This object is exactly same as 'ifMtu' in
ifTable from IF-MIB for the same ifIndex
value , except that it is configurable by the
administrator. For more description of this
object refer to 'ifMtu' in IF-MIB.rw Integer32 (40..2147483647 ) .1.3.6.1.4.1.9.9.276.1.1.2.1.7 |
cieIfContextNameThe ContextName denotes the interface
'context' and is used to logically separate
the MIB management.
RFC 2571 and RFC 2737 describe this approach.
When the agent supports a different SNMP
context, as detailed in RFC 2571 and
RFC 2737, for different interfaces, then the
value of this object specifies the context
name used for this interface.ro OCTET STRING .1.3.6.1.4.1.9.9.276.1.1.2.1.8 |
cieIfOperStatusCauseThis object represents the detailed
operational cause reason for the current
operational state of the interface.
The current operational state of the interface
is given by the 'ifOperStatus' defined
in IF-MIB.
The corresponding instance of
'cieIfOperStatusCauseDescr' must be used to
get the information about the operational
cause value mentioned in this object.
For interfaces whose 'ifOperStatus' is 'down'
the objects 'cieIfOperStatusCause' and
'cieIfOperStatusCauseDescr' together provides
the information about the operational cause
reason and the description of the cause.
The value of this object will be 'none' for
all the 'ifOperStatus' values except for
'down'. Its value will be one status cause
defined in the 'IfOperStatusReason' textual
convention if 'ifOperStatus' is 'down'.
The value of this object will be 'other'
if the operational status cause is not one
defined in 'IfOperStatusReason'.ro IfOperStatusReason (CISCO-TC) .1.3.6.1.4.1.9.9.276.1.1.2.1.9 |
cieIfOperStatusCauseDescrThe description for the cause of current
operational state of the interface, given
by the object 'cieIfOperStatusCause'.
For an interface whose 'ifOperStatus' is not
'down' the value of this object will be
'none'.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.276.1.1.2.1.10 |
cieIfSpeedReceiveAn estimate of the interface's current receive bandwidth in
bits per second. This object is provided for interface with
asymmetric interface speeds like ADSL and should be used in
conjunction with ifSpeed object. For interfaces which do not
vary in bandwidth or for those where no accurate estimation can
be made, this object should contain the nominal bandwidth. If
the bandwidth of the interface is greater than the maximum value
reportable by this object then this object should report its
maximum value (4,294,967,295) and ifHighSpeed must be used to
report the interace's speed. For a sub-layer which has no
concept of bandwidth, this object should be zero.ro Gauge32 .1.3.6.1.4.1.9.9.276.1.1.2.1.11 |
cieIfHighSpeedReceiveAn estimate of the interface's current receive bandwidth in
units of 1,000,000 bits per second. If this object reports a
value of `n' then the speed of the interface is somewhere in the
range of `n-500,000' to `n+499,999'. For interfaces which do
not vary in bandwidth or for those where no accurate estimation
can be made, this object should contain the nominal bandwidth.
For a sub-layer which has no concept of bandwidth, this object
should be zero.ro Gauge32 .1.3.6.1.4.1.9.9.276.1.1.2.1.12 |
cieIfStatusListTableThis table contains objects for providing
the 'ifIndex', interface operational mode and
interface operational cause for all the
interfaces in the modules.
This table contains one entry for each
64 interfaces in an module.
This table provides efficient way of encoding
'ifIndex', interface operational mode and
interface operational cause, from the point
of retrieval, by combining the values a set
of 64 interfaces in a single MIB object. SEQUENCE OF CieIfStatusListEntry .1.3.6.1.4.1.9.9.276.1.1.3 |
cieIfStatusListEntryEach entry represents the 'ifIndex',
interface operational mode and interface
operational cause for a set of 64 interfaces
in a module. CieIfStatusListEntry .1.3.6.1.4.1.9.9.276.1.1.3.1 |
cieIfStatusListIndexAn arbitrary integer value, greater than
zero, which identifies a list of 64 interfaces
within a module. Unsigned32 (1..33554432 ) .1.3.6.1.4.1.9.9.276.1.1.3.1.1 |
cieInterfacesIndexThis object represents the 'ifIndex' for a
set of 64 interfaces in the module.ro InterfaceIndexList .1.3.6.1.4.1.9.9.276.1.1.3.1.2 |
cieInterfacesOperModeThis object represents the operational mode
for a set of 64 interfaces in the module.ro InterfaceOperModeList .1.3.6.1.4.1.9.9.276.1.1.3.1.3 |
cieInterfacesOperCauseThis object represents the operational status
cause for a set of 64 interfaces in the
module.ro InterfaceOperCauseList .1.3.6.1.4.1.9.9.276.1.1.3.1.4 |
ciscoIfExtSystemConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.2 |
cieSystemMtuGlobal system MTU in octets.
This object specifies the MTU on all interfaces.
However, the value specified by cieIfMtu
takes precedence for an interface, which means
that the interface's MTU uses the value
specified by cieIfMtu, if it is configured.rw Integer32 .1.3.6.1.4.1.9.9.276.1.2.1 |
cieLinkUpDownEnableIndicates whether cieLinkUp/cieLinkDown
or standard mib-II defined linkUp/Down or
both, notifications should be generated
for the interfaces in the system.
'standard' - only generate standard defined
mib-II linkUp/linkDown notification
if 'ifLinkUpDownTrapEnable' for
the interface is 'enabled'.
'cisco' - only generate cieLinkUp/cieLinkDown
notifications for an interface if
the 'ifLinkUpDownTrapEnable' for the
interface is 'enabled'.
If both bits are selected then linkUp/linkDown and
cieLinkUp/cieLinkDown are both generated for an
interface if the 'ifLinkUpDownTrapEnable' for the
interface is 'enabled'.rw Bits .1.3.6.1.4.1.9.9.276.1.2.2 |
cieStandardLinkUpDownVarbindsIndicates whether to send the extra
varbinds in addition to the varbinds defined
in linkUp/linkDown notifications.
'standard' - only send the varbinds defined in
the standard linkUp/linkDown
notification.
'additional' - send the extra varbinds in addition
to the defined ones.rw Enumeration .1.3.6.1.4.1.9.9.276.1.2.3 |
ciscoIfExtDot1qCustomEtherType OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.3 |
cieIfDot1qCustomEtherTypeTableA list of the interfaces that support
the 802.1q custom Ethertype feature. SEQUENCE OF CieIfDot1qCustomEtherTypeEntry .1.3.6.1.4.1.9.9.276.1.3.1 |
cieIfDot1qCustomEtherTypeEntryAn entry containing the custom EtherType
information for the interface.
Only interfaces with custom 802.1q
ethertype control are listed in the
table. CieIfDot1qCustomEtherTypeEntry .1.3.6.1.4.1.9.9.276.1.3.1.1 |
cieIfDot1qCustomAdminEtherTypeThe Dot1qEtherType allow administrator
to select a non-standard (other than 0x8100)
2-byte ethertype for the interface to
interoperate with third party vendor's system
that do not use the standard 0x8100 ethertype
to identify 802.1q-tagged frames.
The current administrative value of the
802.1q ethertype for the interface. The
administrative 802.1q ethertype value may
differ from the operational 802.1q ethertype
value. On some platforms, 802.1q ethertype
may be assigned per group rather than per port.
If multiple ports belong to a port group,
the 802.1q ethertype assigned to any of
the ports in such group will apply to all
ports in the same group.
To configure non-standard dot1q ethertype
is only recommended when the Cisco device
is connected to any third party vendor device.
Also be advised that the custom ethertype value
needs to be changed in the whole cloud of
Cisco device with the same custom ethertype
value if the third party device are separated
by number of Cisco device in the middle.rw Integer32 (0..65535 ) .1.3.6.1.4.1.9.9.276.1.3.1.1.1 |
cieIfDot1qCustomOperEtherTypeThe current operational value of the
802.1q ethertype for the interface.ro Integer32 (0..65535 ) .1.3.6.1.4.1.9.9.276.1.3.1.1.2 |
ciscoIfExtUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.4 |
cieIfUtilTableThis table contains the interface utilization
rates for inbound and outbound traffic on an
interface. SEQUENCE OF CieIfUtilEntry .1.3.6.1.4.1.9.9.276.1.4.1 |
cieIfUtilEntryAn entry containing utilization rates for the
interface.
Every interface for which the inbound and
outbound traffic information is available
has a corresponding entry in this table. CieIfUtilEntry .1.3.6.1.4.1.9.9.276.1.4.1.1 |
cieIfInPktRateFive minute exponentially-decayed moving
average of inbound packet rate for this
interface.ro Unsigned64 UNITS "packets per second" .1.3.6.1.4.1.9.9.276.1.4.1.1.1 |
cieIfInOctetRateFive minute exponentially-decayed moving
average of inbound octet rate for this
interface.ro Unsigned64 UNITS "octets per second" .1.3.6.1.4.1.9.9.276.1.4.1.1.2 |
cieIfOutPktRateFive minute exponentially-decayed moving
average of outbound packet rate for this
interface.ro Unsigned64 UNITS "packets per second" .1.3.6.1.4.1.9.9.276.1.4.1.1.3 |
cieIfOutOctetRateFive minute exponentially-decayed moving
average of outbound octet rate for this
interface.ro Unsigned64 UNITS "octets per second" .1.3.6.1.4.1.9.9.276.1.4.1.1.4 |
ciscoIfExtDot1dBaseMapping OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.5 |
cieIfDot1dBaseMappingTableThis table contains the mappings of the
ifIndex of an interface to its
corresponding dot1dBasePort value. SEQUENCE OF CieIfDot1dBaseMappingEntry .1.3.6.1.4.1.9.9.276.1.5.1 |
cieIfDot1dBaseMappingEntryAn entry containing the mapping between
the ifIndex value of an interface and its
corresponding dot1dBasePort value.
Every interface which has been assigned
a dot1dBasePort value by the system
has a corresponding entry in this table. CieIfDot1dBaseMappingEntry .1.3.6.1.4.1.9.9.276.1.5.1.1 |
cieIfDot1dBaseMappingPortThe dot1dBasePort value for this interface.ro Integer32 (1..65535 ) .1.3.6.1.4.1.9.9.276.1.5.1.1.1 |
ciscoIfExtIfNameMapping OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.1.6 |
cieIfNameMappingTableThis table contains objects for providing
the 'ifName' to 'ifIndex' mapping.
This table contains one entry for each
valid 'ifName' available in the system.
Upon the first request, the implementation
of this table will get all the available
ifNames, and it will populate the entries
in this table, it maintains this ifNames
in a cache for ~30 seconds. SEQUENCE OF CieIfNameMappingEntry .1.3.6.1.4.1.9.9.276.1.6.1 |
cieIfNameMappingEntryAn entry into the cieIfNameMappingTable. CieIfNameMappingEntry .1.3.6.1.4.1.9.9.276.1.6.1.1 |
cieIfNameRepresents an interface name mentioned
in the 'ifName' object of this system. DisplayString .1.3.6.1.4.1.9.9.276.1.6.1.1.1 |
cieIfIndexThis object represents the 'ifIndex'
corresponding to the interface name mentioned
in the 'cieIfName' object of this instance.
If the 'ifName' mentioned in the 'cieIfName'
object of this instance corresponds to multiple
'ifIndex' values, then the value of this object
is the numerically smallest of those multiple
'ifIndex' values.ro InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.9.276.1.6.1.1.2 |
ciscoIfExtensionMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.2 |
ciscoIfExtensionMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.2.1 |
ciscoIfExtensionMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.276.2.2 |