C H A P T E R
17-1
Catalyst 3550 Multilayer Switch Software Configuration Guide
78-11194-03
17
Configuring System Message Logging
This chapter describes how to configure system message logging on your switch.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco
IOS Configuration Fundamentals Command Reference for Release 12.1.
This chapter consists of these sections:
•
Understanding System Message Logging, page 17-1
•
Configuring System Message Logging, page 17-2
•
Displaying the Logging Configuration, page 17-12
Understanding System Message Logging
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.
Note
The syslog format is compatible with 4.3 BSD UNIX.
When the logging process is disabled, messages are sent only to the console. The messages are sent as
they are generated, so message and debug output are interspersed with prompts or output from other
commands. Messages are displayed on the console after the process that generated them has finished.
You can set the severity level of the messages to control the type of messages displayed on the console
and each of the destinations. You can timestamp log messages or set the syslog source address to enhance
real-time debugging and management. For information on possible messages, refer to the Catalyst 3550
Multilayer Switch System Message Guide for this release.
You can access logged system messages by using the switch command-line interface (CLI) or by saving
them to a properly configured syslog server. The switch software saves syslog messages in an internal
buffer. You can remotely monitor system messages by accessing the switch through Telnet, through the
console port, or by viewing the logs on a syslog server.