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

CloudEngine 12800 and 12800E V200R003C00

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

The tunnel up/down event is occurred. (VpnIndex=[VpnIndex], NextHop=[NextHop], Ckey=[Ckey], TrapType=[TrapType])

The tunnel used by a VPN went Up or Down.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Critical

Mnemonic Code

hwTnl2VpnTrapEvent

Trap OID

1.3.6.1.4.1.2011.5.25.177.8.1

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Name Meaning

VpnIndex

Indicates the index of the VPN instance.

NextHop

Indicates the next hop address of the public network.

Ckey

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

TrapType

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

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.6.1.1.1

hwVpnId

hwVpnId;

1.3.6.1.4.1.2011.5.25.177.6.1.1.2

hwVpnPublicNextHop

hwVpnId;

1.3.6.1.4.1.2011.5.25.177.6.1.1.4

hwVpnTrapCkeyValue

hwVpnId;

1.3.6.1.4.1.2011.5.25.177.6.1.1.3

hwTunnelReachablityEvent

hwVpnId;

Impact on the System

If the tunnel used by a VPN goes Down or the VPN can no longer be iterated to a tunnel, the VPN service will be 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 verbose vpn-instance-name command to check if the Tunnel Policy field exists.

    • If the field exists, go to Step 2.
    • If the field does not exist, go to Step 7.

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

    • If a tunnel policy in select-sequence mode is used, run the display tunnel all command to check if there are eligible tunnels.
      NOTE:
      If the mpls te reserved-for-binding command is used to specify a tunnel for VPN binding, this tunnel cannot be used in select-sequence mode.
      • If there are eligible tunnels, go to Step 8.
      • If there are not eligible tunnels, go to Step 3.
    • If a tunnel policy in tunnel binding mode is used, run the display interface tunnel command to check if the bound tunnel interface is up.
      • If the bound tunnel interface is up, go to Step 4.
      • If the bound tunnel interface is down, go to Step 6.

  3. Based on the networking, configure a needed LSP or CR-LSP, or change the VPN tunnel policy. Then, check if the system will still generate the message "L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent: The tunnel up event is occurred".

    • If the system will generate the message, go to Step 9.
    • If the system will not generate the message, go to Step 8.

  4. Enter the tunnel interface view, and run the display this command to check if the mpls te reserved-for-binding command has been configured on the tunnel interface.

    • If it has been configured, go to Step 8.
    • If it has not been configured, go to Step 5.

  5. Enter the tunnel interface view, and run the mpls te reserved-for-binding command. Then, check if the system will generate the message "L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent: The tunnel up event is occurred".

    • If the system will generate the message, go to Step 9.
    • If the system will not generate the message, go to Step 8.

  6. Check the configurations on the TE tunnel interface, and rectify faults based on the TE-related alarms. Then, check if the system will generate the message "L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent: The tunnel up event is occurred".

    • If the system will generate the message, go to Step 9.
    • If the system will not generate the message, go to Step 8.

  7. Check LDP LSP configurations , and rectify faults based on the LSP-related alarms. Then, check if the system will generate the message "L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent: The tunnel up event is occurred".

    • If the system will generate the message, go to Step 9.
    • If the system will not generate the message, go to Step 8.

  8. Contact technical support personnel.
  9. End.
Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004139

Views: 172701

Downloads: 26

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next