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).
A Spoke Fails to Register with a Hub

A Spoke Fails to Register with a Hub

Common Causes

This fault is commonly caused by one of the following:

  • There is no reachable route between the spoke and its remote spoke, or between the spoke and hub.
  • Tunnel interfaces of the spoke and hub are Down.
  • 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

After DSVPN is configured, a spoke fails to register with a hub.

Figure 25-11 shows the troubleshooting flowchart.

Figure 25-11  Troubleshooting flowchart used when a spoke fails to register with a hub

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 the spoke has reachable routes to the remote spoke and hub.

    Run the display ip routing-table command on the spoke to check whether it has routes to the remote spoke, and run the display ip routing-table command on the hub to check whether the hub has routes to the spoke.

    • If there is no reachable route between the spoke and its remote spoke, or between the spoke and hub, check the configurations of routes on the spoke and hub. For the configurations of routes, see the Huawei AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 Series Enterprise Routers Configuration Guide - IP Routing.
    • If there are reachable routes between the spoke and its remote spoke, and between the spoke and hub, go to step 3.

  3. Check that tunnel interfaces of the spoke and hub are Up.

    Run the display interface interface-type interface-number command on the spoke and hub to check whether their connected tunnel interfaces are Up. If some tunnel interfaces are Down, run the undo shutdown command to enable the interfaces to go Up.

    If tunnel interfaces on both ends are Up, go to step 4.

  4. Check that configurations of the spoke and hub are correct.

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

    If the hub does not have dynamic NHRP mapping entries of the spoke, run the display this command on tunnel interfaces of the spoke and hub to check whether the configurations on both ends are the same. The following table lists the fields in the command output that you need to check and follow-up operations.

    Item

    Check Standard and Operation

    NHRP authentication

    Check whether NHRP authentication string configurations of the spoke and hub are the same. If they are different, run the nhrp authentication command to modify the configurations.

    GRE key

    Check whether the GRE key configurations of the spoke and hub are the same. If they are different, run the gre key command to modify the configurations.

    If the preceding configurations on the spoke and hub are correct, go to step 5.

  5. Check that the spoke has sent NHRP Registration Request packets to the hub and the hub has replied with NHRP Registration Reply packets.

    Run the reset nhrp statistics interface interface-type interface-number command on the spoke and hub to clear NHRP packet statistics. Enable the spoke to re-register with the hub, and run the display nhrp statistics interface interface-type interface-number command to check statistics about NHRP Registration Request and Reply packets.

    • If the RegisterRequestSendSuccess field displays 0, the spoke fails to send NHRP Registration Request packets. Go to step 7.
    • If the RegisterRequestSendSuccess field displays a non-zero value but the RegisterReplyCorrectRecv field displays 0, the spoke has sent NHRP Registration Request packets to the hub but has not received NHRP Registration Reply packets from the hub. Go to step 7.
    • If both the RegisterRequestSendSuccess and RegisterReplyCorrectRecv fields display non-zero values, NHRP mapping entries of the spoke have been generated on the hub. If IPSec profiles still need to be bound to interfaces on the spoke and hub, go to step 6.

  6. 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 7.
    • If no IPSec SA is established, rectify the fault according to IPSec Troubleshooting.

  7. 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-05-10

Document ID: EDOC1000079719

Views: 446512

Downloads: 4301

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