Supported Platforms
Related Documentation
- EX Series, QFX Series standalone switches
- Autoprovisioning a Virtual Chassis Fabric
- Preprovisioning a Virtual Chassis Fabric
- Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
- EX Series
- Example: Configuring an EX4200 Virtual Chassis Using a Preprovisioned Configuration File
- Example: Setting Up a Full Mesh EX8200 Virtual Chassis with Two EX8200 Switches and Redundant XRE200 External Routing Engines
- Configuring an EX3300 Virtual Chassis (CLI Procedure)
- Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
- Configuring an EX8200 Virtual Chassis (CLI Procedure)
- Configuring an EX9200 Virtual Chassis
- Configuring a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- QFX Series standalone switches
- Configuring a QFX Series Virtual Chassis (CLI Procedure)
role
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 13.2X50-D15 for the QFX Series.
Statement introduced in Junos OS Release 13.2X51-D20 for Virtual Chassis Fabric (VCF).
Description
Specify the roles of the members of the Virtual Chassis or a Virtual Chassis Fabric (VCF) in a preprovisioned Virtual Chassis.
Virtual Chassis Fabric
Specify the role to be performed by each switch. In a VCF, two spine devices are configured into the Routing Engine role and the remaining spine devices and all leaf devices are configured into the line card role. The role must be associated with the member’s serial number.
EX Series (except EX8200 Virtual Chassis) and QFX Series Virtual Chassis
Specify the role to be performed by each member switch. Associate the role with the member’s serial number.
When you use a preprovisioned configuration, you cannot modify the mastership priority or member ID of member switches through the user interfaces. The mastership priority value is generated by the software, based on the assigned role:
- A member configured as routing-engine is assigned the mastership priority 129.
- A member configured as line-card is assigned the mastership priority 0.
- A member listed in the preprovisioned configuration without an explicitly specified role is assigned the mastership priority 128.
The configured role specifications are permanent. If both routing-engine members fail, a line-card member cannot take over as master of the Virtual Chassis configuration. You must delete the preprovisioned configuration to change the specified roles in a Virtual Chassis.
Explicitly configure two members as routing-engine and configure additional switches as members of the preprovisioned Virtual Chassis by specifying only their serial numbers. If you do not explicitly configure the role of the additional members, they function in a linecard role by default. In that case, a member that is functioning in a linecard role can take over mastership if the members functioning as master and backup (routing-engine role) both fail.
EX8200 Virtual Chassis
Specify the role to be performed by each XRE200 External Routing Engine and each EX8200 member switch. Associate the role with the member’s serial number. An EX8200 Virtual Chassis cannot function when both external Routing Engines, which must be configured in the routing-engine role, have failed.
Options
- line-card—Enables the member to be eligible
to function only in the linecard role. Any member of the Virtual Chassis
or VCF configuration other than the master or backup functions in
the linecard role and runs only a subset of Junos OS for EX Series
switches. A member functioning in the linecard role does not run the
control protocols or the chassis management processes.
A Virtual Chassis must have at least three members for one member to function in the linecard role.
In an EX8200 Virtual Chassis configuration, all member switches must be in the linecard role.
- routing-engine—Enables the member to function
as a master or backup of the Virtual Chassis or VCF configuration.
The master manages all members and runs the chassis management processes
and control protocols. The backup 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.
(All Virtual Chassis composed of EX Series switches, except EX8200 switches, or QFX Series devices) Specify two and only two members as routing-engine. The software determines which of the two members assigned the routing-engine role functions as master, based on the master election algorithm. See Understanding How the Master in a Virtual Chassis Is Elected. In these Virtual Chassis, the routing-engine role is associated with a switch.
(EX8200 Virtual Chassis) All XRE200 External Routing Engines must be in the routing-engine role.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Related Documentation
- EX Series, QFX Series standalone switches
- Autoprovisioning a Virtual Chassis Fabric
- Preprovisioning a Virtual Chassis Fabric
- Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
- EX Series
- Example: Configuring an EX4200 Virtual Chassis Using a Preprovisioned Configuration File
- Example: Setting Up a Full Mesh EX8200 Virtual Chassis with Two EX8200 Switches and Redundant XRE200 External Routing Engines
- Configuring an EX3300 Virtual Chassis (CLI Procedure)
- Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
- Configuring an EX8200 Virtual Chassis (CLI Procedure)
- Configuring an EX9200 Virtual Chassis
- Configuring a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- QFX Series standalone switches
- Configuring a QFX Series Virtual Chassis (CLI Procedure)
Modified: 2016-02-29
Supported Platforms
Related Documentation
- EX Series, QFX Series standalone switches
- Autoprovisioning a Virtual Chassis Fabric
- Preprovisioning a Virtual Chassis Fabric
- Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
- EX Series
- Example: Configuring an EX4200 Virtual Chassis Using a Preprovisioned Configuration File
- Example: Setting Up a Full Mesh EX8200 Virtual Chassis with Two EX8200 Switches and Redundant XRE200 External Routing Engines
- Configuring an EX3300 Virtual Chassis (CLI Procedure)
- Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
- Configuring an EX8200 Virtual Chassis (CLI Procedure)
- Configuring an EX9200 Virtual Chassis
- Configuring a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- QFX Series standalone switches
- Configuring a QFX Series Virtual Chassis (CLI Procedure)