Cisco Systems 3560 사용자 설명서
30-10
Catalyst 3560 Switch Software Configuration Guide
OL-8553-06
Chapter 30 Configuring System Message Logging
Configuring System Message Logging
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.
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
destination. By default, one message of the level warning and numerically lower levels (see
) are stored in the history table even if syslog traps are not enabled.
Beginning in privileged EXEC mode, follow these steps to change the level and history table size
defaults. This procedure is optional.
defaults. This procedure is optional.
When the history table is full (it contains the maximum number of message entries specified with the
logging history size global configuration command), the oldest message entry is deleted from the table
to allow the new message entry to be stored.
logging history size global configuration command), the oldest message entry is deleted from the table
to allow the new message entry to be stored.
To return the logging of syslog messages to the default level, use the no logging history global
configuration command. To return the number of messages in the history table to the default value, use
the no logging history size global configuration command.
configuration command. To return the number of messages in the history table to the default value, use
the no logging history size global configuration command.
Enabling the Configuration-Change Logger
You can enable a configuration logger to keep track of configuration changes made with the
command-line interface (CLI). When you enter the logging enable configuration-change logger
configuration command, the log records the session, the user, and the command that was entered to
change the configuration. You can configure the size of the configuration log from 1 to 1000 entries (the
default is 100). You can clear the log at any time by entering the no logging enable command followed
by the logging enable command to disable and reenable logging.
command-line interface (CLI). When you enter the logging enable configuration-change logger
configuration command, the log records the session, the user, and the command that was entered to
change the configuration. You can configure the size of the configuration log from 1 to 1000 entries (the
default is 100). You can clear the log at any time by entering the no logging enable command followed
by the logging enable command to disable and reenable logging.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
logging history level
1
1.
lists the level keywords and severity level. For SNMP usage, the severity level values increase by 1. For example, emergencies
equal 1, not 0, and critical equals 3, not 2.
Change the default level of syslog messages stored in the history file and
sent to the SNMP server.
sent to the SNMP server.
See
for a list of level keywords.
By default, warnings, errors, critical, alerts, and emergencies messages
are sent.
are sent.
Step 3
logging history size number
Specify the number of syslog messages that can be stored in the history
table.
table.
The default is to store one message. The range is 0 to 500 messages.
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.