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

Related
Documentation
Understanding Virtual Chassis Member ID Numbering in an EX8200 Virtual Chassis
Copyright © 2010, Juniper Networks, Inc.
Chapter 44: EX8200 Virtual Chassis—Overview, Components, and Configurations
Figure 26 on page 1077 shows a basic EX8200 Virtual Chassis topology.
Figure 26: EX8200 Virtual Chassis Basic Topology
In this topology, all VCCP traffic has to travel on one of the two links, which is problematic
because the switches have to send traffic through the external Routing Engine to
communicate with each other.
There is no link redundancy in this topology. If either link fails, one of the switches is no
longer participating in the Virtual Chassis.
There is no redundant external Routing Engine in this topology. If the external Routing
Engine fails, the Virtual Chassis is no longer active.
An EX8200 Virtual Chassis full mesh topology is always recommended. Use the basic
topology only when VCP links have failed or when the equipment to configure a full mesh
topology is unavailable.
EX8200 Virtual Chassis Overview on page 1071
Understanding EX8200 Virtual Chassis Components on page 1072
Example: Setting Up a Full Mesh EX8200 Virtual Chassis with Two EX8200 Switches
and Redundant XRE200 External Routing Engines on page 1087
An EX8200 Virtual Chassis contains member IDs 0 through 9. Member IDs 0 through 7
are reserved for Juniper Networks EX8200 Ethernet Switches, which always assume the
linecard role in the EX8200 Virtual Chassis.
Member IDs 8 and 9 are reserved for the XRE200 External Routing Engines, which assume
either the master or backup role in the EX8200 Virtual Chassis. These member IDs must
be configured before configuring an EX8200 Virtual Chassis. If an XRE200 is not configured
1077