Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Configuring Message Forwarding to the TX Matrix Plus Router

From the perspective of the user interface, the routing matrix appears as a single router. The TX Matrix Plus router (also called the switch-fabric chassis SFC) controls all the T1600 or T4000 routers (also called the line-card chassis LCC) in the routing matrix.

By default, the master Routing Engine on each connected T1600 or T4000 LCC forwards to the master Routing Engine on the SFC all messages from all facilities with severity level of info and higher. To change the facility, the severity level, or both, include the host sfc0-master statement at the [edit system syslog] hierarchy level on the SFC:

[edit system syslog]
host sfc0-master {facility severity;}

To disable message forwarding, set the facility to any and the severity level to none:

[edit system syslog]
host sfc0-master {any none;}

In either case, the setting applies to all connected LCCs in the routing matrix.

To capture the messages forwarded by the T1600 or T4000 LCCs (as well as messages generated on the SFC itself), you must also configure system logging on the SFC. Direct the messages to one or more destinations by including the appropriate statements at the [edit system syslog] hierarchy level on the SFC:

As previously noted, the configuration statements included on the SFC also configure the same destinations on each connected LCC.

When specifying the severity level for local messages (at the [edit system syslog (file | host | console | user)] hierarchy level) and forwarded messages (at the [edit system syslog host sfc0-master] hierarchy level), you can set the same severity level for both, set a lower severity level for local messages, or set a higher severity level for local messages. The following examples describe the consequence of each configuration. (For simplicity, the examples use the any facility in every case. You can also specify different severities for different facilities, with more complex consequences.)

Published: 2013-02-22

Supported Platforms

Published: 2013-02-22