WLC and AIR-AP1231

Unanswered Question
Mar 25th, 2009

Dear all,

We have WLC and AIR-AP1231. All APs have been converted to light weight image successfully and they have joined the Controller and they are working fine.

The problem is that from time to time the access points get de-associated from the controller and I have to shut/no shut the switch port to get the associated again.

I have tried to upgrade the WLC from 4.X to 5.2 to resolve the problem without any luck.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Leo Laohoo Wed, 03/25/2009 - 16:31

Try this ...

Go to Go to Monitor, under Access Point Summary, All APs -> Detail. Choose the AP that's giving you the problem, go to the Advanced tab. Under Power Over Ethernet Settings choose Power Injector State and Installed if AP is powered using an injector OR choose Pre-Standard State if powered with a PoE switch.

abu_khair Wed, 03/25/2009 - 22:35

Thank you for your reply. The Power Over Ethernet Settings are not active for the 1231 APs but there are active for the 1252 APs. I would like to mention here that the 11231 access points powered by power cube not power injecter nor POE switch port.

Leo Laohoo Thu, 03/26/2009 - 16:50

I had the same problem with you. The only way for me to stabilize my AP's was to do this.

abu_khair Fri, 03/27/2009 - 01:12

Thank you. I will investigate why these settings are not active.

zhenningx Fri, 03/27/2009 - 14:07

I see AP rebooting issue with wism 5.2.157 and AP 1231. If I look at the console logs on those APs, usually I see two following logs before the AP reboot:

%CAPWAP-5-DTLSREQSEND: DTLS connection request

sent peer_ip: peer_port: 5246

%CAPWAP-5-DTLSREQSUCC: DTLS connection created

sucessfully peer_ip: peer_port: 5246

I have opened a case and TAC identified a bug CSCsy74738 and are waiting for the fixed version now.


abu_khair Sat, 04/04/2009 - 22:34

Dear all,

I have configured a static IP address on each Access Point and now it is 5 days and none of the AP lose its association with the controller. I hope this will solve the problem.



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