We load balance the APs across the 2 controllers, so I therefore thought I would need 2 vrrp instance, so the controller swould be in a master/backup, backup/master operational state for whicher APs were terminated on them. Again, this is they way our current setup was, so I merely transferring this part of the ocnfig over. I then used the VIP as the LMS IP in the AP System settings. So I could use one of these VIPY for dns?
The wlan is layer2 and traffic is tunnelled back to the controllers, rather than bridged onto the wired network.
Shoud I be creating new subnets for vrrp rather than using the same ones that clients use, or does this not really matter?
In the absence of the master, and APs rebootoing, will they still get their config from the local?
These extracts suggest they would, although its almost a contradiction!, but I assume I would have to be using one of the VIP as dns.
Initial AP configuration:When an AP first boots up, it contactsits master to receive the configuration
generated by the master. The master compares the AP information and determines its group
assignment, and then redirects that AP to the proper local.
P, AM, and SM configuration, management, and software updates:All Aruba APs are dependent APs,
which means they do not, in most instances, store configuration settings in the way that a traditional
autonomous AP would. Instead, at boot time each AP downloads its current configuration from the local.
Its clear from reading the docs that you wouldnt normally terminate the APs on a Master in a Master/Local pair, but again, this is just how things have been.. so perhaps I maybe need to rethink our strategy. However, if an AP will still get its config from the local in the absence of the master, then at least we do have some redundancy. That said, weve never lost the master, then had APs reboot, but you have to factor in such scenarios.