Technical data

Configuring and Managing Routers with Site Manager
D-2 117347-A Rev. A
Configuring the syslogd Daemon
You must configure the UNIX syslogd daemon to specify the log files and the
remote hosts that should receive event messages. To do this, you must edit the file
etc/syslog.conf on each remote host.
The syslogd daemon determines where to write event messages based on the
following:
•A priority code that the syslog application attaches to each event message
• Event data from the syslog.conf file
The priority code consists of a facility and a level.
• The facility describes the system that originates the event message using the
standard (configurable) UNIX facility names LOCAL0 through LOCAL7.
• The level is the UNIX error level (emerg, alert, crit, err, warning, notice, info,
debug) that you associate with the event message severity level (fault, trace,
warning, information, and debug).
For example, you might map all router fault messages to the UNIX CRIT error
level. You can map more than one router severity level to the same UNIX error
level.
You can also assign a facility and severity levels to error levels. For example,
suppose you want to log all fault, warning, and debug messages that the syslogd
daemon receives from the router to a file, for example, /usr/adm/logs/baynet.log,
on the remote host. Assume also that you used Site Manager to map fault
messages to the CRIT error level, warning messages to the WARNING error level,
and debug messages to the UNIX DEBUG level.
You might add a line similar to the following to your syslog.conf file:
local7.crit;local7.warning;local7.debug /usr/adm/logs/baynet.log
Be sure that you use a tab before the path to the file, in this example,
/usr/adm/logs/baynet.log.
In this example, the facility is LOCAL7.
For more information about the syslogd daemon and the syslog.conf file, refer to
the instructions provided in the UNIX man pages.