03-10-2015 01:36 AM
I'm sure I did know the answer to this, but here goes...
Let’s keep it simple in terms of numbers.
- Two local controllers on a site, and a master off-site.
- Each local controller has 8 AP licenses, and so does the master.
- Centralised licensing is OFF.
- Each of the locals has a VRRP which it “owns” (priority), and each is backup for the other.
- Each VRRP is specified as the LMS in 1 of 2 site specific AP groups.
- The backup LMS in each group is the master.
- There are 10 APs in the site. 5 in group 1, and 5 in group 2. So under normal operation, 5 on each local.
I don’t have the lab kit to test it, but I’m pretty sure last time I saw things in this setup, where one of the locals fails, 2 of the APs in that "failing-over" group (i.e. the last 2 of the 5 to try) will continue to try and connect to the other local (via the VRRP) and not the master (backup-lms)? I think this occurs because the other local will still communicate with these APs, it just doesn’t have the licenses to support/enable them? I.e. it's not that the AP>controller tunnel is down, it's more that it's unable to activate service.
The main bit I can't remember in this scenario, is whether the 2 limbo APs will EVER try to move to the backup, or if they persist forever trying to talk to the local that's out of licenses. If they do eventually try to move, I would envisage this is determined by the bootstrap-threshold or similar in the ap-sys profile?
Cheers in advance!
03-10-2015 05:05 AM
The APs get "stuck" on the controller with no licenses with an "L" was the last behavior observed.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base