To direct system log messages to the other Routing Engine on a routing platform with
two Routing Engines installed and operational, include the host other-routing-engine
statement. The statement is not automatically reciprocal, so you must include it in each
Routing Engine’s configuration if you want them to direct messages to each other. In
each message directed to the other Routing Engine, the string re0 or re1 appears after
the timestamp to indicate the source for the message.
For the list of facilities and severity levels to configure under the host statement, see
“Specifying the Facility and Severity of Messages to Include in the Log” on page 8.
To record facility and severity level information in each message, include the
explicit-priority statement. For more information, see “Including Priority Information in
System Log Messages” on page 18.
For information about the match statement, see “Using Regular Expressions to Refine
the Set of Logged Messages” on page 22.
When directing messages to remote machines, you can include the source-address
statement to specify the IP address of the routing platform that is reported in the
messages as their source. In each host statement, you can also include the facility-override
statement to assign an alternative facility and the log-prefix statement to add a string
to each message. For more information, see the following sections:
•
Specifying an Alternative Source Address for System Log Messages on page 13
•
Changing the Alternative Facility Name for Remote Messages on page 13
•
Examples: Assigning an Alternative Facility on page 15
•
Adding a Text String to System Log Messages on page 16
•
Adding a String on page 16
Specifying an Alternative Source Address for System Log Messages
To specify the routing platform that is reported in system log messages as their source
when they are directed to a remote machine, include the source-address statement at
the [edit system syslog] hierarchy level:
[edit system syslog]
source-address source-address;
source-address is a valid IPv4 or IPv6 address configured on one of the routing platform
interfaces. The address is reported in the messages directed to all remote machines
specified in host hostname statements at the [edit system syslog] hierarchy level, but not
in messages directed to the other Routing Engine.
Changing the Alternative Facility Name for Remote Messages
Some facilities assigned to messages logged on the local routing platform have
Junos-specific names (see Table Junos System Logging Facilities in “Specifying the Facility
and Severity of Messages to Include in the Log” on page 8. In the recommended
configuration, a remote machine designated at the [edit system syslog host hostname]
hierarchy level is not a Juniper Networks routing platform, so its syslogd utility cannot
interpret the Junos-specific names. To enable the standard syslogd utility to handle
13Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...
Need help?
General
