- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New Network and layer 3
Currently I have an MX, 2 MS switches and 2 Meraki APs with 5 VLANs. All layers 3 and DHCP is all done on MX if I want to configure all layer 3 routing from one of the MX switch and make MX as just FW, can I just clone my current network and change all the configs I wanted there on the new network and move the devices when I'm ready? . This way I wont get stuck and also have a fallback.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is not possible. While you can stage most MX config in a blank network, you can't stage most switching config.
In theory if you have good grasp of the APIs you could probably script most of the work, but the juice may not be worth the squeeze if it's something new to you.
The way I would do this is make notes about all of your relevant existing config, set up your new transit network and activate layer 3 (this can all be done ahead of time) and move perhaps your least important vlan to test (remove from MX, add static route, rebuild any related mx config, add to L3 Switch)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Moving Devices between Networks will give you more insight on moving devices between networks.
For example: Removing an MX from its former network and moving it to a new network will wipe out the existing configuration on the MX, that it had from its old network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cloning Networks and Organizations in Dashboard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is not possible. While you can stage most MX config in a blank network, you can't stage most switching config.
In theory if you have good grasp of the APIs you could probably script most of the work, but the juice may not be worth the squeeze if it's something new to you.
The way I would do this is make notes about all of your relevant existing config, set up your new transit network and activate layer 3 (this can all be done ahead of time) and move perhaps your least important vlan to test (remove from MX, add static route, rebuild any related mx config, add to L3 Switch)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you both for your quick response. Didn't realize I can't do switch config's on the cloned network. I'm not good on API/scripting. I will do one VLAN to begin with to test, when I do that even though I don't have all the VLAN/subnets moved, during testing only test VLAN will work all other won't work as I would have cut the layer 3 routing already on MX for those correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The subnet and VLAN on the MX will need to be removed PRIOR to re-locating that same subnet and VLAN on the L3 switch (yes).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Layer 3 Switch Example if you want to review prior to configuration changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick response again. I also found this URL explained even better https://documentation.meraki.com/Architectures_and_Best_Practices/Recommended_Topologies/MX_and_MS_B...
Thanks again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes - a better document for your consideration indeed!
