topic Re: AP Fallback in Wireless

AP Fallback

rchester — Sun, 04 Jul 2021 02:47:27 GMT

regarding AP Fallback for 4.0 code:

If a primary controller has failed and then comes back online does the AP re-join automaticaly with loss of service?

Thanks

Re: AP Fallback

Surendra BG — Tue, 08 Feb 2011 14:35:43 GMT

Hi,

If the access point was previously associated to a controller, the IP addresses of the primary, secondary, and tertiary controllers are stored in the access point's non-volatile memory. This process of storing controller IP addresses on access points for later deployment is called priming the access point.

The APs are supposed to join back to the WLC..

lemme know if this answered your question..

Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Re: AP Fallback

rchester — Tue, 08 Feb 2011 14:52:58 GMT

So if the original controller becomes avaialble does the AP join to it automaticaly and is service affected?

thanks

Re: AP Fallback

Surendra BG — Tue, 08 Feb 2011 15:06:26 GMT

Hi,

I guess not.. This doesnot work like HSRP.. i guess on the later version we have the priority configure to it.. but, till we do it manually it wont.. AFAIK

lemme know if this answered your question..

Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Re: AP Fallback

Leo Laohoo — Tue, 08 Feb 2011 21:31:47 GMT

So if the original controller becomes avaialble does the AP join to it automaticaly and is service affected?

Yes. There's a loss of wireless services during the switch over from the secondary/tertiary controller back to the primary controller.

NOTE: Just make sure you configure the primary/secondary/tertiary controllers correctly. During my "playing around" with the 4.0 the configuration of the primary/secondary/tertiary controllers using GUI does not work. The primary/secondary/tertiary controllers details (IP address and WLC names) need to be entered via CLI.