Is there a way to use a template but control specific subnets per site

[RJD_CCIE]

I have read a punch of posts / threads but have not been able to find my answer. Your input is appreciated. Here is the scenario:

Let's say you are replacing a bunch of established locations with Meraki MX. Each site currently has 3 VLAN's & subnets assigned to them

VLAN 10 - Data

VLAN 20 - Voice

VLAN 30 - DMZ

For IP design, the customer has assigned / deployed a 172.(16-31).x.0/22 CIDR per location, giving them 4 /24's to use:

VLAN 10 - 172.16.1.0/24

VLAN 20 - 172.16.2.0/24

VLAN 30 - 172.16.3.0/24

We are trying to leverage templates for both install and post-install maintenance. However we cannot get around the template Addressing & VLAN's limitation (perceived limitation) in which we need to keep these same subnets assigned as part of migration (we don't want the customer to have to re-IP a bunch of devices that are static configured in these subnets). If we try and use the Unique option, it seems we HAVE to have a different CIDR for each VLAN? If I choose 172.16.0.0/16 for more than one VLAN, the dashboard complains. If I chose unique CIDR for each VLAN and attempt to modify individually per site, the dashboard complains saying the subnet MUST be within the assigned CIDR to the template.

Sorry for the long message, but wanted to provide some details. Is there a solution here?

[alemabrahao]

It's not possible. What you can do is try to create a new template, but even then, you won't be able to create a new template that overrides the current template's range (as far as I can tell).

In short, either remove the devices from the template, adjust it, and then add them back, or you'll have to perform a REIP of the network.

[RJD_CCIE]

This seems a bit short sided IMO. We have used automation to get around template limitations before, however this one just kinda got to me. It sounds like our best plan would be the following:

1. Use a template(s) to perform initial consistent config behaviors (3 SSID, auth, 802.1x, etc)
2. Bind to device
3. Unbind from template, retaining configurations
4. Leverage automation tool / orchestration to deploy unique site settings (IP, etc)
5. Sit back with a cool one 🍻

[Ryan_Miles]

Templates are meant for bulk config both for initial deployment and ongoing operations. They’re not intended to be for staging usage or config snippets like perhaps other platforms. 

In the steps you listed above if the end goal is API then you could remove steps 1-3 and accomplish it all with API. 

[Ryan_Miles]

Example template and network with edited subnets post initial binding and auto address assignment. Is this what you're after?

[PhilipDAth]

Hmm. I have used overlapping addressing between templates and sites, but I'm not sure if I have attempted to do this within a single site.

For the cases I have handled, you open a support case and request that they disable the unique IP addressing requirement.  Then it won't check, and you can assign anything you want.