Synchronizing Log Messages - Cisco Catalyst 2960 Software Configuration Manual
Hide thumbs
Also See for Catalyst 2960:
- Configuration manual (2288 pages) ,
- Command reference manual (800 pages) ,
- Hardware installation manual (108 pages)
Table of Contents
Advertisement
Configuring System Message Logging
Command
Step 4
logging file flash:filename
[max-file-size [min-file-size]]
[severity-level-number | type]
Step 5
end
Step 6
terminal monitor
Step 7
show running-config
Step 8
copy running-config startup-config
The logging buffered global configuration command copies logging messages to an internal buffer. The
buffer is circular, so newer messages overwrite older messages after the buffer is full. To display the
messages that are logged in the buffer, use the show logging privileged EXEC command. The first
message displayed is the oldest message in the buffer. To clear the contents of the buffer, use the clear
logging privileged EXEC command.
Use the logging event power-inline-status interface configuration command to enable and to disable
logging of Power over Ethernet (PoE) events on specific PoE-capable ports. Logging on these ports is
enabled by default.
To disable logging to the console, use the no logging console global configuration command. To disable
logging to a file, use the no logging file [severity-level-number | type] global configuration command.
Synchronizing Log Messages
You can synchronize unsolicited messages and debug privileged EXEC command output with solicited
device output and prompts for a specific console port line or virtual terminal line. You can identify the
types of messages to be output asynchronously based on the level of severity. You can also configure the
maximum number of buffers for storing asynchronous messages for the terminal after which messages
are dropped.
When synchronous logging of unsolicited messages and debug command output is enabled, unsolicited
device output appears on the console or printed after solicited device output appears or is printed.
Unsolicited messages and debug command output appears on the console after the prompt for user input
is returned. Therefore, unsolicited messages and debug command output are not interspersed with
solicited device output and prompts. After the unsolicited messages appear, the console again displays
the user prompt.
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE
29-6
Purpose
Store log messages in a file in flash memory on a standalone switch or, in
the case of a switch stack, on the stack master.
•
For filename, enter the log message filename.
•
(Optional) For max-file-size, specify the maximum logging file size.
The range is 4096 to 2147483647. The default is 4096 bytes.
•
(Optional) For min-file-size, specify the minimum logging file size.
The range is 1024 to 2147483647. The default is 2048 bytes.
(Optional) For severity-level-number | type, specify either the logging
•
severity level or the logging type. The severity range is 0 to 7. For a
list of logging type keywords, see
default, the log file receives debugging messages and numerically
lower levels.
Return to privileged EXEC mode.
Log messages to a nonconsole terminal during the current session.
Terminal parameter-setting commands are set locally and do not remain
in effect after the session has ended. You must perform this step for each
session to see the debugging messages.
Verify your entries.
(Optional) Save your entries in the configuration file.
Chapter 29
Configuring System Message Logging
Table 29-3 on page
29-10. By
OL-26520-01
Hide quick links:
Advertisement
Chapters
Table of Contents
Troubleshooting
