Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Creating a Junos Configuration Group

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 Junos OS. 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 OS Defaults Groups.

On routers that support multiple Routing Engines, you can also specify two special group names:

• re0—Configuration statements applied to the Routing Engine in slot 0.
• re1—Configuration statements applied to the Routing Engine in slot 1.

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 router supports group names for the Routing Engines in each T640 router 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 router 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 Junos Configuration Group.

The group names for Routing Engines on the TX Matrix router have the following formats:

• lccn-re0—Configuration statements applied to the Routing Engine in slot 0 in a specified T640 router.
• lccn-re1—Configuration statements applied to the Routing Engine in slot 1 in a specified T640 router.

n identifies the T640 router 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 router and routing matrix, see the Junos OS System Basics Configuration Guide.

Note: The management Ethernet interface used for the TX Matrix Plus router, T1600 or T4000 routers in a routing matrix, and PTX Series Packet Transport Switches, is em0. Junos OS automatically creates the router’s management Ethernet interface, em0.