cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2680
Views
0
Helpful
17
Replies

AP's Disassociating

nickh2022
Level 1
Level 1

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 17

hall.m
Level 1
Level 1

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

No, it is enabled.

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
___________________________________________________________

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.

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
___________________________________________________________

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 ***

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

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

What size controller(s) and how many aps?

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

4402 - 25 licenses

10 AP's connected.

Leo Laohoo
Hall of Fame
Hall of Fame

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

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

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

Leo Laohoo
Hall of Fame
Hall of Fame

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.

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

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: