topic Wireless Clients get disconnected in Wireless

Wireless Clients get disconnected

guardian-de — Sun, 04 Jul 2021 05:36:38 GMT

I have a wireless client getting disconnected but I don't know what is causing the disassociation. Problem is, the client gets disconnected while the customer is working - it takes some time to reconnect, cause the WLC / client is stuck some time in doing new DHCP reassignment after reassociation. Attached the log part - question is : How to find the reason for disconnecting "

Sent Disassociate to mobile on AP e8:ba:70:61:45:80-0 (reason 1, caller apf_ms.c:5558)"

*spamApTask6: Sep 03 16:54:51.529: 68:a8:6d:15:e2:54 Cleaning up state for STA 68:a8:6d:15:e2:54 due to event for AP e8:ba:70:61:45:80(0)

*apfReceiveTask: Sep 03 16:54:51.530: 68:a8:6d:15:e2:54 apfSendDisAssocMsgDebug (apf_80211.c:2162) Changing state for mobile 68:a8:6d:15:e2:54 on AP e8:ba:70:61:45:80 from Associated to Disassociated

*apfReceiveTask: Sep 03 16:54:51.532: 68:a8:6d:15:e2:54 Sent Disassociate to mobile on AP e8:ba:70:61:45:80-0 (reason 1, caller apf_ms.c:5558)

Re: Wireless Clients get disconnected

naburleson — Mon, 03 Sep 2012 20:18:42 GMT

Have you updated the client side drivers?

Sent from Cisco Technical Support iPad App

Re: Wireless Clients get disconnected

guardian-de — Mon, 03 Sep 2012 20:25:41 GMT

As far I see it, it's a disassociation coming from the WLC / AP and the client driver shouldn't be the problem ? The client is a MacBook Air.

Wireless Clients get disconnected

Leo Laohoo — Mon, 03 Sep 2012 22:18:05 GMT

I have a wireless client getting disconnected but I don't know what is causing the disassociation.

Only ONE (1) client having a problem?

How many TOTAL clients do you have?

What is the signal strength from the WLC to the client?

What is the signal strength from the client to the WLC?

What kind of encryption/security are you using?

Do you have Aeronet IE disabled?

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 11:48:59 GMT

Only ONE (1) client having a problem?

Actually I know of one client with that problem. It's a Mac Book Air of 2012.

We have some 10 test clients on this SSID but this person is using it frequently.

How many TOTAL clients do you have?

The 5508 on 7.2.103.0 has 35 APs with 100 Clients connected. Most clients are iPhones

which are connected to another SSID. They do not work like the Mac Book user.

What is the signal strength from the WLC to the client?

The AP is 7 Meters from the client - the client is not moved placed on the desk.

Attached the client stats which is connected to AP name DE-WK1-E2IN-01.

Client Statistics:

Number of Bytes Received................... 321565

Number of Bytes Sent....................... 317435

Number of Packets Received................. 4443

Number of Packets Sent..................... 1754

Number of Interim-Update Sent.............. 0

Number of EAP Id Request Msg Timeouts...... 0

Number of EAP Request Msg Timeouts......... 0

Number of EAP Key Msg Timeouts............. 1

Number of Data Retries..................... 612

Number of RTS Retries...................... 168

Number of Duplicate Received Packets....... 597

Number of Decrypt Failed Packets........... 0

Number of Mic Failured Packets............. 0

Number of Mic Missing Packets.............. 0

Number of RA Packets Dropped............... 0

Number of Policy Errors.................... 0

Radio Signal Strength Indicator............ -54 dBm

Signal to Noise Ratio...................... 27 dB

Nearby AP Statistics:

DE-WK1-E1H4-16058(slot 0)

antenna0: 293 secs ago................... -97 dBm

DE-WK1-E2H4-16057(slot 0)

antenna0: 293 secs ago................... -99 dBm

DE-WK1-EGH4-16051(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-WK1-E2H4-16043(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-WK1-LKH4-16048(slot 0)

antenna0: 356 secs ago................... -95 dBm

DE-WK1-KAH4-16046(slot 0)

antenna0: 293 secs ago................... -99 dBm

DE-WK1-KGC2-16034(slot 0)

antenna1: 16357 secs ago................. -93 dBm

DE-WK1-E2H4-16056(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-JON-RDUG-00011(slot 0)

antenna0: 16357 secs ago................. -92 dBm

antenna1: 16357 secs ago................. -91 dBm

DE-WK1-E2IN-01(slot 0)

antenna0: 293 secs ago................... -63 dBm

antenna1: 293 secs ago................... -60 dBm

What is the signal strength from the client to the WLC?

What kind of encryption/security are you using?

This SSID is running WPA2 AES PSK. We had the MacBook running with EAP-TLS

WPA2 Enterprise but experienced problems with Bluetooth / Wireless on getting back

out of sleep modus. We had to disable / enable the wireless network on the MacBook to

reconnect.

Do you have Aeronet IE disabled?

We had it enabled but after some internet search I disabled it yesterday. So SSID is

running without Aironet IE now.

Wireless Clients get disconnected

George Stefanick — Tue, 04 Sep 2012 16:19:17 GMT

One thing not mentioned and I know could be of interest , is the enable session time out on the WLAN. Is that enabled ?

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 17:16:31 GMT

Hi Gerorge, no session timer on WLAN is disabled. Global user-idle timer ist at 30mins.

Wireless Clients get disconnected

George Stefanick — Tue, 04 Sep 2012 17:25:27 GMT

ok, we can cross that off the list. i guess my next area of interest is ..

1 . can you replicate the issue and if so how often does it happen

2. what OS and rev is on the Air

3. im not on 7.2 code so i cant comment on that one, but you may want to open a tac case and look at the release notes

4. what model aps are you using

5. PSK, we can rule our EAP issues

hummmmm... let me think about this one ..

Wireless Clients get disconnected

daviwatk — Tue, 04 Sep 2012 18:15:42 GMT

Can you post the entire client debug you have so we can see what events are taking place prior to the client being deauthenticated message. It seems like this could be possible RRM channel change or some other AP "event"; maybe even an idle timeout or re-transmissions, maybe broadcast key roation? (Cleaning up state for STA 68:a8:6d:15:e2:54 due to event for AP e8:ba:70:61:45:80(0)) -- "due to event for AP". Also, what model and what mode are these APs running in? Local/FlexConnect? If Flex, are you local switching?

Wireless Clients get disconnected

George Stefanick — Tue, 04 Sep 2012 18:20:07 GMT

All great points David ... +5

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 18:47:06 GMT

Hi Geroge,

to your questions :

1.) Replicate not but it happens at least 1-2 a day.

2.) OS is Mountain Lion Mac Book Air Broadcom Chipset BCM43xx (5.106.98.81.21) - I assume. I do not have access to the OS right now and not until Monday, but I am using the same Mac Book Air Model. I read some posts and now downgraded my driver to Snow Leopard Version 5.10.131.42.4. I planned to do this with the other Air next monday.

3.) I might do so, yes. Started to find a solution here first.

4.) We use 4 x 1242 and 1 x 3502I. The client is mostly connected to 3502I.

5.) Heh - "rule issues" means what ?

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 18:51:44 GMT

I can post it - no access right now. Will do on monday. But those events I posted in the beginning of the thread are the first ones while the client was on "debug client ".

I also thought about an AP event as stated by the message. Question is : How to find this event / what to debug to see AP events related to client events.

All APs are running in Local Mode.

What irritates me is, that sometimes the client starts to roam between the 3502I (7 meters away) and another AP with a much weaker signal. I cannot say if the error is related to the roaming but the error "

due to event for AP e8:ba:70:61:45:80" is linked to the 3502I AP with the right MAC.

Wireless Clients get disconnected

George Stefanick — Tue, 04 Sep 2012 18:52:34 GMT

sorry, type o .. rule out

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 18:55:52 GMT

4.) 4 x 1242 and 1 x 3502 means on this floor. There are more neighbours, but the ones on the floor are DE-WK1-E2*. The 3502 is the only one nearby.

I also thought about a mixed 802.11g / 802.11n Problem, as the 1242 are bg and the 3502I has N enabled also ? Might this cause trouble ? Still I was thinking, that it is a controller driven event like David pointed out - so for me I thought to start finding the "AP event".

Nearby AP Statistics:

DE-WK1-E1H4-16058(slot 0)

antenna0: 293 secs ago................... -97 dBm

DE-WK1-E2H4-16057(slot 0)

antenna0: 293 secs ago................... -99 dBm

DE-WK1-EGH4-16051(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-WK1-E2H4-16043(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-WK1-LKH4-16048(slot 0)

antenna0: 356 secs ago................... -95 dBm

DE-WK1-KAH4-16046(slot 0)

antenna0: 293 secs ago................... -99 dBm

DE-WK1-KGC2-16034(slot 0)

antenna1: 16357 secs ago................. -93 dBm

DE-WK1-E2H4-16056(slot 0)

antenna0: 293 secs ago................... -95 dBm

DE-JON-RDUG-00011(slot 0)

antenna0: 16357 secs ago................. -92 dBm

antenna1: 16357 secs ago................. -91 dBm

DE-WK1-E2IN-01(slot 0)

antenna0: 293 secs ago................... -63 dBm

antenna1: 293 secs ago................... -60 dBm

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 19:02:12 GMT

One more info. The customer said the problem started with switching to 7.2.103.0 code on 5508 controllers. We were on 7.0.x code with 4404 before and are actually migrating. So 35 are on 5508 - 130 left on 4404. The infrastructures are seperated concerning near-by APs, RF Group, Mobility Group, etc. - so we tried to migrate buildings / areas.

Wireless Clients get disconnected

daviwatk — Tue, 04 Sep 2012 19:38:12 GMT

Do you know if you are using Event Driven RRM? It's possible there is aggressive channel changes taking place on the 3502, where-by your client would be deauthenticated (then most likely roam to next best candidate/other AP you mentioned). Do you have any inteferers detected by the 3502i AP in question? MONITOR > CleanAir > 802.11a/n or 802.11b/g/n > Interference Devies and AirQuality Report. Is Event Driven RRM enabled? WIRELESS > 802.11b/g/n or 802.11a/n > DCA > "Event Driven RRM"

If this is on, I would suggest turning it off, unless you have a full CleanAir deployment. Whether you let CleanAir force an immediate channel change due to AirQuality (and only on the CleanAir capable AP will it change immediately, as the others will only change once an RRM/DCA interval is reached), or you suffer with interference, it could lead to a client disconnect. The client should be able to re-associate immediately upon channel change, but may just move over to the next heard AP (a ways away) as you described.

If the debug truly only shows the entries in the original post, it would be helpful to have a wireless sniff on the APs channel along with another debug (started before the client ever associates). Channel changes would be reported in the traplog of the WLC, so you can look at your traplog through the GUI or ">show traplog" on CLI and parse for channel changes.

Since 7.2 allows 2 clients to be debugged, you may enable debug client for AP and the Client, and then turn on RRM debug for DCA
>debug airewave-director channel

or for more extensive RRM info

>debug airewave-director all

I'm not sure how this will behave (ie, if it will only show RRM details for the AP specified in the 2nd debug client-- you would just have to try and see.)

You can also enable telnet/ssh to the AP and directly run (these "should" work)

#debug dot11 mgmt station

#debug dot11 mgmt msg

#debug dot11 mgmt state-machine

Wireless Clients get disconnected

guardian-de — Tue, 04 Sep 2012 19:46:26 GMT

thanks for hints - that's some work. I will start monday, out-of-office for 3 days.

Event Driven RRM is off - I know it. Clean Air is enabled. I will try to debug AP / Client in parallel and follow some steps you described, thanks so far to all. I get back to you next week.

Re: Wireless Clients get disconnected

aaroncoffman — Wed, 05 Sep 2012 01:21:35 GMT

You could try upgrading to 7.2.110. Why just last week Cisco TAC informed me "7.2.103 was plagued with bugs".

There's also the option of running the same software that was on the 4400's. In theory if you configure all settings the same as the 4400's and are running the same software the migration should be completely transparent.

From there you could upgrade to a stable 7.x.x...

Regards,

Aaron