LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch

Description

LSPM/3/MPLSTEFRRSWITCH:OID [oid] Tunnel switches.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer], BypassSessionTunnelId=[integer], BypassLocalLspId=[integer], BypassIngressLsrId=[integer], BypassEgressLsrId=[integer])

The trap message was output when the primary tunnel was Down and the traffic was switched to the bypass tunnel.

Attribute

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

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
SessionTunnelId	ID of the tunnel
LocalLspId	Local LSP ID of a tunnel.
IngressLsrId	LSR ID of the ingress on the tunnel.
EgressLsrId	LSR ID of the egress on the tunnel
MplsTunnelAdminStatus	Management status of the tunnel: 1: Up 2: Down
MplsTunnelOperStatus	Operating status of the tunnel: 1: Up 2: Down
BypassSessionTunnelId	ID of the bypass session tunnel.
BypassLocalLspId	Local LSP ID of a bypass tunnel.
BypassIngressLsrId	LSR ID of the ingress on the bypass tunnel.
BypassEgressLsrId	LSR ID of the egress on the bypass tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The node or the link protected by the bypass tunnel was Down.

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 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 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 whether a path that meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.
- If the path is successfully calculated, run the display current-configuration interface interface-type interface-number command on the ingress to check the tunnel configurations, including the primary tunnel, protection tunnel, and the protection interface. Check whether the mpls te auto-frr command is configured in the MPLS view. If so, it indicates that Auto FRR is enabled. In this case, you can check the primary tunnel. If not, check whether the mpls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured to identify the primary and backup tunnels.
  
  After the primary and backup tunnels are checked, you can check the explicit-path command to verify whether the explicit path is configured; check the mpls te affinity property command to verify whether the affinity property is configured.
  Run the display mpls te cspf destination command and configure the parameters of constraints one by one, including the priority (priority setup-priority), bandwidth (bandwidth), explicit path (explicit-path path-name), affinity property (affinity properties), and hop limit (hop-limit hop-limit-number), and you can check whether the path that meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.
  1. If the explicit path fails to be calculated, check whether the interfaces along the explicit path are in the Up state and are enabled with MPLS and MPLS TE. If the explicit path is successfully calculated, check whether the path calculation according to the affinity property and bandwidth is consistent with the explicit path by running the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
  2. If CSPF path calculation fails after affinity property is configured, run the mpls te affinity property command in the tunnel view to modify the affinity property of the tunnel, or run the mpls te link administrative group on the interfaces along the tunnel to modify the administrative group property of the link.
  3. If CSPF path calculation fails because of other constraints, go to Step 6.
  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 5.
- If CSPF path calculation 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.
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.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume