This section explains how to configure system logging for the T640 Internet routing nodes and TX Matrix platform in a routing matrix. It assumes you are familiar with system logging for single-chassis systems, as described in Configuring System Logging for a Single-Chassis System. For more information about routing matrixes, see TX Matrix Platform Hardware Guide.
To configure system logging for all platforms in a routing matrix, include the syslog statement at the [edit system] hierarchy level on the TX Matrix platform. The syslog statement applies to every platform in the routing matrix.
- [edit system]
-
syslog {
-
-
archive {
-
files number;
-
size size;
- (world-readable | no-world-readable);
- }
-
-
console {
-
facility severity;
- }
-
-
file filename {
-
facility severity;
-
explicit-priority;
-
match "regular-expression";
-
-
structured-data {
- brief;
- }
-
-
archive {
-
files number;
-
size size;
- (world-readable | no-world-readable);
- }
- }
-
-
host (hostname | other-routing-engine | scc-master) {
-
facility severity;
-
explicit-priority;
-
facility-override facility;
-
log-prefix string;
-
match "regular-expression";
- }
-
source-address source-address;
-
time-format (year | millisecond |
year millisecond);
-
-
user (username | *) {
-
facility severity;
-
match "regular-expression";
- }
- }
When included in the configuration on the TX Matrix platform, the following configuration statements have the same effect as on a single-chassis system, except that they apply to every platform in the routing matrix:
The separate match statement at the [edit system syslog host scc-master] hierarchy level applies to messages forwarded from the T640 routing nodes to the TX Matrix platform. See Configuring Optional Features for Forwarded Messages.
The effect of the other statements differs somewhat for a routing matrix than for a single-chassis system. For more information, see the following sections: