AP fallback

[gnijs]

Maybe a silly question, but when AP fallback is configured, when does an AP decide to fallback to its primary controller ?

When this controller responds to a ping ?

When the controller has an active mobility group connection ?

I want to prevent 300 APs from falling back to their primary controller until this controller is completely

ready and configured (AP groups, mobility domains, etc) to handle the APs. I don't want the APs to move back from the moment it replies to a ping, since at that time, the WLAN SSIDs, WLAN interfaces, AP groups etc might not yet have been configured and falling back at that moment, will only generate another downtime....

regards,

Geert

[Scott Fella]

AP Fallback requires the AP to contact the primary wlc. If you don't want the APs to fallback to the primary or secondary, disable ap fallback on the wlc the APs are connected to. APs will try to fallback when the other wlc becomes available when the mobility is up.

Sent from Cisco Technical Support iPhone App

[Abhishek Abhishek]

Hello,

As per your query i can suggest  you the following solution-

AP Fallback

Unlike Hot Standby Router Protocol (HSRP) standby, AP fallback disrupts wireless service while the AP failsover and then falls back to the configured controller. Remember that once an AP joins a controller, the AP is only programmed to leave that controller if:

• The AP loses responses from its keepalives to the controller.
  
• The customer resets the AP via the controller.
  
• The AP receives notification, via the mobility group members update from the current controller, that a configured controller (Primary/Secondary/Tertiary) is up, and the AP is currently joined to an unconfigured controller with AP fallback enabled.
  

It is important to note that the AP only performs AP fallback from an unconfigured controller to a configured controller (Primary/Secondary/Tertiary). The AP does not fall back from a secondary controller to the primary controller if it is currently joined to the secondary controller. This is because the secondary controller is a configured controller.

When the AP is joined to an unconfigured controller and it is notified that a configured controller is up and available via the mobility group members, it immediately leaves the current controller and joins the configured controller.

Hope this will help you.

[Ravi Singh]

Please go through the below link. Hope this will help you.

http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml