MPLS_LSPM/2/hwMplsTunnelHotstandbyDown_active

Message

MPLS_LSPM/2/hwMplsTunnelHotstandbyDown_active: The hot-standby LSP of the tunnel changes to Down. (SessionTunnelId=[SessionTunnelId], TunnelInstIndex=[TunnelInstIndex], IngressLsrId=[IngressLsrId], EgressLsrId=[EgressLsrId], mplsTunnelIfName=[mplsTunnelIfName], hwMplsTunnelDownReason=[hwMplsTunnelDownReason], hwMplsTunnelDownLSRId=[hwMplsTunnelDownLSRId], hwMplsTunnelDownIfAddrType=[hwMplsTunnelDownIfAddrType], hwMplsTunnelDownIfAddr=[hwMplsTunnelDownIfAddr], SignalledTunnelName=[SignalledTunnelName])

Description

The hot-standby LSP of the tunnel changes to Down.

Parameters

Parameter Name	Parameter Meaning
SessionTunnelId	Indicates the ID of the tunnel.
TunnelInstIndex	Indicates the InstIndex of the tunnel.
IngressLsrId	Indicates the LSR ID of the ingress on the tunnel.
EgressLsrId	Indicates the LSR ID of the egress on the tunnel.
mplsTunnelIfName	Indicates the name of a tunnel.
hwMplsTunnelDownReason	Indicates the reason why a tunnel goes Down.
hwMplsTunnelDownLSRId	Indicates the LSR ID of the error node on a tunnel.
hwMplsTunnelDownIfAddrType	Indicates the IP address type of the error interface on a tunnel.
hwMplsTunnelDownIfAddr	Indicates the IP address of the error interface on a tunnel.
SignalledTunnelName	Tunnel alias.

Possible Causes

Cause 1: The interface went Down.
Cause 2: The configuration of the tunnel was deleted.
Cause 3: The link was faulty.
Cause 4: The hot-standby LSP had nodes through which the primary LSP passed.
Cause 5: RSVP-TE LSP resources were preempted.
Cause 6: Transmission of an RSVP message timed out.
Cause 7: RSVP Hello mechanism detected a downstream node failure.
Cause 8: The bypass tunnel in use was Down or unbound from the primary tunnel.
Cause 9: CSPF failed to calculate a path.
Cause 10: The tunnel was manually shut down.

Procedure

Cause 1: The interface went Down.
1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (the node where the alarm is generated) to check the tunnel configuration. Check the Tunnel State Desc field to determine whether the tunnel is down. Run the display mpls te tunnel-interface last-error command to check the error message.
- If the following error information is displayed:
- If "Cspf failed to calculate a path for Tunnel." is displayed, CSPF has been enabled on the ingress, but CSPF path calculation fails. In this case, go to Step 2.
- If "Trigger RSVP failed." is displayed, go to Step 2.
- If "One LSP is deleted at smooth period." is displayed, go to Step 6.
- If "One LSP is deleted at Tunnel aging period" is displayed, go to Step 6.
- If other errors occur, go to Step 6.
- If no error message is displayed, go to Step 2.
2. Run the ping command on the egress to check whether the destination IP address of the tunnel can be pinged successfully.
- If the ping fails, rectify the route fault so that the ingress can ping the destination address of the tunnel. Then, check whether the MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp alarm is generated.
- If yes, go to Step 7.
- If no, go to Step 3.
- If the ping succeeds, go to step 3.
3. Run the display this command in the MPLS view on the ingress to check whether the mpls te cspf command is configured. That is, check whether CSPF is enabled.
- If yes, go to Step 4.
- If no, go to Step 5.
4. Run the display mpls te cspf destination command on the ingress to check whether a path satisfying the specified constraints exists. If such a path is available, the path information is displayed and CSPF path calculation succeeds. If such a path is unavailable, no path information is displayed and CSPF path calculation fails.
- If the path computation is successful, run the display current-configuration interface interface-type interface-number command on the ingress to check tunnel configurations. Determine the working tunnel, protection tunnel, and protection interface. Check whether the mpls te auto-frr command is run in the MPLS view. If the command is run, it indicates that automatic protection is configured. In this case, you can determine which tunnel is the primary tunnel according to the configuration of the tunnel. If the mpls te auto-frr command is not run, run the mpls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel commands to determine the primary and backup tunnels.
After determining the primary and backup tunnels, perform the following checks: Check whether the explicit-path command is run to determine whether an explicit path is configured for the tunnel. Check whether the mpls te affinity property command is run to determine whether the affinity attribute is configured for the tunnel. Check whether the mpls te bandwidth command is run to determine whether the bandwidth is configured for the tunnel.

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 a path that satisfies the constraints exists. If such a path is available, the path information is displayed and CSPF path calculation succeeds. If such a path is unavailable, no path information is displayed and CSPF path calculation fails.
- a. If explicit path calculation fails, check the explicit path and tunnel interface configurations to determine the primary and backup paths. Check whether each interface along the explicit path is up and whether MPLS and MPLS TE are enabled. If explicit path calculation succeeds, check whether the affinity attribute and bandwidth are successfully calculated and whether they are the same as those of the explicit path. You can run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
- b. 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.
- c. If bandwidth-based path computation fails, run the display mpls te link-administration bandwidth-allocation interface interface-type interface-number command to check whether the bandwidth of the outbound interfaces along the tunnel is sufficient. If the bandwidth resources are sufficient, a higher-priority tunnel may preempt bandwidth resources of an existing tunnel. Run the mpls te bandwidth max-reservable-bandwidth and mpls te bandwidth commands to increase bandwidth values.
- d. If path calculation based on other constraints fails, go to Step 6.
Then, check whether the MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp alarm is generated.
- If yes, go to Step 7.
- If no, go to Step 5.
- If path calculation fails, go to Step 5.
5. Run the display explicit-path command to check the interfaces along the tunnel and run the display this command in the interface view to check whether MPLS, MPLS TE, and RSVP-TE are enabled on the interfaces to the destination address.
- If not, run the mpls, mpls te, and mpls rsvp-te commands in the interface view.
- If the interface is not in the Up state, restart the interface. That is, run the shutdown command and then the undo shutdown command in the interface view, or run the restart command in the interface view.
Then, check whether the MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp alarm is generated.
- If yes, go to Step 7.
- If no, go to Step 6.
6. Collect alarm and configuration information, and contact technical support personnel.

7. End.
Cause 2: The configuration of the tunnel was deleted.
The same as Cause 1.
Cause 3: The link was faulty.
The same as Cause 1.
Cause 4: The hot-standby LSP had nodes through which the primary LSP passed.
The same as Cause 1.
Cause 5: RSVP-TE LSP resources were preempted.
The same as Cause 1.
Cause 6: Transmission of an RSVP message timed out.
The same as Cause 1.
Cause 7: RSVP Hello mechanism detected a downstream node failure.
The same as Cause 1.
Cause 8: The bypass tunnel in use was Down or unbound from the primary tunnel.
The same as Cause 1.
Cause 9: CSPF failed to calculate a path.
The same as Cause 1.
Cause 10: The tunnel was manually shut down.
The same as Cause 1.