Juniper EX9200 Series Specification sheet

Virtual Chassis Feature Guide for EX9200 Switches
Modified: 2017-05-22
Copyright © 2017, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Virtual Chassis Feature Guide for EX9200 Switches
Copyright © 2017, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
Copyright © 2017, Juniper Networks, Inc.ii

Table of Contents
AbouttheDocumentation............................................ix
DocumentationandReleaseNotes..................................ix
SupportedPlatforms.............................................ix
UsingtheExamplesinThisManual..................................ix
MergingaFullExample........................................x
MergingaSnippet............................................x
DocumentationConventions.......................................xi
Documentation Feedback........................................xiii
RequestingTechnicalSupport.....................................xiii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
OpeningaCasewithJTAC.....................................xiv
Chapter1 VirtualChassisOverview...........................................15
Understanding EX9200 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Understanding EX Series Virtual Chassis Components . . . . . . . . . . . . . . . . . . . . . 16
Maximum Number of Switches per Virtual Chassis . . . . . . . . . . . . . . . . . . . . . 16
VirtualChassisPorts(VCPs).......................................18
Master Role ....................................................19
Backup Role ...................................................20
Linecard Role ..................................................20
MemberSwitchandMemberID....................................21
MastershipPriority...............................................22
MixedVirtualChassis............................................22
VirtualChassisIdentifier(VCID)....................................23
Part 1 Configuring a Virtual Chassis
Chapter 2 Accessing and Configuring a Virtual Chassis and Managing Files . . . . . . . . 27
Accessing the Virtual Chassis Through the Management Interface . . . . . . . . . . . 28
Managing Files on Virtual Chassis Member Routers or Switches . . . . . . . . . . . . . . 29
Virtual Chassis Slot Number Mapping for Use with SNMP . . . . . . . . . . . . . . . . . . 30
Configuring an EX9200 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Creating Configuration Groups for an EX9200 Virtual Chassis . . . . . . . . . . . . 32
Configuring the EX9200 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creating and Applying Configuration Groups for a Virtual Chassis . . . . . . . . . . . . 36
Chapter3 VirtualChassisPorts..............................................39
Configuring Virtual Chassis Ports to Interconnect Member Routers or
Switches ......................................................40
Deleting Virtual Chassis Ports in a Virtual Chassis Configuration . . . . . . . . . . . . . 42
Verifying the Operation of Virtual Chassis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
iiiCopyright © 2017, Juniper Networks, Inc.

Chapter 4 Upgrading Junos OS in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Upgrading Junos OS Software in an EX9200 Virtual Chassis . . . . . . . . . . . . . . . . 45
Chapter5 DeletingaMemberID..............................................49
Deleting Member IDs in a Virtual Chassis Configuration . . . . . . . . . . . . . . . . . . . . 49
Chapter6 ModuleRedundancyandGRES.....................................51
Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual
Chassis........................................................51
Targeted Distribution in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
BenefitsofTargetedDistribution...................................52
Configuring Module Redundancy for a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . 52
Determining GRES Readiness in a Virtual Chassis Configuration . . . . . . . . . . . . . 54
Chapter 7 Global Roles and Local Roles that Determine Mastership and Switchover
Behavior .........................................................57
Mastership Election in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Global Roles and Local Roles in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 59
RoleNameFormat..............................................59
Global Role and Local Role Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Switching the Global Master and Backup Roles in a Virtual Chassis
Configuration ...................................................61
Chapter 8 Minimizing Network Disruption Using Split Detection . . . . . . . . . . . . . . . . . . 63
Split Detection Behavior in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
How Split Detection Works in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . 63
Effect of Split Detection on Virtual Chassis Failure Scenarios . . . . . . . . . . . . 64
Disabling Split Detection in a Virtual Chassis Configuration . . . . . . . . . . . . . . . . . 68
Part 2 Troubleshooting
Chapter 9 Acquiring Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring the Name of the Virtual Chassis Trace Log File . . . . . . . . . . . . . . . . . . 71
Configuring Characteristics of the Virtual Chassis Trace Log File . . . . . . . . . . . . . . 72
Configuring Access to the Virtual Chassis Trace Log File . . . . . . . . . . . . . . . . . . . . 73
Using Regular Expressions to Refine the Output of the Virtual Chassis Trace Log
File ...........................................................74
Configuring the Virtual Chassis Operations to Trace . . . . . . . . . . . . . . . . . . . . . . . . 75
traceoptions(VirtualChassis).........................................77
Part 3 Routine Monitoring
Chapter10 MonitoringaVirtualChassis........................................83
Verifying the Status of Virtual Chassis Member Routers or Switches . . . . . . . . . . 83
Verifying Neighbor Reachability for Member Routers or Switches in a Virtual
Chassis .......................................................83
Verifying Neighbor Reachability for Hardware Devices in a Virtual Chassis . . . . . 84
Viewing Information in the Virtual Chassis Control Protocol Adjacency
Database......................................................85
Viewing Information in the Virtual Chassis Control Protocol Link-State
Database......................................................85
Copyright © 2017, Juniper Networks, Inc.iv
Virtual Chassis Feature Guide for EX9200 Switches

