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

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 VLL Fault

Troubleshooting Roadmap for a VLL Fault

Common Causes

This fault is commonly caused by the following:

  • The basic routing protocol is running abnormally.

  • LSP flapping occurs.

  • The configurations of the same VPN at two ends of the VLL do not match.

  • The packet length exceeds the MTU value.

Troubleshooting Process

Figure 25-14 shows the VLL troubleshooting process.

Figure 25-14  VLL troubleshooting flowchart

Troubleshooting Procedure

Context

NOTE:

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.

Procedure

  1. Check whether the basic routing protocol is running normally.

    Ping the destination node from the LSP ingress to check the network connectivity.

    • If the LSP ingress can successfully ping the destination node, the basic routing protocol is running normally.

    • If the ping fails, run the display ip routing-table protocol command to check the routing protocol configuration. If the problem persists, go to Step 5.

  2. Check whether the LSP is established.

    If the LSP is not established through LDP, do as follows.

    • Run the mpls te loop-detection command to check the loop detection configuration. The LSP can be established only when the configurations at the two ends are the same.

    • Check whether the LSR IDs are used as the transport addresses for session establishment. The local device must advertise its route containing the LSR ID (loopback address of the LSR), and learn the route containing the remote LSR ID.

    • Check the label distribution modes of the MPLS-capable routers. Ensure that the label distribution modes of routers from different vendors must be the same.

    If the problem persists, go to Step 5.

  3. Check whether the configurations of the same VPN at two ends of the VLL are the same.

    In BGP/MPLS IP VPN, check the RT values at the two ends.

    • In MPLS L2VPN of Martini mode, check the VC ID values at the two ends.

    • In MPLS L2VPN of Kompella mode, check the RT values and remote CE IDs at the two ends.

  4. Check whether the packet length exceeds the MTU value.

    If the packet length exceeds the MTU value, change the MTU to a larger value.

  5. Collect the following information and contact technical support personnel:
    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the router
Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 444580

Downloads: 4297

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