802.11 disassociation, client association expired

NOS48
Conversationalist

802.11 disassociation, client association expired

Hi,

 

We are seeing a lot of [Event Type]-802.11 disassociation, [Details]-client association expired on our wireless network but there doesn't seem to be an obvious reason.  It would initially suggest the client has stopped talking to the AP but in most cases that would not be correct.  I have several examples, whereby, the client was streaming video, or on a video call or just generally surfing the internet and their wireless connection dropped.

 

Does anyone know if this is a known Meraki issue?  We see it across multiple users and often users see it at the same time (when they are connected to the same AP)...it happens across all our 95 APs.  We're running an older version of firmware (25.13) but plan to move to 27.6 very soon.

 

Any ideas would be great...I did wonder if there's something we can adjust on the Wireless NICs.

 

Cheers

Neil

 

 

2 REPLIES 2
cmr
Kind of a big deal
Kind of a big deal

@NOS48 We don't see this issue across our 120+ APs but we are running 28.2 and 28.3 everywhere. 

 

If you are upgrading and don't want to or cannot go to a beta firmware then I'd strongly recommend 27.7.1 as it includes a raft of security fixes.  One point to note is that if you have MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 access points they will run MR 26.8.2 which also includes the security fixes. 

PhilipDAth
Kind of a big deal
Kind of a big deal

First, check that the affected machines are using the latest WiFi drivers.  You may have to go to the WiFi chipset manufacturer to get these, as the OEM may not have made them available.

 

On Windows 10 computers you commonly get problems when the machines are on battery power and power-saving powers down the WiFi NIC briefly.  Try disabling power saving on the WiFi NIC on a test machine and see if that solves it.  This also resolves a lot of Windows 10 WiFi performance issues.

powercfg /SETDCVALUEINDEX SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0
powercfg /SETACVALUEINDEX SCHEME_CURRENT 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0

 

Next, what does Wireless Health say?

 

You might be getting "association expired" expired because the client has roamed to a different AP.  This may not be an actual problem.

 

 

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