Using Debug Commands - Cisco Catalyst 2360 Software Configuration Manual

Chapter 28 Troubleshooting
2 172.2.1.203 12 msec 8 msec 0 msec
3 171.9.16.6 4 msec 0 msec 0 msec
4 171.9.4.5 0 msec 4 msec 0 msec
5 171.9.121.34 0 msec 4 msec 4 msec
6 171.9.15.9 120 msec 132 msec 128 msec
7 171.9.15.10 132 msec 128 msec 128 msec
Switch#
The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds
for each of the three probes that are sent.
Table 28-2
Character
*
?
A
H
N
P
Q
U
To end a trace in progress, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and
release the Ctrl, Shift, and 6 keys and then press the X key.

Using Debug Commands

These sections explains how you use debug commands to diagnose and resolve internetworking
problems:
•
•
•
Because debugging output is assigned high priority in the CPU process, it can render the system
Caution
unusable. For this reason, use debug commands only to troubleshoot specific problems or during
troubleshooting sessions with Cisco technical support staff. It is best to use debug commands during
periods of lower network traffic and fewer users. Debugging during these periods decreases the
likelihood that increased debug command processing overhead will affect system use.
For complete syntax and usage information for specific debug commands, see the command reference
Note
for this release.
OL-19808-01
Traceroute Output Display Characters
Description
The probe timed out.
Unknown packet type.
Administratively unreachable. Usually, this output means that an access list is
blocking traffic.
Host unreachable.
Network unreachable.
Protocol unreachable.
Source quench.
Port unreachable.
Enabling Debugging on a Specific Feature, page 28-18
Enabling All-System Diagnostics, page 28-18
Redirecting Debug and Error Message Output, page 28-18
Catalyst 2360 Switch Software Configuration Guide
Using Debug Commands
28-17