04-18-2017 04:19 AM
Is there anything that tells me the reason for an AP Failover? I am seeing some APs failing over even though there's nothing wrong with the network. The controller has been up since it was installed and serves about 50 active APs, 50 standby APs, some APs are at the same site as the controller, others are at satellite sites connected via a 10Mbps WAN link.
At the satellite sites, I could understand but it's never all the APs failing over, only one or 2. Even a few APs based at the same site as the controller are failing over. Again, it's not all the APs and they are connected into the same switch. I have ruled network congestion out on the satellite sites as usage rarely get over 50% for many of them.
On the HA:FF Settings, I have Inter-Controller heartbeat enabled at 5*100ms. Preemption is disabled. If it was the inter-controller hearbeat that was causing the failover, wouldn't all APs associated with the controller move?
05-31-2017 06:45 AM
I've done some more digging on the issue and found the following error messages in the 'Diagnostics --> ACCESS POINT --> System Status'.
HA Failover Information Date Time Reason (Latest 10) 2017-02-14 17:26:26 Failover request from standby: fail-over to 172.21.1.61 2017-03-07 11:25:58 Failover request from standby: fail-over to 172.20.1.61 2017-04-13 06:48:45 Failover request from standby: fail-over to 172.21.1.61
The AP's primary controller is 172.21.1.61 and is based on a different VLAN at the same site as the AP. The AP's secondary controller is 172.20.1.61 and is on a different site connected via a Private WAN link.
Does this mean it is the controllers that are causing the failover rather than the APs?