@Adam_F wrote: It would also be nice if we can disable auto-firmware-updates on critical infrastructure Technically you can get Meraki to disable it. Its extremely difficult and requires a very high level of approval by your Meraki SE and you better have a rock solid case as to why you need this disabled at an Org level. In our case, we have scheduled quarterly downtime to upgrade MS, MR, Etc. Given that we are a manufacturing company, and our sheer size, having to manage multiple models, hundreds of devices, at hundreds of sites. The cadence of Meraki's software releases, end of support, etc is what sealed the deal for us. For multiple years we ended up having to do upgrades outside of our quarterlies, which requires manufacturing downtime (millions of $ worth of production time); and our team was having to push work to handle upgrades, they disabled it for us Org wide. So now we run X firmware until our maintenance windows, upgrade MS one window, MR's the next, etc. If you really want to yell at Meraki, go read the firmware upgrade process on MS series. Its an incredibly stupid design, where things aren't really verified before a stack begins rebooting, with basically only a timer being using to 'be sure' that downstream devices have 'had a chance'. Without using staged upgrades, its very easy for a complex or large Meraki MS network to have upstream devices reboot well before or during a MS downloading or loading its firmware. While for years we had near zero problems with firmware, the last few years have been lack luster.
... View more