Avaya Managing Routers and BNX Platforms Manual de usuario descargar pdf (Pagina 216)

Managing Routers and BNX Platforms

B-2

Conﬁguring the

syslogd

Daemon

You must conﬁgure the UNIX syslogd daemon to specify the log ﬁles and users to

which you want to forward event messages. To do this, you must edit the ﬁle

etc/syslog.conf on each remote host. The syslogd daemon determines where to

write event messages based on

•A priority code that the syslog application attaches to each event message

• Event data from the syslog.conf ﬁle

The priority code consists of a facility and a level. The facility describes the

system that originates the event message using the standard (conﬁgurable) UNIX

facility names LOCAL0 through LOCAL7. The level is the UNIX error level

(EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG) that you

assign (map) to the severity level (fault, trace, warning, information, and debug)

of the router event message.

For example, you might map all router fault messages to the UNIX CRIT error

level. You could map more than one router severity level to the same UNIX error

level. You can use Site Manager to assign a facility and to map severity levels to

error levels, as described later.

For example, suppose you want to log all fault, warning, and debug messages that

syslogd receives from the router to a ﬁle (/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 ﬁle:

local7.crit;local7.warning;local7.debug /usr/adm/logs/baynet.log

In this example, the facility is LOCAL7.

For more information on syslogd and syslog.conf, refer to the instructions

provided in the UNIX man pages.

1 2 ... 211 212 213 214 215 216 217 218 219 220 221 ... 249 250

Sin comentarios

Avaya Managing Routers and BNX Platforms Manual de usuario Pagina 216