This sounds similar to something we've seen on MR16s & MR18s. It has some correlation with channel changes. Take a look at the RF tab on the AP. You'll likely see a normal traffic pattern followed by an AutoRF/DFS channel change followed by a flatline during which no connections will be made. There's definitely some sort of problem handling channel changes gracefully.
... View more
We weren't given a bug number by support but they said it was a known issue. It extends a couple of revs back. Only on MR32s (150) out of our 750+ total.
... View more
We weren't given a number but were told that it's a known issue. The network is unusable when connected to an MR32. A continuous ping of the local gateway from a device associated to an affected AP shows a pattern of: no responses and high 20 second response times that get shorter and then stop. Rinse. Repeat.
... View more
Contrary to the reports of others: 26.6.1 still has an MR32 bug in it that prevents us from upgrading. It's completely unstable/unusable for us.
... View more
FWIW, I noted traffic shaping was broken in a similar way and support reported: "It's possible that we're encountering a known-issue involving client bandwidth limits not being enforced correctly when the client roams with 802.11r enabled on the SSID, this issue is resolved in MR 26.x"
... View more
@NolanHerring wrote: The only way I see this being fixed is if they actually do some deep-dive root cause analysis. I attempted to assist them with this and provided packet captures, and went out of my way to show them what the issue was (at the time it was basically the AP not sending any Association Response frames after receiving Association Requests, which was fixed by rebooting the AP or changing the radio channel to another one which effectively 'rebooted' the radio). Stupid bug tricks: Take a look at your pcaps and note the mismatches in the HT and DS Channels in beacons (from memory, could be wrong). Take a look at your local config page and you'll see the AP claiming to be on one channel and the dashboard reports another.
... View more
Definitely a firmware issue that I'm intimately familiar with. We saw it on 2.4 and 5. Scripted reboots alleviate some pain as a last resort. If you are able, use a static channel plan on 2.4 and 5 and avoid DFS channels. If you are able, try 26.6. The release notes include a fix that sounds suspiciously on target: Unexpected beacon behavior & instability following a channel change (802.11ax MRs) (Don't believe the ax-only business. I don't think that's true as other fixes are labeled that way when they seem to impact non-ax APs.) Fortunately, we were able to divest ourselves of our MR18 inventory.
... View more
Meraki Device Type identification is probably not accurate enough for your application. Depending on how critical it is for you keep devices off you may want to turn the tables and concentrate on only allowing known devices on the network via device registration or certificate-based 802.1x -- both would require heavy lifting. Depending on your client count you might want to use something low-tech like sorting Clients by First seen time to locate new devices and block undesired devices.
... View more
So it is the WPA2 preshared key that is wrong and not a splash password or something? Sorry to be so precise but it helps diagnose how far your packets are going. For grins, has the troubled AP changed channels recently?
... View more
However, on a single Access point, as we get within it's range, it says the password is incorrect for the guest network. Just to be clear, you are connecting to your guest network with some sort of authentication and your client (an iOS device, let's say) displays on its screen that the password is bad?
... View more
"unspecified reason" coupled with frequent associate/disassociate may be interference. Perhaps a helpful person has introduced a new device or turned on their phone hotspot. Check out that AP in RF Overview. Here's an example of a helpful person at my site. Super helpful, actually, stomping over a large swath of airspace with an 80MHz channel.
... View more
What is occurring at around 2:00 CDT? I was thrown off by the word "constant"...It looks like this only happens once a day at 02:00. What prompted you to look at this? I'm going to guess that this once-per-day disassociation is probably not the cause of the problem you're investigating. Just a rabbit trail...
... View more
