Will an AP join the desired Flexconnect group by default in an HA N+1 redundancy as it does in HA-SSO as a cloud entry ? Does it join the same Flexconnect group of which it was a member of prior to switchover or do I need to add it into the desired Flexconnect group manually in an HA N+1 scenario ?
In N+1 design, you need to make sure all the configurations are identical except for the obvious, hostname and ip. If you didn’t configure the groups for example, if the ap moved to that controller, it would use the default group. Best is to make sure your primary is exactly what you want and then run a diff to compare config a from the primary and secondary to make sure nothing is missing.
@Scott Fella@Supermantech When AP receives the Flexconnect group it is supposed to join either through cloud provisioning or via a previous WLC configuration (say primary WLC) then it by joins the "SAME GROUP" name in Secondary WLC by default as a "Cloud" entry.
If tat particular AP is added as a member of some another flexconnect group (different than as in primary WLC) in secondary WLC, then it overrides the prev Flex group name it received from primary WLC and joins the Flex Group its added into in Secondary WLC, this is called an "Admin" entry.
I have never ever heard of that since FlexConnect has been a feature in AireOS. An ap will join a FlexConnect group you a manual assignment and that group has to be the same name on all other WLCs or else it will join the default group. Does not make sense to have different configurations on a backup controller(s). If your design is to have two controllers and not have them identical, then you have two separate instances of controllers that do not back each other up.
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
