- Download
Software
- Research a
Problem - Case Management
- Communities and Forums
- Contract & Product Management
- Technical Documentation Advanced Search
- Documentation Feedback Form
- Documentation Symbols Key
- End-of-Life Products
- Guidelines and Policies
- Security Resources
Juniper was the first North American IP routing vendor to achieve the prestigious TL 9000 certification by the Quality of Excellence for Suppliers of Telecommunications (QuEST) Forum in the router category, for design, development, provision and service and support.
What is J-Care?
It's the world-class service and support that you expect from a company that delivers the industry's best infrastructure and security products. With J-Care, you now have the confidence knowing that Juniper will do our part to keep you on top of the world!
- Download PDFs
-
Understanding Virtual Chassis Configuration
- Related Topics
- Virtual Chassis Overview
- Understanding Virtual Chassis Components
- Understanding How the Master in a Virtual Chassis Is Elected
- Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets
- Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet
- Example: Configuring a Virtual Chassis with a Preprovisioned Configuration File
Understanding Virtual Chassis Configuration
You configure and manage almost all aspects of a virtual chassis through the master of the virtual chassis. However, you can also configure virtual chassis parameters when an EX 4200 is a standalone switch not interconnected with other members.
An EX 4200 switch has some innate characteristics of a virtual chassis by default. A standalone EX 4200 switch is assigned member ID 0 and is the master of itself. Therefore, you can edit its virtual chassis configuration. When the standalone switch is interconnected with an existing virtual chassis, the virtual chassis configuration statements and any VCP uplink settings that you previously specified on the standalone switch remain part of its configuration.
A switch cannot be recognized as a member of a virtual chassis configuration until it is interconnected with the master, or interconnected with an existing member of the virtual chassis configuration. When a switch is located too far away to be interconnected with the dedicated virtual chassis ports, you can specify an uplink as a virtual chassis port using the request virtual-chassis vc-port command. This command, setting an uplink port as a VCP must be executed on the standalone switch, because it is not yet part of the virtual chassis configuration. Without an uplink VCP, the standalone switch cannot be recognized by the master as belonging to the virtual chassis.
While an uplink port is set as a VCP interface, it cannot be used for any additional purpose. If you want to use the uplink port for another purpose, you can delete the VCP setting by using the request virtual-chassis vc-port command. You can execute this command directly on the member whose uplink VCP setting you want to delete or through the master of the virtual chassis.
In addition, you may choose to create a preprovisioned configuration. This type of configuration allows you to deterministically control the member ID and role assigned to a member switch by tying it to its serial number. For an example of a preprovisioned configuration, see Example: Configuring a Virtual Chassis with a Preprovisioned Configuration File.