No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Enterprise
Worldwide
Huawei Global - English
Search
Support Documentation
Alarm Handling
S1700, S2720, S5700, and S6700 V200R019C10

This document provides the explanations, causes, and recommended actions of alarms on the product.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
TUNNEL

TUNNEL

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1 hwMplsPsSwitchPtoW

Description

TUNNEL/4/TUNN_PS_PTOW: OID [OID] switched to work tunnel. (IfIndex=[INTEGER], WorkTunnel=[OCTET], WorkTunnelId=[INTEGER], ProtectionTunnel=[OCTET], ProtectionTunnelId=[INTEGER], SwitchResult=[INTEGER], WorkTunnelState=[INTEGER], ProtTunnelState=[INTEGER], LocalState=[INTEGER])

The protection group switched from the protection tunnel back to the work tunnel.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.12.7.1.4.1 Warning processingErrorAlarm(4)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index value of the work tunnel.

WorkTunnel

Indicates the name the work tunnel.

WorkTunnelId

Indicates the tunnel ID of the work tunnel.

ProtectionTunnel

Indicates the name of the protection tunnel.

ProtectionTunnelId

Indicates the tunnel ID of the protection tunnel.

SwitchResult

Indicates the result of the switchover. The value 1 indicates that the tunnel becomes the work tunnel.

WorkTunnelState

Indicates the status of the work tunnel.

ProtTunnelState

Indicates the status of the protection tunnel.

LocalState

Indicates the status of local node.

Impact on the System

Services will not be affected.

Possible Causes

The work tunnel returned to the normal state and the protection tunnel switched to the work tunnel.

Procedure

  1. Run the display mpls te protection tunnel all verbose command to check the work-tunnel name field to obtain the name of the work tunnel.
  2. Run the display interface tunnel interface-number command to check the status of the work tunnel.

    • If the status of the work tunnel is Up, it indicates that the trap message is informational only, and no action is required.
    • If the status of the work tunnel is Down, it indicates that faults occur on both the protection and work tunnels. Do as follows on both the protection and work tunnels:

  3. Run the display this interface command in the tunnel interface view to check whether the route destined for the destination exists.

    • If so, go to Step 4.
    • If not, configure the route destined for the destination. After that, if the fault disappears, go to Step 10; if the fault persists, go to Step 4.

  4. Run the display this command in the tunnel interface view to check whether the destination address of the tunnel, tunnel type, and tunnel ID are correctly configured, and whether the mpls te commit command is configured.

    • If so, go to Step 5.
    • If not, modify the configurations. After that, if the fault disappears, go to Step 10; if the fault persists, go to Step 5.

  5. Run the display this command in the tunnel view to check whether the mpls te path explicit-path path-name command is configured, that is, whether the explicit path is configured.

    • If so, go to Step 6.
    • If not or only parts of the explicit path are configured, go to Step 9.

  6. Run the display explicit-path path-name command to check the IP address of each hop on the explicit path.
  7. Run the display ip interface interface-type interface-number command to check whether the interface at each hop is Up.

    • If all interfaces are Up, go to Step 8.
    • If an interface is Down, check whether the interface is configured with the shutdown command. If so, run the undo shutdown command. After that, if the fault disappears, go to Step 10; if the fault persists, go to Step 8.

  8. Run the display this command on each interface on the tunnel to check whether MPLS, MPLS TE, and RSVP-TE are enabled.

    • If so, go to Step 9.
    • If a function is disabled, enable it. After that, if the fault disappears, go to Step 10; if the fault persists, go to Step 9.

  9. Collect alarm information and configuration information, and then contact technical support personnel.
  10. End.

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2 hwMplsPsSwitchWtoP

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.2 hwMplsPsSwitchWtoP

Description

TUNNEL/4/TUNN_PS_WTOP: OID [OID] switched to protection tunnel. (IfIndex=[INTEGER], WorkTunnel=[OCTET], WorkTunnelId=[INTEGER], ProtectionTunnel=[octet], ProtectionTunnelId=[INTEGER], SwitchResult=[INTEGER], WorkTunnelState=[INTEGER], ProtTunnelState=[INTEGER], LocalState=[INTEGER])

