Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WLC - 2504

Hi people, 


Does some body can help me, I'm setting a WLC 2504 HA (high availability) and after the tests I noticed that when the primary controller get down the AP (Access Points) take about 20 minutes to register on th secundary controller (I'm not sure if its correct). 


There's an other point, when i log in on the SSID of the any AP (wireless net), I can't manage the controller and when a use net cable I can. 



  • Getting Started with Wireless
New Member

Hello, To add the ability to



To add the ability to manage your WLC via wireless you must enable the feature on the 2504.


Click Management > Mgmt Via Wireless. Check the mark and click Apply


For your HA issue, can you add a bit more information about your two controllers?

What version of code are both WLC's running? (show sysinfo)

Ensure your HA is configured on each AP. It sounds like you may be running two different codes or that the APs are not configured for HA properly.


Thank you

New Member

I agree your first line. The

I agree your first line.


The second problem:

I think he bought a HA controller 2504. In less the a second the standby controller becomes active, AP's and licenses are migrated directly. The AP HA is not an issue to me. It's recommended to fill in the primairy and secondary controller but in a HA setup not required.

Hall of Fame Super Gold

Just be aware the 2504 does

Just be aware the 2504 does not support AP SSO.  So when you fail the primary you will get a "hit" between 20 to 45 seconds.  


Now to your issue:  What is the setting for the "AP Failover Priority" for each AP?  By default it is set to "Low".  Have you tried setting this to "Critical"?

Hall of Fame Super Gold

I have already responded to

This widget could not be displayed.