Troubleshooting guide

(DRAFT LABEL) FINAL DRAFT - CISCO CONFIDENTIAL 2/13/02

A-2

ATM and Layer 3 Switch Router Troubleshooting Guide

OL-1969-01

Appendix

Using the Debug Interface

This section explains how to diagnose and resolve internetworking problems by using debug commands,

and covers the following topics:

• Entering debug Commands

• Using the debug ? Command

• Using the debug all Command: Warning

• Generating debug Command Output

• Redirecting Debugging and Error Message Output

Caution Because debugging output is assigned a high priority in the multiservice route processor, it can render

the system unusable. For this reason, use debug commands only to troubleshoot specific problems

or during troubleshooting sessions with customer support. Moreover, it is best to use debug

commands during periods of lower network traffic and fewer users. Debugging during these periods

decreases the likelihood that the increased overhead of debug command processing will affect

system use.

Entering debug Commands

All debug commands are entered in privileged EXEC mode, and most debug commands take no

arguments. For example, to enable the debug atm packet command, enter the following in privileged

EXEC mode at the command line:

Switch# debug atm packet

ATM packets debugging is on

Displaying all ATM packets

To display the status of each debugging option, enter the show debugging command in privileged EXEC

mode:

Switch# show debugging

Generic ATM:

ATM packets debugging is on

Switch#

To turn off the debug atm packet command in privileged EXEC mode, enter the no form of the

command at the command line:

Switch# no debug atm packet

ATM packets debugging is off

Switch#