Switching from MS220-48FP to MS120-48FP

Riser
Getting noticed

Switching from MS220-48FP to MS120-48FP

We are looking at switching from MS220-48FP to MS120-48FP. Currently, we have 8 MS220-48FP on our network. Is there an easy way to effect this change and move all the settings at once from the existing 8 MS220-48FP to the new 8 MS120-48FP?

Of course, it will take time to configure all the port settings individually. Any suggestions will be appreciated.

11 Replies 11
alemabrahao
Kind of a big deal
Kind of a big deal

Clone the actual network and add the new switch in the new network cloned.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

The reason why I didn't want to move with the option is that the same network has 3 MS225, which we will be retaining. Cloning the entire network will mean cloning the same settings for the 3 switches, which will still be retained, right?

alemabrahao
Kind of a big deal
Kind of a big deal

You can configure via the API as mentioned, but I find it so easy to configure via the dashboard that working on a script to configure via the API is an unnecessary waste of time.

 

Just configure from scratch and that's it. Meraki is too easy.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

Cloning a switch network won't bring over any port configs so this isn't an option

ww
Kind of a big deal
Kind of a big deal

For switch ports i would use the api to get the ports configs. Then put the to the new switches

https://developer.cisco.com/meraki/api-latest/get-device-switch-ports/ 

BlakeRichardson
Kind of a big deal
Kind of a big deal

Depending how populated the switches are just do it by hand. You could export your existing port config as a CSV and just work through it that way plugged each thing into it's own spot. 

 

The beauty of Meraki is if you muck a switch port up it's usually very easy to identify whats connected it it via the client info either on the switch port itself or network wide page.

Agree with @BlakeRichardson , by the time you’ve written the API you could have installed and configured the replacement switches 

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

I don't think it will allow it - but try the switch cloning tool.
https://documentation.meraki.com/MS/Other_Topics/Switch_Cloning 

Switch cloning requires source & destination switches to be the same model https://documentation.meraki.com/MS/Other_Topics/Switch_Cloning

PhilipDAth
Kind of a big deal
Kind of a big deal

I have found Google Bard quite good at writing scripts to do Meraki changes.  Perhaps give it a try.

https://bard.google.com/ 

KarstenI
Kind of a big deal
Kind of a big deal

How many *different* port configs do you have? With virtual stacking, you can configure hundreds of ports simultaneously, and the new Port-Profiles (still beta) would make It even easier.

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