Virtual Chassis

Workflow for VC formation with Mist for EX2300, EX4650 and QFX5120

Please note that currently EX2300, EX4650 and QFX5120 do not form a virtual chassis (VC) by default, hence the following workflow to form a Virtual Chassis only applies to EX4650 and QFX5120 model switches. The other switches EX2300, EX3400, EX4100, EX4300, EX4400, EX4600 have dedicated VC ports and hence form a VC as described in...

What is a Virtual Chassis and why is it needed

Using Virtual Chassis With VC, you can combine multiple EX Series Switches, so they act as a single logical device with in the Juniper Mist cloud. Using VC eliminates the risk of loops, the need for legacy redundancy protocols such as spanning tree and VRRP, and the time required for individual device management. In core/distribution...

Adding a Switch to an Existing Virtual Chassis

The first thing to verify about the new switch to be added into the stack, is to make sure it is on its default factory configuration and that it has the same OS version as the other members in the stack; once that is verified, the next steps can be followed:   1. Power off...

Renumbering the Virtual Chassis Members

The master switch typically assumes a member ID of 0 because it is the first switch powered on. Member IDs can be assigned manually using the preprovisioned configuration method or dynamically from the master switch. If assigned dynamically, the master switch assigns each member added to the Virtual Chassis a member ID from 1 through...

Setting up Mastership Priority for Virtual Chassis

Default mastership determination: Member with highest user configured priority (1-155), default is 128. Member previously functioning as master prior to reboot Member with the longest standing time (difference must be greater than 1 minute) Member with the lowest MAC Address (used as a tie breaker if all is equal through the first three determination steps)...

Virtual Chassis – Primary and Backup Change After Reboot

When there’s a change of roles we can recover the mastership to the intended member with the following procedure, we just need to identify If the VC is preprovisioned or non-preprovisioned. Both scenarios are explained below.   Recovering Primary Role Using a Preprovisioned Configuration File Power down the master and the backup members Power on...

Virtual Chassis Formation for Mixed Mode

The below document explains how VC formation for mixed mode works using both preprovisioned and non-preprovisioned: The following is the list of supported switch model by MIST: Supported Switch Models From all the supported switches by MIST, the following ones are the only ones that can be considered as ”mixed configurable”: EX4300 EX4300-MP EX4600 If...

Virtual Chassis Member Replacement

The below document explains the process of replacing a member of an existing Virtual Chassis in Preprovisioned and Non-preprovisioned configurations. Preprovisioned This type of configuration looks like: Set virtual-chassis preprovisioned Set virtual-chassis member 0 serial-number abc123 role routing-engine Set virtual-chassis member 1 serial-number abc123 role routing-engine Set virtual-chassis member 2 serial-number abc123 role line-card  ...