MPLS_LSPM/4/FRRSWITCH

Message

MPLS_LSPM/4/FRRSWITCH: Tunnel frr switches. (TunnelId=[TunnelId], LocalLspId=[LocalLspId], IngressLsrId=[IngressLsrId], EgressLsrId=[EgressLsrId], TunnelAdminStatus=[TunnelAdminStatus], TunnelOperStatus=[TunnelOperStatus], BypassSessionTunnelId=[BypassTunnelId], BypassLocalLspId=[BypassLocalLspId], BypassIngressLsrId=[BypassIngressLsrId], BypassEgressLsrId=[BypassEgressLsrId], TunnelType=[TunnelType], ProtectedIfName=[ProtectedIfName], BypassTunnelPath=[BypassTunnelPath], SubGroupId=[SubGroupId], SubGroupOrignatorId=[SubGroupOrignatorId], FrrMethod=[FrrMethod])

Description

Traffic switched to the bypass tunnel after the primary tunnel failed.

Parameters

Parameter Name	Parameter Meaning
TunnelId	Primary tunnel ID
LocalLspId	LSP ID of the primary tunnel
IngressLsrId	Ingress LSR ID of the primary tunnel
EgressLsrId	Egress LSR ID of the primary tunnel
TunnelAdminStatus	Administrative status of the primary tunnel
TunnelOperStatus	Operational status of the primary tunnel
BypassTunnelId	Bypass Tunnel Id.
BypassLocalLspId	Bypass Local Lsp Id.
BypassIngressLsrId	Bypass Ingress Lsr Id.
BypassEgressLsrId	Bypass Egress Lsr Id.
TunnelType	Primary tunnel type.
ProtectedIfName	Protected Interface Name.
BypassTunnelPath	Bypass Tunnel Path.
SubGroupId	Sub-Group ID.
SubGroupOrignatorId	Sub-Group Originator ID.
FrrMethod	FRR mode (facility,one-to-one).

Possible Causes

The tunnel interface or link of the primary tunnel that a bypass tunnel protects goes Down.

Procedure

1. Check whether the configurations for the current tunnel interface, RSVP, an IGP, link connectivity, and bandwidth for links along the tunnel are correct.

If an explicit path is configured, check whether the interfaces along the explicit path are faulty.
If an interface fails, go to Step 2.
If all interfaces work properly, go to Step 3.
If no explicit path is configured, check whether the path that satisfies the configuration condition exists. If the path exists, go to Step 3.

2. Rectify the link fault and check whether the log is displayed:

If the log is no longer displayed, go to Step 5.
If the log persists, go to Step 3.

3. Run the display mpls te tunnel-interface last-error command to check error information.

Check possible causes for error information before proceeding to the next step:
"Cspf failed to calculate a path for Tunnel": CSPF is enabled on the ingress but CSPF fails to calculate a path for the tunnel. Check whether configurations for explicit paths are correct, whether IS-IS TE or OSPF TE has been enabled, and whether routing configurations are correct. After correcting the configuration, check whether the log is displayed:
If the log is no longer displayed, go to Step 5.
If the log persists, go to Step 4.
"Receive Error-Node(192.168.1.2) at ENUM_TEM_LSPFSM_STATE_SETUPING state." or "Routing Problem:Bad initial subobject.": A node (192.168.1.2) on the tunnel is defective. Check that MPLS TE and RSVP-TE configurations are correct on this node. Then check whether the log is displayed.
If the log is no longer displayed, go to Step 5.
If the log persists, go to Step 4.
"Sig. reports connect timeout at ENUM_TEM_LSPFSM_STATE_SETUPING state.": RSVP-TE is not enabled on a downstream node or its inbound interface. Enable RSVP-TE and check whether the log is displayed.
If the log is no longer displayed, go to Step 5.
If the log persists, go to Step 4.
"Crlsp receive Sig. ResvTear at ENUM_TEM_LSPFSM_STATE_SETUPING state.": A link to a downstream node or a downstream node fails. Check and rectify the fault. Check whether the log is displayed.
If the log is no longer displayed, go to Step 5.
If the log persists, go to Step 4.
If other errors occur, go to Step 4.
If no error information is displayed, go to Step 4.

4. Collect the trap information, log information, and configuration of the router, and Collect log information and configuration information, and then contact technical support personnel..

5. End.