Cisco 3560G 48TS Software Configuration Guide - Page 463

Chapter 25 Configuring System Message Logging Configuring System Message Logging Table 25-3 Message Logging Level Keywords Level Keyword emergencies alerts critical errors warnings notifications informational debugging Level 0 1 2 3 4 5 6 7 Description System unstable Immediate action needed Critical conditions Error conditions Warning conditions Normal but significant condition Informational messages only Debugging messages Syslog Definition LOG_EMERG LOG_ALERT LOG_CRIT LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO 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, refer to 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. Limiting Syslog Messages Sent to the History Table and to SNMP If you enabled syslog message traps to be sent to an SNMP network management station by using the snmp-server enable trap global configuration command, you can change the level of messages sent and stored in the switch history table. You also can change the number of messages that are stored in the history table. Messages are stored in the history table because SNMP traps are not guaranteed to reach their destination. By default, one message of the level warning and numerically lower levels (see Table 25-3 on page 25-9) are stored in the history table even if syslog traps are not enabled. 78-16156-01 Catalyst 3560 Switch Software Configuration Guide 25-9