Reassignment; Chassis - Juniper JUNOS OS 10.3 - SOFTWARE Manual

Merging Virtual Chassis Configurations
Copyright © 2010, Juniper Networks, Inc.
It contains both the stable master and the stable backup (that is, the master and
backup from the original Virtual Chassis configuration before the split).
It contains the stable master and the configuration is greater than half the Virtual
Chassis size.
It contains the stable backup and is at least half the Virtual Chassis size.
Due to the rules given in the second and third list items, if the Virtual Chassis configuration
splits into two equal parts and the stable master and stable backup are in different parts,
then the part that contains the stable backup will become active.
NOTE: The number of members in the Virtual Chassis configuration includes
all member switches connected to date minus the number whose Virtual
Chassis member IDs have been recycled. Therefore, the size of the Virtual
Chassis configuration increases when a new member switch is detected and
decreases when a member switch's ID is recycled (that is, made available
for reassignment).
These rules ensure that only one of the two separate Virtual Chassis configurations
created by the split remains active. The member switches in the inactive Virtual Chassis
configuration remain in a linecard role. For the inactive members to become active again,
one of the following things must happen:
The problem that caused the original Virtual Chassis configuration to split is resolved,
allowing the two Virtual Chassis configurations to merge.
You load the factory default configuration on the inactive members, which causes the
inactive members to function as standalone switches or become part of a different
Virtual Chassis configuration.
NOTE: When you remove a member switch from a Virtual Chassis
configuration, you should recycle the member ID using the
virtual-chassis recycle
There are two scenarios in which separate Virtual Chassis merge:
A Virtual Chassis configuration that had split into two is now merging back into a single
configuration because the problem that had caused it to split has been resolved.
You want to merge two Virtual Chassis that had not previously been configured together.
Every Virtual Chassis configuration has a unique ID that is automatically assigned when
the Virtual Chassis configuration is formed. You can also explicitly assign a Virtual Chassis
ID using the
set virtual-chassis id
precedence over automatically assigned Virtual Chassis IDs.
Chapter 43: Virtual Chassis—Overview, Components, and Configurations
command.
command. A Virtual Chassis ID that you assign takes
request
943