Juniper JUNOS OS 10.3 - SOFTWARE Manual page 1093

Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual
Chassis Merge
Requirements
Overview and Topology
Copyright © 2010, Juniper Networks, Inc.
Disabling Fast Failover in a Virtual Chassis Configuration on page 1030
Configuring a Virtual Chassis (CLI Procedure) on page 1011
Configuring a Virtual Chassis (J-Web Procedure) on page 1015
You can explicitly assign a Virtual Chassis ID so that, when two Virtual Chassis
configurations merge, the ID that you assigned takes precedence over the automatically
assigned Virtual Chassis IDs and becomes the ID of the newly merged Virtual Chassis
configuration.
This example describes how to assign the Virtual Chassis ID in a Virtual Chassis
configuration:
Requirements on page 997
Overview and Topology on page 997
Configuration on page 998
Verification on page 998
This example uses the following hardware and software components:
Junos OS Release 9.3 or later for EX Series switches
Two EX4200-48P switches
Two EX4200-24T switches
Before you begin, be sure you have:
Installed the switches. See Mounting an EX3200 or EX4200 Switch on Two Posts in
1.
a Rack or Cabinet, Mounting an EX3200 or EX4200 Switch on a Desk or Other Level
Surface, or Mounting an EX3200 or EX4200 Switch on a Wall.
Cabled the switches to create the Virtual Chassis configuration. See Connecting a
2.
Virtual Chassis Cable to an EX4200 Switch.
Every Virtual Chassis configuration has a unique ID that is automatically assigned when
the Virtual Chassis configuration is formed. You can also configure a Virtual Chassis ID
using the set virtual-chassis id
Chassis ID that you assigned takes precedence over the automatically assigned Virtual
Chassis IDs and becomes the ID for the newly merged Virtual Chassis configuration.
The topology for this example consists of four switches:
Two EX4200-24T switches
Chapter 44: Virtual Chassis—Configuration Examples
command. When two Virtual Chassis merge, the Virtual
997