Table of Contents
Advertisement
Using Debug Commands
Use TDR to diagnose and resolve cabling problems in these situations:
•
•
•
Running TDR and Displaying the Results
To run TDR, enter the test cable-diagnostics tdr interface interface-id privileged EXEC command:
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:
•
•
•
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.
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 Switched Port Analyzer (SPAN):
Switch# debug span-session
The switch continues to generate output until you enter the no form of the command.
Catalyst 2960 Switch Software Configuration Guide
32-18
Replacing a switch
Setting up a wiring closet
Troubleshooting a connection between two devices when a link cannot be established or when it is
not operating properly
Enabling Debugging on a Specific Feature, page 32-18
Enabling All-System Diagnostics, page 32-19
Redirecting Debug and Error Message Output, page 32-19
Chapter 32
Troubleshooting
OL-8603-04
Advertisement
Chapters
Table of Contents
Troubleshooting
