Table 13 on page 30 specifies which messages are included in the logs on the T640 routing
nodes and the TX Matrix platform. The T640 routing nodes forward only those messages
with severity critical and higher, so the log on the TX Matrix platform does not include
the messages with severity error, warning, or notice that the T640 routing nodes log
locally:
Table 13: Example: Local Severity Is notice, Forwarded Severity Is critical
Lowest Severity IncludedSource of MessagesLog Location
noticeLocalT640 routing node
noticeLocalTX Matrix platform
criticalForwarded from T640 routing
nodes
Messages Logged When Local Severity Level Is Higher
When the severity level is higher for local messages than for forwarded messages, the
log on the TX Matrix platform includes fewer forwarded messages than when the severities
are the same, and all local logs contain fewer messages overall.
For example, you can specify severity critical for the /var/log/messages file and severity
notice for forwarded messages:
[edit system syslog]
file messages {
any critical;
}
host scc-master {
any notice;
}
Table 14 on page 30 specifies which messages are included in the logs on the T640
routing nodes and the TX Matrix platform. Although the T640 routing nodes forward
messages with severity notice and higher, the TX Matrix platform discards any of those
messages with severity lower than critical (does not log forwarded messages with severity
error, warning, or notice). None of the logs include messages with severity error or lower.
Table 14: Example: Local Severity Is critical, Forwarded Severity Is notice
Lowest Severity IncludedSource of MessagesLog Location
criticalLocalT640 routing node
criticalLocalTX Matrix platform
criticalForwarded from T640 routing
nodes
We do not recommend this type of configuration, because it wastes bandwidth for the
routing nodes to forward messages that are not recorded in the log on the TX Matrix
platform.
Copyright © 2010, Juniper Networks, Inc.30
Junos 10.3 System Log Messages Reference