Moving MX network to another site as a Vlan

[BMoody]

Hello, 

I have multiple buildings with Meraki MX devices participating in the site to site vpn in hub(mesh) configuration. None of the MX devices have multiple vlans enabled yet. One site (MX105) is closing down but we need to maintain the subnet that is in use there and have it still be available to the rest of the auto VPN participants, just from another building.  Namely, database servers. They must retain their current static ip configurations.  

Current plan:

• remove the MX105 and its network from the dashboard completely.
•  Move the servers to the new site (MX68)
• Change the MX68 to multiple vlan mode.
• create a sql vlan with the required subnet information that matches the relocated servers. Advertise to auto VPN participants
• Trunk from MX68 lan port to a switch configured with same sql vlan.
• Place servers on ports configured for sql vlan.
• sql vlan can now be reached from auto vpn participants and locally on the MX68 along side the native vlan.

Does this sound like it would work?  Should we first upgrade the MX68 to the MX105?  After? Seems silly not to. 

Thanks!

BM

[IvanJukic · Accepted solution]

Hi BMoody,

That sounds like a fine plan to me. To mke things easier for you. You can clone the MX105 nextwork, and add the MX68 to the Clone and enable the VLAN for VPN. See below guide for details.

https://documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Differ...

Cheers,
Ivan Jukić

[PhilipDAth]

>Trunk from MX68 lan port to a 

If there aren't too many devices you can put some of the MX68 LAN ports directly into that VLAN and plug the servers directly into the MX68.

[BMoody]

Sorry for the delayed response. Thank you guys for your input!.