Concept Guide

controllers for that AP. This feature does not require that the active controller act the configuration master for
the local standby controller . A master controller in a master-local deployment can act as an active or a standby
controller .
When the AP first connects to its active controller, that controller sends the AP the IP address of a standby
controller, and the AP attempts to connect to the standby controller. If an AP that is part of a cluster with
multiple backup controllers fails to connect to the first standby controller, the active controller will select a new
standby controller for that AP, and the AP will attempt to connect to that standby controller. APs using control
plane security establish an IPsec tunnel to their standby controllers. APs that are not configured to use control
plane security send clear, unencrypted information to the standby controller.
An AP will failover to its backup controller if it fails to contact its active controller through regular heartbeats
and keepalive messages, or if the user manually triggers a failover using the WebUI or CLI.
A controller using this feature can have one of three high availability roles – active, standby or dual. An active
controller serves APs, but cannot act as a failover standby controller for any AP except the ones that it serves
as active. A standby controller acts as a failover backup controller, but cannot be configured as the primary
controller for any AP. A dual controller can support both roles, and acts as the active controller for one set of
APs, and also acts as a standby controller for another set of APs.
Examples
The following commands configures a high availability group, and assigns controllers and roles to each
controller in the group.
(host) (config) #ha group-profile new
(host) (HA group information "new") #controller 192.0.2.2 role active
(host) (HA group information "new") #controller 192.0.2.3 role active
(host) (HA group information "new") #controller 192.0.2.4 role standby
(host) (HA group information "new") #preemption
Command History
Version Description
ArubaOS 6.3 Command introduced
ArubaOS 6.4 The following parameters were introduced
l heartbeat
l heartbeat-interval
l heartbeat-threshold
l over-subscription
l pre-shared-key
l state-sync
Command Information
Platform License Command Mode
Available on all platforms Available in the base operating
system.
Config mode on master and
local controllers.
Dell Networking W-Series ArubaOS 6.5.x | Reference Guide ha | 394