Using The Ping Or Ping6 Command; Syntax; Troubleshooting - Cisco ASR 5500 Administration Manual

Using the ping or ping6 Command

To switch between contexts enter the following command at the root prompt for the Exec mode:
[local]
context_name is the name of the context to which you wish to switch. The following prompt appears:
[context_name]
Using the ping or ping6 Command
The ping or ping6 command verifies the system's ability to communicate with a remote node in the network
by passing data packets between and measuring the response. This command is useful in verifying network
routing and if a remote node is able to respond at the IP layer.

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
• 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
• If there is still no response, it is likely that the packets are getting discarded by a network device. Use
ASR 5500 System Administration Guide, StarOS Release 19
172
host_name context context_name
#
host_name
#
your system configuration is correct. Verify that the device you are attempting to ping is powered and
functioning properly.
system from that device.
the traceroute or traceroute6 and show ip static-route commands discussed in this chapter to further
troubleshoot the issue.
Troubleshooting