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

Complete Software Guide for Junos
Overview and Topology
970
®
OS for EX Series Ethernet Switches, Release 10.4
Before you configure the uplink module interfaces and network interfaces on Virtual
Chassis member switches as VCPs and interconnect the members to form a LAG, be
sure you have:
Installed the SFP uplink modules in the SWA-0 and SWA-2 switches and installed
1.
the XFP uplink modules in the SWA-1 and SWA-3 switches. See Installing an Uplink
Module in an EX4200 Switch.
Powered on SWA-0, connected it to the network, and run the EZSetup program. See
2.
"Connecting and Configuring an EX Series Switch (CLI Procedure)" on page 199 or
"Connecting and Configuring an EX Series Switch (J-Web Procedure)" on page 201 for
details.
Configured SWA-0 with the virtual management Ethernet (VME) interface for remote,
3.
out-of-band management of the Virtual Chassis configuration, if desired. See
"Configuring the Virtual Management Ethernet Interface for Global Management of
an EX4200 Virtual Chassis (CLI Procedure)" on page 999.
Ensured that SWA-1 is not powered on and then interconnected SWA-0 and SWA-1
4.
using the dedicated VCPs on the rear panel.
NOTE: The interfaces for the dedicated VCPs are operational by default.
They do not need to be configured.
Ensured that SWA-2, SWA-3, and SWA-4 are not powered on. They are not connected
5.
in any way, so when initially powered up they will be standalone switches.
In this example, five EX4200 switches will be interconnected to form LAGs for ease of
monitoring and manageability. Two of these switches (SWA-0 and SWA-1) are located
in wiring closet A and the three others (SWA-2, SWA-3, and SWA-4) are located in wiring
closet B. SWA-0 will form one LAG with SWA-2 and another LAG with SWA-4, and SWA-1
will form a LAG with SWA-3.
We will use fiber-optic cables connected to the uplink and network VCPs to interconnect
the member switches in wiring closet A to the member switches in wiring closet B.
We will specify the highest mastership priority value (255) for SWA-0 to make it the
master before we power on SWA-1. Because SWA-0 and SWA-1 are interconnected with
the dedicated VCPs, the master detects that SWA-1 is a member of its Virtual Chassis
configuration and assigns it a member ID.
We will use SWA-2 as the backup of the Virtual Chassis configuration. We will configure
the same mastership priority value for SWA-2 (255) that we configured for the master.
Because we power on SWA-0 before we power on SWA-2, SWA-0 retains mastership
of the Virtual Chassis configuration.
Copyright © 2010, Juniper Networks, Inc.