MPLS-LSR-STD-MIB

        This MIB module contains managed object definitions for
the Multiprotocol Label Switching (MPLS) Router as
        
defined in: Rosen, E., Viswanathan, A., and R.
Callon, Multiprotocol Label Switching Architecture,
RFC 3031, January 2001.
        
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3812. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
    
Source file
MPLS-LSR-STD-MIB
Last revised
Identity
mplsLsrStdMIB
Base OID
1.3.6.1.2.1.10.166.2
Imported Objects
IANA-ADDRESS-FAMILY-NUMBERS-MIB AddressFamilyNumbers
IF-MIB ifCounterDiscontinuityGroup (no object page) ifGeneralInformationGroup (no object page) InterfaceIndexOrZero
INET-ADDRESS-MIB InetAddress InetAddressType
MPLS-TC-STD-MIB MplsBitRate MplsLabel MplsLSPID MplsOwner mplsStdMIB
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 Gauge32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 zeroDotZero
SNMPv2-TC RowPointer RowStatus StorageType TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'MPLS-LSR-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MPLS-LSR-STD-MIB::mplsLsrStdMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MPLS-LSR-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-LSR-STD-MIB::mplsLsrStdMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (97)
.1.3.6.1.2.1.10.166.2
.1.3.6.1.2.1.10.166.2.0
.1.3.6.1.2.1.10.166.2.1
.1.3.6.1.2.1.10.166.2.1.1
.1.3.6.1.2.1.10.166.2.1.1.1
.1.3.6.1.2.1.10.166.2.1.1.1.1
.1.3.6.1.2.1.10.166.2.1.1.1.2
.1.3.6.1.2.1.10.166.2.1.1.1.3
.1.3.6.1.2.1.10.166.2.1.1.1.4
.1.3.6.1.2.1.10.166.2.1.1.1.5
kilobits per secondMPLS-TC-STD-MIBMplsBitRate
.1.3.6.1.2.1.10.166.2.1.1.1.6
.1.3.6.1.2.1.10.166.2.1.1.1.7
Bits
.1.3.6.1.2.1.10.166.2.1.1.1.8
.1.3.6.1.2.1.10.166.2.1.10
.1.3.6.1.2.1.10.166.2.1.10.1
.1.3.6.1.2.1.10.166.2.1.10.1.1
Enumeration
.1.3.6.1.2.1.10.166.2.1.10.1.10
.1.3.6.1.2.1.10.166.2.1.10.1.2
.1.3.6.1.2.1.10.166.2.1.10.1.3
.1.3.6.1.2.1.10.166.2.1.10.1.4
.1.3.6.1.2.1.10.166.2.1.10.1.5
.1.3.6.1.2.1.10.166.2.1.10.1.6
.1.3.6.1.2.1.10.166.2.1.10.1.7
.1.3.6.1.2.1.10.166.2.1.10.1.8
Enumeration
.1.3.6.1.2.1.10.166.2.1.10.1.9
Unsigned32
.1.3.6.1.2.1.10.166.2.1.11
.1.3.6.1.2.1.10.166.2.1.12
.1.3.6.1.2.1.10.166.2.1.13
.1.3.6.1.2.1.10.166.2.1.13.1
.1.3.6.1.2.1.10.166.2.1.13.1.1
Unsigned32
.1.3.6.1.2.1.10.166.2.1.13.1.2
.1.3.6.1.2.1.10.166.2.1.13.1.3
.1.3.6.1.2.1.10.166.2.1.13.1.4
.1.3.6.1.2.1.10.166.2.1.13.1.5
.1.3.6.1.2.1.10.166.2.1.13.1.6
.1.3.6.1.2.1.10.166.2.1.14
.1.3.6.1.2.1.10.166.2.1.14.1
.1.3.6.1.2.1.10.166.2.1.14.1.1
.1.3.6.1.2.1.10.166.2.1.14.1.2
.1.3.6.1.2.1.10.166.2.1.14.1.3
.1.3.6.1.2.1.10.166.2.1.14.1.4
.1.3.6.1.2.1.10.166.2.1.15
.1.3.6.1.2.1.10.166.2.1.2
.1.3.6.1.2.1.10.166.2.1.2.1
.1.3.6.1.2.1.10.166.2.1.2.1.1
.1.3.6.1.2.1.10.166.2.1.2.1.2
.1.3.6.1.2.1.10.166.2.1.2.1.3
.1.3.6.1.2.1.10.166.2.1.2.1.4
.1.3.6.1.2.1.10.166.2.1.3
.1.3.6.1.2.1.10.166.2.1.4
.1.3.6.1.2.1.10.166.2.1.4.1
.1.3.6.1.2.1.10.166.2.1.4.1.1
.1.3.6.1.2.1.10.166.2.1.4.1.10
.1.3.6.1.2.1.10.166.2.1.4.1.11
.1.3.6.1.2.1.10.166.2.1.4.1.2
.1.3.6.1.2.1.10.166.2.1.4.1.3
.1.3.6.1.2.1.10.166.2.1.4.1.4
Integer32
.1.3.6.1.2.1.10.166.2.1.4.1.5
.1.3.6.1.2.1.10.166.2.1.4.1.6
.1.3.6.1.2.1.10.166.2.1.4.1.7
.1.3.6.1.2.1.10.166.2.1.4.1.8
.1.3.6.1.2.1.10.166.2.1.4.1.9
.1.3.6.1.2.1.10.166.2.1.5
.1.3.6.1.2.1.10.166.2.1.5.1
.1.3.6.1.2.1.10.166.2.1.5.1.1
.1.3.6.1.2.1.10.166.2.1.5.1.2
.1.3.6.1.2.1.10.166.2.1.5.1.3
.1.3.6.1.2.1.10.166.2.1.5.1.4
.1.3.6.1.2.1.10.166.2.1.5.1.5
.1.3.6.1.2.1.10.166.2.1.5.1.6
.1.3.6.1.2.1.10.166.2.1.6
.1.3.6.1.2.1.10.166.2.1.7
.1.3.6.1.2.1.10.166.2.1.7.1
.1.3.6.1.2.1.10.166.2.1.7.1.1
.1.3.6.1.2.1.10.166.2.1.7.1.10
.1.3.6.1.2.1.10.166.2.1.7.1.11
.1.3.6.1.2.1.10.166.2.1.7.1.12
.1.3.6.1.2.1.10.166.2.1.7.1.2
.1.3.6.1.2.1.10.166.2.1.7.1.3
.1.3.6.1.2.1.10.166.2.1.7.1.4
.1.3.6.1.2.1.10.166.2.1.7.1.5
.1.3.6.1.2.1.10.166.2.1.7.1.6
.1.3.6.1.2.1.10.166.2.1.7.1.7
.1.3.6.1.2.1.10.166.2.1.7.1.8
.1.3.6.1.2.1.10.166.2.1.7.1.9
.1.3.6.1.2.1.10.166.2.1.8
.1.3.6.1.2.1.10.166.2.1.8.1
.1.3.6.1.2.1.10.166.2.1.8.1.1
.1.3.6.1.2.1.10.166.2.1.8.1.2
.1.3.6.1.2.1.10.166.2.1.8.1.3
.1.3.6.1.2.1.10.166.2.1.8.1.4
.1.3.6.1.2.1.10.166.2.1.8.1.5
.1.3.6.1.2.1.10.166.2.1.8.1.6
.1.3.6.1.2.1.10.166.2.1.9
.1.3.6.1.2.1.10.166.2.2
.1.3.6.1.2.1.10.166.2.2.1
.1.3.6.1.2.1.10.166.2.2.2
Dependencies (9) 7 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (2)
OctetString range: 1..24
OctetString range: 1..24
Conformance Groups (9)
Collection of objects needed for MPLS interface
and interface performance information.
.1.3.6.1.2.1.10.166.2.2.1.1
Collection of objects needed to implement an in-
segment.
.1.3.6.1.2.1.10.166.2.2.1.2
Collection of objects needed to implement an out-

