[edit system syslog host hostname]
facility severity;
facility-override facility;
In general, it makes sense to specify an alternative facility that is not already in use on
the remote machine, such as one of the localX facilities. On the remote machine, you
must also configure the syslogd utility to handle the messages in the desired manner.
Table 8 on page 15 lists the facilities that you can specify in the facility-override statement.
Table 8: Facilities for the facility-override Statement
DescriptionFacility
Authentication and authorization attemptsauthorization
Actions performed or errors encountered by system processesdaemon
Actions performed or errors encountered by the FTP processftp
Actions performed or errors encountered by the Junos kernelkernel
Local facility number 0local0
Local facility number 1local1
Local facility number 2local2
Local facility number 3local3
Local facility number 4local4
Local facility number 5local5
Local facility number 6local6
Local facility number 7local7
Actions performed or errors encountered by user-space processesuser
We do not recommend including the facility-override statement at the [edit system syslog
host other-routing-engine] hierarchy level. It is not necessary to use alternative facility
names when directing messages to the other Routing Engine, because its Junos system
logging utility can interpret the Junos-specific names.
Examples: Assigning an Alternative Facility
Log all messages generated on the local routing platform at the error level or higher to
the local0 facility on the remote machine called monitor.mycompany.com:
[edit system syslog]
host monitor.mycompany.com {
any error;
15Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...
Need help?
General
