Association errors

[Alex1231]

Hi all,

I'm having some issues with client association errors on our dash for our new network:

auth_mode='wpa3-psk' 11k='1' 11v='1' reason='reserved' radio='2' vap='4' channel='85' rssi='46'

Seems to occur on an initial connection and sometimes when roaming. The issue only occurs on 6 Ghz - If we disable 6 Ghz on the client and fall back to 5 Ghz, there is no error. Disconnecting/reconnecting to the network triggers the error.

Looking at wireshark, there doesn't appear to be anything out of the norm (4 Packets Authentication, 2 Packets association, then 4 packets for handshake):

Authentication, SN=356, FN=0, Flags =.
Authentication, SN=396, FN=0, Flags=
Authentication, SN=357, FN=0, Flags=
Authentication, SN=397, FN=0, Flags =.
Association Request, SN=358, FN=0, Flags=
Association Response, SN=0, FN=0, Flags=
Key (Message 1 of 4)
Key (Message 2 of 4)
Key (Message 3 of 4)
Key (Message 4 of 4)

<DHCP stuff>

From a performance perspective, the error isn't noticeable on the client. There is also nothing of note in the WLAN report.

We're running MR 30.7.1 / CW9166I APs / WPA3-SAE / Intel AX211 (also had same issue on Netgear A8000)

Any ideas?

[b-ganesan-srvcprvdr]

Not Yet. We're still working with TAC. Almost did everything possible at the AP and Network driver ends. nothing helped out.

[macnerd1]

We are the same, also in contact with TAC. Previously we tested, iPhone and Android, same issue, we think it’s may not be related to Windows OS drivers

[b-ganesan-srvcprvdr]

Here we have Intel AX211 6E 23.120.0.3, the majority of users are causing issues

[macnerd1]

@b-ganesan-srvcprvdr

on the 15th last month, mr31.1.7 was released as release candidate. in the changed log, there is a mention of <code 0 : reserved> being fixed. we upgraded but we are still having the same behaviour.

drivers version that we have tested :

these are the drivers that we tested until we found that Apple iOS is exhibiting the same behaviour previously.

22.120 : totally unable to detect 6GHz band
22.130 : totally unable to detect 6GHz band
22.140 : totally unable to detect 6GHz band
22.150 : totally unable to detect 6GHz band
22.160 : totally unable to detect 6GHz band
22.170 : able to detect 6GHz band but exhibit the same behaviour
22.180 : able to detect 6GHz band but exhibit the same behaviour
22.190 : able to detect 6GHz band but exhibit the same behaviour
22.240 : able to detect 6GHz band but exhibit the same behaviour
23.50 : able to detect 6GHz band but exhibit the same behaviour

after we upgraded to mr31.1.7, we tested the 23.130.1, Intel latest. same behaviour

[badreddine]

Hello community,

Is this an ongoing issue that hasn’t been resolved in any firmware version yet?

Thank you !

[Alex1231]

Still ongoing. I haven't had an update from cisco since May.

[Alex1231]

Issue is resolved for me with MR 31.1.8