Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual page 1107

For ex series ethernet switches
Table of Contents

Advertisement

Disabling Split and Merge in an EX4200 Virtual Chassis (CLI Procedure)
Related
Documentation
Assigning the Virtual Chassis ID to Determine Precedence During an EX4200 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 an EX4200
Virtual Chassis. You can disable the split and merge feature. If you disable the split and
merge feature and the Virtual Chassis splits, both parts of the split Virtual Chassis
configuration remain active.
In a preprovisioned EX4200 Virtual Chassis configuration, if both of the Routing Engines
end up in the same Virtual Chassis configuration after a split, the other part of the 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 an EX4200 Virtual Chassis configuration:
[edit]
user@switch# set virtual-chassis no-split-detection
Example: Assigning the Virtual Chassis ID to Determine Precedence During an EX4200
Virtual Chassis Merge on page 967
Configuring an EX4200 Virtual Chassis (CLI Procedure) on page 981
Configuring an EX4200 Virtual Chassis (J-Web Procedure) on page 985
Understanding Split and Merge in an EX4200 Virtual Chassis on page 912
Understanding EX4200 Virtual Chassis Configuration on page 904
Every EX4200 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
configurations 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 an EX4200
Virtual Chassis Merge on page 967
Configuring an EX4200 Virtual Chassis (CLI Procedure) on page 981
Configuring an EX4200 Virtual Chassis (J-Web Procedure) on page 985
Understanding Split and Merge in an EX4200 Virtual Chassis on page 912
Chapter 39: Configuring EX4200 Virtual Chassis
command. When two Virtual Chassis
1003

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos os 10.4

Table of Contents