topic Re: Clients disassociated simultanously in Wireless

Clients disassociated simultanously

tsgruu2000 — Mon, 05 Jul 2021 14:36:30 GMT

Hi all,

We have seen lots of disassociations with Reason:Unspecified ReasonCode:1 in a Customers WLC. It seems that several clients on the same Access Point are disassociated in the same millisecond. This happens on several Access Points.

Most clients do not care about this but there are Spectralink Phones which have to associate to another Access Point in this case. I wonder what causes these disassociations. RRM is disabled.

Could Rogue Detection cause such disassociations? I have no idea...

Aug 30 16:02:04.675: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:28:6a:ba:a0:7a:61 Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.3.130.146 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.675: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:60:f1:89:72:8d:ec Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.33.142.205 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.675: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:40:b8:37:b0:0b:00 Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.33.137.210 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.676: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:6c:19:c0:b5:54:3e Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.33.139.226 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.676: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:d0:87:e2:42:f9:8e Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.33.137.86 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.676: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:e8:50:8b:b4:83:56 Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:228014421069891@scm-eapsim.ch Ip Address:10.33.128.218 Reason:Unspecified ReasonCode:1
Aug 30 16:02:04.676: %APF-3-DISASSOC_TRAP: apf_80211.c:15616 Client Disassociated: MACAddress:00:61:71:6e:90:8c Base Radio MAC:cc:d5:39:e3:fe:00 Slot:0 User Name:unknown Ip Address:10.33.140.25 Reason:Unspecified ReasonCode:1

Many Thanks!

Best Regards,
Urs

Re: Clients disassociated simultanously

Rasika Nayanajith — Mon, 04 Sep 2017 10:15:50 GMT

Is it possible to take a wireless packet capture on a channel that AP operate while this is happening ? That will tell us what's going on.

Do you have any spectrum analyzer to see how is RF looks like in this environment ?

HTH

Rasika

Re: Clients disassociated simultanously

tsgruu2000 — Mon, 04 Sep 2017 12:19:56 GMT

Hi Rasika,

I am going to ask the Customer to do a capture using Netmon. Unfortunately these issues are not predictable. They occur on different Access Points from time to time.

Is there something other than RRM that could cause an Access Point to disassociate its clients?
RRM is disabled.

Many Thanks for your advice!

Regards,

Urs

Re: Clients disassociated simultanously

Scott Fella — Mon, 04 Sep 2017 13:55:41 GMT

Can you tell us more about your setup? I'm assuming it's a hospital since you are using Spectralink phones? What controller model, code and AP's? You have other sites that have this issue also running the same equipment and code? I'm just curious as to why there was a decision to disable RRM? I have setup a bunch of hospitals and never disabled RRM.

-Scott

*** Please rate helpful posts ***

Re: Clients disassociated simultanously

tsgruu2000 — Tue, 05 Sep 2017 11:54:03 GMT

Yes, it is a hospital. The Controllers are WISM2 with OS 8.0.132.
We've only found clients on APs 3502 with this issue. Probably there are others as well but as
the majority of APs is of type 3502 it is hard to say.

I knew someone would ask about RRM. We decided to disable RRM in some areas.
To be honest, areas without RRM work much better with spectralink phones.
About a year ago we set up the WLC regarding Spectralinks Guide for Cisco WLAN.
This setup was unusable. Phones did not roam smoothly, we had one-way audio, Phones were frozen and had to be rebooted ... After several Software Updates on Phones and disabling RRM in some areas
we could eliminate nearly all issues.

Just to clarify: RRM is not disabled. Only Channels and Power levels have been fixed in some areas. A site survey showed, that power levels with RRM were rather low in some areas.