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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical 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).
IPv6 over IPv4 Tunnel Troubleshooting

IPv6 over IPv4 Tunnel Troubleshooting

This chapter describes common causes of the IPv6 over IPv4 tunnel faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

Two IPv6 Networks Cannot Communicate Over a 6to4 Tunnel

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that prevents two IPv6 networks from communicating over a 6to4 tunnel.

Common Causes
This fault is most commonly caused due to the following reasons:
  • Routing entries on the two IPv6 networks or routing entries on the IPv4 network between the two IPv6 networks are abnormal.

  • The 6to4 tunnel interface goes Down.

  • The format of the 6to4 tunnel address is incorrect.

  • The link transmission delay is too long. The source end, therefore, cannot receive a response packet from the destination end within the waiting time.

  • A hardware fault occurs.

Troubleshooting Flowchart

Figure 4-39 shows the troubleshooting flowchart for the fault that prevents two IPv6 networks cannot from communicating over a 6to4 tunnel.

Figure 4-39 Troubleshooting flowchart for the fault that prevents two IPv6 networks from communicating over a 6to4 tunnel

Troubleshooting Procedure
Context
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check whether the devices on the IPv4 network between the two IPv6 networks can ping each.

  2. Check whether the IPv6 routes are correctly configured on the source and destination ends.

    Run the display ipv6 routing-table command on the source end to check whether the source end has a route destined to the destination end, and run the display ipv6 routing-table command on the destination end to check whether the destination end has a route destined to the source end.
    • If the source end does not have a route destined to the destination end, or the destination end does not have a route destined to the source end, run the ipv6 route-static dest-ipv6-address prefix-length interface-type interface-number command on the source end or the destination end to add a static route to the source end or the destination end. Then, go to Step 3.

    • If the IPv6 routes are correctly configured on the source and destination ends, go to Step 3.

  3. Run the display ipv6 interface interface-type interface-number command on the source and destination ends to check whether the physical status of the 6to4 tunnel is Up.

    • If the physical status of the tunnel interface is Administratively DOWN, run the undo shutdown command in the tunnel interface view and go to Step 4.

    • If the physical status of the tunnel interface is DOWN,
      1. Run the display this command in the tunnel interface view to check whether the tunnel source address and the tunnel mode are configured.
        • If the tunnel source address and the tunnel mode are configured, that is, the source field and the tunnel-protocol ipv6-ipv4 6to4 field are displayed, go to Step b.

        • If the tunnel source address or the tunnel mode is not configured, run the source {source-ip-address | interface-type interface-number } command or the tunnel-protocol ipv6-ipv4 6to4 command to configure the tunnel source address or the tunnel mode. Then, go to Step b.

      2. Run the display ip interface brief command to check whether the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface exists.
        • If the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface exists, go to Step 4.

        • If the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface does not exist, go to Step 4.

    • If the physical status of the tunnel interface is UP, go to Step 4.

  4. Run the display ipv6 interface interface-type interface-number command on the source and destination ends to check whether the status of the 6to4 tunnel protocol is Up.

    • If the status of the 6to4 tunnel protocol is DOWN, run the display this command to check whether the tunnel interface is configured with an IPv6 address.
      • If the tunnel interface is configured with an IPv6 address, go to Step 8.

      • If the tunnel interface is not configured with an IPv6 address, run the ipv6 address command to configure an IPv6 address for the tunnel interface, and go to Step 5.

    • If the status of the 6to4 tunnel protocol is UP, go to Step 5.

  5. Run the display ipv6 interface interface-type interface-number command on the source and destination ends to check whether the IPv6 address of the 6to4 tunnel is in the 6to4 address format, and the IPv4 address in the 6to4 tunnel address is the source 6to4 tunnel address.

    NOTE:

    6to4 tunnel addresses are in the format of 2002:IPv4 address:Subnet ID::Interface ID.

    • If the 6to4 tunnel address is not in the 6to4 address format, run the ipv6 address ipv6-address prefix-length command to modify the address to be in the 6to4 address format, and go to Step 6.

    • If the 6to4 tunnel address is in the 6to4 address format, go to Step 6.

  6. Determine whether the packets are discarded in the receiving or sending direction and where the packets are discarded.

    Run the reset ipv6 statistics command on the source and destination ends to delete the IPv6 statistics, and run the ping ipv6 command and display icmpv6 statistics [ interface interface-type interface-number ] command again to view the statistics on the received and sent ICMPv6 packets on the interface.
    • If the Echoed value in the Sent packets field does not increase, the source end has not sent any IPv6 packets. Go to Step 7.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field do not increase on the destination end, the destination end has not received the IPv6 packets that were sent by the source end. Go to Step 7.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and the Echoed value in the Received packets field increases but the Echo replied value in the Sent packets field does not increase on the destination end, the source end has sent the IPv6 packets, and the destination end has received the IPv6 packets but has not sent any response packets. Go to Step 7.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field increase on the destination end, the source end has sent IPv6 packets but has not any received response packets, and the destination end has received the IPv6 packets and sent the response packets. Go to Step 7.

    • If the Echoed value in the Sent packets field and the Echo replied value in the Received packets field increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field increase on the destination end, the source end has sent the IPv6 packets and received the response packets, and the destination has received the IPv6 packets and sent the response packets. The fault that prevents two IPv6 networks from pinging each other over a 6to4 tunnel may be caused by an excessively long link transmission delay. Run the ping ipv6 -t timeout command to increase the timeout period for sending an ICMPv6 response packet.
      • If the ping succeeds, go to Step 9.

      • If the ping still fails, go to Step 7.

  7. Determine the position on which the fault occurs.

    Locate the position based on the direction in which the fault occurs. Perform the following operations to enable IPv6 packet debugging:
    NOTE:

    Enabling debugging affects the system performance. So confirm the action before you enable debugging.

    <HUAWEI> debugging rawip ipv6 packet
    <HUAWEI> debugging ipv6 packet
    <HUAWEI> terminal debugging

    Run the ping ipv6 -c echo-number destination-ipv6-address command to send five ping packets. Check whether the source end has sent five packets and received five response packets, and whether the destination end has received five packets and sent five response packets. If no related information is displayed, go to Step 8.

  8. If the fault persists, collect the following information and contact Huawei.

    • Results of this operation procedure
    • Configuration files, log files, and alarm files of the device

  9. End.
Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

