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, 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).
L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent

L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent

Description

L3VPN/4/L3V_TRAP_TUNNEL_UPDOWN_EVENT:OID [oid] The tunnel up/down event is occurred. (VpnIndex=[gauge], NextHop=[ipaddr], Ckey=[gauge], TrapType=[gauge])

The status of the tunnel used by a VPN changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.177.8.1

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnIndex

Indicates the index of the VPN instance.

NextHop

Indicates the next hop address of the public network.

TrapType

Indicates the trap type:
  • 1: indicates that a tunnel goes Up.
  • 2: indicates that a tunnel goes Down.

Ckey

Indicates the Ckey value, which is used to obtain information about the current iterated tunnel.

Impact on the System

The VPN services of the VPN instance with the specified index will be restored or interrupted.

Possible Causes

1. The status of the tunnel currently used by VPN services changed from reachable to unreachable or from unreachable to reachable.

2. During the tunnel switchover for VPN services, the result of tunnel iteration changed from success (a tunnel is iterated) to failure (a tunnel fails to be iterated); or the opposite.

Procedure

  1. Run the display ip vpn-instance vpn-instance-name verbose command in the VPN instance view to check whether the tnl-policy field exists.

    • If so, go to Step 2.
    • If not, go to Step 3.

  2. Run the display tunnel-policy tunnel-policy-name command to check the contents of the tunnel policy.

    • If the tunnel policy is the select-sequence policy, run the display tunnel-info all command to check whether there is a tunnel of the type configured in the tunnel policy.
      • If so, go to Step 4.
      • If not, change the tunnel policy used by VPN services.
    • If the tunnel policy is the tunnel binding policy, run the display interface tunnel command to check whether the bound tunnel interface in the tunnel policy is Up.
      • If so, go to Step 4.
      • If not, check the configuration on the TE interface.

  3. Run the display tunnel-info all command to check whether an LSP tunnel exists.

    • If so, go to Step 4.
    • If not, check the configuration of the LSP tunnel (LDP LSP, BGP LSP, or static LSP).

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

Document ID: EDOC1100041475

Views: 75039

Downloads: 47

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