MPLS MIB

The MIB module contains managed object definitions for Multiprotocol Label Switching (MPLS).

Supported object groups

Object group name OID Supported?

mplsLsrStdMIB

1.3.6.1.2.1.10.166.2

Yes

mplsInterfaceTable

1.3.6.1.2.1.10.166.2.1.1

Yes

mplsInterfacePerfTable

1.3.6.1.2.1.10.166.2.1.2

Yes

mplsInSegmentIndexNext

1.3.6.1.2.1.10.166.2.1.3

Yes

mplsInSegmentTable

1.3.6.1.2.1.10.166.2.1.4

Yes

mplsInSegmentPerfTable

1.3.6.1.2.1.10.166.2.1.5

Yes

mplsOutSegmentIndexNext

1.3.6.1.2.1.10.166.2.1.6

Yes

mplsOutSegmentTable

1.3.6.1.2.1.10.166.2.1.7

Yes

mplsOutSegmentPerfTable

1.3.6.1.2.1.10.166.2.1.8

Yes

mplsXCIndexNext

1.3.6.1.2.1.10.166.2.1.9

Yes

mplsXCTable

1.3.6.1.2.1.10.166.2.1.10

Yes

mplsMaxLabelStackDepth

1.3.6.1.2.1.10.166.2.1.11

Yes

mplsLabelStackIndexNext

1.3.6.1.2.1.10.166.2.1.12

Yes

mplsLabelStackTable

1.3.6.1.2.1.10.166.2.1.13

Yes

mplsInSegmentMapTable

1.3.6.1.2.1.10.166.2.1.14

Yes

mplsXCNotificationsEnable

1.3.6.1.2.1.10.166.2.1.15

Yes

mplsTeStdMIB

1.3.6.1.2.1.10.166.3

Yes

mplsTeScalars

1.3.6.1.2.1.10.166.3.1

Yes

mplsTeObjects

1.3.6.1.2.1.10.166.3.2

Yes

mplsLdpStdMIB

1.3.6.1.2.1.10.166.4

Yes

mplsLdpObjects

1.3.6.1.2.1.10.166.4.1

Yes

mplsLdpConformance

1.3.6.1.2.1.10.166.4.2

Yes

Table 1. MPLS-LDP-STD-MIB Notifications
Object Name OID Description
mplsLdpPathVectorLimitMismatch 1.3.6.1.2.1.10.166.4.0.2 This notification is sent when the 'mplsLdpEntityPathVectorLimit' does NOT match the value of the 'mplsLdpPeerPathVectorLimit' for a specific Entity.
mplsLdpSessionUp 1.3.6.1.2.1.10.166.4.0.3 If this notification is sent when the value of 'mplsLdpSessionState' enters the 'operational(5)' state.
mplsLdpSessionDown 1.3.6.1.2.1.10.166.4.0.4 This notification is sent when the value of 'mplsLdpSessionState' leaves the 'operational(5)' state.
Table 2. MPLS-TE-STD-MIB Notifications
Object Name OID Description
mplsTunnelReoptimized 1.3.6.1.2.1.10.166.3.0.4 This notification is generated when a tunnel is reoptimized. If the mplsTunnelARHopTable is used, then this tunnel instance's entry in the mplsTunnelARHopTable MAY contain the new path for this tunnel sometime after this trap is issued by the agent.
Table 3. MPLS-LSR-STD-MIB Notifications
Object Name OID Description
mplsXCUp 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.
mplsXCDown 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.