LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown

Description

LSPM/2/MPLSTUNNELDOWN:OID [oid] Tunnel Changes to Down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet], OutIfName=[octet], mplsTunnelDownReason=[integer])

A trap was generated when the current tunnel became faulty and went Down.

Attribute

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

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
SessionTunnelId	ID of the tunnel
LocalLspId	LSP ID of a session.
IngressLsrId	LSR ID of the ingress on the tunnel
EgressLsrId	LSR ID of the egress on the tunnel
OutIfIndex	Outbound interface index of the ingress of the LSP that goes Down.
mplsTunnelAdminStatus	Management status of the tunnel: 1: Up 2: Down
mplsTunnelOperStatus	Operating status of the tunnel: 1: Up 2: Down
mplsTunnelIfName	Name of a tunnel
OutIfName	Name of the outgoing interface on the ingress of the LSP that goes Down.
mplsTunnelDownReason	Reason of Tunnel down. 1: other 2: staticLspDown 3: staticCrlspDown 4: outIfDown 5: resourcePreempted 6: rsvpMessageTimeout 7: rsvpNbrLost 8: bypassTunnelDownOrUnbinded 100: clear

Impact on the System

The service traffic to be forwarded through the tunnel will be interrupted.

Possible Causes

1. The interface was Down.

2. 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.

3. The link was faulty.

Procedure

Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.
- In the case of the following error prompts, do as required:
  - If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
  - If the error prompt is "Trigger Rsvp failed", go to Step 2.
  - If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
  - If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
  - For other types of errors, go to Step 6.
- If there is no error prompt, go to Step 2.
Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.
- If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarmLSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
  - If so, go to Step 7.
  - If not, go to Step 3.
- If the ping is successful, go to Step 3.
Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.
- If so, go to Step 4.
- If not, go to Step 5.
Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
- If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
  - Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
  - Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
  - Check whether the explicit-path command is run to configure an explicit path.
  - Check whether the mpls te affinity property command is run to configure affinities.
  - Check whether the mpls te bandwidth command is run to configure bandwidth values.
  Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
  1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
  2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
  3. If the other constraints fail to be used to compute a path, go to Step 6.
  Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
  - If this alarm is generated, go to Step 7.
  - If this alarm is not generated, go to Step 5.
- If path computation fails, go to Step 5.
Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.
- If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
- If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view, or run the restart command in the interface view.
Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
- If so, go to Step 7.
- If not, go to Step 6.
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.2.1.10.166.3.0.1 mplsTunnelUp