Meraki

cmr · ‎Aug 17 2023

I discovered today that if you upgrade a network containing a single MS220-8p that was on MS 15.21.1, that then became MS 15.21.1/CS 15.21.1 with the firmware split, the ghost CS entry gets left at 15.21.1 with no way to upgrade or remove it... 🤔

As you would expect the only options for the network upgrades are the MS tree.

If my answer solves your problem please click Accept as Solution so others can benefit from it.

DarrenOC · ‎Aug 17 2023

So for anyone with OCD that’s really going to play havoc….

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.

cmr · ‎Aug 17 2023

😬

If my answer solves your problem please click Accept as Solution so others can benefit from it.

DarrenOC · ‎Aug 17 2023

🫣

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.

cmr · ‎Aug 17 2023

It even breaks a network that was on MS 15.20. I upgraded it to MS 16.2.2 and you get MS 16.2.2 / CS 15.21.1

If my answer solves your problem please click Accept as Solution so others can benefit from it.

Meraki

Community

Split MS/CS firmware display anomaly

Split MS/CS firmware display anomaly