Do you use templates?

EMU_IT
Here to help

Do you use templates?

As we prepare to deploy Meraki APs it seems like I'm regularly finding features in the dashboard that do not work when templates are in use, such as group policies page not listing clients affected by a policy, and the Meraki app not supporting push alert notifications for template bound networks.

 

Do you use templates?  If so, how do you feel about the limitations they bring?

13 Replies 13
alemabrahao
Kind of a big deal
Kind of a big deal

I use it in most deployments, especially when it comes to Wi-Fi.
In general, it works very well for me, both for Wi-Fi and MX.

When I encounter some kind of limitation, I prefer to leave it out of the template.

What exactly are you having trouble with besides the Meraki App OS issue?

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.
EMU_IT
Here to help

The most annoying limitation (at the moment) is the fact that you can't get alerts via the Meraki iOS app for networks that are bound to a template.

I tried to work around it by using a webhook to a Teams channel, but couldn't get that working.  I'm testing to see if the Teams channel email will work.

Ryan_Miles
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Mobile app alerts work for me and template bound networks/devices. Is this what you’re referring to?

 

IMG_4721.jpeg

EMU_IT
Here to help

Hi Ryan_Miles,

 

Yes, that is exactly what I'm referring to.  How did you get that to work?

 

The mobile app won't let me enable notifications, and Meraki support says "I just confirmed the Meraki App cannot setup alerts on bound networks."

 

djz

Ryan_Miles
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

I don't recall doing anything special. Checking my app settings > notifications > wireless it looks like this. Does yours look different?

 

Ryan_Miles_0-1758895574944.jpeg

 

Ryan_Miles_1-1758895656777.jpeg

 

EMU_IT
Here to help

Indeed, the look is different on my phone.  (I'm using iOS if that makes a difference.)

 

There is no "Notifications" option in Settings, but there is an Alerts tab at the bottom, and in that tab there is a gear icon in the upper right to configure alerts.  Any option I select looks like this:

IMG_4018.png

Ryan_Miles
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Ok, so I poked around the app some more. If you're in a non template bound network the settings > notifications section is visible. If you're in a template bound network it's not shown and looks like your screenshot. I too am on iOS 26 running the current mobile app version.

 

So, if you go to a non template bound network do you see notifications? And if so enable it and them test downing a template bound device if possible.

 

When in a non template bound network.

 

Ryan_Miles_0-1758897895796.jpeg

 

When in a template bound network.

 

Ryan_Miles_1-1758897903678.jpeg

 

EMU_IT
Here to help

Thanks for the suggestion.

 

I created a network that is not bound to a template.  I then opened the app and selected that network and was able to enable alerts via Settings / Notifications...

IMG_4071.png

 

I then disconnected an AP in a bound network.  Unfortunately, nothing changed... I did not receive a notification on my phone from the app.

 

Thanks anyway.

 

Ryan_Miles
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Did you leave the device offline for >1 hr given your trigger config in the screenshot?

EMU_IT
Here to help

Thanks for highlighting that, which I missed in my testing.  I changed it to 5 minutes and tried it again today, but it didn't make a difference... still no notification when an AP in a bound network goes off-line.

 

You don't have to spend more time on this... I have a work around using a Webhook to a Teams channel that is good enough for now.

RaphaelL
Kind of a big deal
Kind of a big deal

Yes and no.

 

Our smaller sites ( 500-700 ) are all bound to different templates

Our bigger sites ( 500ish ) are not bound to templates. 

 

The main reason we do not use templates for the bigger sites is to load balance the load to our DC hubs. Since all spokes from the same template have to use the same hubs , that did cause us issues in the past.

 

For templates limitations , the only things that bothers us at the moment is NBAR , VLAN profiles and probably some minor things that are annoying that I'm forgetting.

PhilipDAth
Kind of a big deal
Kind of a big deal

I use them on any network that uses many branches that are the same, e,g. retail chain stores.

JamesC_AB
Here to help

My favourite thing about Configuration Templates is the ability to unbind while retaining configurations 😀. It's a get of jail free card that wasn't always there for people who later regretted choosing this feature:
https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_...

Based on my experience, I only recommend Configuration Templates for initial provisioning of networks (e.g. if you really want to use the Switch Templates). Even then, if I can get away with a non-template empty network that serves as something to clone from, I do. Once provisioned, I recommend unbinding any templated networks (while retaining configurations) because:

  1. It's difficult to phase the rollout of new firmware or architecture changes as all template-bound networks upgrade/change on the same schedule. Firmware regressions or upgrade issues can therefore have a nationwide impact.
  2. Technician/Operator human-error mistakes have a nationwide impact. In practice, Meraki Dashboard controls and warnings about the impact of Configuration Template changes have proven ineffective (e.g. someone wanting to change a SSID's PSK at one location without realising the wider impact).
  3. Meraki's back-end infrastructure supporting Configuration Templates has proven unreliable between 2021-2024, hindering fast paced provisioning of networks at scale.
  4. Configuration Template bound networks have historically shared certain resources in Meraki's back-end infrastructure which has been found to hinder scalability (e.g., whitelisted client limits).
  5. Configuration Templates are often late to support new features (e.g. IPv6, VLAN names, MultiWAN Backup Uplink).
Get notified when there are additional replies to this discussion.