Users Guide

Starting with ArubaOS 6.4, a controller is assigned the dual role if no other role is specified
The high availability feature supports redundancy models with an active controller pair, or an active/standby
deployment model with one backup controller supporting one or more active controllers. Each of these
clusters of active and backup controllers comprises a high-availability group. All active and standby controllers
within a single high-availability group must be deployed in master-local or independent masters topologies. An
independent masters topology requires all independent master controllers to have the same WLAN
configuration.
Pre-Deployment Information
Refer to the following sections of this document for deployment models and feature details to help you plan
your high availability solution:
l High Availability Deployment Models on page 618
l High Availability Extended Controller Capacity on page 621
l Client State Synchronization on page 620
l High Availability Inter-Controller Heartbeats on page 621
Configuring High Availability
Configure the high availability feature in the WebUI or CLI using the high-availability and high-availability group
profiles.
In the WebUI
To configure High Availability using the WebUI:
1. Navigate to Configuration > Advanced Services > Redundancy.
2. In the HA Group Configuration section, click Add New. A pop-up window appears.
3. In the Name field, enter a name for the HA group you just created.
4. In the controller IPaddress field, enter the IP address of a controller in the HA group.
5. Click the IP Version drop-down list and select either IPv4 or IPv6 to identify the IP address version type used
by the controller.
6. Click the Role drop-down list to assign a role to the controller. The IP address of each controller must be
reachable by APs and must be the IP address that appears in the Configuration > Controller > System
settings tab of the controller WebUI, or in the output of the show controller-ip CLI command.
l Active: Controller is active and serving APs.
l Dual: Controller serves some APs and acts as a standby controller for other APs.
l Standby: Controller does not serve APs and only acts as a standby in case of failover.
7. Click Add to add the controller to the group.
8. (Optional) The high availability inter-controller heartbeat feature allows for faster AP failover from an active
controller to a standby controller, especially in situations where the active controller reboots or loses
connectivity to the network. To edit the default heartbeat threshold and interval values:
a. Enter a heartbeat threshold in the Heartbeat Threshold field to define the number of heartbeats that
must be missed before the APs are forced to failover to the standby controller. This value must be
between 3 and 10, inclusive.
b. Enter a heartbeat interval in the Heartbeat Interval field to define how often inter-controller
heartbeats are sent. This value must be between 100 and 1000 ms, inclusive.
Dell Networking W-Series ArubaOS 6.5.x | User Guide Increasing Network Uptime Through Redundancy and VRRP |
623