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

L2V_1. hwCCCVcUp


L2V/3/CCCVC_UP_T:OID [oid] The status of the CCC VC turned UP. (CccName=[STRING], InterfaceIndex=[INTEGER], InterfaceIndex=[INTEGER], HWL2VpnStateChangeReason=[INTEGER], InterfaceName=[STRING])

The trap was generated when the CCC VC was Up.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the name of the CCC connection.


Index of the interface used as the table index.


Index of the interface reported to the network management system as a parameter.


Indicates the cause of the VC status change. For details, refer to hwCCCVcStateChangeReason in the appendix of HUAWEI-CCC-MIB.


Indicates the interface name.

Impact on the System

The CCC service will be recovered.

Possible Causes


The trap was generated when a VC became Up.


The configuration was modified. For example, the next hop address of the CCC was changed.


  1. Check whether the service is restored.

    • If so, it indicates that the trap message is informational only, and no action is required.
    • If not, go to Step 2.

  2. Check whether the current configuration is the same as the original configuration. For example, check whether the next hop address of the CCC is the same as the address of the peer interface of the outbound interface.

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

  3. Restore the original configuration and check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 5.
    • If the trap is no cleared, go to Step 4.

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

Document ID: EDOC1100041475

Views: 101481

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next