The protection group switched from the work tunnel to the protection tunnel.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.12.7.1.4.2 Warning processingErrorAlarm(4)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

IfIndex

Index of the working tunnel

WorkTunnel

Name of the working tunnel.

WorkTunnelId

Tunnel ID of the working tunnel

ProtectionTunnel

Name of the protection tunnel.

ProtectionTunnelId

Tunnel ID of the protection tunnel.

SwitchResult

Result of the switchover. The value 2 indicates that the work tunnel switches to the protection tunnel.

WorkTunnelState

Status of the work tunnel.

ProtTunnelState

Status of the protection tunnel.

LocalState

Status of local node.

Impact on the System

When the primary tunnel is faulty, traffic is switched from the primary tunnel to the backup tunnel.

Possible Causes

1. The interface along the TE tunnel was shut down.

2. Interfaces along the TE tunnel were not enabled with MPLS, MPLS TE, or RSVP-TE.

3. The tunnel configurations such as destination address, type, or TE tunnel ID were incorrect or were not committed.

4. The explicit path was not the expected one.

5. A fault was detected by an OAM session or a BFD session.

6. The TE tunnel interface failed to forward packets.

Procedure

  1. For an RSVP-TE tunnel, run the display mpls te tunnel path command to view information about interfaces along a tunnel. For a static tunnel, run the display current-configuration command to view information about interfaces along the static LSP.
  2. Run the display this command in the view of an interface along the TE tunnel to check whether the interface goes Up and whether MPLS, MPLS TE, and RSVP-TE are enabled.

    • If the interface goes Down, run the undo shutdown command.
    • If MPLS, MPLS TE, and RSVP-TE are disabled, run the mpls, mpls te, and mpls rsvp-te commands in sequence.
    • If the fault is rectified, go to Step 9. If the fault persists, go to Step 3.

  3. Run the display this command in the tunnel interface view to check whether an explicit path is configured through the mpls te path explicit-path path-name command.

    • If so, go to Step 4.
    • If not, go to Step 5.

  4. Run the display explicit-path path-name command to view the address of each hop along the explicit path. Using the address of each hop along the explicit path, run the display ip interface interface-type interface-number command to check whether the interface along the primary tunnel is Up.

    • If all interfaces are Up, go to Step 6.
    • If an interface is Down, run the undo shutdown command.
    • If the fault is rectified, go to Step 9. If the fault persists, go to Step 6.

  5. 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 there is an incorrect configuration, run one of the following commands to correct the configuration:
      1. Run the tunnel-protocol mpls te command to configure a correct tunnel type.
      2. Run the destination dest-ip-address command to specify a correct destination address of the tunnel.
      3. Run the mpls te tunnel-id tunnel-id command to specify a correct tunnel ID.
    • If the configurations are not committed, run the mpls te commit command.
    • If the fault is rectified, go to Step 9. If the fault persists, go to Step 6.

  6. Run the ping lsp te tunnel interface-number command to check connectivity of the tunnel LSP.

    • If the LSP is reachable, go to Step 8.
    • If the LSP is unreachable, go to Step 7.

  7. Run the display bfd session all command to view BFD detection results.

    • If a BFD session is Down, refer to the troubleshooting manuals for BFD.
    • If BFD sessions are Up, go to Step 8.

  8. Collect alarm information and configuration information, and then contact technical support personnel.
  9. End.

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.1 hwMplsPsSwitchPtoW

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

  1. 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.
  2. 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.

  3. 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.

  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.

  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.

  6. Run the display explicit-path path-name command to view the address of each hop along the explicit path.
  7. 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.

  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.

  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.

  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.

  11. Collect alarm information and configuration information, and then contact technical support personnel.
  12. End.

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.8 hwMplsApsOutageRecovery

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.8 hwMplsApsOutageRecovery

Description

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

The tunnel protection group recovered from a fault.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.12.7.1.4.8 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

None

Possible Causes

The tunnel protection group recovered from a fault.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.7 hwMplsApsOutage

Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 75917

Downloads: 321

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :