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

Complete Software Guide for Junos
954
®
OS for EX Series Ethernet Switches, Release 10.4
If all member switches could be interconnected with their dedicated VCPs, you could
simply power on the switches after saving and committing the preprovisioned
configuration file. The master detects the connection of the members through the
dedicated VCPs and applies the parameters specified in the preprovisioned configuration
file.
However, the Virtual Chassis cables that interconnect the VCPs of member switches
within a single wiring closet are not long enough to connect member switches across
wiring closets. Instead, you can configure the uplink module ports and the SFP networks
ports on EX4200-24F switches as VCPs to interconnect the member switches in wiring
closet A to the member switch in wiring closet B. For redundancy, this example connects
uplink VCPs from two member switches in wiring closet A (SWA–0 and SWA–2) to two
member switches (SWA-5 and SWA-7) in wiring closet B.
NOTE: You can use interfaces on SFP, SFP+, and XFP uplink modules and
the SFP network ports on EX4200-24F switches as VCPs. When an uplink
module port or SFP network port is set as a VCP, it cannot be used for any
other purpose. The SFP uplink module has four 1-Gbps ports; the SFP+ uplink
module has four 1-Gbps or two 10-Gbps ports; the XFP uplink module has
two 10-Gbps ports. The uplink module ports that are not set as VCPs can be
configured as trunk ports to connect to a distribution switch.
Because this particular preprovisioned configuration is for a Virtual Chassis that is
interconnected across wiring closets, we will bring up the Virtual Chassis configuration
in stages. First, we power on SWA-0 (without powering on any other switches) and create
the preprovisioned configuration file. Then we power on the remaining switches in wiring
closet A. If we check the status of the Virtual Chassis configuration at this point by using
the
show virtual-chassis status
4 . The members that have not yet been interconnected will not be listed.
Next power on SWA-5 without powering on the remaining switches (SWA-6 through
SWA-9) in wiring closet B. Bring up SWA-5 as a standalone switch and set one of its
uplinks as a VCP prior to interconnecting it with the Virtual Chassis configuration in wiring
closet A. Without this setting, SWA-5 cannot be detected as a member switch by the
master of the Virtual Chassis configuration.
You can set the uplink VCP of SWA–5 without running the EZSetup program by directly
connecting to the console port. If you wish, you can run the EZSetup program and specify
identification parameters. When you interconnect SWA-5 with the master of the Virtual
Chassis configuration, the master overwrites any conflicting parameters.
After setting the VCP in SWA-5, connect this VCP with the VCP of SWA-0 in wiring closet
A. SWA-5 (serial number pqr678) is specified as a
configuration file.
This example uses SWA-5 as the backup of the Virtual Chassis configuration. If a problem
occurred in wiring closet A, SWA-5 would take control of the Virtual Chassis configuration
and maintain the network connections. Specify both SWA-0 and SWA-5 as
command, it will display only
routing-engine
Copyright © 2010, Juniper Networks, Inc.
through
member 0 member
in the preprovisioned
routing-engine
.