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

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

L3VPN_1. mplsL3VpnVrfDown


The interface bound to the VPN instance went Down. (VpnInstanceName=[VpnInstanceName], IfName=[IfName], IfCurRowStatus=[IfCurRowStatus], VRFOperationStatus=[VRFOperationStatus])

Of the interfaces that are bound to VPN instance, the last interface in the Up state goes Down.




Alarm or Event


Trap Severity


Mnemonic Code


Trap OID

Alarm ID


Alarm Type


Raise or Clear


Match trap

L3VPN_1. mplsL3VpnVrfUp


Name Meaning


Indicates the name of the VPN.


Indicates the name of the interface.


Indicates the row status of the interface. Including:

  • 1: Active

  • 2: Not in Service

  • 3: Not Ready

  • 4: Create and Go

  • 5: Create and Wait

  • 6: Destroy


Indicates the status of the VRF. Including:

  • 1: Up

  • 2: Down



VB Name

VB Index






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.


  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 ip adress ipv4-address command to configure IP 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 IP addresses.

    • If so, go to Step 4.
    • If not, run ip adress ipv4-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 shut down.

    • 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 the trap information, log information, and configuration information, and contact technical personnel.
  6. End.
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 128455

Downloads: 27

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next