|
|
This chapter describes:
For information about starting and stopping the Syslog service, setting basic options, and controlling access to Syslog, see the chapter titled "Configuring Services with the Service Configuration Manager".
The Syslog service receives messages from applications on the local host or from remote hosts (for example, a router or a printer) that have been configured to forward messages. Syslog directs messages to a log file. To each message that Syslog handles, it adds a timestamp, the message type keyword at the beginning of the message, and a newline at the end of the message.
The default message log for informational messages from the services is MultiNet/log/info.log, which is located in the directory where you installed the CDDM or the Cisco Server Suite 1000.
 | Caution If you use Cisco's Syslog service, messages from your operating system utilities that attempt to use the native syslog routines are not logged. Therefore, you may not be notified about problems with your system. |
Syslog forwards messages based on message class. The message class is a combination of the facility that issues the message and the priority. Table 6-1 shows the facilities and the keyword associated with each facility. Keywords local0 through local7 are for other, user-defined services. Although some of these keywords are pre-assigned to facilities, you may use them if you are not running those facilities.
| Facility | Keyword |
|---|---|
| Authorization messages | auth or security |
| BootP messages | bootp |
| Daemon (background processes) messages | daemon |
| Domain Name System messages | named |
| GATED (gateway messages) | gated |
| Kernel messages | kern |
| Mail utility messages | |
| Network Time Protocol (NTP) messages | ntp |
| User-defined service | local0 |
| User-defined service | local1 (also used by BootP) |
| User-defined service | local2 (also used by BIND) |
| User-defined service | local3 (also used by GATED) |
| User-defined service | local4 |
| User-defined service | local5 (also used by NTP) |
| User-defined service | local6 |
| User-defined service | local7 |
Message priorities follow, listed from most severe to least severe:
The message class is in the form message type.priority level. Some examples of message classes are listed in Table 6-2.
| Example | Description |
|---|---|
| ntp.info | NTP messages with priority of info (information messages) |
| gated.warn | GATED messages with priority of warn (warning messages) |
| *.debug | All messages with debug priority |
| security.* | Authorization and security services messages of all priorities |
Syslog forwards system messages to different log files based on message class. To specify the log files for the different message classes:
Step 1 Start the SCM.
Step 2 Select Syslog in the Available Services box.
Step 3 Click on the Config tab.
Step 4 Enter the message class in the format message type.priority level in the Class field.
Step 5 Enter the path and file name of the log file in the Log File field. The default log files are shown are shown in the screen for each service.
To forward messages to a log file on a different host, enter @hostname (where hostname is the host where messages should be logged) in the Log File field. The other host must be running a syslog daemon.
Step 6 Click on Add.
Step 7 Repeat steps 4 through 6 until you have added all of your message classes and log files.
Step 8 Choose Save Configuration from the File menu.
Changes take effect after you stop and restart the Syslog service.
|
|