@Christofferwrote:
So now you´re saying that with 2 standalone controllers, running 8.2, configured for "master redundancy 6.5 style" without a mobility master there´s no config sync? Hence it´s not master redundancy but just a vrrp redundancy? I´d have to configure all AP groups, profiles and roles etc individually on each controller?
Once again sorry for the confusion but I need to understand the limitations of this kind of setup :)
No worries, it's important to get terminology right. ;)
In 6.x, the master and standalone roles were basically synonymous. A standalone controller was simply a master with no locals. In 8.x that is no longer the case.
To expand on my previous comment, in 8.x the Master controller (MCM) can not terminate APs. Since a controller only operates in one mode, either master, or standalone, it does not perform both functions. If there are only two controllers deployed today with 6.x, setting the controller's role to MCM in 8.x without adding another component is not how you would want to go.
The standalone controller role does terminate AP tunnels, and standalone controllers also support VRRP redundancy. However, standalone controllers do not sync configuration with each other, as they are standalone managed entities.
For an existing deployment with only two controllers, the options for migrating to 8.x and retaining redundancy are: standalone controllers (not masters, no config sync) with VRRP, or add a Mobility Master (or VMM) and have the two controllers operate as MDs from the MM.