EasyManua.ls Logo

3Com 4210 PWR - Troubleshooting Ipv6 Application

3Com 4210 PWR
567 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Troubleshooting IPv6 Application 547
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 31/46/110 ms
# On SWA, configure static routes to SWC, the Telnet Server, and the TFTP Server.
<SWA> system-view
[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.
<SWA> tracert ipv6 3002::1
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.
<SWA> tftp ipv6 3001::3 get filetoget flash:/filegothere
.
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.
<SWA> telnet ipv6 3001::2
Trying 3001::2...
Press CTRL+K to abort
Connected to 3001::2 ...
Telnet Server>
Troubleshooting IPv6
Application
Unable to Ping a Remote
Destination
Symptom
Unable to ping a remote destination and return an error message.
Solution
Check that the IPv6 addresses are configured correctly.
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.
Use the display ipv6 route-table command to verify that the destination is
reachable.
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.

Table of Contents

Related product manuals