IBM 12.1(22)EA6 - Manual (Page 477)

25-11
Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter, Software Configuration Guide
24R9746
Chapter 25 Troubleshooting
Using Debug Commands
Using Debug Commands
This section explains how you use the debug commands to diagnose and resolve internetworking
problems. It contains this information:
• Enabling Debugging on a Specific Feature, page 25-11
• Enabling All-System Diagnostics, page 25-12
• Redirecting Debug and Error Message Output, page 25-12
• Using the debug auto qos Command, page 25-12
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 problems or during
troubleshooting sessions with 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.
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 command to enable the
debugging for EtherChannel:
Switch# debug etherchannel
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, consider these possibilities:
• The switch might not be properly configured to generate the type of traffic 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 feature you are
debugging, you can use commands such as the TCP/IP ping command to generate network traffic.
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