Juniper JUNOS OS 10.3 - SOFTWARE Manual page 1127

Disabling Split and Merge in a Virtual Chassis Configuration (CLI Procedure)
Related
Documentation
Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis
Merge (CLI Procedure)
Related
Documentation
Copyright © 2010, Juniper Networks, Inc.
The split and merge feature is enabled by default on EX4200 switches in a Virtual Chassis
configuration. You can disable the split and merge feature using the
command. If you disable the split and merge feature and the Virtual
no-split-detection
Chassis configuration splits, both parts of the split Virtual Chassis configuration remain
active.
In a preprovisioned Virtual Chassis configuration, if both of the Routing Engines end up
in the same Virtual Chassis configuration after a split, the other split Virtual Chassis
configuration remains inactive. If the Routing Engines end up in different parts of the split
Virtual Chassis configuration and the rest of the member switches are configured as
having linecard roles, then a backup Routing Engine might not be selected for either part.
To disable the split and merge feature in a Virtual Chassis configuration:
[edit]
user@switch# set virtual-chassis no-split-detection
Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual
Chassis Merge on page 997
Configuring a Virtual Chassis (CLI Procedure) on page 1011
Configuring a Virtual Chassis (J-Web Procedure) on page 1015
Understanding Split and Merge in a Virtual Chassis Configuration on page 942
Understanding Virtual Chassis Configuration on page 934
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
attempt to merge, the Virtual 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.
To configure the Virtual Chassis ID:
[edit]
user@switch# set virtual-chassis id id
Example: Assigning the Virtual Chassis ID to Determine Precedence During a Virtual
Chassis Merge on page 997
Configuring a Virtual Chassis (CLI Procedure) on page 1011
Configuring a Virtual Chassis (J-Web Procedure) on page 1015
Understanding Split and Merge in a Virtual Chassis Configuration on page 942
Chapter 45: Configuring Virtual Chassis
command. When two Virtual Chassis configurations
set virtual-chassis
1031