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

L3VPN_1. mplsL3VpnVrfUp


L3VPN/2/L3V_TRAP_VRF_UP:OID [oid] The interface bound to the VPN instance went Up. (VpnInstanceName=[octet], IfIndex=[integer], BindingVpnInstanceName=[octet], IfCurRowStatus=[integer], VRFOperationStatus=[integer], IfName=[octet])

One of the interfaces in the Down state that are bound to VPN instance goes Up.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the name of the VPN.


Indicates the index of the interface.


Indicates the name of the binding VPN .


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


Indicates the name of the interface.

Impact on the System

At least one available interface is bound with the VPN instance.

Possible Causes

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

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

3. Multiple interfaces were bound with the VPN instance, all the interfaces went Down, and then the first interface went Up.


  • This alarm message is informational only, and no action is required.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 103482

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next