Troubleshooting ipv6 applications, Unable to ping a remote destination, Symptom – H3C Technologies H3C S3100 Series Switches User Manual
Page 937: Solution, Unable to run traceroute
2-5
# On SWA, configure static routes to SWC, the Telnet Server, and the TFTP Server.
[SWA] ipv6 route-static 3002:: 64 3003::1
[SWA] ipv6 route-static 3001:: 64 3003::1
[SWA] quit
# Trace the IPv6 route from SWA to SWC.
traceroute to 3002::1 30 hops max,60 bytes packet
1 3003::1 30 ms 0 ms 0 ms
2 3002::1 10 ms 10 ms 0 ms
# SWA downloads a file from TFTP server 3001::3.
.
File will be transferred in binary mode
Downloading file from remote tftp server, please wait....
TFTP: 13 bytes received in 1.243 second(s)
File downloaded successfully.
# SWA Connect to Telnet server 3001::2.
Trying 3001::2...
Press CTRL+K to abort
Connected to 3001::2 ...
Telnet Server>
Troubleshooting IPv6 Applications
Unable to Ping a Remote Destination
Symptom
Unable to ping a remote destination and return an error message.
Solution
z
Check that the IPv6 addresses are configured correctly.
z
Use the display ipv6 interface command to determine the interfaces of the source and the
destination and the link-layer protocol between them are up.
z
Use the display ipv6 route-table command to verify that the destination is reachable.
z
Use the ping ipv6 -t timeout { destination-ipv6-address | hostname } [ -i interface-type
interface-number ] command to increase the timeout time limit, so as to determine whether it is due
to the timeout limit is too small.
Unable to Run Traceroute
Symptom
Unable to trace the route by performing traceroute operations.
Solution
z
Check that the destination host can be pinged.
z
If the host can be pinged through, check whether the UDP port that was included in the tracert ipv6
command is used by an application on the host. If yes, you need to use the tracert ipv6 command
with an unreachable UDP port.