AP keeps disassociating

Answered Question
Mar 4th, 2010
User Badges:

I have an AP(1131) that keeps disassociating from the controller. It stays alive for about 10 mins then it doens't work anymore. I tired changing the AP but that didn't make a difference. I also tried changing the port on your 500 POE switch. My last effort to fix it was to put the AP on a 3550 switch with a power injector. Still no luck.


I don't understand why its doing this. I am able to connected to it and surf the internet for about 10 mins. After that It leaves the controller and just cycles through different colors.

Correct Answer by Leo Laohoo about 5 years 1 month ago
Some AP's are ok but some other are not, They are same model. We run the code 6.0.199.4 on the WLC's.

Can you try to upgrade your firmware to either 7.0.X or 7.2.X and try?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (3 ratings)
Loading.
Leo Laohoo Thu, 03/04/2010 - 12:04
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Would be  nice if you can post the error messages.  What firmware are you running?  Is your AP using PoE or power injector?  Is your AP rebooting?

Scott Fella Fri, 03/05/2010 - 07:34
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Like Leo mentioned, you need to tell us more.  Console into the AP and log the output and post that.  That will be a good start.

cschweigert Mon, 03/08/2010 - 12:36
User Badges:

I am having a similar issue. Here are the messages from the WLC. I have LWAP's and I have tried resetting them, unplugging them and alos clearing the config. Nothing seems to work.


0Mon Mar 8 14:40:20 2010AP 'CFC_2_AP125211', MAC: 00:24:14:85:84:d0 disassociated  previously due to AP Reset. Last reboot reason: operator changed 11g  mode
1Mon Mar 8 14:40:16 2010AP 'CFC_1_AP125210', MAC: 00:24:14:85:9b:b0 disassociated  previously due to AP Reset. Last reboot reason: operator changed 11g  mode
2Mon Mar 8 14:40:09 2010AP Disassociated. Base Radio MAC:00:24:14:85:84:d0
3Mon Mar 8 14:40:09 2010AP's Interface:1(802.11a) Operation State Down: Base Radio  MAC:00:24:14:85:84:d0 Cause=Max Retransmission
4Mon Mar 8 14:40:09 2010AP's Interface:0(802.11b) Operation State Down: Base Radio  MAC:00:24:14:85:84:d0 Cause=Max Retransmission
5Mon Mar 8 14:40:04 2010AP Disassociated. Base Radio MAC:00:24:14:85:9b:b0
6Mon Mar 8 14:40:04 2010AP's Interface:1(802.11a) Operation State Down: Base Radio  MAC:00:24:14:85:9b:b0 Cause=Max Retransmission
7Mon Mar 8 14:40:04 2010AP's Interface:0(802.11b) Operation State Down: Base Radio  MAC:00:24:14:85:9b:b0 Cause=Max Retransmission
8Mon Mar 8 14:39:52 2010AP 'CFC_2_AP125211', MAC: 00:24:14:85:84:d0 disassociated  previously due to AP Reset. Last reboot reason: operator changed 11g  mode
9Mon Mar 8 14:39:47 2010AP 'CFC_1_AP125210', MAC: 00:24:14:85:9b:b0 disassociated  previously due to AP Reset. Last reboot reason: operator changed 11g mode
Leo Laohoo Mon, 03/08/2010 - 15:00
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

What firmware are you running?  Is your AP using PoE or power injector?  Is your AP rebooting?

cschweigert Mon, 03/08/2010 - 15:12
User Badges:

AP is not rebooting. I am running boot version 12.4.10.0 software version 5.2.157.0. The AP is using PoE

Leo Laohoo Mon, 03/08/2010 - 15:53
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Errrr ... Do you know that the 1250 requires a minimum of 19.0 watts of power to operate both radios?  PoE will only support up to 15.4 watts.  If you upgrade to 6.0.182.0 and later, both radios will be fully operational (at 15.4 watts of power) but at a lower MCS rates.

cschweigert Mon, 03/08/2010 - 15:55
User Badges:

I did not know that. I do know that I have 12 AP's total at this one site and two are having this issue. All AP's are the same model and configuration. All running both radios.

Leo Laohoo Mon, 03/08/2010 - 15:59
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

And I'd stay away form the 5.X firmware.  It's imfamously known for full of bugs.  I had issues when the radios would just shut down and recover for no apparent reason.  Upgraded the firmware and wallah!

