3500i Access Point Primary Secondary Join issues

[jbongiorno2]

Question: We have a site that is running 8.0.121 and has (85) 3502i access points. When we fail access points to the secondary controller that exists in another site same code version, anywhere from 15%-45% of the access points will not rejoin the Primary controller following a reboot. To get them to come back to the Primary Controller we must completely factory reset the access points and then they come to the primary and we can re-configure them accordingly. Unfortunately this does not guarantee their correct action the next time. Has anyone seen this and if so what was/is your recommendation to solve? Thanks JB

[Freerk Terpstra]

How are the access-points configured and learn about both controllers? For an predictive fail-over and fall-back you should configure the primary and secondary controller for all access-points on a individual level (High Availability tab). To make sure that the access-points go back to their primary WLC once joined on the secondary WLC, the option "AP Fallback" should be enabled on the secondary WLC. This options can be found under the global "Controller" tab of the WLC.

If the configuration described above is in place, please provide us with the console output of one of the access-points not joining the primary controller.

Please rate useful posts... :-)