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

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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_1.3.6.1.4.1.2011.5.12.7.1.4.9 hwMplsApsDegraded

TUNNEL_1.3.6.1.4.1.2011.5.12.7.1.4.9 hwMplsApsDegraded

Description

TUNNEL/2/MPLS_APS_DEGRADED: OID [oid] Tunnel protection group receives an APS degraded alarm.(IfIndex=[INTEGER], SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], WorkTunnel=[OCTET], SignalingProtocol=[integer])

A tunnel in an APS protection group failed, which decreased the usability of the APS protection group.

Attribute

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

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

IfIndex

Index of the working tunnel

SessionTunnelId

Tunnel ID

LocalLspId

LSP ID

IngressLsrId

LSR ID of the ingress

EgressLsrId

LSR ID of the egress

WorkTunnel

Name of the working tunnel in a protection group

SignalingProtocol

Signaling protocol used by a tunnel

Impact on the System

The usability of the APS protection group decreased, which adversely affects the protection group.

Possible Causes

A tunnel in an APS protection group failed.

Procedure

  1. Run the display mpls te protection tunnel interfaceallverbose command to view the tunnel name. Check whether a tunnel fails.

    • If a tunnel fails, go to Step 2.
    • If no tunnel fails, go to Step 8.

  2. Check whether a fault trap is sent to an NMS.

    • If a trap is sent to the NMS, following the procedure for handling the alarm. A tunnel fault triggers an hwMplsExtTunnelDown, hwMplsOamRdi, hwMplsOamSF, or hwMplsOamBDI trap.
    • If no trap is sent to the NMS, go to Step 3.

  3. Run the display mpls te tunnel-interface tunnelinterface-number command to view the tunnel status.

    • If the status of all tunnels is Up, go to Step 8.
    • If a tunnel is Down, go to Step 4.

  4. Run the display this command in the tunnel interface view and 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 the configuration of the tunnel interface is correct, go to Step 5.
    • If the tunnel interface is incorrectly configured, correct the configuration. 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 and check whether the mpls te path explicit-path path-name command is run to configure an explicit path.

    • If an explicit path is configured, go to Step 6.
    • If no explicit path is configured or explicit paths are configured for some tunnels, go to Step 9.

  6. Run the display explicit-path path-name command to view the IP address of each hop on an explicit path.
  7. Obtain the IP addresses and run the display ip interface interface-type interface-number command. Check whether the interface status at each hop on the tunnel is Up.

    • If all interfaces are Up, go to Step 8.
    • If an interface is Down, check whether the undo shutdown command is run on a physical or logical interface. If the fault is rectified, go to Step 12. If the fault persists, go to Step 8.

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

    • If all functions are enabled, go to Step 9.
    • If a function is disabled, enable it. 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 a tunnel.

    • If the ping is successful, go to Step 10.
    • If the ping fails, go to Step 11.

  10. Check whether the physical link over which the primary or backup tunnel is established is faulty.

    • If a fault occurs, rectify it and check whether the trap is cleared.

    • If no fault occurs, go to Step 11.

  11. Collect alarm information and configuration information, and then contact technical support personnel.
  12. End.
Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 130418

Downloads: 40

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next