Verifying Network Connectivity; Using The Ping Or Ping6 Command; Troubleshooting - Cisco ASR 5500 Installation Manual

Troubleshooting

Verifying Network Connectivity

There are multiple commands supported by the system to verify and/or troubleshoot network connectivity.
Note that network connectivity can only be tested once system interfaces and ports have been configured and
bound.
The commands specified in this section should be issued on a context-by-context basis. Contexts act like
virtual private networks (VPNs) that operate independently of other contexts. Ports, interfaces, and routes
configured in one context cannot be tested from another context without additional configuration.
To switch between contexts enter the following command at the root prompt for the Exec mode:
[local]host_name#
context_name is the name of the context to which you wish to switch. The following prompt appears:
[context_name]host_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
[ size
]
ping6
[ size
]
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.
context
context_name
[ count
host_ipv4_address
] [ src {
octet_count
[ count
host_ipv6_address
] [ src {
octet_count
] [ flood ] [ pattern
num_packets
|
src_host_name src_host_ipv4_address
] [ flood ][ pattern
num_packets
|
src_host_name src_host_ipv6_address
Verifying Network Connectivity
]
packet_pattern
} ] [ vrf
vrf_nam
]
packet_pattern
} ] [ vrf
vrf_nam
Troubleshooting
23