Supported Platforms
Related Documentation
- 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 a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- Replacing a Member Switch of an EX Series Virtual Chassis Configuration (CLI Procedure)
role
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Description
Specify the roles of the members of the Virtual Chassis in a preprovisioned Virtual Chassis.
EX2200 Virtual Chassis, EX3300 Virtual Chassis, EX4200 Virtual Chassis, EX4500 Virtual Chassis, EX4550 Virtual Chassis, and Any Mixed 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
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 configuration. The master
manages all members of the Virtual Chassis configuration 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 EX2200, EX3300, EX4200, EX4500, or EX4550 switches) 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 an EX Series 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
- 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 a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- Replacing a Member Switch of an EX Series Virtual Chassis Configuration (CLI Procedure)
Published: 2012-12-07
Supported Platforms
Related Documentation
- 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 a Virtual Chassis on an EX Series Switch (J-Web Procedure)
- Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)
- Replacing a Member Switch of an EX Series Virtual Chassis Configuration (CLI Procedure)