31-11
Cisco Catalyst Blade Switch 3130 for Dell Software Configuration Guide
OL-13270-01
Chapter31 Configuring System Messa ge Logging Configuring System Message Logging
Beginning in privileged EXEC mode, follow these steps to change the level and history table size
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.
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.
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 re-enable logging.
Use the show archive log config {all | number [end-number] | user username [ session number] number
[end-number] | statistics} [provisioning] privileged EXEC command to display the complete
configuration log or the log for specified parameters.
The default is that configuration logging is disabled.
For information about the commands, see the Cisco IOS Configuration Fundamentals and Network
Management Command Reference, Release 12.3 T at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_command_reference_chapter0918
6a00801a8086.html#wp1114989
Command Purpose
Step1 configure terminal Enter global configuration mode.
Step2 logging history level1
1. Table3 1-3 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.
See Table31-3 on page 31-10 for a list of level keywords.
By default, warnings, errors, critical, alerts, and emergencies messages
are sent.
Step3 logging history size number Specify the number of syslog messages that can be stored in the history
table.
The default is to store one message. The range is 0 to 500 me ssag es.
Step4 end Return to privileged EXEC mode.
Step5 show running-config Verify your entries.
Step6 copy running-config startup-config (Optional) Save your entries in the configuration file.