LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown

Description

LSPM/3/MPLSTUNOBKDOWN:OID [oid] The ordinary LSP of the tunnel changes to Down. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The ordinary LSP of the tunnel changes to Down.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.51	Minor	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
SessionTunnelId	ID of the tunnel
TunnelInstIndex	InstIndex of the tunnel
IngressLsrId	LSR ID of the ingress on the tunnel
EgressLsrId	LSR ID of the egress on the tunnel
mplsTunnelIfName	Name of a tunnel
hwMplsTunnelDownReason	Reason why a tunnel goes Down
hwMplsTunnelDownLSRId	LSR ID of the error node on a tunnel
hwMplsTunnelDownIfAddrType	IP address type of the error interface on a tunnel
hwMplsTunnelDownIfAddr	IP address of the error interface on a tunnel

Impact on the System

If traffic is not forwarded along the backup LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the backup LSP of the tunnel and another backup LSP is configured, traffic will be switched to the other backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: The interface went Up.

Cause 2: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.

Cause 4: An LSP with higher priority became Up.

Procedure

Run the display mpls te tunnel-interface tunnel-name command on the ingress (where the alarm is generated) to check the tunnel status. The PrimaryLSP State field indicates whether the primary LSP of the tunnel is in the Up state and the Hot-Standby LSP State field indicates whether the Hot-standby LSP is in the Up state.
- If the primary LSPs or hot-standby LSPs are in the Up state, the backup LSP cannot go Up. To address such a problem, go to Step 8.
- If both the primary and hot-standby LSPs are in the Down state, go to Step 2.
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 3.
  - If the error prompt is "Trigger Rsvp failed", go to Step 3.
  - If the error prompt is "One LSP is deleted at smooth period", go to Step 7.
  - If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 7.
  - For other types of errors, go to Step 7.
- If there is no error prompt, go to Step 3.
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.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp is generated.
  - If so, go to Step 8.
  - If not, go to Step 4.
- If the ping is successful, go to Step 4.
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 5.
- If not, go to Step 6.
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 7.
  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 8.
  - If this alarm is not generated, go to Step 6.
- If path computation fails, go to Step 6.
Run the display explicit-path command or identify interfaces that an LSP passes through based on the network topology 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.
Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp is generated.
- If so, go to Step 8.
- If not, go to Step 7.
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.50 hwMplsTunnelOrdinaryUp