AP registered into WLCs

Unanswered Question
May 25th, 2009

Hi I have two Wireless LAN Controller version 4.2, and the 1131 access point. The WLC number is called WLC01 and the name of the second WLC is WLC02. In the access points the Primary Controller Name and the Secondary Controller Name are configured as WLC01 and WLC02. The problem is that when the WLC1 (for example) fails the access points are not re-register in the WLC01, these remain registered in the Secondary Controller. To resolve this problem I restart the access point and these are registered in your primary wireless controller.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Leo Laohoo Mon, 05/25/2009 - 15:02

Hi Ricardo,

How or what method did you use to configure the Primary and Secondary Controller?

It WILL NOT WORK if you configured the parameters using the HTML/GUI method. Why? Because it's a bug. You can verify this by going using the CLI on the WLC: sh ap config general .

On the 2nd page, look at the entries of the Primary Cisco Switch Name and the Primary Cisco Switch IP Address.

To get this to work, you need BOTH the WLC name and the WLC IP Address. In the HTML/GUI it will only take EITHER the WLC name or the WLC IP Address. So the only way to get this to work in the 4.X.X IOS is to go through CLI (I know how painful it is): config ap primary-base

This bug was finally fixed after the 5.0 IOS.

Hope this helps.

derict Tue, 07/07/2009 - 20:41

We have one 1 WLC running but still unable to make the PRIMARY/2ndary setting to work. We have configured it but its not running ... Does this version still have the problem ?? Can't find anything in the caveat for this version and the 1 after this....

Leo Laohoo Wed, 07/08/2009 - 15:34

If you are talking about the "Global" settings, YES. A bug for the 5.0.X exist. Individual APs, NO. They've fixed this.

Hope this helps.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode