Win10 clients can not connect/roam to 2802i-e but roams fine with 2702i-2 in the same area

hamid.nabil1 · ‎02-27-2019

Client can not connect to 2802 AP while roaming from 2702. I see the following msgs in AP logs. As soon as client is in 2702 radius then it connects again. Let me know if you need more info. Any help is appreciated.

Feb 26 12:26:46 kernel: [*02/26/2019 12:26:46.8048] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (72 64)
Feb 26 12:26:56 kernel: [*02/26/2019 12:26:56.7994] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (88 64)
Feb 26 12:27:06 kernel: [*02/26/2019 12:27:06.8232] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (104 64)
Feb 26 12:27:16 kernel: [*02/26/2019 12:27:16.8400] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 12:27:26 kernel: [*02/26/2019 12:27:26.8202] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 12:27:36 kernel: [*02/26/2019 12:27:36.8315] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 12:27:46 kernel: [*02/26/2019 12:27:46.4437] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 12:27:56 kernel: [*02/26/2019 12:27:56.4335] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 13:03:48 kernel: [*02/26/2019 13:03:48.1204] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (72 64)
Feb 26 13:03:58 kernel: [*02/26/2019 13:03:58.1152] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (88 64)
Feb 26 13:04:08 kernel: [*02/26/2019 13:04:08.0921] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (104 64)
Feb 26 13:04:18 kernel: [*02/26/2019 13:04:18.0919] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Feb 26 13:04:28 kernel: [*02/26/2019 13:04:28.0926] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (136 64)
Feb 26 13:04:38 kernel: [*02/26/2019 13:04:38.1088] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (136 64)
Feb 26 13:15:37 kernel: [*02/26/2019 13:15:37.8342] Sending GTK KEY message failed hostapd CISCO GTK_KEY bbc7xxxxxxxxxxxxxxx
Feb 26 14:17:04 kernel: [*02/26/2019 14:17:04.2767] Sending GTK KEY message failed hostapd CISCO GTK_KEY 3567cxxxxxxxxxxxxxx
Feb 26 15:18:55 kernel: [*02/26/2019 15:18:55.9041] Sending GTK KEY message failed hostapd CISCO GTK_KEY 16373xxxxxxxxxxxxxx
Feb 26 16:20:48 kernel: [*02/26/2019 16:20:48.3322] Sending GTK KEY message failed hostapd CISCO GTK_KEY 8bb13xxxxxxxxxxxxxx
Feb 26 17:21:54 kernel: [*02/26/2019 17:21:54.0340] Sending GTK KEY message failed hostapd CISCO GTK_KEY 12945xxxxxxxxxxxxxx
Feb 26 18:22:57 kernel: [*02/26/2019 18:22:57.2691] Sending GTK KEY message failed hostapd CISCO GTK_KEY 45d8bxxxxxxxxxxxxxx
Feb 26 19:24:34 kernel: [*02/26/2019 19:24:34.6204] Sending GTK KEY message failed hostapd CISCO GTK_KEY c3d22xxxxxxxxxxxxxx
Feb 26 20:26:10 kernel: [*02/26/2019 20:26:10.3756] Sending GTK KEY message failed hostapd CISCO GTK_KEY 8a5c2xxxxxxxxxxxxxx
Feb 26 21:27:15 kernel: [*02/26/2019 21:27:15.4937] Sending GTK KEY message failed hostapd CISCO GTK_KEY 1ee2dxxxxxxxxxxxxxx

patoberli · ‎02-28-2019

What software version is running on the WLC or on the AP? (show version)
Is this affecting only one client and working for others or are all clients affected? If it's just one client, update it's Wi-Fi adapter driver.

hamid.nabil1 · ‎03-04-2019

wlc is 8.5.140.0- it is the same for all clients regardless of NIC or driver version. Testet with different settings and hardware still no success. SSID is certificate based and is OK for other locations.

patoberli · ‎03-04-2019

Ok, software is good.
Can you run a debug client [macaddress] on the WLC while you roam or trying a fresh association on the 2802?
Please post the output here.

a.stephan · ‎04-16-2019

Same here, also when roaming from 2700 to 2800 or between 2800 and other 2800 APs.

Apr 8 02:51:04 kernel: [*04/08/2019 02:51:04.9748] Sending GTK KEY message failed hostapd CISCO GTK_KEY 196cde1e91032a67075864e405994801
Apr 8 03:51:37 kernel: [*04/08/2019 03:51:37.5556] Sending GTK KEY message failed hostapd CISCO GTK_KEY c7e47c69167a3cf689742c2278aa8760
Apr 8 04:51:51 kernel: [*04/08/2019 04:51:51.8938] Sending GTK KEY message failed hostapd CISCO GTK_KEY 10810cd1002040b890c7b1ffa2795da1
Apr 8 05:52:21 kernel: [*04/08/2019 05:52:21.8502] Sending GTK KEY message failed hostapd CISCO GTK_KEY 19b062196160ed824acdb7b649f425e7
Apr 8 06:53:10 kernel: [*04/08/2019 06:53:10.9942] Sending GTK KEY message failed hostapd CISCO GTK_KEY c9313a50ce658e91c24c55ed9f69760b
Apr 8 06:58:15 kernel: [*04/08/2019 06:58:15.6549] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (72 64)
Apr 8 06:58:25 kernel: [*04/08/2019 06:58:25.6584] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (88 64)
Apr 8 06:58:35 kernel: [*04/08/2019 06:58:35.6565] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (104 64)
Apr 8 06:58:45 kernel: [*04/08/2019 06:58:45.6576] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (120 64)
Apr 8 06:58:55 kernel: [*04/08/2019 06:58:55.6902] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (136 64)
Apr 8 06:59:05 kernel: [*04/08/2019 06:59:05.6918] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 06:59:15 kernel: [*04/08/2019 06:59:15.6860] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 06:59:25 kernel: [*04/08/2019 06:59:25.6874] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 06:59:35 kernel: [*04/08/2019 06:59:35.6921] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 06:59:45 kernel: [*04/08/2019 06:59:45.6894] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 06:59:55 kernel: [*04/08/2019 06:59:55.6955] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 07:00:05 kernel: [*04/08/2019 07:00:05.6938] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 07:00:15 kernel: [*04/08/2019 07:00:15.6961] macMgmtMlme_AssocReAssocReqHandler[line 2339] out of boundary (152 64)
Apr 8 07:53:32 kernel: [*04/08/2019 07:53:32.8974] Sending GTK KEY message failed hostapd CISCO GTK_KEY 9d4931a459b8cea032edf59c9ee85c5f
Apr 8 08:54:28 kernel: [*04/08/2019 08:54:28.4764] Sending GTK KEY message failed hostapd CISCO GTK_KEY f1e8eac8bf6e520d08b14c58fa0dc3f5
Apr 8 09:54:28 kernel: [*04/08/2019 09:54:28.2880] Sending GTK KEY message failed hostapd CISCO GTK_KEY 77587d91a3db93eb26ff961a9100b350
Apr 8 10:55:02 kernel: [*04/08/2019 10:55:02.9047] Sending GTK KEY message failed hostapd CISCO GTK_KEY f992ad8ec5bea6db80588ae0bdf17be4
Apr 8 11:55:04 kernel: [*04/08/2019 11:55:04.8318] Sending GTK KEY message failed hostapd CISCO GTK_KEY b24a69b8eddd4e162cc7a5d724c88c1f
Apr 8 12:55:08 kernel: [*04/08/2019 12:55:08.8659] Sending GTK KEY message failed hostapd CISCO GTK_KEY 5c17c1bfa4586a42a3a5573d2689048c
Apr 8 13:55:28 kernel: [*04/08/2019 13:55:28.5759] Sending GTK KEY message failed hostapd CISCO GTK_KEY 50ea5232017c24bd73041136a790fe32
Apr 8 14:55:34 kernel: [*04/08/2019 14:55:34.0246] Sending GTK KEY message failed hostapd CISCO GTK_KEY 2ad6580a1e2bcaaac172143fa5126fee
Apr 8 15:56:02 kernel: [*04/08/2019 15:56:02.1208] Sending GTK KEY message failed hostapd CISCO GTK_KEY ee7f21200d1a4971db6371c7334bfe71

patoberli · ‎04-16-2019

Which software version are you running?

a.stephan · ‎04-16-2019

8.3.143.0

patoberli · ‎04-16-2019

Do you have FT (802.11r) enabled? If yes, please disable and test again.

a.stephan · ‎04-16-2019

fast transition is not enabled on our WLC.

patoberli · ‎04-16-2019

Then I'm out of ideas (if it affects several clients) and I suggest you open a TAC.

a.stephan · ‎04-16-2019

ok, thank you though!

EDIT: Yes, affects all clients, no matter if Windows client or iPhone.

Scott Fella · ‎04-16-2019

Looks like you need to open a TAC case since you have done what we all would of:

Updated the driver
Disable 802.11kvr
You are on a good code

-Scott
*** Please rate helpful posts ***

a.stephan · ‎04-17-2019

Thanks!

BTW it happens only in Flexconnect mode. I was informed yesterday by our network support company that there is a known bug with 2800 series APs and Flexconnect setup, but no bug fix as of now. As we only have fielded less than 10 pieces of 2800 at our flexconnect sites, I will replace them with 1800 series and re-use the 2800 for our headquaters in local mode.

hamid.nabil1 · ‎04-23-2019

Do you have the bug#? (regarding 2800 and Flexconnect) I have some clients that isn't working as soon as I disable FT.

patoberli · ‎04-23-2019

What client is that? FT is a fairly new feature which isn't supported by many APs. Every client should work without FT enabled.