38-20
Catalyst 2960 and 2960-S Switch Software Configuration Guide
OL-8603-09
Chapter 38 Troubleshooting
Using Debug Commands
To display the results, enter the show cable-diagnostics tdr interface interface-id privileged EXEC
command. For a description of the fields in the display, see the command reference for this release.
Using Debug Commands
These sections explains how you use debug commands to diagnose and resolve internetworking
problems:
• Enabling Debugging on a Specific Feature, page 38-20
• Enabling All-System Diagnostics, page 38-21
• Redirecting Debug and Error Message Output, page 38-21
Caution Because debugging output is assigned high priority in the CPU process, it can render the system
unusable. For this reason, use debug commands only to troubleshoot specific proble ms 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 decrease s the
likelihood that increased debug command processing overhead will affect system use.
Note For complete syntax and usage information for specific debug commands, see the command reference
for this release.

Enabling Debugging on a Specific Feature

When you enable debugging, it is enabled only on the stack ma ster. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then, enter the debug command at the command-line prompt of the stack member.
Note Stacking is supported only on Catalyst 2960-S switches running the LAN base image.
All debug commands are entered in privileged EXEC mode, and most debug commands take no
arguments. For example, beginning in privileged EXEC mode, enter this c ommand to enable the
debugging for Switched Port Analyzer (SPAN):
Switch# debug span-session
The switch continues to generate output until you enter the no form of the command.
If you enable a debug command and no output appears, consi der these possibilities:
• The switch might not be properly configured to generate the type of traffic you want to monitor. Use
the show running-config command to check its configuration.
• Even if the switch is properly configured, it might not generate the type of traffic you want to
monitor during the particular period that debugging is enabled. Depending on the featur e you are
debugging, you can use commands such as the TCP/IP ping command to generate net work traffic.