segment.
.1.3.6.1.2.1.10.166.2.2.1.3
Collection of objects needed to implement a
cross-connect entry.
.1.3.6.1.2.1.10.166.2.2.1.4
Collection of objects providing performance
information
about an LSR.
.1.3.6.1.2.1.10.166.2.2.1.5
Object(s) providing performance information
specific to out-segments for which the object
mplsInterfaceInOctets wraps around too quickly.
.1.3.6.1.2.1.10.166.2.2.1.6
Object(s) providing performance information
specific to out-segments for which the object
mplsInterfaceOutOctets wraps around too
quickly.
.1.3.6.1.2.1.10.166.2.2.1.7
Objects needed to support label stacking.
.1.3.6.1.2.1.10.166.2.2.1.8
Set of notifications implemented in this
module.
.1.3.6.1.2.1.10.166.2.2.1.9
Compliance Statements (2)

OID .1.3.6.1.2.1.10.166.2.2.2.1
Compliance statement for agents that provide full
support for MPLS-LSR-STD-MIB. Such devices can
then be monitored and also be configured using
this MIB module.
Required groups
mandatory IF-MIB::ifGeneralInformationGroup
mandatory IF-MIB::ifCounterDiscontinuityGroup
mandatory mplsInterfaceGroup
mandatory mplsInSegmentGroup
mandatory mplsOutSegmentGroup
mandatory mplsXCGroup
mandatory mplsPerfGroup
optional mplsLabelStackGroup This group is only mandatory for LSRs that wish to
support the modification of LSP label stacks.
optional mplsHCInSegmentPerfGroup This group is mandatory for those in-segment entries
for which the object mplsInSegmentOutOctets wraps
around too quickly based on the criteria specified in
RFC 2863 for high-capacity counters.
optional mplsHCOutSegmentPerfGroup This group is mandatory for those out-segment entries
for which the object mplsOutSegmentPerfOctets wraps
around too quickly based on the criteria specified in
RFC 2863 for high-capacity counters.
optional mplsLsrNotificationGroup This group is only mandatory for those implementations
which can efficiently implement the notifications
contained in this group.
Object refinements
ObjectAccessSyntaxDescription
mplsInSegmentRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is
not required.
mplsOutSegmentNextHopAddrType
unknown(0), ipv4(1), ipv6(2)
Only unknown(0), ipv4(1) and ipv6(2) support
is required.
mplsOutSegmentNextHopAddr An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes.
mplsOutSegmentRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
mplsLabelStackRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
mplsXCRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.