cschweigert Mon, 03/08/2010 - 16:00
User Badges:

ic, well thanks for your help. I will see about doing an upgrade. I will reply to the post if that fixes the 'issue'

cschweigert Mon, 03/15/2010 - 14:13
User Badges:

So we upgraded the WLC to version 6.0.196 from 5.x. There was a bug with running capwap and having AP's join the WLC across a layer 3 boundary. So the symptoms that we were seeing was the AP's would join up for a short time (Maybe 20 seconds) and then dis-associate.The AP would just go from Join to Config, as it tried to pull down the configuration, and then back to discovery. One thing that we did to trouble shoot was place a bad AP in the spot that a known good one was working. The AP came right up like it should. The known good one, once placed in the bad AP's spot would immediately start having issues. I hope this helps anyone who may be having some similar issues. And if anyone has some more details about this that I have left out, please feel free to fill in the missing pieces.


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsx69535


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsy88329



I have placed some log data from the AP's. These logs were continuously repeating.


*Mar  1 00:00:37.295: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:00:37.303: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:00:38.287: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:00:38.295: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar  1 00:00:39.391: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:00:48.391: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar 10 21:37:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.x.x.x peer_port: 5246
*Mar 10 21:37:21.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.x.x.x peer_port: 5246
*Mar 10 21:37:21.663: %CAPWAP-5-SENDJOIN: sending Join Request to 10.x.x.x
*Mar 10 21:37:21.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Mar 10 21:37:21.755: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Mar 10 21:37:39.755: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
., 1)
*Mar 10 21:37:39.755: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Mar 10 21:37:39.755: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.x.x.x
*Mar 10 21:37:39.791: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 10 21:37:39.791: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 10 21:37:39.799: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 10 21:37:39.799: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 10 21:37:39.803: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 10 21:37:39.807: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 10 21:37:39.811: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 10 21:37:39.811: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 10 21:37:39.819: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 10 21:37:39.819: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 10 21:37:39.823: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Scott Fella Mon, 03/15/2010 - 18:51
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Looks like you narrowed it down to maybe the cable or the switchport.  Move the cable to a good known AP switchport if you can and see if that works, if not... time to test that cable.  Since you were able to take one of those AP's that were having issues and make it work on another cable and switchport, then you don't have any issues with the AP and that is why I'm thinking its either the cable or switchport or switchport config.

Leo Laohoo Mon, 03/15/2010 - 18:54
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Good point from Scott.  If your switch happens to be a 2350, 2750, 2960, 3560/3560E, 3750/3750E then you can test your copper cable using the "test cable-diagnostic tdr interface " command.  To view the result, use the "show cable-diagnostic tdr interface ".

cschweigert Tue, 03/16/2010 - 15:37
User Badges:

We resolved the issue with an upgrade of the WLC. I providing the Bug's that were matching to justify this upgrade. It did not seem to be a cabling or routing issue but a bug in the version of code the WLC was pushing out to the AP's.

Leo Laohoo Tue, 03/16/2010 - 15:40
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

If the issue has been resolved after a firmware upgrade, can you rate Scott's and my post and mark this topic as "Answered"?  Thank you very much.

cschweigert Tue, 03/16/2010 - 15:49
User Badges:

Yes sure. I did not ask the original question or else I would mark this as being answered for sure!

Scott Fella Tue, 03/16/2010 - 17:43
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

That is weird since you took one of the AP's and connected it to a good known port and it worked and took a good known AP and connected it to a known bad port and that didn't work.  Oh well.... you got it working.

david_mayor Thu, 06/14/2012 - 06:18
User Badges:

Hello,

We are facing the same issue as described. The error message is the same:


disassociated previously due to AP Reset. Uptime: 68 days, 13 h 14 m 40 s . Last reset reason: operator changed 11g mode.


Some AP's are ok but some other are not, They are same model. We run the code 6.0.199.4 on the WLC's.


Any ideas ?


Thanks a lot.

Correct Answer
Leo Laohoo Thu, 06/14/2012 - 15:50
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Some AP's are ok but some other are not, They are same model. We run the code 6.0.199.4 on the WLC's.

Can you try to upgrade your firmware to either 7.0.X or 7.2.X and try?

Actions

This Discussion