I am also seeing something similar after upgrading to 29.4.1. Anyone know if an upgrade to 29.5 is worth a shot? ... View more

"And later this year you’ll be able to manage and configure your Catalyst 9300 switches in the Meraki dashboard."   So will this be "a la MS390" where the ability to access IOS disappears and configuration is only possible via Meraki dashboard?   Or will be Catalyst 9300 management via Merkai in effect modify the IOS config with SSH into IOS remaining available (e.g. for debugging and "advanced config" not available via Meraki dashboard?)   Richard ... View more

I am an IT Director at a school which has been Cisco for many years. Two years ago, we decided to replace aging Cisco switches and WiFi with Meraki equivalents. We trialed MS390, but at the time it was missing functionality we needed, so we deployed MS250/350. We needed to keep traditional Cisco switches at the core, to give flexibility around IPv6, complex ACLs, etc, so opted to migrate these to Cisco 9500 in our roadmap (as there are not Meraki equivalents).   We really like Cisco's current direction of the travel, as we will now be able to integrate our Cisco 9500 core switches into the Meraki console for single-pane-of-glass network visibility / monitoring. Converged Cisco hardware, able to run IOS or Meraki, really makes sense at lots of levels. It gives customers choice and flexibility and simplifies supply chains, hopefully lowering costs.   However, the bottom line here is that things will need to work far better than what has happened with MS390 which has been a "pilot" for converged Cisco/Meraki hardware. From what I can ascertain, MS390 is a rebadged 9300 running a Meraki management layer, and from discussion above doesn't seem like it has ever been properly stable.... I don't know what the problem is/was. Maybe the Meraki layer was simply "retrofitted" - so perhaps designing "ground up" in future with both usage cases in mind can yield better results. I want this to work, and certainly hope it will! ... View more