topic Re: Change subnets after cloning errors in Cloud Networking Platform

Change subnets after cloning errors

m.x — Wed, 25 Jun 2025 07:23:19 GMT

Hi all,

As a new Meraki user I was wondering how to change the subnets after cloning a network.

Under an existing organisation I'm building a new site (network) and cloned my example network. But when I try to change the subnet, I keep getting error that the DHCP settings are not in the range. When I try to change the DHCP, its not in the range of VLAN.

Is there a way to change the subnet without having to delete what I wanted to clone? They are not online, so only a warning would be enough so I could fix the issue, now I can't save and see no other option then deleting the vlans and start anew..

Am I missing something?

Edit: I removed the DHCP reserved range and could then change the VLAN subnet. Is that the only way?

Re: Change subnets after cloning errors

Shubh3738 — Wed, 25 Jun 2025 07:30:21 GMT

You can proceed to create a new VLAN ID by referring to the official Meraki documentation at the link below:

Configuring VLANs on the MX Security Appliance - Cisco Meraki Documentation

Re: Change subnets after cloning errors

m.x — Wed, 25 Jun 2025 07:34:37 GMT

Thanks for responding. Sadly I cloned the site becoause I needed to keep the exact setup, but with a different subnet.

Removing special DHCP config did the trick, but now I need to make a notepad with said settings to add later.. So cloning is not what I expected

Re: Change subnets after cloning errors

Shubh3738 — Wed, 25 Jun 2025 07:39:37 GMT

Cloning can work, you just need to create a new VLAN or a modify the existing one.

In the Meraki Dashboard, follow these steps on cloned network. : Go to Security & SD-WAN > Addressing & VLANs Edit the VLAN .

The Subnet (under VLAN settings).

https://documentation.meraki.com/MX/Networks_and_Routing/Configuring_VLANs_on_the_MX_Security_Appliance

Re: Change subnets after cloning errors

Nicolas Rennetaud — Wed, 25 Jun 2025 07:40:23 GMT

Hi,

Do you have Fixed IP or Reserved IP ranges ? This could be blocking update from vlan side. You have to delete these options before updating vlan configuration.

Try and let us know 🙂

Re: Change subnets after cloning errors

Philip D'Ath — Wed, 25 Jun 2025 20:31:50 GMT

Turn off DHCP, change the VLAN, then turn DHCP back on.

Re: Change subnets after cloning errors

Nicolas Rennetaud — Thu, 26 Jun 2025 08:11:37 GMT

I tried yesterday before answering and I was not able to modify vlan configuration if DHCP has been disabled with reserved or fixed ranges. I thought it was possible as you said.