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

CLI-based Configuration Guide - VPN

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document describes VPN features on the device and provides configuration procedures and configuration examples.
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).
Subnets Between Spokes Cannot Communicate Directly in Shortcut Mode

Subnets Between Spokes Cannot Communicate Directly in Shortcut Mode

Fault Description

After the shortcut mode is configured, subnets between Spokes cannot communicate.

Procedure

  1. Check that subnet routes are available between Spokes, and between Spokes and the Hub.

    Run the display ip routing-table command on the local Spoke to check whether routes to the remote Spoke exist in the local IP routing table. Run the display ip routing-table 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 V200R010 Configuration Guide - IP Routing.
    • If subnet routes are available between Spokes, and between Spokes and the Hub, go to step 2.

  2. Check whether the next hop to the destination subnet is the tunnel address of the Hub.

    Run the display ip routing-table command on the local Spoke to check whether routes to the remote Spoke exist.

    • If the next hop to the destination subnet is not the tunnel address of the Hub, configure routing information to set the next hop to the destination subnet to the tunnel address of the Hub. For details, see Configuring Routes.
    • If the next hop to the destination subnet is the tunnel address of the Hub, go to step 3.

  3. Check whether NHRP mapping entries of a local Spoke have been generated on the Hub and the remote Spoke.

    Run the display nhrp peer command on the Hub and Spoke to check NHRP mapping entries.

    If no NHRP mapping entry of the Spoke is generated on the Hub, rectify the fault according to Spoke Fails to Register with a Hub.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100033725

Views: 145317

Downloads: 361

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