Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switches

Iansays1
Here to help

Replacing MX 100 + Stacked Switches with MX 105 + 3 NEW stacked switches

I'm able to clone the MX100 and prep the MX105 with all the config, firewall rules, etc..

 

Not sure of the approach to take with the 3 new MS350s (old are also MS350). And/or how to integrate the newly stacked switch into the new combined network the cloned 105 is currently the only member of.

 

 

And while I'm asking, I have 3 APs (MR33) that were (incorrectly, I think) added as a seperate 'wireless' network in the same physical location as the old MX100 network, and ideally, I'd like to migrate them into the combined new network.

 

We are moving offices and the replaced equipment (MX100 and 3 stacked MS350s) is going to be delicensed and mothballed for disaster recovery options. And I'm trying to stage as much of the new equipment as I can, running in parallel, aside from the MR33s.

 

Thank for any thoughts, advice, well wishes.

 

Ian

7 Replies 7
DarrenOC
Kind of a big deal
Kind of a big deal

Why can’t you leave the existing MS350 switches in situ and just replace the MX100?  Seems a wasted effort to replace a switch for the same model.  What do you gain?

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

Ah…skimmed over the last paragraph…office move.

 


Presume all eqpt claimed into the same Org and you’ve configured a new Network for the new site?  In all honesty it isn’t going to take much effort to configure the 3 new switches in the new office. Plus, your new offices aren’t going to be an exact mirror of your current office environment as not everything is going to be patched in the same!

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.
Iansays1
Here to help

>as not everything is going to be patched in the same!

 

You are exactly correct. I had visions in my head about preserving some of the port specific settings we've made over the last several years (ports that started dying and had to be set to 100 non-duplex, for example), but all my new ports should work properly without any of that. Thanks for reminding me of that!

DarrenOC
Kind of a big deal
Kind of a big deal

Enjoy the freedom of a new greenfield site.  Start afresh 😁

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.
RWelch
A model citizen

Moving Devices between Networks should help you move the APs from old to new network.

Iansays1
Here to help

Thank you. Will review that today.

Iansays1
Here to help

Still struggling with this. Cloning the existing network seems to work ok, but after adding the new MX105 & 3 unconfigured switches to the new, cloned, network, the 3 new switches go dormant or offline. I'm assuming this happens because the config on the MX105 has changed and the IPs it was assigning the switches are no longer in the right DHCP scope the MX105 inherited from the clone. The newly cloned MX105 also won't give out IPs in the cloned scope to the switches or even a laptop plugged directly into a LAN port on the MX105. Not sure what's going on here.

 

Also weird: removing the MX105 from a network and trying to do a factory reset doesn't work. It retains the static IPs one would assign in the local config page. And I can only get to the local config page by hard coding my laptop NIC to 192.168.0.x

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