APs Randomly Stops Associating with LWAPP Controller

Unanswered Question
Apr 23rd, 2007
User Badges:

We currently have 250+ AP1020 and AP1220s deployed. Every two to three weeks, an AP randomly stops getting associated with the LWAPP controller. The odd thing is how this phenomenon only effects one AP at a time ...seems like 1 is always getting left out.

If left alone, after 2 to 5 days, the problem fixes itself ...the AP in question starts working again, but another one gets left out in the cold.

This has been an ongoing cycle for the last four months. It's not a major problem. ...solutions for it that I have done include replacing the AP, restarting the AP and doing a shut/noshut on the switchport it's connected to, or just waiting it out.

I really just want to know why this is happening, is it happening to anyone else, and how can I get it to stop?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Mon, 04/23/2007 - 08:42
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi West,

It almost sounds as if you might be running into this issue;

Field Notice: FN - 62561 - Wireless Lan Controller (WLC) Fails to Decrypt Lightweight Access Point Protocol (LWAPP) Control Traffic - Requires Upgrade

From this doc;


Hope this helps!



This Discussion



Trending Topics - Security & Network