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).
Failed to Ping the IP Address of the Remote Tunnel Interface

Failed to Ping the IP Address of the Remote Tunnel Interface

Common Causes

This fault is commonly caused by one of the following:

  • Interfaces on both ends of a tunnel use different tunnel encapsulation modes.

  • No IP address is assigned to interfaces on either end, or no tunnel source or destination address is configured on the two interfaces.

  • No reachable route exists between the tunnel source and destination addresses.

Troubleshooting Flowchart

After each device is configured as shown in Figure 25-1, PC1 and PC2 cannot communicate. To rectify the fault, follow the troubleshooting flowchart shown in Figure 25-2.

Figure 25-1  GRE networking diagram

Figure 25-2  Troubleshooting flowchart for the ping failure

Troubleshooting Procedure

NOTE:

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

Procedure

  • To troubleshoot when the network layer protocol of one or both ends of a tunnel is Down, perform the following steps:
    1. Check that interfaces on both ends of a tunnel use the same tunnel encapsulation mode.

      Run the display this interface command in the tunnel interface view to check whether interfaces on both ends use the same tunnel encapsulation mode. If Tunnel protocol/transport GRE/IP is displayed, the tunnel encapsulation mode is GRE.

      • If the two interfaces use different tunnel encapsulation modes, run the tunnel-protocol command in the tunnel interface view to reconfigure the tunnel encapsulation mode.

        NOTE:

        After you reconfigure the tunnel encapsulation mode, reconfigure the tunnel source and destination addresses because configurations of the original source and destination addresses were lost.

      • If the two interfaces use the same tunnel encapsulation mode, go to step 2.

    2. Check that IP, tunnel source, and tunnel destination addresses are configured for interfaces on both ends of the tunnel. A tunnel source address and a tunnel destination address uniquely identify a tunnel.

      Check whether the local tunnel source address is the peer tunnel destination address and the local tunnel destination address is the peer tunnel source address. If not, no tunnel can be established between the two interfaces.

      Run the display this command in the tunnel interface view to check the interface configuration. Ensure that the local tunnel source address is the peer tunnel destination address and the local tunnel destination address is the peer tunnel source address.

      • If the tunnel source and destination addresses are incorrect, reconfigure the addresses in the tunnel interface view.
      • If the tunnel source and destination addresses are correct, go to step 3.

    3. Check that reachable routes exist between the tunnel source and destination addresses.

      If the interface configurations on both ends are correct but the tunnel status is still Down, check whether reachable routes exist between interfaces on both ends of the tunnel:

      • If the tunnel is established between two indirectly connected interfaces, check whether reachable routes exist between the two interfaces.

      • If the tunnel is established between two directly connected interfaces, routes are not required.

      Run the display ip routing-table command to view the IP routing table. If the IP routing table is correct, run the display fib command to check the forwarding table (FIB table) and check whether data can be forwarded correctly. Routing information in the FIB table must be consistent with that in the routing table.

      • If no reachable route exists between the tunnel source and destination addresses, configure static routes or a dynamic routing protocol to ensure that reachable routes exist between the tunnel source and destination addresses.

      • If there are reachable routes between the tunnel source and destination addresses but the fault persists, go to step 4.

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

      • Results of the preceding troubleshooting procedure
      • Configuration file, log file, and alarm file of the device

  • To troubleshoot when the network layer protocol of interfaces on both ends of a tunnel is Up, perform the following steps:
    1. Check that GRE key configurations of interfaces on both ends are consistent.

      Run the display interface tunnel command on the two interfaces to check whether their GRE key configurations are consistent. Ensure that:

      • Neither interface is configured with a GRE key.

      • Both interfaces are configured with the same key number.

      If GRE key configurations of interfaces on both ends are consistent but the fault persists, go to step 2.

    2. Check IP addresses of interfaces on both ends of the tunnel.

      If the network protocol status of the two interfaces is Up but they cannot ping each other, check whether their IP addresses are on the same network segment:

      • If IP addresses of the two interfaces are on different network segments, configure static routes or a dynamic routing protocol to ensure that reachable routes exist between the two devices.

      • If IP addresses of the two interfaces are on the same network segment or reachable routes exist between the two devices, go to step 3.

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

      • Results of the preceding troubleshooting procedure
      • Configuration file, log file, and alarm file of the device

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 456012

Downloads: 4321

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