Removing an AOS-CX VSF Stack Member Using UI

You can remove a member from the AOS-CX VSF stack in Aruba Central (on-premises) only when the member is offline. It involves completing procedures both inside and outsideAruba Central (on-premises). The procedure will vary based on the switches firmware versions.

Switches running AOS-CX 10.07 or later versions

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

  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 Aruba Central (on-premises), navigate to the VSF Stacking page and complete the following steps:
    1. Expand the stack for which you want to delete the member.
    2. Point to the row for the member you want to delete and click the delete icon.

      A confirmation window is displayed.

    3. Click Delete.

      The member will be removed from the VSF Stacking table.

  • The removed member must be reset to the factory-default configuration before connecting back to Aruba Central (on-premises) again.
  • Conductor member cannot be deleted as an individual member.

Switches running AOS-CX 10.6 or earlier versions

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

  1. Disable Aruba Central (on-premises) 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 Aruba Central (on-premises).

  3. Delete the stack from the template group or UI group in Aruba Central (on-premises).

    See Deleting an Offline Switch.

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

    For example, in a three-member stack, run 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 a member (other than the conductor) is removed 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 the conductor itself is removed from the stack, then the conductor reboots as a standalone switch and its configuration resets to factory default, and the standby takes the role of the conductor in the stack.
  5. Disconnect the physical VSF links for the member.
  6. In the case of template group, update the template in template group Aruba Central (on-premises) with the configuration from the remaining stack.
  7. Enable Aruba Central (on-premises) from the switch CLI.

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

    switch(config-aruba-central)# enable

    OR

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

    Before moving the stack to a UI group in Aruba 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 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 and subscribe the remaining members in the AOS-CX stack to Aruba Central (on-premises).