Wireless Access

Hi

 

, I have a deployment at client site – the client keeps complain about disconnecting and connecting every few sec (even when not moving) while using Androids/ipads/iphones. I checked the issue with the client itself. And it's keep happening – no matter what I'm doing. Keep getting this Death …. stm Deauth from sta: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f Reason STA has left and is deauthenticated

 

 

 

Controller:3400

AP units: AP-105

AOS tested: 6.1.3.6 + 6.2.1.2

DEVICES: iPHONE5|iPAD3|SamsungGalaxySIII + other android devices.

PC & LAPTOPS seems to keep connectivity without any issue. 

SECUTIRY: WPA-2-PERSONAL-AES

Radio: 802.11N 2.4Ghz only.

 

 

FULL LOG OF An IPAD a room near the AP unit - using TUNEIN and browing the internenet all time,and all the time keeps connecting & disconnecting:

---------------------------------------------------------------

Jun 17 10:37:52  stm Deauth from sta: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f Reason STA has left and is deauthenticated
Jun 17 10:37:53  stm Auth request: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f auth_alg 0
Jun 17 10:37:53  stm Auth success: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  stm Assoc request @ 10:37:53.092478: b0:65:bd:39:e8:e0 (SN 3): AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  stm Assoc request @ 10:37:51.465445: b0:65:bd:39:e8:e0 (SN 3): AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  stm Assoc success @ 10:37:51.466611: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  stm Assoc success @ 10:37:53.095434: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  authmgr MAC=b0:65:bd:39:e8:e0 Station UP: BSSID=24:de:c6:c0:d9:f1 ESSID=Tama-Guest VLAN=859 AP-name=TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  authmgr MAC=b0:65:bd:39:e8:e0 ingress 0x0x10133 (tunnel 307), u_encr 32, m_encr 32, slotport 0x0x2000 , type: local, FW mode: 0, AP IP: 0.0.0.0 mdie 0 ft_complete 0
Jun 17 10:37:53  authmgr MAC=b0:65:bd:39:e8:e0, wired: 0, vlan:859 ingress:0x0x10133 (tunnel 307), ingress:0x0x10133 new_aaa_prof: Tama_guest, stored profile: Tama_guest stored wired: 0 stored essid: Tama-Guest, stored-ingress: 0x0x10133
Jun 17 10:37:53  authmgr Idle timeout should be driven by STM for MAC b0:65:bd:39:e8:e0.
Jun 17 10:37:53  authmgr dot1x_supplicant_up(): MAC:b0:65:bd:39:e8:e0, pmkid_present:False, pmkid:N/A
Jun 17 10:37:53  authmgr MAC=b0:65:bd:39:e8:e0 Station Updated Update MMS: BSSID=24:de:c6:c0:d9:f1 ESSID=Tama-Guest VLAN=859 AP-name=TAMA_SYSTEM_0d:9f
Jun 17 10:37:53  authmgr MAC=b0:65:bd:39:e8:e0 IP=0.0.0.0 User miss: ingress=0x10133, VLAN=859 flags=0x48
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 55, signature 370103060F77FC.
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 57, signature 3905DC.
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 61, signature 3D01B065BD39E8E0.
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 50, signature 32AC100083.
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 51, signature 330076A700.
Jun 17 10:37:53  authmgr MAC b0:65:bd:39:e8:e0, dhcp option 12, signature 0C49746179732D69506164.
Jun 17 10:38:07  stm Deauth from sta: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f Reason STA has left and is deauthenticated
Jun 17 10:43:26  stm Auth request: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f auth_alg 0
Jun 17 10:43:26  stm Auth success: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:43:26  stm Assoc request @ 10:43:26.897687: b0:65:bd:39:e8:e0 (SN 3): AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:43:26  stm Assoc request @ 10:43:26.895482: b0:65:bd:39:e8:e0 (SN 3): AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f
Jun 17 10:43:26  stm Assoc success @ 10:43:26.899547: b0:65:bd:39:e8:e0: AP 1.0.2.193-24:de:c6:c0:d9:f1-TAMA_SYSTEM_0d:9f

.................

 

 

this death happning in iphones and also in SG3+and other android devices also.

#3400

A deauth from a station is typical when they roam to another access point.  What is your coverage in that area?

• I know&aware to that.
• But there is a good coverage there between good=-59 to worst=-65 -67 , and this client isnt moving at all.
• The iPAD is on table in a room nearby the ap unit itself.
• You can see this client connecting and after a few sec disconnecting and so on....forever....and he isnt moving at all.

How many access points can you see in that area that are stronger than -67?  There might be too much coverage.

 

Can you run the show  ap association client-mac <client mac> a couple of times to see if the device keeps hoping to different APs over and over .

 

And also do a show  ap  remote debug mgmt-frames ap-name <ap name>

 

This usually is only needed for Apple devices but have you considered enabling to validate PMKID under the 802.1x profile or disabling OKC?

Can you run the show ap association client-mac <client mac> a couple of times to see if the device keeps hoping to different APs over and over

* i checked it via device trail... (GUI) and no ..it's staying and trying to connect to the same ap unit over and over.... agian the client isnt moving at all (u can also notice it in the logs i posted)

*i tried with vaildate PMKID and without validte PMKID - same issue.

*OKC? please explain - how does this effect ?

 

Actually OKC it won't apply in this scenario since its only used at the initial communication attempt the device makes to the AP and your devices are already connected the issue occurs after the device is associated.

 

What type of authentication are you using ?

it's hapenning even with open-system....

kdisc98,

 

Do you have anything like 802.11k, local-probe-response-threshold, or handoff assist enabled?

 

i passed every settings in AAA.8021.x/ 802.11k/ ARM / VAP / SSID /RF - checked that every "v" is where is supposed to be.

And then i found - by your advise - the misconfiguration: ( I hope so)

 

Hand-off assist was marked ON with 1 value.

 

I disable it (Like the default configuration need to be) for the meantime - it's seems very steady (iPhone5). And it's even make sense - that's why it's happen even in open-system.:smileyhappy:

 

 Thanks.

 Me

---

@kdisc98 wrote:

i passed every settings in AAA.8021.x/ 802.11k/ ARM / VAP / SSID /RF - checked that every "v" is where is supposed to be.

And then i found - by your advise - the misconfiguration: ( I hope so)

 

Hand-off assist was marked ON with 1 value.

 

I disable it (Like the default configuration need to be) for the meantime - it's seems very steady (iPhone5). And it's even make sense - that's why it's happen even in open-system.:smileyhappy:

 

 Thanks.

 Me

---

I don't expect that particular value to cause your issue, but if it holds, please let us know..  Please look at anything that is not the defaults as a starting point.

 

I will know better tommorw.

(it's night time here :) )

 

but it's seems like after i deleted the "v" from hand-off assisit - the diassoaction stopped.

 

I will keep u guys updated.

Just 2 AP units | can seen in this room.