37-7
Catalyst 4500 Series, Catalyst 2948G, Catalyst 2948G-GE-TX, and Catalyst 2980G Switches Software Configuration Guide—Release 8.2GLX
78-15908-01
Chapter 37 Configuring System Message Logging
Configuring System Message Logging on the Switch
To limit the number of syslog messages, perform this task in privileged mode:
This example shows how to limit the number of syslog messages to messages with a severity level of
notifications(5):
Console> (enable) set logging history severity 5
System logging history set to severity <5>
Console> (enable)
Configuring the syslog Daemon on a UNIX syslog Server
Before you can send system log messages to a UNIX syslog server, you must configure the syslog
daemon on a UNIX server.
To configure the syslog daemon, follow these steps:
Step 1 Log in to the UNIX server as root.
Step 2 Add a line such as the following to the file /etc/syslog.conf:
user.debug /var/log/myfile.log
Note There must be five tab characters between user.debug and /var/log/myfile.log. Refer to entries
in the /etc/syslog.conf file for further examples.
The switch sends messages according to specified facility types and severity levels. The user keyword
specifies the UNIX logging facility that is used. The messages from the switch are generated by user
processes. The debug keyword specifies the severity level of the condition that is being logged. You can
set UNIX systems to receive all messages from the switch.
Step 3 Create the log file by entering these commands at the UNIX shell prompt:
$ touch /var/log/myfile.log
$ chmod 666 /var/log/myfile.log
Make sure that the syslog daemon reads the new changes by entering this command:
$ kill -HUP `cat /etc/syslog.pid
Configuring syslog Servers
Note Before you can send system log messages to a UNIX syslog server, you must configure the syslog
daemon on the UNIX server as described in the “Configuring the syslog Daemon on a UNIX syslog
Server” section on page 37-7.
Task Command
Step 1
Limit the number of syslog messages. set logging history severity severity_level
Step 2
Verify the system message logging configuration. show logging
To Next Page
Loading...