Viewing Information About Virtual Chassis Port Interfaces in the Virtual Chassis
ControlProtocolDatabase........................................86
Viewing Virtual Chassis Control Protocol Statistics for Member Devices and
VirtualChassisPorts.............................................87
Part 4 Configuration Statements and Operational Commands
Chapter11 ConfigurationStatements..........................................91
aggregated-ether-options............................................92
logical-interface-fpc-redundancy (Aggregated Ethernet Subscriber
Interfaces).....................................................93
member ..........................................................94
no-split-detection ..................................................95
preprovisioned .....................................................96
role ..............................................................97
serial-number .....................................................99
targeted-distribution (Static Interfaces over Aggregated Ethernet) . . . . . . . . . . 100
traceoptions(VirtualChassis)........................................101
virtual-chassis ....................................................104
Chapter 12 Operational Commands: Administrative . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
request virtual-chassis member-id delete (MX Series Virtual Chassis) . . . . . . . 108
request virtual-chassis member-id set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
request virtual-chassis routing-engine master switch . . . . . . . . . . . . . . . . . . . . . . 111
requestvirtual-chassisvc-port........................................113
Chapter 13 Operational Commands: Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
show virtual-chassis active-topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
show virtual-chassis device-topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
show virtual-chassis protocol adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
show virtual-chassis protocol database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
show virtual-chassis protocol interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
showvirtual-chassisprotocolroute....................................138
show virtual-chassis protocol statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
showvirtual-chassis................................................144
showvirtual-chassisvc-port.........................................149
vCopyright © 2017, Juniper Networks, Inc.
Table of Contents

Copyright © 2017, Juniper Networks, Inc.vi
Virtual Chassis Feature Guide for EX9200 Switches

