Users Guide

heartbeat-threshold <heartbeat-threshold>
no ...
over-subscription
pre-shared-key <key>
preemption
state-sync
A controller using the high availability features must be defined as a member of a high availability group. To
add a controller to the new high availability group, issue following CLI command:
(host)(config)#ha group-membership <ha-group>
Migrating from VRRP or Backup-LMS Redundancy
ArubaOS has a local management switch (LMS) and a backup LMS. In a typical deployment, the AP contacts the
master controller and is directed to the controller that handles the AP connection and traffic via the LMS
parameter. If the LMS becomes unreachable and a backup LMS is specified, the AP attempts to reconnect to
that backup controller. This function provides Layer 3 and site redundancy when this level of redundancy is
required.
High Availability: Fast Failover provides redundancy for APs, but not for controllers. Deployments that require master
controller redundancy should continue to use an existing VRRP redundancy solution.
If your deployment currently uses a backup-LMS or VRRP redundancy solution, use the following procedures
to migrate to a High-Availability-based solution. For more information on this topology, see Master-
Redundancy Deployment Model on page 663.
Configuring a Master Controller for Redundancy and High Availability
Starting with ArubaOS 6.4, a backup master controller can use the High Availability feature. However, a backup-
master controller can only accept standby connections from APs, and will not serve active APs as long as its
master redundancy role is backup.
This typeof High Availability deployment has the following requirements and limitations:
l A backup-master controller can only form an active-standby pair with the master controller.
l The backup master cannot terminate active APs.
l Both the backup-master and master controllers must be configured with the dual controller role.
l The controller IPaddress defined in the high availability group profile must be the IP address of the VRRP
interface.
l The inter-controller heartbeat feature is not recommended for backup-master and master
controller pairs using the High Availability feature. If the inter-controller heartbeat feature is
enabled in a high availability group profile for redundant masters, the inter-controller failover time must be
greater than the VRRP failover time. That is, the (heartbeat interval * heartbeat threshold threshold) value
should be greater than the (advertisement time * 3 + preemption delay + skew time [which is based on
priority]).
Perform the following steps to configure controller high availability on a backup-master and master controller
pair.
1. Configure the high-availability group profile with a dual role for the master controller.
(host)(config) #ha group-profile grp1
(host)(HA group information "grp1"): controller <VRRP interface ipaddress> role dual
2. Configure the high-availability group profile with a dual role for the backup-master controller.
(host) (HA group information "grp1"): controller <VRRP interface ipaddress> role dual
Dell Networking W-Series ArubaOS 6.4.x | User Guide Increasing Network Uptime Through Redundancy and VRRP |
669