TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.7 hwMplsApsOutage

Description

TUNNEL/2/MPLS_APS_OUTAGE: OID [oid] Tunnel protection group changed to defect state.(IfIndex=[INTEGER], SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], WorkTunnel=[OCTET], SignalingProtocol=[integer])

A tunnel protection group went faulty.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.12.7.1.4.7	Major	qualityOfServiceAlarm(3)

Parameters

Name	Meaning
OID	Indicates the MIB object ID of the alarm.
IfIndex	Index of the working tunnel in a tunnel protection group
SessionTunnelId	Tunnel ID of a session
LocalLspId	LSP ID of a tunnel session
IngressLsrId	LSR ID of the ingress of a tunnel
EgressLsrId	LSR ID of the egress of a tunnel
WorkTunnel	Name of the working tunnel in a tunnel protection group
SignalingProtocol	Signaling protocol used by a tunnel session

Impact on the System

The tunnel protection group goes Down, and services on the tunnel protection group are interrupted.

Possible Causes

The working tunnel and the protection tunnel in the tunnel protection group were both Down.

Procedure

Run the display mpls te protection tunnel all verbose command to check the Work-tunnel name field to obtain the name of the working tunnel.
Run the display interface tunnel interface-number command to check the working tunnel status.
- If the working tunnel status is Up, go to Step 9.
- If the working tunnel status is Down, both the working tunnel and the protection tunnel are faulty. Perform the following steps on the working tunnel and the protection tunnel simultaneously.
Run the display this interface command in the tunnel interface view to check whether the route destined for the destination address exists.
- If the route exists, go to Step 4.
- If no route is destined for the destination address, configure the correct route. After the configuration is complete, perform the either of following steps as needed:
  - If the fault is rectified, go to Step 12.
  - If the fault persists, go to Step 4.
Run the display this command in the tunnel interface view to check whether the destination address, tunnel type, and TE tunnel ID are correct and whether the mpls te commit command is run.
- If the configuration of the tunnel interface is correct, go to Step 5.
- If the configuration of the tunnel interface is incorrect, modify the configuration. After the modification is complete, perform either of the following steps as needed:
  - If the fault is rectified, go to Step 12.
  - If the fault persists, go to Step 5.
Run the display this command in the tunnel interface view to check whether an explicit path is configured using the mpls te path explicit-path path-name command.
- If the explicit path is configured, go to Step 6.
- If no explicit path is configured or only part of the explicit path is configured, go to Step 9.
Run the display explicit-path path-name command to view the address of each hop along the explicit path.
Run the display ip interface interface-type interface-number command to check whether the interfaces along the working tunnel are Up based on the address of each hop along the explicit path.
- If all interfaces are Up, go to Step 8.
- If an interface is Down, check whether the link is connected properly or whether the undo shutdown command is configured on the interface. After the check is complete, perform the either of following steps as needed:
  - If the fault is rectified, go to Step 12.
  - If the fault persists, go to Step 8.
Run the display this command in the interface view along the tunnel to check whether MPLS, MPLS TE, and RSVP-TE are enabled on the interfaces.
- If all the three functions are enabled, go to Step 9.
- If one of the functions is disabled, enable the function on the interfaces. After the configuration is complete, perform the either of following steps as needed:
  - If the fault is rectified, go to Step 12.
  - If the fault persists, go to Step 9.
Run the ping lsp te tunnel interface-number command to check the connectivity of the LSP.
- If the link over the LSP is connected, go to Step 11.
- If the link over the LSP is disconnected, go to Step 10.
Check whether the physical link over which the tunnel protection group is configured goes Down.
- If the link is faulty, rectify the fault. Check whether the alarm is cleared:
  - If the alarm is cleared, go to Step 12.
  - If the alarm is not cleared, go to Step 11.
- If the link is working properly, go to Step 11.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.8 hwMplsApsOutageRecovery