Features limitation with Template

StevePF
Getting noticed

Features limitation with Template

Hi, 

Anyone came across a list of features that is not compatible with template?

 

We start questioning the use of templates and if we would be better off with a tool like Bondless Digital to manage our devices.

 

Thanks,

Steve

4 Replies 4
alemabrahao
Kind of a big deal

Hi,

 

- Configuration templates cannot be used on networks with Systems Manager.


- Templates are less effective if your networks have significant variations. Some settings can be overridden per site, but extensive differences can be challenging.


- All networks tied to a template must run the same firmware version. Updating the firmware on the template applies it to all attached networks.

 

- When binding a template, local settings like IP addresses and DHCP configurations can be lost unless specifically preserved.

 

Managing Multiple Networks with Configuration Templates - Cisco Meraki Documentation

Solved: Templates & Cloning - The Meraki Community

Implementing Templates - The Meraki Community

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Inderdeep
Kind of a big deal

jimmyt234
A model citizen

We tend to use templates for LAN/WLAN but for SDWAN it just lacks the flexibility to be useful.

 

If more overrides were available (load-balancing I am looking at you) and the full L7 NBAR list then we would be getting somewhere.

MaghM
Meraki Employee
Meraki Employee

 

Below are overrides that can be configured for networks bounded to a template. Please refer to the product specific guides for more details:

 

MX/Z - MX Templates Best Practices

  • Addressing & VLANs subnets

  • DHCP exceptions

  • NAT / Forwarding rules

  • SD-WAN & Traffic shaping Uplink Configuration

  • Client VPN

 

MS - Templates for Switching Best Practices

  • Switch ports (Access Policies*, Port Schedules*)

  • Routing and DHCP

  • OSPF Routing

  • Port Management Profile

  • Stack Management

  • DHCP Snooping

  • Dynamic ARP Inspection (DAI)

 

MR Access Points

  • SSIDs (name, enable/disable)

  • Access control

  • Radio Settings (RF Profiles)

*Note: These configuration must be defined at the template level

 

If anything else you think it's suitable to be override please submit a feature request . Any wish that is made it sends an email to our Product Managers and Development Teams.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.