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).
Spokes Fail to Learn Routes from Each Other

Spokes Fail to Learn Routes from Each Other

Common Causes

This fault is commonly caused by one of the following:

  • There is no reachable route between spokes, and between spokes and the hub.
  • Tunnel interfaces of spokes and the hub are Down.
  • A spoke fails to register with the hub.
  • GRE key configurations of the spoke and hub are different.
  • NHRP authentication string configurations of the spoke and hub are different. For example, an NHRP authentication string is configured on the hub but not on the spoke; or different NHRP authentication strings are configured on the spoke and hub.
  • IPSec profile configurations of the spoke and hub are different.

Troubleshooting Flowchart

Spokes fail to learn routes from each other.

Figure 25-12 shows the troubleshooting flowchart.

Figure 25-12 Troubleshooting flowchart used when spokes fail to learn routes from each other

Troubleshooting Procedure

NOTE:

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

Procedure

  1. Check whether IPSec profiles have been bound to interfaces on the spoke and hub.

    • If IPSec profiles have been bound to interfaces on the spoke and hub, run the undo ipsec profile command on the interfaces to unbind the IPSec profiles from the interfaces, and go to step 2.
    • If no IPSec profile is bound to interfaces on the spoke and hub, go to step 2.

  2. Check that subnet routes are available between spokes, and between spokes and the hub.

    If subnets are configured on spokes and the hub, run the display ip routing-table command on the local spoke to check whether subnet routes to the remote spoke exist in the local IP routing table, and run this command on the hub to check whether subnet routes to spokes exist in the local IP routing table.

    • If no subnet route is available between spokes, and between spokes and the hub, configure subnet routes. For the configurations of routes, see the Huawei AR Series Access Routers Configuration Guide - IP Routing.
    • If subnet routes are available between spokes, and between spokes and the hub, go to step 3.

  3. Check that NHRP mapping entries of spokes have been generated on the hub.

    Run the display nhrp peer command on the hub to check NHRP mapping entries.

    • If no NHRP mapping entry of spokes is generated on the hub, rectify the fault according to A Spoke Fails to Register with a Hub.
    • If NHRP mapping entries of spokes have been generated on the hub, go to step 4.

  4. Check that spokes have generated NHRP mapping entries of each other.

    • Run the diagnose command in the system view on a spoke to enter the diagnostic view.
    • Run the debugging nhrp condition all command to enable NHRP debugging.
    • Run the reset nhrp statistics interface interface-type interface-number command to clear NHRP packet statistics. Enable one spoke to send traffic to the other spoke, and run the display nhrp statistics interface interface-type interface-number command to check statistics about NHRP Resolution Request and Reply packets.

      • If the ResolutionRequestSendSuccess field displays 0, the local spoke fails to send NHRP Resolution Request packets to the remote spoke. When this occurs, the two spokes cannot generate NHRP mapping entries of each other. Go to step 6.
      • If both the ResolutionRequestSendSuccess and ResolutionReplyCorrectRecv fields display non-zero values, the local spoke has sent NHRP Resolution Request packets to and has received NHRP Resolution Reply packets from the remote spoke. When this occurs, the two spokes can generate NHRP mapping entries of each other. If IPSec profiles still need to be bound to interfaces on the spoke and hub, go to step 5.

  5. Bind IPSec profiles to interfaces on the spoke and hub.

    Run the ipsec profile command on each interface to bind a specified IPSec profile to it. Run the display ipsec sa command on the spoke and hub to check whether an IPSec SA is established on interfaces on both ends.

    • If an IPSec SA has been established, run the display nhrp peer command on the hub to check whether NHRP mapping entries of the spoke have been generated. If NHRP mapping entries of the spoke have been generated on the hub, the fault is rectified. Otherwise, go to step 6.
    • If no IPSec SA is established, rectify the fault according to "IPSec Troubleshooting."

  6. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure

    • Configuration files, log files, and alarm files of the devices

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 496011

Downloads: 4534

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