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.


AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
Troubleshooting Roadmap for a Ping Failure

Troubleshooting Roadmap for a Ping Failure

Common Causes

This fault is commonly caused by the following:

  • The VC status is Down.

  • The configurations at two ends do not match.

  • No license is uploaded.

Troubleshooting Process

Figure 25-15 shows the troubleshooting process for a ping failure.

Figure 25-15 Troubleshooting flowchart for a ping failure

Troubleshooting Procedure



Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide technical support personnel.


  1. Check whether conditions are met for configuring L2VPN on an interface.

    L2VPN can be configured on a VLAN interface only when the following conditions are met.

    • The MPLS/BGP IP VPN, multicast, or VLL service is not configured on the VLAN interface.

    • The VLAN interface is not used by a super-VLAN or sub-VLAN.

  2. Check the interface configuration.

    MPLS L2VPN supports multiple link layer protocols, but all the nodes in the same VPN must use the same encapsulation type.

    If the interface configuration is correct, go to Step 3.

    If the interface configuration is incorrect, modify the configuration.

  3. Check whether the license status is normal.

    If the license status is abnormal, upload licenses first.

  4. Check the VC types at the two ends.

    Run the display mpls l2vccommand to check the VC type. If the VC types of two devices at the ends are different, change them to be the same.

  5. If the problem persists, troubleshoot the problem by referring to Troubleshooting Procedure.
  6. Collect the following information and contact technical support personnel:
    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the router
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 490115

Downloads: 4503

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