AP Fast Failover does not provide redundancy for controllers or AP’s master discovery process, and hence customers using VRRP for controller redundancy should continue to use it. Also when a AP reboots it does not retain the information of the LMS. To provide full redundancy for a network which has a Master and Local controller, we need to configure VRRP, LMS/BKup LMS along with High Availability.
When AP Fast Failover is enabled, it has higher precedence over legacy lms/backup-lms based failover. i.e, the APs will first attempt AP Fast Failover.
- AP Fast Failover does not provide redundancy for controllers or AP’s master discovery process.
- To provide full redundancy we need to have VRRP for controller redundancy
- AP Fast Failover can coexist with VRRP, as long as VRRP-IP is not used in ha group-profile and as LMS in AP system profile.
- We can have vrrp ip on the dhcp server or DNS so the Aps can locate Aruba controller.
- Controller IP addresses configured in HA group profile must be IP address of vlan interface on which VRRP instance exists and also they should be switch ip-addresses.
- Need to configure a backup LMS ip on the system profile.
- AP gets ip address and master ip from the DHCP server or DNS
- Assuming we have vrrp ip as Master ip so even if one of them is down, the AP can still come up
- Aps will come up on the LMS ip
- Establish tunnels and perform HA failover if the LMS goes down
- If the LMS does not recover for a longer period, for the AP to survive a hard reboot, we need to configure backup LMS ip in the system profile.
- So when it reboots and finds out that LMS is not available it will try to use backup LMS ip. This is not HA rather legacy failover
#show datapath session table | include <ip address of AP>
#logging level debugging system process ha_mgr
#show ap debug system-status ap-name <ap-name>