MPLS_LSPM/2/hwMplsStaticCRLspDown_active

Message

MPLS_LSPM/2/hwMplsStaticCRLspDown_active: Static CR-LSP went Down. (LspIndex=[LspIndex], InSegmentIndex=[InSegmentIndex], OutSegmentIndex=[OutSegmentIndex], OutIfIndex=[OutIfIndex], LspName=[LspName], LspStatus=[LspStatus], OutIfName=[OutIfName], InIfIndex=[InIfIndex], InIfName=[InIfName], DownReason=[DownReason])

Description

The trap message was sent when the bandwidth of the tunnel changed.

Parameters

Parameter Name	Parameter Meaning
LspIndex	Indicates the index of the LSP.
InSegmentIndex	Indicates the inSegment index of a static CR-LSP.
OutSegmentIndex	Indicates the outSegment index of a static CR-LSP.
OutIfIndex	Indicates the outbound interface index of a static CR-LSP.
LspName	Indicates the name of a static CR-LSP.
LspStatus	Indicates the status of a static CR-LSP.
OutIfName	Indicates the outbound interface name of a static CR-LSP.
InIfIndex	Indicates the inbound interface index of a static CR-LSP.
InIfName	Indicates the inbound interface name a static CR-LSP.
DownReason	Indicates the reason that the static CR-LSP down.

Possible Causes

Cause 1: Others
Cause 3: MPLS disabled on an interface
Cause 4: MPLS TE disabled on an interface
Cause 5: Route change
Cause 6: Tunnel binding associated with the CR-LSP deleted
Cause 8: Inbound interface Down
Cause 9: Outbound interface Down
Cause 10: Tunnel associated with the static CR-LSP has been shut down
Cause 11: Static CR-LSP configuration update
Cause 12: The bound ring is invalid

Procedure

Cause 1: Others
1. Run the display mpls interface command. If the trap is generated on the ingress of static CR-LSPs, you need to check the information about only the outbound interface; if the trap is generated on the egress of static CR-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, and whether the TE Attr field is En.
- If the interface status is not Up, check the interface.
- If the MPLS or MPLS TE is not enabled, configure this function.
- If the trap is generated on the ingress, egress, or a transit node, go to Step 2.
Then check whether the trap is cleared.
- If the trap is cleared, go to Step 5.
- If the trap is not cleared, go to Step 2.
2. Run the display current-configuration interface tunnel interface-number command on the ingress to check whether the corresponding tunnel is correctly configured.
- If the tunnel is not consistent with the destination address of the static CR-LSP, you need to enter the corresponding tunnel view and run the destination command to modify the destination address of the tunnel.
- If the signaling mode is not cr-static, run the mpls te signal-protocol cr-static command to modify the signaling mode of the tunnel.
- After modifying the configuration of the tunnel, run the commit command to commit the modification.
- If neither preceding operations can locate the fault, go to Step 3.
3. If the static CR-LSP is configured with the bandwidth attribute, run the display current-configuration interface interface-number command to check the maximal bandwidth and the maximal reservable bandwidth on the outbound interface.
- If neither preceding operations can locate the fault, go to Step 4.
- If the available bandwidth of the outgoing interface is smaller than the bandwidth required by the static CR-LSP, you need to enter the corresponding interface view and run the mpls te bandwidth max-reservable-bandwidth command to increase the bandwidth of the outgoing interface.
- After modifying the configuration of the tunnel, run the commit command to commit the modification.
Then check whether the trap is cleared.
- If the trap is cleared, go to Step 5.
- If the trap is not cleared, go to Step 4.
4. Collect alarm information and configuration information, and then contact technical support personnel.

5. End.
Cause 3: MPLS disabled on an interface
The same as Cause 1.
Cause 4: MPLS TE disabled on an interface
The same as Cause 1.
Cause 5: Route change
The same as Cause 1.
Cause 6: Tunnel binding associated with the CR-LSP deleted
The same as Cause 1.
Cause 8: Inbound interface Down
The same as Cause 1.
Cause 9: Outbound interface Down
The same as Cause 1.
Cause 10: Tunnel associated with the static CR-LSP has been shut down
The same as Cause 1.
Cause 11: Static CR-LSP configuration update
The same as Cause 1.
Cause 12: The bound ring is invalid
The same as Cause 1.