in the configuration for the Routing Engine in slot 0 (re0), the re0 Routing Engine on each
T640 routing node sends messages to the re1 Routing Engine on its platform only. It does
not also send messages directly to the re1 Routing Engine on the TX Matrix platform.
Because the configuration on the TX Matrix platform applies to the T640 routing nodes,
any T640 routing node that has interfaces for direct access to the Internet also directs
messages to the remote machine which has the following consequences:
•
If the T640 routing nodes are configured to forward messages to the TX Matrix platform
(as in the default configuration), the remote machine receives two copies of some
messages: one directly from the T640 routing node and the other from the TX Matrix
platform. Which messages are duplicated depends on whether the severities are the
same for local logging and for forwarded messages. For more information, see
“Messages Logged When Local Severity Level Is Lower” on page 29,“Messages Logged
When Local Severity Level Is Higher” on page 30, and “Messages Logged When Local
and Forwarded Severity Level Are the Same” on page 29.
•
If the source-address statement is configured at the [edit system syslog] hierarchy
level, all platforms in the routing matrix report the same source routing platform in
messages directed to the remote machine. This is appropriate, because the routing
matrix functions as a single routing platform.
•
If the log-prefix statement is included, the messages from all platforms in the routing
matrix include the same text string. You cannot use the string to distinguish between
the platforms in the routing matrix.
Configuring System Logging Differently on Each Platform
We recommend that all platforms in a routing matrix use the same configuration, which
implies that you include system logging configuration statements on the TX Matrix
platform only. In rare circumstances, however, you might choose to log different messages
on different platforms. For example, if one platform in the routing matrix is experiencing
problems with authentication, a Juniper Networks support representative might instruct
you to log messages from the authorization facility on that platform.
To configure platforms separately, include configuration statements in the appropriate
groups at the [edit groups] hierarchy level on the TX Matrix platform:
•
To configure settings that apply to the TX Matrix platform but not the T640 routing
nodes, include them in the re0 and re1 configuration groups.
•
To configure settings that apply to particular T640 routing nodes, include them in the
lccn-re0 and lccn-re1 configuration groups, where n is the line-card chassis (LCC) index
number of the routing node.
When you use configuration groups, do not issue CLI configuration-mode commands to
change the statements at the [edit system syslog] hierarchy level on the TX Matrix
platform. If you do, the resulting statements overwrite the statements defined in
configuration groups and apply to the T640 routing nodes also. (We further recommend
that you do not issue CLI configuration mode commands on the T640 routing nodes at
any time.)
33Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...
Need help?
General