OID .1.3.6.1.2.1.10.166.2.2.2.2
Compliance requirement for implementations that only
provide read-only support for MPLS-LSR-STD-MIB. Such
devices can then be monitored but cannot be configured
using this MIB module.
Required groups
mandatory IF-MIB::ifGeneralInformationGroup
mandatory IF-MIB::ifCounterDiscontinuityGroup
mandatory mplsInterfaceGroup
mandatory mplsInSegmentGroup
mandatory mplsOutSegmentGroup
mandatory mplsXCGroup
mandatory mplsPerfGroup
optional mplsLabelStackGroup This group is only mandatory for LSRs that wish to
support the modification of LSP label stacks.
optional mplsHCInSegmentPerfGroup This group is mandatory for those in-segment entries
for which the object mplsInSegmentOutOctets wraps
around too quickly based on the criteria specified in
RFC 2863 for high-capacity counters.
optional mplsHCOutSegmentPerfGroup This group is mandatory for those out-segment entries
for which the object mplsOutSegmentPerfOctets wraps
around too quickly based on the criteria specified in
RFC 2863 for high-capacity counters.
optional mplsLsrNotificationGroup This group is only mandatory for those implementations
which can efficiently implement the notifications
contained in this group.
Object refinements
ObjectAccessSyntaxDescription
mplsInSegmentLabel readonly
Write access is not required.
mplsInSegmentLabelPtr readonly
Write access is not required.
mplsInSegmentNPop readonly
Integer32
Write access is not required. This object
SHOULD be set to 1 if it is read-only.
mplsInSegmentAddrFamily readonly
Write access is not required. A value of other(0)
should be supported because there may be cases where
the agent may not know about or support any address
types.
mplsInSegmentRowStatus readonly
active(1)
Write access is not required.
mplsInSegmentStorageType readonly
Write access is not required.
mplsOutSegmentInterface readonly
Write access is not required.
mplsOutSegmentPushTopLabel readonly
Write access is not required.
mplsOutSegmentTopLabel readonly
Write access is not required.
mplsOutSegmentTopLabelPtr readonly
Write access is not required.
mplsOutSegmentNextHopAddrType readonly
unknown(0), ipv4(1), ipv6(2)
Write access is not required. Only unknown(0),
ipv4(1) and ipv6(2) support is required.
mplsOutSegmentNextHopAddr readonly Write access is not required. An implementation is
only required to support unknown(0), ipv4(1) and
ipv6(2) sizes.
mplsOutSegmentRowStatus readonly
active(1)
Write access is not required.
mplsOutSegmentStorageType readonly
Write access is not required.
mplsXCLabelStackIndex readonly
Write access is not required.
mplsXCAdminStatus readonly
Read only support is required.
mplsXCRowStatus readonly
active(1)
Write access is not required.
mplsXCStorageType readonly
Write access is not required.
mplsLabelStackLabel readonly
Write access is not required.
mplsLabelStackLabelPtr readonly
Write access is not required.
mplsLabelStackRowStatus readonly
Write access is not required.
mplsLabelStackStorageType readonly
Write access is not required.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.2.1.10.166.2.0.1
This notification is generated when the
mplsXCOperStatus object for one or more contiguous
entries in mplsXCTable are about to enter the up(1)
state from some other state. The included values of
mplsXCOperStatus MUST both be set equal to this
new state (i.e: up(1)). The two instances of
mplsXCOperStatus in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For
cases where a contiguous range of cross-connects
have transitioned into the up(1) state at roughly
the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single cross-connect entry, then
the instance identifier (and values) of the two
mplsXCOperStatus objects MUST be the identical.
.1.3.6.1.2.1.10.166.2.0.2
This notification is generated when the
mplsXCOperStatus object for one or more contiguous
entries in mplsXCTable are about to enter the
down(2) state from some other state. The included values

of mplsXCOperStatus MUST both be set equal to this
down(2) state. The two instances of mplsXCOperStatus
in this notification indicate the range of indexes
that are affected. Note that all the indexes of the
two ends of the range can be derived from the
instance identifiers of these two objects. For
cases where a contiguous range of cross-connects
have transitioned into the down(2) state at roughly
the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single cross-connect entry, then
the instance identifier (and values) of the two
mplsXCOperStatus objects MUST be identical.