Syntax
The
ping
command has the following syntax:
ping host_ipv4_address [ count num_packets ] [ flood ] [ pattern packet_pattern ] [ size octet_count ]
[ src { src_host_name | src_host_ipv4_address } ] [ vrf vrf_nam ]
ping6 host_ipv6_address [ count num_packets ] [ flood ][ pattern packet_pattern ] [ size octet_count ]
[ src { src_host_name | src_host_ipv6_address } ] [ vrf vrf_nam ]
For complete information on the above commands, see the
Exec Mode Commands
chapter of the
Command
Line Interface Reference
.
The following displays a sample of a successful
ping
(IPV4) response.
PING 192.168.250.1 (192.168.250.1): 56 data bytes
64 bytes from 192.168.250.1: icmp_seq=0 ttl=255 time=0.4 ms
64 bytes from 192.168.250.1: icmp_seq=1 ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=2 ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=3 ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=4 ttl=255 time=0.2 ms
--- 192.168.250.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.4 ms
Troubleshooting
If no response is received from the target follow these troubleshooting procedures:
•
Verify that the correct IP address was entered.
•
Attempt to ping a different device on the same network. If the ping was successful then it is likely that
your system configuration is correct. Verify that the device you are attempting to ping is powered and
functioning properly.
•
Verify the port is operational.
•
Verify that the configuration of the ports and interfaces within the context are correct.
•
If the configuration is correct and you have access to the device that you're attempting to ping, ping the
system from that device.
•
If there is still no response, it is likely that the packets are getting discarded by a network device. Use
the
traceroute
or
traceroute6
and
show ip static-route
commands discussed in this chapter to further
troubleshoot the issue.
Using the traceroute or traceroute6 Command
The
traceroute
or
traceroute6
command collects information on the route data will take to a specified host.
This is a useful troubleshooting command that can be used to identify the source of significant packet delays
or packet loss on the network. This command can also be used to identify bottle necks in the routing of data
over the network.
ASR 5500 System Administration Guide, StarOS Release 21.5
160
Troubleshooting
Using the traceroute or traceroute6 Command