AOS-Switch Stack
A switch stack is a set of switches that are interconnected through stacking ports. The switches in a stack elect a primary switch called Conductor and a backup switch as Member. The following table lists the switches that support stacking:
|
AOS-Switch Platform |
Maximum Number of Stack Members |
Minimum Supported Version |
Supported Stack Type (Frontplane (VSF) / Backplane (BPS)) | Supported Configuration Group Type for Stacking (UI / Template) |
|---|---|---|---|---|
|
Aruba 2930F Switch Series |
8 |
|
VSF |
UI and Template |
|
Aruba 2930M Switch Series |
10 |
|
BPS |
UI and Template |
|
Aruba 3810 Switch Series |
10 |
|
BPS |
UI and Template |
|
Aruba 5400R Switch Series |
2 |
|
VSF |
Template only |
Provisioning and configuring of Aruba 5400R Switch Series and switch stacks is supported only through configuration templates. Aruba Central (on-premises) does not support moving Aruba 5400R Switch Series from the template group to a UI group. If an Aruba 5400R switch is preassigned to a UI group, then the device is moved to an unprovisioned group after it joins Aruba Central (on-premises).
For more information on topology and configuration of switch stacks, see the ArubaOS-Switch Management and Configuration Guide for the respective switch series.
Provisioning AOS-Switch Stacks in Aruba Central (on-premises)
The switch elected as the conductor establishes a WebSocket connection to Aruba Central (on-premises). The following criteria apply to provisioning and management of switch stacks in Aruba Central (on-premises):
- Switch stacks can be added only to a template group and cannot be moved to a UI group.
- If the standalone switches in a group join to form a switch stack, the switch is moved to the Unprovisioned state.
- If a switch stack in the template group joins Aruba Central (on-premises) as a stand-alone Switch, it is blocked unless it is deleted from the stack. After it is removed from the stack, the stand-alone switch is moved to the pre-provisioned group.
- If a switch stack is moved from a pre-provisioned group to an existing group in the UI, it will be moved to Unprovisioned state.
- After forming a switch stack, you can remove a member and erase its stacking configuration. However, the member can join Aruba Central (on-premises) as a standalone switch only after it is deleted from the switch stack.
- When a stack is removed, the stack members cannot join Aruba Central (on-premises) until the stack entry is deleted. For more information on deleting the stack, see Configuring AOS-Switch Stacks Using UI Groups. When a stack entry is not deleted and the member tries to rejoin Aruba Central (on-premises), an event is triggered in the Audit Trail page stating that the stack association is detected.
Assigning Labels and Sites
Aruba Central (on-premises) supports organizing your devices into sites for ease of monitoring. Sites refer to physical locations in which the devices are installed. Administrators can assign switch stacks to a single site for ease of managing installations and monitoring the overall site health. For more information on assigning devices to sites, see Managing Sites.
Similarly, switch stacks can also be tagged using labels. Labels allow you to identify or tag devices installed in a specific site for ease of monitoring. For more information on assigning labels, see Managing Labels.
If any one member of the switch stack is assigned to a site, Aruba Central (on-premises) automatically assigns all other members in a switch stack to the same site. Similarly, if a label is assigned to an individual member in a stack, the same label is applied to all other members of the stack.
Because all members of a switch stack must be assigned to the same site and label, Aruba Central (on-premises) automatically corrects the site and label assignment for switch stacks that were earlier assigned to different labels or sites. If you have such switch stacks in your account, you will notice that all stack members are migrated to the same site or label to which the conductor was assigned. Aruba recommends that you review the sites and labels assigned by Aruba Central (on-premises) to verify that the switch stacks in your account are assigned to sites and labels that you intended to use, and if required, assign all members of stack to a common site or label of your choice.
Configuring AOS-Switch Stacks
For information on configuring switch stacks using template groups, see Configuring AOS-Switch Stacks Using Template Groups.
For information on configuring switch stacks using UI groups, see Configuring AOS-Switch Stacks Using UI Groups.
Monitoring Switch Stacks
See Monitoring Switches and Switch Stacks.
