MPLS_LSPM/2/hwMplsStaticLspDown_active

Message

MPLS_LSPM/2/hwMplsStaticLspDown_active: Static LSP went Down. (LspIndex=[LspIndex], InSegmentIndex=[InSegmentIndex], OutSegmentIndex=[OutSegmentIndex], OutIfIndex=[OutIfIndex], LspName=[LspName], LspStatus=[LspStatus], OutIfName=[OutIfName], InIfIndex=[InIfIndex], InIfName=[InIfName], ReasonIndex=[ReasonIndex], Reason=[Reason])

Description

Static LSP went Down.

Parameters

Parameter Name	Parameter Meaning
LspIndex	Indicates the index of the LSP.
InSegmentIndex	Indicates the inSegment index of a static LSP.
OutSegmentIndex	Indicates the outbound interface index of a static LSP.
OutIfIndex	Indicates the outbound interface index of a static LSP.
LspName	Indicates the name of a static LSP.
LspStatus	Indicates the status of a static LSP.
OutIfName	Indicates the outbound interface name of a static LSP.
InIfIndex	Indicates the inbound interface index of a static LSP.
InIfName	Indicates the inbound interface name a static LSP.
ReasonIndex	Indicates the reason that the static LSP down.
Reason	Alarm cause.

Possible Causes

Cause 1: Others
Cause 2: MPLS disabled on an interface
Cause 3: Route change
Cause 4: Inbound interface Down
Cause 5: Outbound interface Down
Cause 6: Static LSP configuration update

Procedure

Cause 1: Others
1. Run the display mpls interface command. If the trap is generated on the ingress of static LSPs, you need to check the information about only the outbound interface; if the trap is generated on the egress of static LSPs, you need to check the information about only the inbound interface; if the trap is generated on the transit of static LSPs, you need to check the information about the outbound interface and inbound interface. You need to check whether the corresponding interface is displayed in the command output, whether the Status field of the interface is Up.
- If the interface is not Up, check and correct the interface configuration. Then go to Step 2.
- If the interface information is not displayed, MPLS is disabled on the interface. Enable MPLS on the interface and go to Step 2.
2.Run the display ip routing-table ip-address command on the ingress to check whether a valid route to the next-hop IP address exists.
- If such a route exists, go to Step 3.
- If such a route does not exist, check and correct the route configuration to ensure the next-hop IP address is reachable. Then go to Step 4.
3.Run the display mpls lsp command on the ingress to check whether dynamic LSPs with the same prefix as the static LSP are configured.
- If such an LSP exists, block it and go to Step 4.
- If such an LSP does not exist, go to Step 5.
4.Check whether this trap message is cleared.
- If the trap message is cleared, go to Step 6.
- If the trap message persists, go to Step 5.
5.Collect alarm information and configuration information, and then contact technical support personnel.

6.End.
Cause 2: MPLS disabled on an interface
The same as Cause 1.
Cause 3: Route change
The same as Cause 1.
Cause 4: Inbound interface Down
The same as Cause 1.
Cause 5: Outbound interface Down
The same as Cause 1.
Cause 6: Static LSP configuration update
The same as Cause 1.