Can anyone help to see why the pre-emption is not working?
1. AP connected to the master MD,
2. the master MD failed, AP failed over to the backup MD.
3. AP stayed connecting with the backup MD and did not go to connect to the Master MD unless rebooting AP.
Here are config for two managed devices.
(OAW-4750XM-2) #show vrrp
Virtual Router 12:Description mc-vrrpAdmin State UP, VR State MASTERIP Address 172.16.0.241, MAC Address 00:00:5e:00:01:0c, vlan 1Priority 110, Advertisement 1 sec, Preemption Enable Delay 30Auth type PASSWORD, Auth data: ********tracking is not enabled(OAW-4750XM-2) #
(172.16.0.252) #show vrrp
Virtual Router 12:Description mc-vrrpAdmin State UP, VR State BACKUPIP Address 172.16.0.241, MAC Address 00:00:5e:00:01:0c, vlan 1Priority 100, Advertisement 1 sec, Preemption Disable Delay 0Auth type PASSWORD, Auth data: ********tracking is not enabled(172.16.0.252) #
What version of AOS are you running? Is there a Mobility Master?
How are the APs discovering the master controller IP? ADP, DNS, DHCP, or static?
To clarify your question, is VRRP pre-emption not working, or has the master for the virtual IP moved back to OAW-4750XM-2 and the APs have not moved with it?
Thank you for your help!
1. version: 18.104.22.168
2. there is a mobility master
3. AP discovers the controller by Static IP (VIP)
4. virtual IP moved back to OAW-4750XM-2 and the APs have not moved with it.
Are the two MDs part of a cluster?
@BCroll wrote:Yes, thanks!
Because the two controllers are clustered, this makes sense.
The discovery methods (DNS/DHCP/Static/ADP/etc) are used to discover some/any node in the cluster. Once that node is contacted, the AP downloads the nodelist with all the IPs for controllers in the cluster. This nodelist contains the physical IPs, not virtual-IPs. The cluster leader also determines the APs anchor and standby anchor controller, and the AP builds tunnels to both.
In the case of clustering, the VIP from VRRP is used solely for discovering the cluster. AP tunnels do not use the VIP. The VIP adds robustness to prior discovery methods to ensure that as long as any controller in the cluster is active, APs will be able to discover the cluster.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.