Explanation/Reference:
Explanation:
By default, switches send the output from system messages and debug privileged EXEC commands to a logging process. The logging process controls the distribution of logging messages to various destinations, such as the logging buffer, terminal lines, or a UNIX syslog server, depending on your configuration. The process also sends messages to the console.
Table 29-3 Message Logging Level Keywords
Level Keyword
Level
Description
Syslog Definition
emergencies
System unstable
LOG_EMERG
alerts
Immediate action needed
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
Normal but significant condition
LOG_NOTICE
informational
Informational messages only
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
The software generates four other categories of messages:
Error messages about software or hardware malfunctions, displayed at levels warnings through

emergencies. These types of messages mean that the functionality of the switch is affected. For information on how to recover from these malfunctions, see the system message guide for this release.
Output from the debug commands, displayed at the debugging level. Debug commands are typically

used only by the Technical Assistance Center.
Interface up or down transitions and system restart messages, displayed at the notifications level. This

message is only for information; switch functionality is not affected. Reload requests and low-process stack messages, displayed at the informational level. This message

is only for information; switch functionality is not affected.
References: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2950/software/release/12-
1_9_ea1/configuration/guide/scg/swlog.html
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960/software/release/12- 2_55_se/ configuration/guide/scg_2960/swlog.html