That's what I figured, just a sanity check. Thanks! ... View more

I want to take the credit but unfortunately I can't. Support alerted me to the bug. The frustrating part isn't that there's a bug in beta firmware. The aggravation comes from a bug that's known to support but not in the release notes, on top of the fact that this fw was a suggested alternative to fix a different bug. ... View more

Circling back for completeness sake. We were passing the group policy name from ISE to Meraki using the Airspace-ACL-Name radius attribute (and have been for years). This will make the connection fail and also reboot the ap every 10-ish minutes if the AP's on 29.2 Beta. If you use Filter-ID instead it lets you connect and the AP will not spontaneously reboot.    Afraid of what else 29.2 will reveal.  ... View more

I wish you the best of luck then. These were all 45's, ISE 3.0. ... View more

DO NOT TOUCH 29.2 with a 10 ft pole. Maybe 20ft. Make it 20km.   Tried it over the weekend. Was a disaster.... ap's were rebooting every 10-30 min. Apparently 29.2 has an issue with radius that does this. Reverted back to 28.6. Support's indicated this happens after approximately 2 months of uptime. We'll be on a 1 month reboot schedule..  ... View more

For all clients on the same ssid? Nah... this is unique to individual clients... other clients on same ap and same ssid work just peachy.   Had a second incident reported a couple days after the one mentioned above. This one was 0 response from it's svi but again other clients on same ap were fine. This client, roaming to a neighboring ap was ok, then back to the problem ap failed. After packet capturing... the arp request client makes to the svi never received a response. Packet capturing on the switchport the ap is connected to though shows the request AND response. It appears the AP never transmits the response back to the client. The was receiving other random broadcast/multicast traffic from the AP though so it doesn't seem to be an rf issue. The roam/dot1x/dhcp/etc worked fine..... ... View more

Got reports of this again today. Tech on site was able to replicate.  Got meraki on the line and went at it for a long while. Our entire Meraki infrastructure is all L2. SVI's, routing, etc happens on an upstream device.   The client had heavy packet loss to it's svi, and on packets that did get a response time was through the roof, 500+ms to 4 digit range. Capturing on ap's wifi interface didn't show anything out of ordinary, infact it showed all normal times and no drops. Capturing on wired port and suddenly things started working normally again.   Makes me think either packet didn't make it to AP, or AP dropped it without notice.    Coincidentally - the ap client was connected to was on opposite side of building, down a floor. Auto power has it so high though that the client hears it louder then the units much closer (and on the same floor!). I don't believe this has to do with the issue at hand though because client can pass traffic through the further ap just fine when not in this failure mode.  ... View more

Unfortunately no, not completely. Maybe made it less often. Haven't heard anything since the upgrade in March. Then in the last week or two I got another report. This time we haven't been able to replicate to allow for troubleshooting. The users tend to report the issue, then move/roam, powercycle, etc until it starts working, leaving us stranded on the troubleshooting front.   I'll take every few months vs every few weeks though. ... View more

While that's a possibility that's not what was happening here. My two test clients were on the same ap, with no other clients on it, on 5ghz.   After fighting the automatic firmware update scheduler all ap's at the site are on 28.6 now. Time will tell. ... View more

Running into something similar. Clients on the ap can associate and authenticate just fine but user traffic has such high latency its essentially unusable. If your only seeing 100ms your lucky... ours reaches 4 digits. Reboot and it's peachy until the next ap over, or the one on other side of building, does the same thing. Reboot, rinse, repeat.   Seems to have started a few months back and progressively getting worse. Happens across multiple platforms. Worked with support earlier after getting another example we could replicate. Captures indicated simple pings weren't making it to wired side of AP. Same client can roam to another ap and work just fine with no other changes other then walking away from the culprit AP.   Auto upgrade to 28.6 (from 28.5) was set to happen in a week. Forced it for overnight. Time will tell. ... View more