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 V200R005C00

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.150.6.2_hwL3vpnVrfV6Down

L3VPN_1.3.6.1.4.1.2011.5.25.150.6.2_hwL3vpnVrfV6Down

Description

The IPv6 status of all interfaces bound to a VPN instance went Down. (VPN instance name=[VpnInstanceName], interface name=[IfName])

The IPv6 status of all interfaces bound to a VPN instance went Down.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwL3vpnVrfV6Down

Trap OID

1.3.6.1.4.1.2011.5.25.150.6.1

Alarm ID

0x00F1004d

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

1.3.6.1.4.1.2011.5.25.150.6.1_hwL3vpnVrfV6Up

Parameters

Name Meaning

VpnInstanceName

Indicates the name of the VPN.

IfIndex

Indicates the index of the interface.

Parameters

Name Meaning

VpnInstanceName

Indicates the name of the VPN.

IfIndex

Indicates the index of the interface.

Impact on the System

No available interface is bound with the VPN instance.

Possible Causes

1. One interface was bound with the VPN instance, and the interface status changed from Up to Down.

2. Multiple interfaces were bound with the VPN instance; the status of all the interfaces changed from Up to Down; the last interface in the Up state went Down.

3. The last interface with Up state is disassociated from the VPN instance.

Procedure

  1. Run the display ip vpn-instance verbose vpn-instance-name command to check which interfaces are bound with the VPN instance.

    • If no interface is bound with the VPN instance, search the log file and find whether there is a log message containing the keywords "undo ip binding vpn-instance" and generated with the alarm.
      • If so, and the VPN instance should be unbound, the problem is resolved, go to step 6. If the VPN instance cannot be unbound, run the ip binding vpn-instance vpn-instance-name command in the interface view to bound the interface with the VPN instance, and then run ipv6 address ipv4-address command to configure IPv6 address for the interface.
      • If there is not the relative log, go to step 5.
    • If there are some interfaces bound with the VPN instance, go to Step 2.

  2. Run the display ip interface brief command to check whether there are one or more interfaces bound with the VPN instance and in Up state.

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

  3. Check whether the interfaces are configured with IPv6 addresses.

    • If so, go to Step 4.
    • If not, run ipv6 address ipv6-address comand to configure IP addresses for the interfaces if necessary. Then,

  4. Run the display this command in the interface view to check whether the interfaces are shutdown.

    • If so, run the undo shutdown command on the interfaces if necessary. Then,
    • If all the interfaces are not shut down, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 90550

Downloads: 21

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