32-20
Catalyst2950 and Catalyst2955 Switch Software Configuration Guide
78-11380-10
Chapter32 Troubleshooting
Using Debug Commands
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, refer to the command
reference for this release.
Enabling Debugging on a Specific Feature
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 om mand t o en abl e th e
debugging for EtherChannel:
Switch# debug etherchannel
The switch continues to generate output until you enter t he no form of the command.
If you enable a debug command and no output appears, consi d er t hese possi biliti es:
•The switch might not be properly configured to generate the type of t raffic that you want to monitor.
Use the show running-config command to verify the configuration.
•Even if the switch is properly configured, it might not generate the type of traffic that 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 t raffic.
To disable debugging of EtherChannel, enter this command in privileged EXEC mode:
Switch# no debug etherchannel
Alternately, in privileged EXEC mode, you can enter the undebug form of the command:
Switch# undebug etherchannel
To display the state of each debugging option, enter this command in privileged EXEC mode:
Switch# show debugging
Enabling All-System Diagnostics
Beginning in privileged EXEC mode, enter this command to enable all-system diagnostics:
Switch# debug all
Caution Because debugging output takes priority over other network traffic, and because the debug all privileged
EXEC command generates more output than any other debug command, it can severely diminish switch
performance or even render it unusable. In virtually all cases, it is best to use more specific debug
commands.