
C-58
Troubleshooting
Debug/Syslog Operation
Operating Notes for Debug and Syslog
■
Rebooting the Switch or pressing the Reset button resets the
Debug Configuration.
■
Debug commands do not affect normal message output to the
Event Log.
Using the
debug event
command, you can specify that Event Log messages
are sent to the debug destinations you configure (CLI session and/or
Syslog servers) in addition to the Event Log.
■
Ensure that your Syslog servers accept Debug messages.
All Syslog messages resulting from a debug operation have a “debug”
severity level. If you configure the switch to send debug messages to a
Syslog server, ensure that the server’s Syslog application is configured to
accept the “debug” severity level. (The default configuration for some
Syslog applications ignores the “debug” severity level.)
Debug Option
Effect of a Reboot or Reset
logging (debug destination)
If Syslog server IP addresses are stored in the startup-config
file, they are saved across a reboot and the logging
destination option remains enabled. Otherwise, the logging
destination is disabled.
session (debug destination)
Disabled.
ACL (debug type)
Disabled.
All (debug type)
Disabled.
event (debug type)
If a Syslog server IP address is configured in the startup-
config file, the sending of Event Log messages is reset to
enabled
, regardless of the last active setting.
If no Syslog server is configured, the sending of Event Log
messages is
disabled
.
IP (debug type)
Disabled.
3500-5400-6200-8200-MCG-Jan08-K_13_01.book Page 58 Monday, January 28, 2008 10:04 AM