Description

To remove a switch from a Virtual Chassis without replacing it, use following procedures:

Solution

  1. Power off and disconnect the member switch you want to remove from the Virtual Chassis.
  2. If the Virtual Chassis configuration is preprovisioned, on the Virtual Chassis primary, remove the removed switch’s member setting from the preprovisioned configuration.
[edit virtual-chassis]
user@vc-primary# delete member removed-member-id
  1. If the Virtual Chassis configuration is nonprovisioned, change the mastership-priority values of each member switch as needed to reconfigure the Virtual Chassis roles. See Configuring Primary Role of a Virtual Chassis.
  2. (Optional) If removing a member switch leaves only two remaining member switches in the Virtual Chassis, we recommend you disable split detection in a two-member Virtual Chassis. See Disabling Split and Merge in a Virtual Chassis for details.
  3. Commit any configuration changes made in previous steps.
  4. (For a mixed Virtual Chassis only) If removing this member switch changes the Virtual Chassis from a mixed to a non-mixed Virtual Chassis, you must also remove the mixed-mode setting from the Virtual Chassis. See Understanding Mixed EX Series and QFX Series Virtual Chassis for details on the combinations of switches that comprise a mixed Virtual Chassis. You must reboot the Virtual Chassis for the mode change to take effect. To do this, you can include the reboot option with the request virtual-chassis mode mixed disable command that turns off mixed mode, or reboot all member switches of the Virtual Chassis separately when ready to do so, as shown below.
user@vc-primary> request virtual-chassis mode mixed disable all-members
user@vc-primary> request system reboot all-members
  1.  
  2. NOTE: Step 7 describes how to remove the mixed mode and other settings from the removed switch if needed.
  3. When you remove a member switch from a Virtual Chassis configuration, the primary keeps that member switch’s member ID in reserve. Use the following command on the Virtual Chassis primary to make that member ID available for reassignment:
user@vc-primary> request virtual-chassis recycle member-id member-id
  1. If you want to use the removed switch as a standalone switch, you must remove any Virtual Chassis configuration items and settings on that switch. For a smooth transition to a new role as a standalone switch, we recommend to revert the switch to its default factory configuration using the request system zeroize command, and then apply the configuration items you want on the switch.
  2. If you do not want to revert to default factory settings, use commands such as the following to remove Virtual Chassis settings for the mode and VCPs from the removed switch:
  3. If you removed the switch from a mixed-mode Virtual Chassis that is not an EX4300 mixed Virtual Chassis, disable the mixed-mode setting on the switch as follows:
user@switch> request virtual-chassis mode mixed disable
  1. If you removed a non-multigigabit model EX4300 switch from a mixed EX4300 Virtual Chassis that contains multigigabit EX4300 switches (EX4300-48MP), when you disable mixed mode, you must also disable the special ieee-clause-82 port mode on the removed switch if you want to reconfigure it as a standalone switch or use it in any other type of mixed Virtual Chassis or non-mixed Virtual Chassis. Otherwise, the VCPs on the switch will not connect with other Virtual Chassis members or those ports will not operate properly as network ports.
  2. In this case, to disable mixed mode and the port mode on the switch:
user@switch> request virtual-chassis mode mixed ieee-clause-82 disable
  1. See Understanding EX4300 Multigigabit and Other EX4300 Model Switches in a Mixed EX4300 Virtual Chassis for more information about this special port mode on EX4300 switches.
  2. Delete the VCP settings for any ports that were used as VCPs:
user@switch> request virtual-chassis vc-port delete pic-slot pic-slot port port-number
  1. Reboot the standalone switch for settings such as mode changes to take effect.

 

Modification History

9/25/2023