Being able to quickly and easily deploy new networks from a predefined configuration is a massive boost when you are trying to deploy a number of similar sites, but what if not every site should share an identical configuration, or if you want to further tweak a specific site’s configuration after deployment without modifying the entire template configuration? This is where template local overrides come into play.

Local overrides enable you to manually override certain configurations of template child networks from the template-assigned values. Many, but not all, settings can have a local override configured if the template-assigned value is undesirable for any reason. As an example, this can be extremely useful for deployments configured for unique subnetting that are using a very strict subnetting scheme across sites, as by default the subnets for a given child network are taken at random from the pool of available subnets defined at the template level. For example, a network may be assigned two /25 subnets from a template pool of 10.0.0.0/8, but there is no guarantee that the chosen subnets will be contiguous from the previous site that was deployed from the same template, or even between themselves at the same site. As a result, it may be necessary to manually adjust the assigned subnets to remain in line with a predefined addressing scheme across different sites.

Pro Tip

Subnets allocated from templates to child networks will never overlap with an existing configured subnet within the organization unless this ability is explicitly enabled by Meraki Support for your organization.

Local overrides like this can be easily performed by simply navigating directly to the child network in question and modifying the configuration in that network, very similar to a network that is not bound to a configuration template. While not every setting can be configured with a local override, many of the most common configurations across devices can be, to still allow for further customization as needed even when attached to a configuration template.

Leave a Reply

Your email address will not be published. Required fields are marked *

Explore More

Configuring Auto VPN – MX and MG Best Practices – Cisco Meraki

Figure 5-10 shows the Security & SD-WAN > Site-to-Site VPN page of a network configured as an Auto VPN spoke pointing back to two different hub devices, with the primary

IDS/IPS – MX and MG Best Practices – Cisco Meraki

Alongside Cisco AMP, you can configure the IDS/IPS feature set for even further security monitoring. When enabled, the IDS/IPS feature set inspects all routed traffic passing through the MX while

Cisco Umbrella – MX and MG Best Practices – Cisco Meraki

Through the use of the Meraki Dashboard, MX devices can also be integrated with Cisco Umbrella to utilize predefined Umbrella content filtering and security policies. Utilizing a simple API-based integration,