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, syslog servers, or both) 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.)

Duplicate IP addresses are not stored in the list of syslog servers.

If the default severity value is in effect, all messages that have severities greater than the default value are passed to syslog. For example, if the default severity is "debug," all messages that have severities greater than debug are passed to syslog.

There is a limit of six syslog servers. All syslog servers are sent the same messages using the same filter parameters. An error is generated for an attempt to add more than six syslog servers.

The debug destination logging command allows the forwarding of debug logging activities to the configured Syslog servers.

Switch events can be sent to the current console or the debug logging buffer using the debug event command followed by the debug destination session or debug destination buffer command respectively.

The no logging <ip-address> and no logging commands disable the sending of event logs to Syslog servers. These commands will not affect the results of the debug event and debug destination <session | buffer | logging> commands.

If the Syslog server is configured, the no debug destination logging command does not disable the sending of events to Syslog. It does disable the sending of other debug logs to the Syslog server.

If Syslog is configured, the no debug event or no debug all commands do not disable the sending of events to Syslog unless the debug destination is set to buffer or session.

When debugging is finished and the no debug all command is entered, the commands being sent to the previously configured Syslog server(s) are not affected, and no additional commands are needed. If both debug event and debug destination logging are configured, duplicate events are not sent to the configured Syslog servers.

The show debug command won’t display debug event or debug destination logging unless the debug event command is executed for buffer or session destinations.

You can check on the configured Syslog settings with the show syslog config command. The Syslog settings also are visible in the output of show running-config or show startup-config.