WPA-2 Enterprise deauthentication/disassociation problem MR42

Murat
Just browsing

WPA-2 Enterprise deauthentication/disassociation problem MR42

Hi all

 

we are using MR42 AP which is version 27.4  and used WPA-2 Enterprise 802.1x auth with ISE. 

 

recently, all user having deauthentication and disassociation problem every time

 

we tought this problem might be caused by session-timeout and We sent the session-timeout  attribute via ISE to MR but not resolved . 

 

for some users meraki event type and log details below 

 

meraki_error.jpg

 

 

do you have any suggestion related this issue?

Thanks 

 

 

2 Replies 2
DarrenOC
Kind of a big deal
Kind of a big deal

Hi @Murat , the unknown reason indicates that this hasn’t been triggered by the AP and there are therefore other elements interfering with the re-association.

 

Have you gathered any packet captures?

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
PhilipDAth
Kind of a big deal
Kind of a big deal

Is their another brand of WiFi kit also in the environment using the same ssid.  It may be sending de-auth packets.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels