LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

Description

LSPM/4/MPLSXCDOWN:OID [oid] LSP went Down. (BeginLspIndex=[octet].[octet].[octet], EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Down.

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.10.166.2.0.2	Warning	communicationsAlarm(2)

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
BeginLspIndex	Index of the starting LSP, which is expressed in the format of [index of the starting LSP].[index of the inbound interface on the starting LSP].[index of the outbound interface on the starting LSP].
EndLspIndex	Index of the ending LSP, which is expressed in the format of [index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].

1. If the protection function, such as FRR, is configured, services will not be affected.

2. If the protection function is not configured, all the services to be forwarded through the LSP will be interrupted.

The interface went Down.
LDP LSPs went Down.
Static LSPs went Down.
In the case that the LDP LSP or BGP LSP was set Up, routes changed; or, in the case that the static LSP was bound to the tunnel, the next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.
The link was faulty.

If the snmp-agent trap enable feature-name mpls_lspm trap-name is run and the trap functions indicating the status of LSPs are enabled in the LSPM, you can check the traps to obtain the types of the LSPs that go Down. If no trap functions indicating the status of LSPs are enabled in the LSPM, you can check the values of the BeginLspIndex and EndLspIndex fields in the traps to obtain the types of the LSPs that go Down. (Run the display mpls entry summary command in the diagnostic view to view the index ranges of LSPs of different protocols of the MPLS module.)
- If static LSPs went Down, refer to the solution described in LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLspDown. Then, go to Step 3.
- If the fault persists, go to Step 2.
Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
End.