36-18
Cisco ME 3400 EthernetAccess Switch SoftwareConfiguration Guide
78-17058-01
Chapter36 Troubleshooting
Using Debug Commands
Using Debug Commands
These sections explains how you use debug commands to diagnose and resolve internetworking
problems:
•Enabling Debugging on a Specific Feature, page 36-18
•Enabling All-System Diagnostics, page 36-19
•Redirecting Debug and Error Message Output, page 36-19
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

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 Switched Port Analyzer (SPAN):
Switch# debug span-session
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 check its 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 SPAN, enter this command in privileged EXEC mode:
Switch# no debug span-session
Alternately, in privileged EXEC mode, you can enter the undebug form of the command:
Switch# undebug span-session
To display the state of each debugging option, enter this command in privileged EXEC mode:
Switch# show debugging