Two IPv6 Networks Cannot Communicate Over a Manual IPv6 over IPv4 Tunnel

This section describes common causes of the fault that prevents two IPv6 networks from communicating over a manual IPv6 over IPv4 tunnel, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

Common Causes
This fault is most commonly caused due to the following reasons:
  • Routing entries on the two IPv6 networks or routing entries on the IPv4 network between the two IPv6 networks are abnormal.

  • The manual IPv6 over IPv4 tunnel goes Down.

  • The IPv6 address configured for the manual IPv6 over IPv4 tunnel is incorrect.

  • The link transmission delay is too long. The source end, therefore, cannot receive a response packet from the destination end within the waiting time.

  • A hardware fault occurs.

Troubleshooting Flowchart

Figure 4-40 shows the troubleshooting flowchart for the fault that prevents two IPv6 networks from communicating over a manual IPv6 over IPv4 tunnel.

Figure 4-40 Troubleshooting flowchart for the fault that prevents two IPv6 networks cannot communicate over a manual IPv6 over IPv4 tunnel

Troubleshooting Procedure
Context
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check whether the devices on the IPv4 network between the two IPv6 networks can ping each.

  2. Check whether the IPv6 routes are correctly configured on the source and destination ends.

    Run the display ipv6 routing-table command on the source end to check whether the source end has a route destined to the destination end, and run the display ipv6 routing-table command on the destination end to check whether the destination end has a route destined to the source end.
    • If the source end does not have a route destined to the destination end, or the destination end does not have a route destined to the source end, run the ipv6 route-static dest-ipv6-address prefix-length interface-type interface-number command to add a static route to the source end or the destination end.

    • If the IPv6 routes are correctly configured on the source and destination ends, go to Step 3.

  3. Run the display ipv6 interface interface-type interface-number command on the source and destination ends to check whether the physical status of the manual IPv6 over IPv4 tunnel is Up.

    • If the physical status of the tunnel interface is Administratively DOWN, run the undo shutdown command in the tunnel interface view and go to Step 4.

    • If the physical status of the tunnel interface is DOWN, perform the following steps.
      1. Run the display this command in the tunnel interface view to check whether the tunnel source address, tunnel destination address, and tunnel mode are configured.
        • If the tunnel source address, tunnel destination address, and tunnel mode are configured (that is, the source, destination, and tunnel-protocol ipv6-ipv4 6to4 fields are displayed), go to Step b.

        • If the tunnel source address, tunnel destination address, or tunnel mode is not configured, run the source {source-ip-address | interface-type interface-number } command, the destination dest-ip-address command, or the tunnel-protocol ipv6-ipv4command to configure a tunnel source address (or a source interface address), a tunnel destination address, or a tunnel mode. Then, go to Step b.

      2. Run the display ip interface brief command to check whether the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface exists.
        • If the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface exists, go to Step c.

        • If the interface mapping the tunnel source address or the IPv4 address of the tunnel source interface does not exist, configure a tunnel source address (or a source interface address) and a tunnel destination address, and then go to Step c.

      3. Run the display ip routing-table ip-address command to check whether the route destined to the destination address exists.
        • If the route destined to the destination address exists, go to Step 4.

        • If the route destined to the destination address does not exist, add a routing protocol or a static route, and go to Step 4.

    • If the physical status of the tunnel interface is UP, go to Step 4.

  4. Run the display ipv6 interface interface-type interface-number command on the source and destination ends to check whether the protocol status of the manual IPv6 over IPv4 tunnel is Up.

    • If the status of the protocol is DOWN, run the display this command to check whether the tunnel interface is configured with an IPv6 address.
      • If the tunnel interface is configured with an IPv6 address, go to Step 9.

      • If the tunnel interface is not configured with an IPv6 address, run the ipv6 address command to configure an IPv6 address for the tunnel interface, and go to Step 5.

    • If the status of the protocol on the tunnel interface is UP, go to Step 5.

  5. Run the display this command in the tunnel interface views on the source and destination ends to check whether the source address and the destination address of the tunnel are symmetrical.

    • If the source address and the destination address are symmetrical, go to Step 6.

    • If the source address and the destination address are not symmetrical, run the source {source-ip-address | interface-type interface-number } command or the destination dest-ip-address command to modify the source address or the destination address so the two address become symmetrical.

  6. Run the display this command in the tunnel interface views on the source and destination ends to check whether the IPv6 addresses are correctly configured on the two ends.

    • If the IPv6 addresses are correctly configured on the two ends, go to Step 7.

    • If the IPv6 addresses are incorrectly configured on the two ends, run the ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } command in the tunnel interface views to reconfigure the IPv6 addresses of the tunnel, and go to Step 7.

  7. Determine whether the packets are discarded in the receiving or sending direction and where the packets are discarded.

    Run the reset ipv6 statistics command on the source and destination ends to delete statistics on IPv6 traffic, and run the ping ipv6 command and display icmpv6 statistics [ interface interface-type interface-number ] command again to view the statistics on the received and sent ICMPv6 packets on the interface.
    • If the Echoed value in the Sent packets field does not increase on the source end, the source end has not sent any IPv6 packets. Go to Step 8.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field do not increase on the destination end, the destination end has not received the IPv6 packets that were sent by the source end. Go to Step 8.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and the Echoed value in the Received packets field increases but the Echo replied value in the Sent packets field does not increase on the destination end, the source end has sent the IPv6 packets, and the destination end has received the IPv6 packets but has not sent any response packets. Go to Step 8.

    • If the Echoed value in the Sent packets field increases but the Echo replied value in the Received packets field does not increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field increase on the destination end, the source end has sent IPv6 packets but has not any received response packets, and the destination end has received the IPv6 packets and sent the response packets. Go to Step 8.

    • If both the Echoed value in the Sent packets field and the Echo replied value in the Received packets field increase on the source end, and both the Echo replied value in the Sent packets field and the Echoed value in the Received packets field increase on the destination end, the source end has sent the IPv6 packets and received the response packets, and the destination has received the IPv6 packets and sent the response packets. The fault that two IPv6 networks from communicating over a manual IPv6 over IPv4 tunnel may be caused by an excessively long link transmission delay. Run the ping ipv6 -t timeout destination-address command to increase the timeout period for sending an ICMPv6 response packet.
      • If the ping succeeds, go to Step 10.

      • If the ping still fails, go to Step 8.

  8. Determine where the packets are discarded.

    Locate the position based on the direction in which the fault occurs. Perform the following operations to enable IPv6 packet debugging:
    NOTE:

    Enabling debugging affects the system performance. Therefore, confirm the action before you enable debugging.

    <HUAWEI> debugging rawip ipv6 packet
    <HUAWEI> debugging ipv6 packet
    <HUAWEI> terminal debugging

    Run the ping ipv6 -c echo-number destination-ipv6-address command to send five ping packets. Check whether the source end has sent five packets and received five response packets, and whether the destination end has received five packets and sent five response packets. If the related information is not displayed, go to Step 9.

  9. If the fault persists, collect the following information and contact Huawei.

    • Results of this operation procedure
    • Configuration files, log files, and alarm files of the device

  10. End.
Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13736

Downloads: 257

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