Users Guide

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 619.
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
Migrating from VRRP Redundancy
Perform the following steps to migrate from VRRP to High-Availability redundancy:
1. Remove the VRRP IP address as the LMS IP address of the AP:
(host) (AP system profile) #no lms-ip
2. Configure the AP to use the active controller’s IP address (not VRRP the IP address) as the LMS-IP for the AP:
(host) (AP system profile) #lms-ip <ipaddress>
3. Configure the AP to use the standby controller IP address (not VRRP the IP address) as the backup LMS-IP
for the AP:
(host) (AP system profile) #bkup-lms-ip <ipaddress>
4. Configure the master controller with a dual role in the high-availability group profile:
(host) (config) #ha group-profile grp1
(host) (HA group information "grp1"): controller <ipaddress> role dual
5. Configure the standby controller with a dual role in the high-availability group profile:
(host) (HA group information "grp1"): controller <ipaddress> role dual
Migrating from Backup-LMS Redundancy
Perform the following steps to migrate from Backup-LMS to High-Availability redundancy and maintain the
existing configuration as defined by the lms-ip and bkup-lms-ip parameters in the APsystem profile.
1. Configure the controller serving the AP with a dual role in the high-availability group profile:
Dell Networking W-Series ArubaOS 6.5.x | User Guide Increasing Network Uptime Through Redundancy and VRRP | 625