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


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


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

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).
RM_1. hwTunnelGroupDown

RM_1. hwTunnelGroupDown


RM/2/TNLGROUP_DOWN:OID [oid] The status of the tunnel group changed to Down. (Destionation=[IPADDR], TunnelPolicy=[STRING])

The status of the tunnel group used by the service changed to Down.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


Destination IP address of the tunnel on which services depend.


Tunnel policy used by services.

Impact on the System

Services may be interrupted.

Possible Causes


A link fault occurred.


The configuration was changed, causing no available tunnel to the specified destination.


The VPN routes iterated to public network tunnels are deleted.


  1. After a tunnel group fails, the device sends an alarm with information about the destination address and tunnel policy to inform users of the tunnel group failure. You can run the display this command in the tunnel policy view to check whether tunnel-policy tunnel-policy-name is displayed.

    • If tunnel-policy tunnel-policy-name is displayed, run the display tunnel-policy tunnel-policy-name command to check the tunnel policy.
      • If Select-Seq is displayed, the sequence tunnel policy is used. Then, go to Step 2.
      • If Destination and Tunnel Intf are displayed, the binding tunnel policy is used. Then, go to Step 3.
    • If tunnel-policy tunnel-policy-name is not displayed, go to Step 4.

  2. Run the display tunnel-info all command to check whether there are tunnels of the type configured in the tunnel policy.

    • If there are tunnels of the type configured in the tunnel policy, go to Step 5.
    • If there is no tunnel of the type configured in the tunnel policy, change the tunnel policy used by VPN services.

  3. If a binding tunnel policy is used, run the display interface tunnel interface-number command to check whether the bound tunnel interface is Up.

    • If the bound tunnel interface is Up, go to Step 5.
    • If the bound tunnel interface is not Up, configure the TE interface.

  4. Check where there is an LSP.

    • If there is an LSP, go to Step 5.
    • If there is no LSP (LDP LSP, BGP LSP, or static LSP), check the LSP configuration.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 106794

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next