Page 2
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.
Virtual Chassis Overview ......... . . 15 Understanding EX9200 Virtual Chassis ........15 Understanding EX Series Virtual Chassis Components .
Page 4
Upgrading Junos OS in a Virtual Chassis ......45 Upgrading Junos OS Software in an EX9200 Virtual Chassis ....45 Chapter 5 Deleting a Member ID .
® 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.
Virtual Chassis Feature Guide for EX9200 Switches If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the command. These procedures are load merge relative described in the following sections.
Virtual Chassis Feature Guide for EX9200 Switches Table 2: Text and Syntax Conventions Convention Description Examples Bold text like this Represents text that you type. To enter configuration mode, type the configure command: user@host> configure Fixed-width text like this Represents output that appears on the user@host>...
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 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.
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/...
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.
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.
Virtual Chassis Feature Guide for EX9200 Switches Table 3: Maximum Member Switch Support for Virtual Chassis by Junos OS Release (continued) Maximum Member Switch Support Initial Junos OS Release Mixed EX4300 and EX4600 Virtual Chassis 13.2X51-D25—Initial release. Support for up to ten total EX4300 and EX4600 switches.
Virtual Chassis Feature Guide for EX9200 Switches 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 functions as master and which as backup is determined by the software routing-engine based on the master election algorithm.
Virtual Chassis configuration because the original master became unavailable. In a preprovisioned configuration, you assign the role of each member switch. An EX9200 switch does not have a mastership priority and an EX9200 Virtual Chassis, therefore, must be preprovisioned.
Managing Files on Virtual Chassis Member Routers or Switches on page 29 Virtual Chassis Slot Number Mapping for Use with SNMP on page 30 Configuring an EX9200 Virtual Chassis on page 32 Creating and Applying Configuration Groups for a Virtual Chassis on page 36...
Virtual Chassis Feature Guide for EX9200 Switches Accessing the Virtual Chassis Through the Management Interface The management Ethernet interface ( ) on an MX Series router or EX9200 switch is fxp0 an out-of-band management interface, also referred to as a management port, that enables you to use Telnet or SSH to access and manage the device remotely.
Documentation Managing Files on Virtual Chassis Member Routers or Switches In a Virtual Chassis configuration for MX Series 3D Universal Edge Routers or EX9200 switches, you can manage files on local and remote member routers or switches by including a member specification in the following...
MX Series Virtual Chassis or a member switch of an EX9200 Virtual Chassis, keep in mind that the offset used for slot numbering in the Virtual Chassis affects the value that appears for the jnxFruSlot object.
Page 31
Chapter 2: Accessing and Configuring a Virtual Chassis and Managing Files Table 4: jnxFruSlot Numbers and Corresponding Slot Numbers in an MX Series or EX9200 Virtual Chassis (continued) MX Series or EX9200 Virtual Chassis jnxFruSlot Number Line Card Slot Number...
Configuring the EX9200 Virtual Chassis on page 33 Creating Configuration Groups for an EX9200 Virtual Chassis A standalone EX9200 switch uses the re0 and re1 configuration groups to apply groups on both Routing Engines. Because a Virtual Chassis with two member switches has four Routing Engines that often have a need to share configuration amongst one another, you should create four groups—one group for each Routing Engine in the Virtual...
To configure an EX9200 Virtual Chassis: Before you perform this procedure: Ensure that both EX9200 member switches in the Virtual Chassis have dual Routing Engines installed. Ensure all Routing Engines on both member switches are running the same version of Junos OS Release 13.2R2 or later.
Page 34
For instance, if you wanted to configure the switch with chassis serial number JN1234567ABC as member 0 and the switch with chassis serial number JN9876543ZYX as member 1 in your EX9200 Virtual Chassis: [edit virtual-chassis] user@switch-0# set member 0 serial-number JN1234567ABC role routing-engine...
Virtual Chassis Feature Guide for EX9200 Switches Creating and Applying Configuration Groups for a Virtual Chassis For a Virtual Chassis configuration consisting of two MX Series routers or two EX9200 switches, each of which supports dual Routing Engines, you must create and apply on...
Page 37
BEST PRACTICE: We recommend that you use the commit synchronize command to save any configuration changes to the Virtual Chassis. For an EX9200 or MX Series Virtual Chassis, the option is the default force and only behavior when you issue the commit synchronize command.
Page 40
Virtual request virtual-chassis vc-port set Chassis ports on Modular Port Concentrator/Modular Interface Card (MPC/MIC) interfaces. To interconnect the member switches into an EX9200 Virtual Chassis, you must use the request virtual-chassis vc-port set command to configure network ports into Virtual Chassis ports on line card interfaces.
Virtual Chassis software license. A software license is not needed to create an EX9200 Virtual Chassis. To remove the Virtual Chassis ports from both member devices in a Virtual Chassis:...
Guidelines for Configuring Virtual Chassis Ports Verifying the Operation of Virtual Chassis Ports Purpose Verify that the Virtual Chassis ports in an MX Series or EX9200 Virtual Chassis are properly configured and operational. Action To display the status of the Virtual Chassis ports for both member routers or switches in the Virtual Chassis: user@host>...
Upgrading Junos OS Software in an EX9200 Virtual Chassis on page 45 Upgrading Junos OS Software in an EX9200 Virtual Chassis You can upgrade the Junos OS in an EX9200 Virtual Chassis by installing Junos OS software onto each Routing Engine in the Virtual Chassis, and rebooting each Routing Engine individually to complete the installation.
Page 46
Virtual Chassis Feature Guide for EX9200 Switches Exit CLI configuration mode. {master:member0-re0} [edit] user@switch# exit Install the Junos OS software package onto each Routing Engine in the Virtual Chassis: {master:member0-re0} user@switch> request system software add package-name On a properly formed Virtual Chassis, entering the request system software add...
Virtual Chassis software license. A software license is not needed to create an EX9200 Virtual Chassis. To delete the Virtual Chassis member IDs from both member routers or switches and...
Determining GRES Readiness in a Virtual Chassis Configuration on page 54 Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis By default, member routers or switches in an EX9200 or MX Series Virtual Chassis use hash-based traffic distribution for subscriber interfaces in aggregated Ethernet bundles configured without link protection.
Virtual Chassis fails. Before you begin: Configure a Virtual Chassis consisting of two MX Series routers or two EX9200 switches. See Example: Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Virtual Chassis Ensure that the aggregated Ethernet bundle is configured without link protection.
Virtual Chassis Feature Guide for EX9200 Switches Determining GRES Readiness in a Virtual Chassis Configuration Depending on the configuration, a variable amount of time is required before a router or switch is ready to perform a graceful Routing Engine switchover (GRES). Attempting a GRES operation before the device is ready can cause system errors and unexpected behavior.
You cannot configure mastership election for an MX Series or EX9200 Virtual Chassis in the current release. The VCCP software uses the following algorithm to elect the master device for an EX9200 or MX Series Virtual Chassis: Choose the member device that has the highest value for the internal mastership election flag.
Page 58
Choose the member device that belongs to the Virtual Chassis with the largest number of members. NOTE: This criterion is not used in the current release because all EX9200 and MX Series Virtual Chassis configurations have two member devices. Choose the member device that is the accepted (elected) protocol master of the Virtual Chassis.
MX Series or EX9200 Virtual Chassis, applies in the context of split detection behavior. This topic describes the global roles and local roles in a MX Series or EX9200 Virtual Chassis so you can better understand how the Virtual Chassis behaves during a global mastership switch, a local Routing Engine switchover, or when split detection is enabled.
Virtual Chassis Feature Guide for EX9200 Switches —Standby Routing Engine Global Role and Local Role Descriptions Table 5 on page 60 describes the global roles and local roles in an MX Series or EX9200 Virtual Chassis. Table 5: Global Roles and Local Roles Virtual Chassis Role...
Chapter 7: Global Roles and Local Roles that Determine Mastership and Switchover Behavior Related Virtual Chassis Components Overview Documentation Understanding EX9200 Virtual Chassis on page 15 Mastership Election in a Virtual Chassis on page 57 Switching the Global Master and Backup Roles in a Virtual Chassis Configuration on page 61...
Virtual Chassis Feature Guide for EX9200 Switches Issuing the command from the request virtual-chassis routing-engine master switch VC-Mm causes the global role transitions listed in Table 6 on page Table 6: Virtual Chassis Global Role Transitions Before and After Mastership Switchover...
If there is a disruption to a Virtual Chassis configuration for MX Series 3D Universal Edge Routers or EX9200 Switches due to the failure of a member router or switch or one or more Virtual Chassis port interfaces, the resulting connectivity loss can cause a split in the Virtual Chassis configuration.
Virtual Chassis Feature Guide for EX9200 Switches switch is more likely to fail than the Virtual Chassis port interfaces to the backup router or switch. Configuring redundant Virtual Chassis ports on different line cards in each member router or switch reduces the likelihood that all Virtual Chassis port interfaces to the backup router or switch can fail.
Virtual Chassis port links, the resulting connectivity loss can cause a split in the Virtual Chassis configuration. Split detection, which is enabled by default in an MX Series and EX9200 Virtual Chassis, identifies the split and minimizes further network disruption. You can disable split detection by including the...
Virtual Chassis Feature Guide for EX9200 Switches Configuring Characteristics of the Virtual Chassis Trace Log File You can optionally configure the following characteristics of the trace log file for a Virtual Chassis: Maximum number of trace files—When a trace file named...
Virtual Chassis Feature Guide for EX9200 Switches Using Regular Expressions to Refine the Output of the Virtual Chassis Trace Log File By default, the trace operation output includes all lines relevant to the logged events. You can refine the output of the trace log file for a Virtual Chassis by including regular expressions to be matched.
Page 76
Virtual Chassis Feature Guide for EX9200 Switches Specify the tracing flag that represents the operation you want to trace. [edit virtual-chassis] user@host# set traceoptions flag flag (Optional) Specify one or more of the following additional tracing options for the specified flag: To generate detailed trace output, use the option.
Page 78
Virtual Chassis Feature Guide for EX9200 Switches is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the option. size Range: 2 through 1000 Default: 3 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
Verifying Neighbor Reachability for Member Routers or Switches in a Virtual Chassis Purpose Verify that each member router or switch in an MX Series or EX9200 Virtual Chassis has a path to reach the neighbor devices to which it is connected.
Verifying Neighbor Reachability for Hardware Devices in a Virtual Chassis Purpose Verify that each hardware device in an MX Series Virtual Chassis or an EX9200 Virtual Chassis can reach the neighbor routers and devices to which it is connected. On the MX Series routing platform, there is only one active device for each member router.
Page 85
Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Documentation Virtual Chassis Configuring an EX9200 Virtual Chassis on page 32 Example: Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Virtual Chassis Viewing Information in the Virtual Chassis Control Protocol Link-State Database...
Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Documentation Virtual Chassis Configuring an EX9200 Virtual Chassis on page 32 Example: Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Virtual Chassis Viewing Information About Virtual Chassis Port Interfaces in the Virtual Chassis Control...
Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Documentation Virtual Chassis Configuring an EX9200 Virtual Chassis on page 32 Example: Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Virtual Chassis Viewing Virtual Chassis Control Protocol Statistics for Member Devices and Virtual...
Virtual Chassis ports (VCPs) with other member switches, its default member ID is There is no default member ID in an EX8200 or EX9200 Virtual Chassis. An EX8200 or EX9200 Virtual Chassis must be preprovisioned, and that process configures the member IDs.
Configuring a QFX Series Virtual Chassis (CLI Procedure) Configuring an EX4300 Virtual Chassis (CLI Procedure) Configuring EX4600 Switches in a Mixed or Non-Mixed Virtual Chassis (CLI Procedure) Configuring an EX9200 Virtual Chassis on page 32 Configuring a QFX Series Virtual Chassis (CLI Procedure) no-split-detection Syntax no-split-detection;...
Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure) Configuring an EX8200 Virtual Chassis (CLI Procedure) Configuring an EX9200 Virtual Chassis on page 32 Configuring a QFX Series Virtual Chassis (CLI Procedure) Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
Page 98
Configuring an EX4300 Virtual Chassis (CLI Procedure) Configuring EX4600 Switches in a Mixed or Non-Mixed Virtual Chassis (CLI Procedure) Configuring an EX9200 Virtual Chassis on page 32 Configuring a QFX Series Virtual Chassis (CLI Procedure) Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
Virtual Chassis Feature Guide for EX9200 Switches targeted-distribution (Static Interfaces over Aggregated Ethernet) Syntax targeted-distribution; Hierarchy Level [edit interfaces demux0 unit logical-unit-number], [edit interfaces pp0 unit logical-unit-number] Release Information Statement introduced in Junos OS Release 11.2. Statement introduced in Junos OS Release 13.2R2 for EX Series switches.
Page 102
Virtual Chassis Feature Guide for EX9200 Switches is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the option. size Range: 2 through 1000 Default: 3 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
Virtual Chassis Feature Guide for EX9200 Switches request virtual-chassis member-id delete (MX Series Virtual Chassis) Syntax request virtual-chassis member-id delete Release Information Command introduced in Junos OS Release 11.2. Command introduced in Junos OS Release 13.2R2 for EX Series switches.
Page 110
Level Related Configuring Member IDs for a Virtual Chassis Documentation Configuring an EX9200 Virtual Chassis on page 32 Example: Configuring Interchassis Redundancy for MX Series 3D Universal Edge Routers Using a Virtual Chassis List of Sample Output request virtual-chassis member-id set (Assigning a Member ID) on page 110...
Command introduced in Junos OS Release 13.2R2 for EX Series switches. Description Change the mastership in an MX Series Virtual Chassis or EX9200 Virtual Chassis by switching the global roles of the master router or switch and backup router or switch in the Virtual Chassis configuration.
Page 112
Virtual Chassis Feature Guide for EX9200 Switches Determining GRES Readiness in a Virtual Chassis Configuration on page 54 Switchover Behavior in an MX Series Virtual Chassis Mastership Election in a Virtual Chassis on page 57 List of Sample Output request virtual-chassis routing-engine master switch (From Master Router) on page 112...
Page 114
Virtual Chassis Feature Guide for EX9200 Switches Understanding EX Series Virtual Chassis Components on page 16 Understanding QFX Series Virtual Chassis Components List of Sample Output request virtual-chassis vc-port set pic-slot 1 port 0 on page 114 request virtual-chassis vc-port set pic-slot 1 port 1 member 3 on page 114...
Virtual Chassis Feature Guide for EX9200 Switches show virtual-chassis active-topology Syntax show virtual-chassis active-topology <all-members> <local> <member member-id> Release Information Command introduced in Junos OS Release 9.0 for EX Series switches. Command introduced in Junos OS Release 13.2X50-D15 for the QFX Series.
Page 122
Virtual Chassis Feature Guide for EX9200 Switches Table 10: show virtual-chassis device-topology Output Fields (continued) Field Name Field Description The status of the device within the Virtual Chassis or VCF. Outputs include: Status —Device is currently connected to and participating in the Virtual Chassis Prsnt or VCF.
Virtual Chassis Feature Guide for EX9200 Switches Table 11: show virtual-chassis protocol adjacency Output Fields Field Name Field Description Level of Output Name of the Virtual Chassis port (VCP) interface. All levels Interface The MAC address of the device on the receiving side of the VCP link.
Virtual Chassis Feature Guide for EX9200 Switches Table 12: show virtual-chassis protocol database Output Fields Field Name Field Description Level of Output Link-state protocol (LSP) data unit identifier. All levels LSP ID Sequence number of the LSP. All levels Sequence Checksum value of the LSP.
Virtual Chassis Feature Guide for EX9200 Switches Table 13: show virtual-chassis protocol interface Output Fields Field Name Field Description Level of Output Name of the VCP. All levels Interface State of the link. Outputs include: All levels State —The link is up.
Virtual Chassis Feature Guide for EX9200 Switches show virtual-chassis protocol route Syntax show virtual-chassis protocol route <all-members> <destination-id> <local> <member member-id> Release Information Command introduced in Junos OS Release 10.4 for EX Series switches. Command introduced in Junos OS Release 13.2X50-D15 for the QFX Series.
Page 142
Virtual Chassis Feature Guide for EX9200 Switches Table 15: show virtual-chassis protocol statistics Output Fields (continued) Field Name Field Description Number of PDUs received minus the number of PDUs dropped. Processed Number of PDUs dropped. Drops Number of PDUs transmitted since VCCP started or since the statistics were set to zero.
Virtual Chassis Feature Guide for EX9200 Switches show virtual-chassis Syntax show virtual-chassis <status> Release Information Command introduced in Junos OS Release 9.2 for EX Series switches. Command introduced in Junos OS Release 13.2X50-D15 for the QFX Series. Command introduced in Junos OS Release 13.2X51-D20 for Virtual Chassis Fabric (VCF).
Page 146
Virtual Chassis Feature Guide for EX9200 Switches Table 16: show virtual-chassis Output Fields (continued) Field Name Field Description Mixed Mode Mixed mode configuration status: for a member device configured in mixed mode. for a member device not configured in mixed mode.
Page 150
Virtual Chassis Feature Guide for EX9200 Switches Table 17: show virtual-chassis vc-port Output Fields (continued) Field Name Field Description VCP name. Interface or PIC/Port The dedicated VCPs in an EX4200 or EX4500 Virtual Chassis are . The dedicated vcp-0 vcp-1...
Need help?
Do you have a question about the EX9200 and is the answer not in the manual?
Questions and answers