Split MS/CS firmware display anomaly

cmr
Kind of a big deal
Kind of a big deal

Split MS/CS firmware display anomaly

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... 🤔

 

Screenshot_20230817_092433_Chrome.jpg

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

Screenshot_20230817_092935_Chrome.jpg

4 Replies 4
DarrenOC
Kind of a big deal
Kind of a big deal

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
Kind of a big deal
Kind of a big deal

😬

DarrenOC
Kind of a big deal
Kind of a big deal

🫣

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
Kind of a big deal
Kind of a big deal

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 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels