Subnets Between Spokes Cannot Communicate Directly in Shortcut Mode

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 "IP Routing" in the Configuration Guide.
   • 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.