[an error occurred while processing this directive][an error occurred while processing this directive]

Directing Messages to a Remote Destination from the Routing Matrix

You can configure a routing matrix to direct system logging messages to a remote machine or the other Routing Engine on each routing platform, just as on a single-chassis system. Include the host statement at the [edit system syslog] hierarchy level on the TX Matrix platform:

[edit system syslog]
host (hostname | other-routing-engine) {
	facility severity ;
	explicit-priority;
	facility-override facility;
	log-prefix string;
	match "regular-expression";
}
source-address source-address;

The TX Matrix platform directs messages to a remote machine or the other Routing Engine in the same way as a single-chassis system, and the optional statements (explicit-priority, facility-override, log-prefix, match, and source-address) also have the same effect as on a single-chassis system.

For the TX Matrix platform to include priority information when it directs messages that originated on a T640 routing node to the remote destination, you must also include the explicit-priority statement at the [edit system syslog host scc-master] hierarchy level.

The other-routing-engine statement does not interact with message forwarding from the T640 routing nodes to the TX Matrix platform. For example, if you include the statement 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,Messages Logged When Local Severity Level Is Higher, and Messages Logged When Local and Forwarded Severity Level Are the Same.
  • 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.

Published: 2010-04-28

[an error occurred while processing this directive]