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

Configuring System Logging Differently on Each Platform

We recommend that all platforms in a routing matrix use the same configuration, which implies that you include system logging configuration statements on the TX Matrix platform only. In rare circumstances, however, you might choose to log different messages on different platforms. For example, if one platform in the routing matrix is experiencing problems with authentication, a Juniper Networks support representative might instruct you to log messages from the authorization facility on that platform.

To configure platforms separately, include configuration statements in the appropriate groups at the [edit groups] hierarchy level on the TX Matrix platform:

  • To configure settings that apply to the TX Matrix platform but not the T640 routing nodes, include them in the re0 and re1 configuration groups.
  • To configure settings that apply to particular T640 routing nodes, include them in the lccn-re0 and lccn-re1 configuration groups, where n is the line-card chassis (LCC) index number of the routing node.

When you use configuration groups, do not issue CLI configuration-mode commands to change the statements at the [edit system syslog] hierarchy level on the TX Matrix platform. If you do, the resulting statements overwrite the statements defined in configuration groups and apply to the T640 routing nodes also. (We further recommend that you do not issue CLI configuration mode commands on the T640 routing nodes at any time.)

For more information about the configuration groups for a routing matrix, see the chapter about configuration groups in the JUNOS CLI User Guide.

The following example shows how to configure the /var/log/messages files on three platforms to include different sets of messages:

  • On the TX Matrix platform, local messages with severity info and higher from all facilities. The file does not include messages from the T640 routing nodes, because the host scc-master statement disables message forwarding.
  • On the T640 routing node designated LCC0, messages from the authorization facility with severity info and higher.
  • On the T640 routing node designated LCC1, messages with severity notice from all facilities.
[edit groups]
re0 {
	system {
		syslog {
			file messages {
				any info;
			}
			host scc-master {
				any none;
			}
		}
	}
}
re1 {
... same statements as for re0 ...
}
lcc0-re0 {
	system {
		syslog {
			file messages {
				authorization info;
			}
		}
	}
}
lcc0-re1 {
... same statements as for lcc0-re0 ...
}
lcc1-re0 {
	system {
		syslog {
			file messages {
				any notice;
			}
		}
	}
}
lcc0-re1 {
... same statements as for lcc1-re0 ...
}

Published: 2010-04-28

[an error occurred while processing this directive]