Does anyone have any info on implementing fail-over for APs to another Cluster? Simply adding a LMS backup IP (Cluster 2 VIP) in the AP group didnt work :D I know a bootstrap would occur I don't even see the AP in MM after powering off the cluster.
Additional info: I'm using DHCP options 43 and 60 for new APs.
Yes I have two MCs in each Cluster.
I powered off each Cluster member. Watched the A-AAC change to the S-AAC.
Powered off the last MC of cluster.
AP never reported into BLMS (VIP) of Cluster 2.
When you say " you don't even see the AP in the MM" what command are you using the see the AP in the MM?
Is there a specific guide on how AP Failover to another cluster should be configured? i.e. where is the hierarchy the AP-Groups, VLANs, and WLANs should be created? I can find articles stating it can be done using LMS and B-LMS, but no suggestions on the actual configuration.
Do you want to make an AP failover to a specific controller in the cluster?
For more information on how AP load balancing is configured,
refer the AOS UG 126.96.36.199 (Page: 373)
Say I have 2 different datacenters, and a cluster in each datacenter. If datacenter 1 cluster goes down I want the APs that typically terminate to that cluster to failover to datacenter 2 cluster.
So the scenario is like this.
Datacenter 1 - cluster 1 - APs terminated on a controller in this cluster.
Datacenter 2 - cluster 2 - APs should failover to a controller in this cluster if the controller that the APs are terminated to on cluster 1 fails.
Try this solution
Cluster 1 - This will have a MC which acts as a LMS to the APs (say 10.0.0.1 )
Cluster 2- Choose a controller which should act as a B-LMS to the AP when they fail over. (10.0.0.2)
Assuming that the datacenters have L3 connectivity, configure a vrrp instance as follows.
On Cluster 1 MC
vlan <vlan used>
ip address 10.0.0.1
authentication <choice of password>
On cluster 2 Preferred MC
ip address 10.0.0.2
Now go to the AP system profile configured for the APs, can be viewed using the command "show ap system-profile"
open the ap system-profile using the command
ap system-profile <name of the profile used>
lms-ip <cluster 1 MC>
Bckup-lms-ip <cluster 2 MC>
Save and deploy the changes.
--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.--Problem Solved? Click "Accepted Solution" in a post.
A_RAK is correct, that is the way of doing such a scenario. One thing to add. Instead of using a specific controller IP for LMS and Backup LMS I would use the Cluster VRRP for this entry. This makes sure, that the LMS or Backup LMS is available regardless of the status of a single controller.
The AP will first connect to the LMS IP. This should be the cluster VIP of cluster 1. it will then learn all Controllers in cluster 1 and will create tunnels to the AAC and S-AAC in Cluster 1. The Ap will only failover to cluster 2 if all controllers in cluster 1 are down or not reachable. The AP will not create a standby tunnel to a controller in Cluster 2 before all Controllers in cluster 1 are down.
Hope this gives more insights.
Would you need to have all the VLANs configure on both clusters?
e.g. Cluster 1 allowed VLANs configured on Cluster 2, and vice versa?
Yes. OR, you could create the WLANs (Virtual AP) with a VLAN name and then define a name to vlan number mapping on each 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.