7-8
Software Configuration Guide—Release 15.0(2)SG
OL-23818-01
Chapter 7 Checking Port Status and Connectivity
Using IP Traceroute

Running Ping

To ping another device on the network from the switch, enter this command in normal executive and
privileged EXEC mode:
This example shows how to ping a remote host from normal executive mode:
Switch# ping labsparc
labsparc is alive
Switch> ping 72.16.10.3
12.16.10.3 is alive
Switch#
This example shows how to use a ping command in privileged EXEC mode to specify the number of
packets, the packet size, and the timeout period:
Switch# ping
Target IP Address []: 12.20.5.19
Number of Packets [5]: 10
Datagram Size [56]: 100
Timeout in seconds [2]: 10
Source IP Address [12.20.2.18]: 12.20.2.18
!!!!!!!!!!
----12.20.2.19 PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/1/1
Switch
Using IP Traceroute
These sections describe how to use IP traceroute feature:
Understanding How IP Traceroute Works, page 7-8
Running IP Traceroute, page 7-9

Understanding How IP Traceroute Works

IP traceroute allows you to identify the path that packets take through the network on a hop-by-hop basis.
The command output displays all network layer (Layer 3) devices, such as routers, that the traffic passes
through on the way to the destination.
Layer 2 switches can participate as the source or destination of the trace command but does not appear
as a hop in the trace command output.
The trace command uses the time to live (TTL) field in the IP header to cause routers and servers to
generate specific return messages. Traceroute starts by sending a User Datagram Protocol (UDP)
datagram to the destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it
Command Purpose
Switch# ping host Checks connectivity to a remote host.