Removing a Stack Member Using UI

You can remove a member from the AOS-CX VSF Virtual Switching Framework. VSF allows network administrators to stack multiple individual switches into a single logical device using standard Ethernet links. stack in Classic Central only when the member is offline. It involves completing procedures both inside and outside Classic Central. The procedure will vary based on the switch firmware versions.

Switches Running AOS-CX 10.07 or Later Versions

If your switches are running AOS-CX 10.07 or later versions, complete the following steps:

1. Shut down the member in the stack.
2. Disconnect the physical VSF links for the member. Otherwise, the switch will reboot and join the stack again through auto-stacking.
3. Reconnect the physical links as desired.
4. In Classic Central, navigate to the VSF Stacking page and complete the following steps:
   1. Expand the stack for which you want to delete the member.
   2. Wait for the member to display as offline in the VSF Stacking table.

      It may take up to five minutes for the member to appear offline in Classic Central.

   3. Point to the row for the member you want to delete and click the delete icon.

      A confirmation window is displayed. You can delete the member only when the status of the member is offline.

   4. Click Delete.

      The member is removed from the VSF Stacking table.

Switches Running AOS-CX 10.06 or Earlier Versions

If your switches are running AOS-CX 10.06 or earlier versions, complete the following procedure:

1. Disable Classic Central from the switch CLI.

   You must execute these commands only on the conductor of the stack.

   switch# configure
   switch(config)# aruba-central
   switch(config-aruba-central)# disable
2. Wait for the stack to display as offline in the List view.

   It may take up to five minutes for the stack to appear offline in Classic Central.

3. Delete the stack from the template group or UI group in Classic Central.

   See Deleting an Offline Switch.

4. Remove the member from the VSF stack in the switch CLI by issuing the following commands.

   For example, in a three-member stack, issue the following commands to remove member 3.

   switch# configure
   switch(config)# no vsf member 3
   The specified switch will be unconfigured and rebooted
   Do you want to continue (y/n)? y
   • When you remove a member (other than the conductor) from the stack, then the member reboots as a standalone switch, and the configuration resets to factory default. The stack will remain with the conductor and other remaining members.
   • However, when you remove the conductor itself from the stack, then the conductor reboots as a standalone switch and its configuration resets to factory default.
5. Disconnect the physical VSF links for the member.
6. In the case of template groups, update the template in template group Classic Central with the configuration from the remaining stack.
7. Enable Classic Central from the switch CLI by issuing the following command.
   switch(config-aruba-central)# enable

   If this does not work, issue the https-server session close all command.

   switch# https-server session close all
8. In the case of UI groups, after enabling Classic Central, complete the following steps:

   Before moving the stack to a UI group in Classic Central, save the output of the show running config command from the conductor. This is required to restore or apply any configuration that might be lost because of group-level overwrite of configuration. You can apply this configuration after moving the stack to the UI group using the Edit Config option in the MultiEdit MultiEdit mode allows configuring single or multiple AOS-CX switches using the CLI syntax. You can also view the difference between the Central running configuration and the switch running configuration. mode.

   1. Move the stack to the UI group.
   2. Paste the running configuration of the conductor, which you copied before moving the stack to the UI group, in the MultiEdit mode using the Edit Config option.
   3. Save the running configuration.
9. Add the remaining members in the AOS-CX stack to Classic Central and assign a valid license.