[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Message Forwarding in the Routing Matrix

By default, the master Routing Engine on each T640 routing node forwards to the master Routing Engine on the TX Matrix platform all messages from all facilities with severity level of info and higher. To change the facility, the severity level, or both, include the host scc-master statement at the [edit system syslog] hierarchy level on the TX Matrix platform:



[edit system syslog]

host scc-master {

facility severity;
}

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



[edit system syslog]

host scc-master {
any none;
}

In either case, the setting applies to all T640 routing nodes in the routing matrix.

To capture the messages forwarded by the T640 routing nodes (as well as messages generated on the TX Matrix platform itself), you must also configure system logging on the TX Matrix platform. Direct the messages to one or more destinations by including the appropriate statements at the [edit system syslog] hierarchy level on the TX Matrix platform:

To a file, as described in Directing Messages to a Log File.
To the terminal session of one or more specific users (or all users), as described in Directing Messages to a User Terminal.
To the console, as described in Directing Messages to the Console.
To a remote machine that is running the syslogd utility or to the other Routing Engine. For more information, see Directing Messages to a Remote Destination from the Routing Matrix.

As previously noted, the configuration statements included on the TX Matrix platform also configure the same destinations on each T640 routing node.

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 scc-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.)

[Contents] [Prev] [Next] [Index] [Report an Error]