• Downloads
• role    

• Related Topics
• Example: Configuring a Virtual Chassis Using a Preprovisioned Configuration File
• Configuring a Virtual Chassis (CLI Procedure)
• Configuring a Virtual Chassis (J-Web Procedure)
• Adding a New Switch to an Existing Virtual Chassis Configuration (CLI Procedure)
• Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure)
• Understanding Virtual Chassis Configuration

role

Syntax

Hierarchy Level

Release Information

Statement introduced in JUNOS Release 9.0 for EX Series switches.

Description

In a preprovisioned Virtual Chassis configuration, specify the role to be performed by each EX4200 member switch. Associate the role permanently with the member’s serial number.

Options

routing-engine—Enables the member eligible to function as a master or backup of the Virtual Chassis configuration. The master manages all the 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.

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 Configuration Is Elected.

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 Software for EX Series switches. A member functioning in the linecard role does not run the chassis control protocols. A Virtual Chassis configuration must have at least three members in order to include a member that functions in the linecard role.

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 should fail, a line-card member cannot take over as master of the Virtual Chassis configuration. You must delete the preprovisioned configuration in order to change the specified roles.

It is possible to explicitly configure two members as routing-engine and to 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.

Required Privilege Level

routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.