 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
To create a configuration group, include the groups statement at the [edit] hierarchy level:
- [edit]
-
groups {
-
-
group-name {
-
configuration-data;
- }
-
- lccn-re0 {
-
configuration-data;
- }
-
- lccn-re1 {
-
configuration-data;
- }
- }
group-name is the name of a configuration group. You can configure more than one configuration group by specifying multiple group-name statements. However, you cannot use the prefix junos- in a group name because it is reserved for use by the JUNOS software. Similarly, the configuration group juniper-ais is reserved exclusively for Juniper Advanced Insight Solutions (AIS)-related configuration. For more information on the juniper-ais configuration group, see the Juniper Networks Advanced Insight Solutions Guide.
One reason for the naming restriction is a configuration group called junos-defaults. This preset configuration group is applied to the configuration automatically. You cannot modify or remove the junos-defaults configuration group. For more information about the JUNOS default configuration group, see Using JUNOS Default Groups.
On routers that support multiple Routing Engines, you can also specify two special group names:
The configuration specified in group re0 is only applied if the current Routing Engine is in slot 0; likewise, the configuration specified in group re1 is only applied if the current Routing Engine is in slot 1. Therefore, both Routing Engines can use the same configuration file, each using only the configuration statements that apply to it. Each re0 or re1 group contains at a minimum the configuration for the hostname and the management interface (fxp0). If each Routing Engine uses a different management interface, the group also should contain the configuration for the backup router and static routes.
In addition, the TX Matrix platform supports group names for the Routing Engines in each T640 routing node attached to the routing matrix. Providing special group names for all Routing Engines in the routing matrix allows you to configure the individual Routing Engines in each T640 routing node differently. Parameters that are not configured at the [edit groups] hierarchy level apply to all Routing Engines in the routing matrix.
configuration-data contains the configuration statements applied elsewhere in the configuration with the apply-groups statement. To have a configuration inherit the statements in a configuration group, include the apply-groups statement. For information about the apply-groups statement, see Applying a Configuration Group.
The group names for Routing Engines on the TX Matrix platform have the following formats:
n identifies the T640 routing node and can be from 0 through 3. For example, to configure Routing Engine 1 properties for lcc3, you include statements at the
[edit groups lcc3–re1] hierarchy level. For information about the TX Matrix platform and routing matrix, see the JUNOS System Basics Configuration Guide.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |