LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLSPDown

Description

LSPM/2/STATICCRLSPDOWN: OID [oid] Static CR-LSP went Down. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static CR-LSP was in the Down state.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.4	Major	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
LspIndex	Index of the LSP.
InSegmentIndex	InSegment index of a static CR-LSP.
OutSegmentIndex	OutSegment index of a static CR-LSP.
OutIfIndex	Outbound interface index of a static CR-LSP.
LspName	Name of a static CR-LSP.
LspStatus	Status of a static CR-LSP.
OutIfName	Outbound interface name of a static CR-LSP.
InIfIndex	Inbound interface index of a static CR-LSP.
InIfName	Inbound interface name a static CR-LSP.
DownReason	Reason that the static CR-LSP down.

Impact on the System

If there is some service using the tunnel, the service is interrupted. If a backup path is used to protect the tunnel, the flow of the service is changed to the backup path. If there is not any service using the tunnel, there is no impact.

Possible Causes

1. The interface was Down.

2. The link was damaged.

Procedure

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 output is correct, 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.
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 mpls te commit command to commit the modification.
- If neither preceding operations can locate the fault, go to Step 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 the available bandwidth of the outgoing interface is smaller than the bandwidth required by the static CR-LSP, you need to increase the bandwidth of the outgoing interface.
- After modifying the configuration of the tunnel, run the mpls te commit command to commit the modification.
- If neither preceding operations can locate the fault, go to Step 4.
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.
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.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLspUp