close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- Interchassis Redundancy and Virtual Chassis Overview
play_arrow Understanding How a Virtual Chassis Works
play_arrow Configuring a Virtual Chassis
play_arrow Configuring Virtual Chassis Ports to Interconnect Member Devices
play_arrow Configuring Locality Bias to Conserve Bandwidth on Virtual Chassis Ports
play_arrow Configuring Class of Service for Virtual Chassis Ports
play_arrow Configuring Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
play_arrow Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
- Example: Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Unified In-Service Software Upgrade (ISSU)
play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Sequential Upgrade
- How to Use Sequential Upgrade in an MX Series Virtual Chassis
play_arrow Monitoring an MX Series Virtual Chassis
play_arrow Tracing Virtual Chassis Operations for Troubleshooting Purposes
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

keyboard_arrow_right

Creating and Applying Configuration Groups for a Virtual Chassis

date_range 06-Dec-23

arrow_backward

arrow_forward

For a Virtual Chassis configuration consisting of two MX Series routers or two EX9200 switches, each of which supports dual Routing Engines, you must create and apply on the primary device of the Virtual Chassis the following configuration groups, instead of using the standard re0 and re1 configuration groups:

member0-re0
member0-re1
member1-re0
member1-re1

Note:

The membern-ren naming format for configuration groups is reserved for exclusive use by member routers or switches in EX9200 or MX Series Virtual Chassis configurations.

Using configuration group names of the form membern-ren in an existing non-Virtual Chassis configuration or configuration script could interfere with Virtual Chassis operation. This misconfiguration could cause the router or switch to assign no IP address or an incorrect IP address to the fxp0 management Ethernet interface, and could result in a display of the Amnesiac prompt during login.

To create and apply configuration group information from the router or switch to be configured as the primary of the Virtual Chassis:

In the console window on the primary router or switch (member 0 in this procedure), create and apply the member0-re0 configuration group.
```
[edit]
user@host# copy groups re0 to member0-re0
user@host# set apply-groups member0-re0
```
Delete the standard re0 configuration group from the global configuration on member 0.
```
[edit]
user@host# delete apply-groups re0
user@host# delete groups re0
```

Create and apply the member0-re1 configuration group.

content_copy zoom_out_map
[edit]
user@host# copy groups re1 to member0-re1
user@host# set apply-groups member0-re1

Delete the standard re1 configuration group from the global configuration on member 0.
```
[edit]
user@host# delete apply-groups re1
user@host# delete groups re1
```

Create and apply the member1-re0 configuration information.

content_copy zoom_out_map
[edit]
user@host# set groups member1-re0 system host-name host-name
user@host# set groups member1-re0 system backup-router address
user@host# set groups member1-re0 system backup-router destination destination-address
user@host# set groups member1-re0 system backup-router destination destination-address
...
user@host# set groups member1-re0 interfaces fxp0 unit unit-number family inet address address
user@host# set apply-groups member1-re0

The commands in Steps 5 and 6 set the IP address for the fxp0 management interface and add an IP route for it in the event that routing becomes inactive.

Create and apply the member1-re1 configuration information.

content_copy zoom_out_map
[edit]
user@host# set groups member1-re1 system host-name host-name
user@host# set groups member1-re1 system backup-router address
user@host# set groups member1-re1 system backup-router destination destination-address
user@host# set groups member1-re1 system backup-router destination destination-address
...
user@host# set groups member1-re1 interfaces fxp0 unit unit-number family inet address address
user@host# set apply-groups member1-re1

Commit the configuration.

Best Practice:
We recommend that you use the commit synchronize command to save any configuration changes to the Virtual Chassis.

For an EX9200 or MX Series Virtual Chassis, the force option is the default and only behavior when you issue the commit synchronize command. Issuing the commit synchronize command for a Virtual Chassis configuration has the same effect as issuing the commit synchronize force command.

arrow_backward PREVIOUS Preparing for a Virtual Chassis Configuration

NEXT arrow_forward Configuring Preprovisioned Member Information for a Virtual Chassis

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

Creating and Applying Configuration Groups for a Virtual Chassis

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

Creating and Applying Configuration Groups for a Virtual Chassis

Related Documentation

Stay in touch