Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Cisco Support Community site will be in read only mode on Dec14, 2017 from 12:01am PST to 11:30am for standard maintenance. Sorry for the inconvenience.

New Member

AP's Disassociating

4402 - Ver 5.1.151.0

AP 1242

I keep receiving these errors from WCS about my AP's dropping

AP 'AP NAME' disassociated from Controller 'CONTROLLER IP'. (6 times)

Then 2 minutes later I get another message that it associated. This will happen many times through out the day. When I look at the controller there are 3 traps that keep coming up. They are.

AP's Interface:0(802.11b) Operation State Down: Base Radio MAC: Cause=Admin Configured

AP's Interface:1(802.11a) Operation State Down: Base Radio MAC: Cause=Detecting in-line power

AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:Cause=Heartbeat Timeout

I have another controller with the same software version with 1242 connected and dont have this problem.

Would would cause the problem with this specific controller and AP's?

17 REPLIES
New Member

Re: AP's Disassociating

Do you have AP fallback disabled on the controller that you are having issues with?

New Member

Re: AP's Disassociating

No, it is enabled.

Re: AP's Disassociating

How are these being powered? Are all these patched back to the same switch or more than 1 switch?

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: AP's Disassociating

Powered by 2 PoE switches. I have a total of 10 APs that are plugged into the 2 switches and when they drop, they all drop.

Re: AP's Disassociating

do they all drop at the same time or randomly. Have you tried debug any of the events?

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: AP's Disassociating

They all pretty much drop at the same time. Here is some of the errors from the eventlog on the AP. You will see at the bottom that it drops, then reconects.

*Jun 15 15:20:23.272: %LWAPP-3-CLIENTERRORLOG: Retransmission count for packet e

xceeded max(ECHO_REQUEST

, 1)

*Jun 15 15:20:23.273: %LWAPP-3-CLIENTERRORLOG: GOING BACK TO DISCOVER MODE

*Jun 15 15:20:23.273: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

*Jun 15 15:20:23.273: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

*Jun 15 15:20:23.274: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a

dministratively down

*Jun 15 15:20:23.274: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to a

dministratively down

*Jun 15 15:20:23.274: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Jun 15 15:20:23.275: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 15 15:20:23.275: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r

eset

*Jun 15 15:20:23.305: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Jun 15 15:20:23.307: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r

eset

*Jun 15 15:20:23.334: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 15 15:20:23.335: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r

eset

*Jun 15 15:20:23.365: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

--More-- or (q)uit

*Jun 15 15:20:33.283: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Jun 15 15:20:33.284: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a

dministratively down

*Jun 15 15:20:33.284: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to a

dministratively down

*Jun 15 15:20:34.283: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio

0, changed state to down

*Jun 15 15:20:34.283: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio

1, changed state to down

*Jun 15 15:20:38.294: %LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join

response (controller - MVD-WLC)

*Jun 15 15:20:38.295: %LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP

manager IP addresses remain

*Jun 15 15:20:43.305: %LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join

response (controller - MVD-WLC)

*Jun 15 15:20:43.305: %LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP

manager IP addresses remain

*Jun 15 15:20:48.344: *** Access point reloading. Reason: DID NOT GET JOIN RESPO

NSE ***

*Mar 1 00:01:02.221: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Mar 1 00:01:02.221: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad

ministratively down

*Mar 1 00:01:02.221: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to ad

ministratively down

*Jun 15 15:21:37.929: %LWAPP-5-CHANGED: LWAPP changed state to CFG

*Jun 15 15:21:43.007: *** Access point reloading. Reason: DID NOT GET CONFIG RES

PONSE ***

New Member

Re: AP's Disassociating

Hi,

What model of switch are these access points connected to? Since you mentioned that this is a POE switch, see if the url below helps:

http://www.cisco.com/en/US/docs/wireless/controller/5.1/configuration/guide/c51lwap.html#wp1111701

Regards,

Nagendra

New Member

Re: AP's Disassociating

3560's. Ill check out the URL..Thanks

Re: AP's Disassociating

What size controller(s) and how many aps?

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: AP's Disassociating

4402 - 25 licenses

10 AP's connected.

Hall of Fame Super Gold

Re: AP's Disassociating

*** Access point reloading. Reason: DID NOT GET CONFIG RESPONSE ***

Has any one of the 1242 AP's joined the controller before?

New Member

Re: AP's Disassociating

Yes they have. For example all of my AP's were connected yesterday. Then over night they disassociated/associated several times.

Hall of Fame Super Gold

Re: AP's Disassociating

Try the new firmware, 6.0.182.0, and see if this improves things. If not, then you can always run the secondary image on the WLC.

New Member

Re: AP's Disassociating

I did upgrade the firmware to 5.163.0 and things have been a little better...now the AP's are only dropping overnight.

New Member

Re: AP's Disassociating

You said you have another WLC that works just fine. Try on making the other APs there register to the WLC that's having problems. And try to register the APs that are dissasociating to the working WLC. From here, maybe we can get some ideas why you're having those problems.

Re: AP's Disassociating

Im working on an install this evening and i have a similar issue...

Get this ...

I have 30 AP1220s. These are setup to joing controller 1 for (first) controller 1 for (second) and controller 1 for (third) attempt. For testing..

The APs are on controller 2.

When you enable fallback these APS attempt to join controller 1, but cant. So they bounce... and stay on controller 2.

I disable failback and everything is fine...

i will sniff the ap tomorrow to see what it says ...

interesting .. wondering if there is a bug on the older aps...

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________

Re: AP's Disassociating

in my case its the 1220's ONLY that wont move...

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
1196
Views
0
Helpful
17
Replies
CreatePlease to create content