Hi there,
Solved! Go to solution.
Yes, you can certainly set up your Cisco Meraki MX75, MS210, and APs at home and then move them to another location. This is one of the benefits of Meraki's cloud-managed nature - devices can be configured remotely before they're physically deployed.
Regarding the public IP address change, it won't be a problem. The Meraki devices are designed to automatically check in with the Meraki Cloud Controller, no matter what their public IP address is. When you move the devices to a new location, they will simply use the new public IP address assigned by the ISP at the new location to connect to the Meraki Cloud Controller.
Here are the steps you would typically follow:
Remember to ensure that the necessary firewall rules and ports are open at the new site to allow the Meraki devices to communicate with the Meraki Cloud Controller. If there are any restrictions on outgoing connections, you may need to adjust those to allow the devices to connect.
Also, keep in mind that if you are using features that depend on the public IP address (like static IP assignments, VPN connections, etc.), you will need to adjust your configuration for the new public IP once the devices are at the new location.
Are you using DHCP on the MX to get the public address?
As long as you use DHCP on the MX, you just connect the Devices on the new site. Via Internet the devices will register into the existing Meraki organization again.
rgds
roger
Yes, you can certainly set up your Cisco Meraki MX75, MS210, and APs at home and then move them to another location. This is one of the benefits of Meraki's cloud-managed nature - devices can be configured remotely before they're physically deployed.
Regarding the public IP address change, it won't be a problem. The Meraki devices are designed to automatically check in with the Meraki Cloud Controller, no matter what their public IP address is. When you move the devices to a new location, they will simply use the new public IP address assigned by the ISP at the new location to connect to the Meraki Cloud Controller.
Here are the steps you would typically follow:
Remember to ensure that the necessary firewall rules and ports are open at the new site to allow the Meraki devices to communicate with the Meraki Cloud Controller. If there are any restrictions on outgoing connections, you may need to adjust those to allow the devices to connect.
Also, keep in mind that if you are using features that depend on the public IP address (like static IP assignments, VPN connections, etc.), you will need to adjust your configuration for the new public IP once the devices are at the new location.
You can absolutely pre-deploy these items at home to configure them and then move them. The only change you may need to make is on the MX for the IP address if you are not using DHCP. Take a look at the information for the local status page if you do have a static IP for the MX. https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Me...
@PJB We do as you are suggesting all the time. As @rwiesmann and @KathleenJ suggested only the WAN config on the MX might need attention when you move the equipment.