Yes, this is an annoying bug of some sort. Each evening between 6-7 EDT we get a list of anywhere from a few to a few dozen. Being going on for months.   My AP pages are almost universally littered with the pink box "The Cisco Meraki Cloud is having difficulty communicating with this device." ...and I can talk to and manipulate them just fine. ... View more

OH! I wish I was at the office right now! ... View more

I'm sure everyone shares  your frustration. WE know that it's probably not a wireless problem but the user generally doesn't understand everything else that goes on.   My two standard diagnostic questions in cases like this are:   How did you come to that conclusion? (Give them the benefit of the doubt that they've actually taken some evidence, processed it, and made a conclusion. It's a more graceful way to say, "Um, some details would be nice.")   What do you mean by <word or phrase used by client>? (Again, eliciting more details and clearing up differences in vocabulary..."I speak boy. You speak girl.:) ... View more

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

@cmr wrote:   Is there a reason you want the devices to use an AP on their floor, device count etc.? This is probably a carryover from experience with other wireless vendors. In my testing I've seen some vendors want to create small management domains like this...but I'm sure they (somehow) must have policy that efficiently glues those domains together for roaming and other things.   I would suggest using Tags to facilitate managing smaller groupings. ... View more

@Uberseehandel wrote:   unless devices are mobile, wire them Sooooooooooooooooo underrated!!!!       ... 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

While it may be a bug, we leverage it to investigate coverage holes. Our environment is fairly isolated. If someone's been on our network before and then fires up a hotspot it is most likely because we're providing poor coverage. We send the user an email and ask if they were encountering a problem with our network. We also suggest that their use of a hotspot often serves to make any problem worse. (Makes us real popular 🙂   ... 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

Dumb question: are the parenthetical model numbers exhaustive? It looks more generic than in prior versions.   We've got very similar problems on APs models not listed. Most specifically this Known Issue that I'm guessing we initially reported:   EAPOL Key 3 is not sent from AP to 802.11b/g clients on PSK SSIDs (802.11ax MRs) ... View more

This happens to me on random APs on occasion. Firewall's just fine...just a report of 1 AP of (700+) having trouble. I've considered it spurious. ... View more

Pcap analysis:   I see that the EAPOL handshake is failing after the second message meaning the AP is not responding back. The device keeps trying and at one point the AP simply starts deauthenticating.   Seems like an AP problem. ... View more

Yes. We opened a case two days ago with the same symptoms. I encourage you to open one as well. We free to reference our case: 04178048 ... View more

Definitely not my strong suit and I'm not sure I'm following you, but...   Check the applicability of the Local Identification and/or Peer Identification fields in the General tab of your IKE Gateway config.  ... View more

I'd ask for the case to be escalated. I'm pretty sure they can roll back. It's a pain in the neck for them which is probably why you're getting push back.   If you keep getting the runaround have your legal department send Cisco a demand letter. You are entitled to a working AP. They can either rollback, patch (now), or provide you a working model. ... View more

We encountered the MR32 DHCP issue that's known in 26.2 when we tried it last week. It was very debilitating. Given the number of MR32s in the field I might expect it to never make it to RC. ... 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

FWIW, I see this for one or two random APs occasionally. Firewall rules are in good shape. I consider them false positives. If there was a firewall problem many more APs would be impacted. ... View more

I have tons mounted vertically. No problem at all. ... 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