Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Configuring System Logging Differently on Each T1600 Router in a Routing Matrix

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

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

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

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

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

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

  • On the TX Matrix Plus router, local messages with severity info and higher from all facilities. The file does not include messages from the T1600 routers, because the host sfc0-master statement disables message forwarding.
  • On the T1600 router designated LCC0, messages from the authorization facility with severity info and higher.
  • On the T1600 router designated LCC1, messages with severity notice from all facilities.
    [edit groups]re0 {system {syslog {file messages {any info;}host sfc0-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: 2012-11-15

Supported Platforms

Published: 2012-11-15