Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

AP will not connect properly to the primary controller but goes to the secondary

Unanswered Question
Sep 3rd, 2010
User Badges:

I have a strange situation in which I have 2 remote APs running HREAP that will not connect to the primary controller. It keeps going to what I designated to be my secondary controller. Yes, the name and IP address are correct ( double and triple checked) when I entered the information in the High availability fields for Primary and secondary.  It's seems to ignore what I have for the Primary controller. I have 40 other remote APs and they all or not acting like this. I can test and totally remove the info from the secondary field and see what happens but was wondering has anybody seen this ?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Kayle Miller Fri, 09/03/2010 - 08:13
User Badges:
  • Silver, 250 points or more

The only time I have seen something similar to this TAC couldn't find a cause but rebooting the primary controller resolved the issue. No one is really sure why.. Some AP's could join the primary controller but others couldn't.. it was wierd.

Hope this help.. Please rate useful posts.


kwanm63my Fri, 09/03/2010 - 09:58
User Badges:

anybody know the command under the controller CLI where you can manually tell the AP which controller to go to ?  Want to give that a shot first.. I did it once but can't remember the command.

Surendra BG Fri, 09/03/2010 - 10:07
User Badges:
  • Cisco Employee,

AP#lwapp ap ip address
AP#lwapp ap ip default−gateway
AP#lwapp ap controller ip address
AP#lwapp ap hostname

Surendra BG Fri, 09/03/2010 - 10:09
User Badges:
  • Cisco Employee,

use "clear lwapp private-config" then use those commands.. this will erase config which the AP downloaded fro mthe previous WLC




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