List of Tables
AbouttheDocumentation..........................................ix
Table1:NoticeIcons..................................................xi
Table2:TextandSyntaxConventions...................................xii
Chapter1 VirtualChassisOverview...........................................15
Table 3: Maximum Member Switch Support for Virtual Chassis by Junos OS
Release........................................................16
Part 1 Configuring a Virtual Chassis
Chapter 2 Accessing and Configuring a Virtual Chassis and Managing Files . . . . . . . . 27
Table 4: jnxFruSlot Numbers and Corresponding Slot Numbers in an MX Series
orEX9200VirtualChassis........................................30
Chapter 7 Global Roles and Local Roles that Determine Mastership and Switchover
Behavior .........................................................57
Table5:GlobalRolesandLocalRoles..................................60
Table 6: Virtual Chassis Global Role Transitions Before and After Mastership
Switchover ....................................................62
Chapter 8 Minimizing Network Disruption Using Split Detection . . . . . . . . . . . . . . . . . . 63
Table 7: Effect of Split Detection on Common Virtual Chassis Failure
Scenarios .....................................................64
Part 2 Troubleshooting
Chapter 9 Acquiring Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 8: Tracing Flags for Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Part 4 Configuration Statements and Operational Commands
Chapter 13 Operational Commands: Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 9: show virtual-chassis active-topology Output Fields . . . . . . . . . . . . . . . . 116
Table 10: show virtual-chassis device-topology Output Fields . . . . . . . . . . . . . . . 121
Table 11: show virtual-chassis protocol adjacency Output Fields . . . . . . . . . . . . . 128
Table 12: show virtual-chassis protocol database Output Fields . . . . . . . . . . . . . 132
Table 13: show virtual-chassis protocol interface Output Fields . . . . . . . . . . . . . 136
Table 14: show virtual-chassis protocol route Output Fields . . . . . . . . . . . . . . . . 138
Table 15: show virtual-chassis protocol statistics Output Fields . . . . . . . . . . . . . . 141
Table 16: show virtual-chassis Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Table 17: show virtual-chassis vc-port Output Fields . . . . . . . . . . . . . . . . . . . . . . 149
viiCopyright © 2017, Juniper Networks, Inc.

Copyright © 2017, Juniper Networks, Inc.viii
Virtual Chassis Feature Guide for EX9200 Switches

About the Documentation
•Documentation and Release Notes on page ix
•Supported Platforms on page ix
•Using the Examples in This Manual on page ix
•Documentation Conventions on page xi
•Documentation Feedback on page xiii
•Requesting Technical Support on page xiii
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
•EX Series
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
ixCopyright © 2017, Juniper Networks, Inc.

If the example configuration does not start at the top level of the hierarchy, the example
isasnippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
Copyright © 2017, Juniper Networks, Inc.x
Virtual Chassis Feature Guide for EX9200 Switches

