Users Guide

Switch Management Commands 2109
Serviceability Commands
Debug commands cause the output of the enabled trace to display on a serial
port or telnet console. Note that the output resulting from enabling a debug
trace always displays on the serial port. The output resulting from enabling a
debug trace displays on all login sessions for which any debug trace has been
enabled. The configuration of a debug command remains in effect the whole
login session.
The output of a debug command is always submitted to the SYSLOG service
at a DEBUG severity level. As such, it can be forwarded to a SYSLOG server,
stored in the buffer log, or otherwise processed in accordance with the
configuration of the SYSLOG service. Configuration of console logging in the
SYSLOG service is not required in order to view the output of debug traces.
Debug commands are provided in the normal CLI tree. Debug settings are
not persistent and are not visible in the running configuration. To view the
current debug settings, use the show debugging command.
The output of debug commands can be voluminous and may adversely affect
system performance. Therefore, debug commands should be used with
caution. Switch behavior may be adversely affected by the additional
processing load incurred by enabling debug output. Use of debug level
logging when performing operations such as switch fail-over is not
recommended.
Enabling debug for all IP packets can cause a serious impact on the system
performance; therefore, it is limited by ACLs. This means debug can be
enabled for IP packets that conform to the configured ACL. This also limits
the feature availability to only when the QoS component is available. Debug
for VRRP and ARP are available on routing builds.
NOTE: Debug commands are not persistent across resets.
debug aaa
Use the debug aaa command to track AAA events.
Use the no form of the command to disable accounting debugging.
Syntax
debug aaa { accounting | coa | pod }