This page allows you to issue ICMP PING packets to troubleshoot IP connectivity issues.
After you press , ICMP packets are transmitted, and the sequence number and round trip time are displayed upon reception of a reply. The amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space(the ICMP header). The page refreshes automatically until responses to all packets are received, or until a timeout occurs.
PING server 10.10.132.20, 56 bytes of data. 64 bytes from 10.10.132.20: icmp_seq=0, time=10ms 64 bytes from 10.10.132.20: icmp_seq=1, time=10ms 64 bytes from 10.10.132.20: icmp_seq=2, time=10ms 64 bytes from 10.10.132.20: icmp_seq=3, time=10ms 64 bytes from 10.10.132.20: icmp_seq=4, time=10ms Sent 5 packets, received 5 OK, 0 bad
This page allows you to retrieve the local or remote OAM MIB variable data on a particular port. Select the appropriate radio button and enter the port number of the switch to retrieve the content of interest. Click on to retrieve the content. Click on to retrieve another content of interest.
This page allows you to issue ICMPv6 PING packets to troubleshoot IPv6 connectivity issues.
After you press , ICMPv6 packets are transmitted, and the sequence number and round trip time are displayed upon reception of a reply. The page refreshes automatically until responses to all packets are received, or until a timeout occurs.
PING6 server ff02::2, 56 bytes of data. 64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=0, time=10ms 64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=0, time=10ms 64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=1, time=10ms 64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=1, time=10ms 64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=2, time=10ms 64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=2, time=10ms 64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=3, time=10ms 64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=3, time=10ms 64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=4, time=10ms 64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=4, time=10ms Sent 5 packets, received 10 OK, 0 bad
You can configure the following properties of the issued ICMP packets:
This page allows you to issue ICMP, TCP, or UDP packets to diagnose network connectivity issues.
After you press , Traceroute sends packets with gradually increasing TTL value, starting with TTL value of 1. The first router receives the packet, decrements the TTL value and drops the packet because it then has TTL value zero. The router sends an ICMP Time Exceeded message back to the source. The next set of packets are given a TTL value of 2, so the first router forwards the packets, but the second router drops them and replies with ICMP Time Exceeded. Proceeding in this way, traceroute uses the returned ICMP Time Exceeded messages to build a list of routers that packets traverse, until the destination is reached and returns an ICMP Echo Reply message.
traceroute to 202.39.253.11 (202.39.253.11), 30 hops max, 40 byte packets 1 192.168.10.254 ae-2-3508.edge4.Atlanta2.Level3.net. (192.168.10.254) 10 ms 10 ms 10 ms 2 59-125-13-254.HINET-IP.hinet.net. (59.125.13.254) 20 ms 20 ms 20 ms 3 h146.s228.ts.hinet.net. (168.95.228.146) 20 ms 10 ms 20 ms 4 tchn-3011.hinet.net. (220.128.16.194) 20 ms TCHN-3112.hinet.net. (220.128.17.142) 20 ms tchn-3011.hinet.net. (220.128.16.202) 20 ms 5 TPDT-3012.hinet.net. (220.128.17.6) 20 ms TPDT-3011.hinet.net. (220.128.16.10) 20 ms TPDT-3012.hinet.net. (220.128.17.6) 40 ms 6 CHCH-3112.hinet.net. (220.128.2.13) 20 ms tchn-3011.hinet.net. (220.128.1.9) 10 ms CHCH-3112.hinet.net. (220.128.2.13) 30 ms 7 211.22.41.237 CHCH-3112.hinet.net. (211.22.41.237) 20 ms 30 ms 30 ms 8 202-39-253-11.HINET-IP.hinet.net. (202.39.253.11) 10 ms 10 ms
You can configure the following properties:
: Click to start transmitting ICMP packets.
: Click to re-start diagnostics with PING.