2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xi defines notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xii defines the text and syntax conventions used in this guide.
xiCopyright © 2017, Juniper Networks, Inc.
About the Documentation

Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type.Bold text like this
user@host> show chassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
•A policy term is a named structure
that defines match conditions and
actions.
•Junos OS CLI User Guide
•RFC 1997, BGP Communities Attribute
•Introduces or emphasizes important
new terms.
•Identifies guide names.
•Identifies RFC and Internet draft titles.
Italic text like this
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
•To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•The console port is labeled CONSOLE.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)
broadcast | multicast
(string1 |string2 |string3)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
| (pipe symbol)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
same line as the configuration statement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
Copyright © 2017, Juniper Networks, Inc.xii
Virtual Chassis Feature Guide for EX9200 Switches

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
•In the Logical Interfaces box, select
All Interfaces.
•To cancel the configuration, click
Cancel.
Represents graphical user interface (GUI)
items you click or select.
Bold text like this
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of menu
selections.
>(bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/.
•E-mail—Send your comments to [e-mail]. Include the document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
support contract, or are covered under warranty, and need post-sales technical support,
you can access our tools and resources online or open a case with JTAC.
•JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
xiiiCopyright © 2017, Juniper Networks, Inc.
About the Documentation

•Find CSC offerings: http://www.juniper.net/customers/support/
•Search for known bugs: http://www2.juniper.net/kb/
•Find product documentation: http://www.juniper.net/techpubs/
•Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2017, Juniper Networks, Inc.xiv
Virtual Chassis Feature Guide for EX9200 Switches

CHAPTER 1
Virtual Chassis Overview
•Understanding EX9200 Virtual Chassis on page 15
•Understanding EX Series Virtual Chassis Components on page 16
Understanding EX9200 Virtual Chassis
NOTE: For deployments with EX9200 switches, we recommend planning or
moving to MC-LAG or Junos Fusion Enterprise architectures rather than using
a Virtual Chassis. We do not recommend using EX9200 switches in a Virtual
Chassis.
EX9200 Virtual Chassis brings the Virtual Chassis flexible, scaling switch solution to
Juniper Networks EX9200 Ethernet Switches. You can connect two EX9200 switches
into an EX9200 Virtual Chassis and manage the interconnected switches as a single
chassis. The advantages of connecting multiple switches into a Virtual Chassis include
better-managed bandwidth at a network layer, simplified configuration and maintenance
because multiple devices can be managed as a single device, increased fault tolerance
and high availability (HA) because a Virtual Chassis can remain active and network traffic
can be redirected to other member switches when a single member switch fails, and a
flatter, simplified Layer 2 network topology that minimizes or eliminates the need for
loop prevention protocols such as Spanning Tree Protocol (STP).
NOTE: Starting with Junos OS Release 17.1R1, EX9200 switches support
EX9200-RE2 module. You cannot form a Virtual Chassis using an EX9200
switch with an EX9200-RE2 module installed in it.
You configure an EX9200 Virtual Chassis by configuring optical interfaces into Virtual
Chassis ports (VCPs). VCPs connect switches together to form a Virtual Chassis, and
are responsible for passing all data and control traffic between member switches in the
Virtual Chassis.
You can increase VCP bandwidth between member switches by configuring multiple
interfaces between the same two switches into VCPs. When multiple VCPs are
interconnecting the same two member switches, a link aggregation group (LAG) bundle
is automatically formed when the VCPs are on interfaces supporting identical speeds.
15Copyright © 2017, Juniper Networks, Inc.

For instance, if you have two 10-Gigabit SFP+ interfaces configured as VCPs between
member switches, a LAG with two member links with 20 Gbps of total bandwidth is
formed.
An EX9200 Virtual Chassis can be composed of any two EX9200 switches. Both EX9200
switches must have dual Routing Engines installed, and all Routing Engines must be
running the same version of Junos OS. All combinations of EX9204, EX9208, and EX9214
switches can be interconnected to form a Virtual Chassis.
Related
Documentation
Configuring an EX9200 Virtual Chassis on page 32•
Understanding EX Series Virtual Chassis Components
NOTE: This topic applies to all EX Series Virtual Chassis except EX8200
Virtual Chassis.
This topic describes the components of EX Series Virtual Chassis—including the
components of any mixed Virtual Chassis that contains EX series member
switches—except EX8200 Virtual Chassis.
This topic covers:
•Maximum Number of Switches per Virtual Chassis on page 16
•Virtual Chassis Ports (VCPs) on page 18
•Master Role on page 19
•Backup Role on page 20
•Linecard Role on page 20
•Member Switch and Member ID on page 21
•Mastership Priority on page 22
•Mixed Virtual Chassis on page 22
•Virtual Chassis Identifier (VCID) on page 23
Maximum Number of Switches per Virtual Chassis
The maximum number of switches that a Virtual Chassis supports varies by Virtual
Chassis and can depend on the Junos OS release running on the Virtual Chassis.
Table 3 on page 16 lists the maximum member switch support by Virtual Chassis and
Junos OS release.
Table 3: Maximum Member Switch Support for Virtual Chassis by Junos
OS Release
Initial Junos OS ReleaseMaximum Member Switch Support
12.2R1—Initial release. Support for up to four
EX2200 member switches.
EX2200 Virtual Chassis
Copyright © 2017, Juniper Networks, Inc.16
Virtual Chassis Feature Guide for EX9200 Switches

Table 3: Maximum Member Switch Support for Virtual Chassis by Junos
OS Release (continued)
Initial Junos OS ReleaseMaximum Member Switch Support
15.1X53-D50—Initial release. Support for up to
four EX2300 member switches.
EX2300 Virtual Chassis
11.3R1—Initial release. Support for up to six
EX3300 member switches
12.2R1—Starting in Junos OS Release 12.2R1, an
EX3300 Virtual Chassis can support up to ten
EX3300 member switches.
EX3300 Virtual Chassis
15.1X53-D50—Initial release. Support for up to
ten EX3400 member switches
EX3400 Virtual Chassis
9.0R1—Initial release. Support for up to ten
EX4200 member switches
EX4200 Virtual Chassis
13.2X50-D10—Initial release. Support for up to
ten EX4300 member switches
13.2X50-D20—Starting in Junos OS Release
13.2X50-D20, EX4300 switch support was
added in a mixed QFX Series Virtual Chassis or
in a VCF. See Understanding QFX Series Virtual
Chassis Components or Understanding Virtual
Chassis Fabric Components.
EX4300 Virtual Chassis
11.1R1—Initial release. Support for up to two
EX4500 switches
11.4R1—Support for up to ten EX4500 member
switches
EX4500 Virtual Chassis
12.2R1—Initial release. Support for up to ten
EX4550 switches
EX4550 Virtual Chassis
13.2X51-D25—Initial release. Support for up to
ten EX4600 switches
EX4600 Virtual Chassis
11.1R1—Initial release. Support for up to two
EX4500 switches and up to eight EX4200
switches
11.2R1—Support for up to nine EX4200 switches
11.4R1—Support for up to nine EX4500 switches
Mixed EX4200 and EX4500 Virtual Chassis
12.2R1—Initial release. Support for up to ten total
EX4200 and EX4550 switches
Mixed EX4200 and EX4550 Virtual Chassis
12.2R1—Initial release. Support for up to ten total
EX4200, EX4500, and EX4550 switches
Mixed EX4200, EX4500, and EX4550 Virtual
Chassis
17Copyright © 2017, Juniper Networks, Inc.
Chapter 1: Virtual Chassis Overview

Table 3: Maximum Member Switch Support for Virtual Chassis by Junos
OS Release (continued)
Initial Junos OS ReleaseMaximum Member Switch Support
13.2X51-D25—Initial release. Support for up to
ten total EX4300 and EX4600 switches.
EX4600 switches must assume Routing Engine
role.
Mixed EX4300 and EX4600 Virtual Chassis
12.2R1—Initial release. Support for up to ten total
EX4500 and EX4550 switches
Mixed EX4500 and EX4550 Virtual Chassis
13.2R2—Initial release. Support for up to two
EX9200 switches.
EX9200 Virtual Chassis
Virtual Chassis Ports (VCPs)
You use Virtual Chassis ports (VCPs) to interconnect the member switches in a Virtual
Chassis.
Some switches have dedicated VCPs. Dedicated VCPs allow you to interconnect switches
without requiring any additional interface configuration.
These switches have dedicated VCPs:
•EX4200 switches, on the rear panel
•EX4500 switches, on the Virtual Chassis module
•EX4550 switches, on the Virtual Chassis module
Some switches have ports that are configured as VCPs by default. You do not need to
explicitly configure those as VCPs to use them to interconnect those switches into a
Virtual Chassis.
To interconnect switches that do not have dedicated VCPs or to interconnect switches
across greater distances than allowed by a dedicated-VCP connection, you configure an
optical port as a VCP. You can configure those VCPs on these switches:
•EX2200 switches, through an uplink port
NOTE: All RJ-45 interfaces, including built-in network ports with
10/100/1000BASE-T Gigabit Ethernet connectors and 1000BASE-T RJ-45
transceivers, on EX2200 and EX2200-C switches, can also be configured
into VCPs.
•EX2300 switches, through uplink ports with SFP+ tranceivers and configured as VCPs
NOTE: You cannot use SFP tranceivers to form a Virtual Chassis on EX2300
switches.
Copyright © 2017, Juniper Networks, Inc.18
Virtual Chassis Feature Guide for EX9200 Switches

•EX3300 switches, through uplink ports
NOTE: Uplink ports 2 and 3 on EX3300 switches are configured as VCPs
by default.
•EX3400 switches, through uplink ports
NOTE: All QSFP+ uplink ports on EX3400 switches are configured as VCPs
by default, or you can configure the SFP or SFP+ uplink ports as VCPs.
•EX4200 switches, through uplink module ports (SFP, SFP+, or XFP) or through an
SFP+ port on the EX4200-24F switch
•EX4300 switches, through uplink ports
NOTE: All QSFP+ ports on EX4300 switches are configured as VCPs by
default.
•EX4500 switches, through any SFP+ port configured as a VCP
•EX4550 switches, through any SFP+ port configured as a VCP
•EX4600 switches, through SFP+ and QSFP+ ports configured as VCPs
All supported SFP, SFP+, and XFP uplink connections between EX4200, EX4500, and
EX4550 switches can be configured as VCPs.
You can increase the Virtual Chassis bandwidth between member switches by configuring
multiple optical ports connecting the switches as VCPs. The optical ports configured as
VCPs automatically form a Link Aggregation Group (LAG) bundle. See Understanding EX
Series Virtual Chassis Port Link Aggregation.
Master Role
The member that functions in the master role in the Virtual Chassis:
•Manages the member switches.
•Runs Junos OS for EX Series switches in a master role.
•Runs the chassis management processes and control protocols.
•Represents all the member switches interconnected within the Virtual Chassis
configuration. (The hostname and other properties that you assign to this switch during
setup apply to all members of the Virtual Chassis configuration.)
When an EX Series switch that supports Virtual Chassis is powered on as a standalone
switch, it is considered the master member. In a Virtual Chassis, one member functions
as the master and a second member functions as the backup:
19Copyright © 2017, Juniper Networks, Inc.
Chapter 1: Virtual Chassis Overview

•In a preprovisioned configuration, one of the two members assigned as routing-engine
functions as the master member. The selection of which member assigned as
routing-engine functions as master and which as backup is determined by the software
based on the master election algorithm. See Understanding How the Master in a Virtual
Chassis Is Elected.
•In a configuration that is not preprovisioned, the selection of the master and backup
is determined by the mastership priority value and secondary factors in the master
election algorithm.
In a mixed EX4300 and EX4600 Virtual Chassis, an EX4600 switch must assume the
master role.
In any mixed Virtual Chassis configuration that includes EX4200 switches, EX4500
switches, or EX4550 switches, any switch can be configured in any role in any
configuration.
Backup Role
The member that functions in the backup role in the Virtual Chassis:
•Maintains a state of readiness to take over the master role if the master fails.
•Runs Junos OS for EX Series switches in a backup role.
•Synchronizes with the master in terms of protocol states, forwarding tables, and so
forth, so that it is prepared to preserve routing information and maintain network
connectivity without disruption in case the master is unavailable.
You must have at least two member switches in the Virtual Chassis configuration in order
to have a backup member.
•In a preprovisioned configuration, one of the two members assigned as routing-engine
functions in the backup role. The selection of which member assigned as routing-engine
functions as master and which as backup is determined by the software based on the
master election algorithm. See Understanding How the Master in a Virtual Chassis Is
Elected.
•In a configuration that is not preprovisioned, the selection of the master and backup
is determined by the mastership priority value and secondary factors in the master
election algorithm.
In a mixed EX4300 and EX4600 Virtual Chassis, we strongly recommend configuring an
EX4600 switch into the backup role. A mixed EX4300 and EX4600 Virtual Chassis must
use an EX4600 member switch in the master role, and configuring an EX4600 switch
into the backup role ensures that the Virtual Chassis remains up after a switchover event.
In any mixed Virtual Chassis configuration that includes EX4200 switches, EX4500
switches, or EX4550 switches, any switch can be configured in any role in any
configuration.
Linecard Role
A member that functions in the linecard role in the Virtual Chassis:
Copyright © 2017, Juniper Networks, Inc.20
Virtual Chassis Feature Guide for EX9200 Switches