Contents

MPLS-LSR-STD-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

mplsXCUp· 1

mplsXCDown· 2

 

 

MPLS-LSR-STD-MIB

About this MIB

A label switching router (LSR) is a router that performs MPLS forwarding. Based on the traditional routing table, LSRs establish label switching paths through a label distribution protocol to perform fast label switching.

MPLS-LSR-STD-MIB is a standard MIB based on RFC 3813.

MIB file name

rfc3813-mpls-lsr-std.mib

Notifications

mplsXCUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.2.0.1	mplsXCup	Informational	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the MPLSXC state (mplsXCOperStatus) of a tunnel (such as LDP tunnel or MPLS TE tunnel) changes to UP.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te command.

OFF

CLI: Use the undo snmp-agent trap enable te command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.2.1.10.1.9 (mplsXCAdminStatus)	Operational status of the label.	mplsXCIndex mplsXCInSegmentIndex mplsXCOutSegmentIndex	INTEGER	up(1) , down(2) , testing(3)
1.3.6.1.2.1.10.166.2.1.10.1.10 (mplsXCOperStatus)	Actual operational status of the cross-connect.	mplsXCIndex mplsXCInSegmentIndex mplsXCOutSegmentIndex	INTEGER	up(1) , down(2) ,  testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7)

 

Recommended action

No action is required.

mplsXCDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.2.0.2	A cross-connect enters down state.	Error	Major	1.3.6.1.2.1.10.166.2.0.1 (mplsXCUp)	ON

 

Notification triggers

This notification is generated when the MPLSXC state (mplsXCOperStatus) of a tunnel (such as LDP tunnel or MPLS TE tunnel) changes to down.

Possible causes:

MPLS is disabled on the interfaces that the tunnel passes through.

A protocol fault occurs on the tunnel. For example, LDP is disabled globally or on the interfaces that the tunnel passes through.

A fault occurs on the path that the tunnel passes through.

Dependent routes of the tunnel have been withdrawn.

The tunnel is switched to a new path and the new path has problem 1 or 2.

System impact

Service traffic carried on the tunnel will be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable te command.

OFF

CLI: Use the undo snmp-agent trap enable te command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.2.1.10.1.9 (mplsXCAdminStatus)	Operational status of the label.	mplsXCIndex mplsXCInSegmentIndex mplsXCOutSegmentIndex	INTEGER	up(1) , down(2) , testing(3)
1.3.6.1.2.1.10.166.2.1.10.1.10 (mplsXCOperStatus)	Actual operational status of the cross-connect.	mplsXCIndex mplsXCInSegmentIndex mplsXCOutSegmentIndex	INTEGER	up(1) , down(2) ,  testing(3) , unknown(4) , dormant(5) , notPresent(6) , lowerLayerDown(7)

 

Recommended action

To resolve this issue, perform the following tasks using the protocol, tunnel destination address, outgoing interface/next hop and outgoing label information in the mplsXCDown notification message.

1.Check routes: Execute the display ip routing-table command or the display ipv6 routing-tablecommand to view whether the route corresponding to the tunnel destination address exists.

  - If the route does not exist, configure a proper routing protocol to generate a route to the tunnel destination address. Check whether an mplsXCUp notification is generated. If yes, the issue is resolved. If no, go to step 2.

  - If the route exists, go to step 2.

2.According to the outgoing interface/next hop information, execute the display mpls interface command to identify whether the outgoing interface is enabled with MPLS.

  - If the interface is not enabled with MPLS, execute the mpls enable command on the interface. Check whether an mplsXCUp notification is generated. If yes, the issue is resolved. If no, go to step 3.

  - If the interface is enabled with MPLS, go to step 3.

3.According to the tunnel protocol information, check the protocol capabilities on the interface. Take an LDP tunnel as an example. Execute the display mpls ldp interface command to check whether LDP is enabled on the outgoing interface.

  - If LDP is not enabled, execute the mpls ldp command in system view to enable LDP globally and the mpls ldp enable command in interface view to enable LDP on the interface. Check whether an mplsXCUp notification is generated. If yes, the issue is resolved. If no, go to step 4.

  - If LDP is enabled globally and on the outgoing interface, go to step 4.

4.According to the route in step 1, find the next hop. Execute step 1 through step 3 on the next hop device. Repeat this step to troubleshoot all the nodes that the tunnel passes until the issue is resolved.

5.If the issue persists, contact H3C Support.