Replacing MS320 with MS350

Solved
Digitaltek
Conversationalist

Replacing MS320 with MS350

This is a live environment and I am looking for the best method of replacing the MS320 with a new MS350. I don't believe the MS350 will inherit the settings from the MS320. I have taken screenshots of the MS320 settings, do I have to manually input everything or what is the best practice?

 

The MS320 is still in place as I don't want the network to go down. 

 

Here is the current topology. 

Digitaltek_1-1731510567310.png

 

1 Accepted Solution
Mloraditch
A model citizen

Cloning requires the source and destination switches to be the same so you will need to load the new switch in your network and preprogram all the ports, etc., manually or via the API 

 

If the switch is performing any layer 3 functions you would move them from the routing and dhcp settings page after the new one is online.

 

Normally what I would do for something like this is:

1) Uplink the new switch to your existing network to a port providing DHCP (can be an isolated network), allow it come online do all  it's firmware updates, etc.
2) Program the switchports
3) If you use static management addresses, do not program this yet and leave it on DHCP (to avoid an ip conflict) OR if your management subnet does not provide DHCP, program a new address to use, you can change later if necessary
4) Physically swap the switches

5) Move any routing and dhcp and update the management address if necessary in your setup.


View solution in original post

2 Replies 2
Mloraditch
A model citizen

Cloning requires the source and destination switches to be the same so you will need to load the new switch in your network and preprogram all the ports, etc., manually or via the API 

 

If the switch is performing any layer 3 functions you would move them from the routing and dhcp settings page after the new one is online.

 

Normally what I would do for something like this is:

1) Uplink the new switch to your existing network to a port providing DHCP (can be an isolated network), allow it come online do all  it's firmware updates, etc.
2) Program the switchports
3) If you use static management addresses, do not program this yet and leave it on DHCP (to avoid an ip conflict) OR if your management subnet does not provide DHCP, program a new address to use, you can change later if necessary
4) Physically swap the switches

5) Move any routing and dhcp and update the management address if necessary in your setup.


DarrenOC
Kind of a big deal
Kind of a big deal

Agree with @Mloraditch ‘s method here. Bring the switch on line, pre-stage and then swap out.

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