Syntax
groups {
group-name {
configuration-data;
when {
chassis chassis-id;
member member-id;
model model-id;
node node-id;
peers [ names-of-peers ]
routing-engine routing-engine-id;
time <start-time> [to <end-time>];
}
conditional-data;
}
lccn-re0 {
configuration-data;
}
lccn-re1 {
configuration-data;
}
}
Description
Create a configuration group.
Note: Junos OS does not support configuring statements corresponding
to third-party YANG data models, for example, OpenConfig or custom
data models, under the [edit groups]
hierarchy.
Options
group-name |
Name of the configuration group. To configure multiple
groups, specify more than one group name.
|
configuration-data |
The configuration statements that are to be applied
elsewhere in the configuration with the apply-groups statement,
to have the target configuration inherit the statements in the group.
|
when |
Define conditions
under which the configuration group should be applied. Conditions
include the type of chassis, model, or Routing Engine, virtual chassis
member, cluster node, and start and optional end time of day. If you
specify multiple conditions in a single configuration group, all conditions
must be met before the configuration group is applied.
chassis chassis-id—Specify
the chassis type of the router. Valid types include SCC0, SCC1, LCC0,
LCC1 ... LCC3.
member member-id—Specify
the name of the member of the virtual chassis.
model model-id—Specify
the model name of the router, such as m7i or tx100.
node node-id—Specify
the cluster node.
peers names-of-peers—Specify
the names of the MC-LAG peers participating in commit synchronization.
routing-engine routing-engine-id—Specify the type of Routing Engine, re0 or re1.
time start-time [to end-time] —Specify the start
time or time duration for this configuration group to be applied.
If only the start time is specified, the configuration group is applied
at the specified time and remains in effect until the time is changed.
If the end time is specified, then on each day, the applied configuration
group is started and stopped at the specified times. The syntax for
specifying the time uses the format yyyy-mm-dd.hh:mm, hh:mm, or hh.
|
conditional-data |
Option introduced in Junos 11.3. The conditional statements
that are to be applied when this configuration group is applied. On
routers that support multiple Routing Engines, you can also specify
two special group names:
On routers that support multiple Routing Engines, you can also
specify two special group names:
The configuration specified in group re0 is applied
only if the current Routing Engine is in slot 0; likewise, the configuration
specified in group re1 is applied only 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.
(Routing matrix only) The TX Matrix router supports group names
for the Routing Engines in each connected T640 router in the following
formats:
Note: The management Ethernet interface used for the TX Matrix
Plus router, T1600 routers in a routing matrix, and PTX Series Packet
Transport Routers, is em0 . Junos OS automatically creates
the router’s management Ethernet interface, em0 .
lccn-re0 —Configuration
statements applied to the Routing Engine in slot 0 of the specified
T640 router that is connected to a TX Matrix router.
lccn-re1 —Configuration
statements applied to the specified to the Routing Engine in slot
1 of the specified T640 router that is connected to a TX Matrix router.
n identifies the T640 router
and can be from 0 through 3.
|
Required Privilege Level
configure—To enter configuration mode.
Release Information
Statement introduced before Junos OS Release
7.4.