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

Configuring Preprovisioned Member Information for a Virtual Chassis

date_range 06-Dec-23

arrow_backward

arrow_forward

To configure a Virtual Chassis for MX Series routers, you must create a preprovisioned configuration on the primary router by including the virtual-chassis stanza at the [edit virtual-chassis] hierarchy level. The preprovisioned configuration specifies the chassis serial number, member ID, and role for both member routers in the Virtual Chassis.

When a new member router joins the Virtual Chassis, the software compares its serial number against the values specified in the preprovisioned configuration. If the serial number of a joining router does not match any of the configured serial numbers, the software prevents that router from becoming a member of the Virtual Chassis.

To configure the preprovisioned member information for an MX Series Virtual Chassis:

Specify that you want to create a preprovisioned Virtual Chassis configuration.
```
[edit virtual-chassis]
user@host# set preprovisioned
```
Configure the member ID (0 or 1), role (routing-engine), and chassis serial number for each member router in the Virtual Chassis.
```
[edit virtual-chassis]
user@host# set member member-number role routing-engine serial-number serial-number
user@host# set member member-number role routing-engine serial-number serial-number
```
Note:
In a two-member MX Series Virtual Chassis configuration, you must assign the routing-engine role to each router. The routing-engine role enables the router to function either as the primary router or backup router of the Virtual Chassis.
(Optional) Enable locality bias in the Virtual Chassis configuration.
```
[edit virtual-chassis]
user@host# set locality-bias
```
Best Practice:
Starting in Junos OS Release 14.1, you can enable locality bias in the Virtual Chassis configuration. Locality bias can cause traffic loss and oversubscription on egress interfaces if you configure it in a network that is not designed to handle locality biasing. Make sure you understand the utilization requirements, such as total and available bandwidth, for the local links in your network before changing the locality bias configuration.

(Optional) Enable tracing of Virtual Chassis operations.

For example:

content_copy zoom_out_map
[edit virtual-chassis]
user@gladius# set traceoptions file filename
user@gladius# set traceoptions file size maximum-file-size
user@gladius# set traceoptions flag flag

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 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 an MX Series Virtual Chassis configuration has the same effect as issuing the commit synchronize force command.

The following example shows an MX Series Virtual Chassis preprovisioned configuration for two member routers.

content_copy zoom_out_map
[edit virtual-chassis]
user@gladius# show
preprovisioned;
no-split-detection;
locality-bias;
traceoptions {
    file vccp size 10m;
    flag all;
}
member 0 {
    role routing-engine;
    serial-number JN115FDADAFB;
}
member 1 {
    role routing-engine;
    serial-number JN10C78D1AFC;
}

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release

Description

14.1

Starting in Junos OS Release 14.1, you can enable locality bias in the Virtual Chassis configuration.

arrow_backward PREVIOUS Creating and Applying Configuration Groups for a Virtual Chassis

NEXT arrow_forward Configuring Enhanced IP Network Services for a Virtual Chassis

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

Configuring Preprovisioned Member Information for a Virtual Chassis

Change History Table

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

Configuring Preprovisioned Member Information for a Virtual Chassis

Related Documentation

Change History Table

Stay in touch