Have you ever felt the Meraki templates were too restrictive for your use case? If you have, you are not alone.
The Meraki configuration templates are most useful in cases where a large number of sites share a common network design.
They allow many Cisco Meraki devices to be deployed following a single base configuration, so in this kind of scenario, they are a great asset to speed up network provisioning and maintain consistency across your organization.
However, the reality of a high number of Administrators is much different.
Network Administrators may be able to use the Configuration Templates to provision new networks in a consistent way. However, the moment they need to change a specific configuration on just a handful of networks, the Meraki Templates will not work. And here is where the real struggle begins.
The first and most common one is running the configuration changes manually. It clearly isn’t the sexiest option for most of us but is the one we know the best.
If you just need to configure one or two fields in a few networks, making these changes manually may be fine. The problem comes when the changes impact hundreds of networks. In this case, running manual configuration changes can be not only time-consuming but also quite error-prone.
To overcome this issue, Meraki has opened access to its Dashboard API.
The API contains a set of tools for building software and applications that communicate with the Meraki Dashboard. It can be used for multiple use cases, including bulk configuration changes, providing you with much more flexibility than with the simple use of the native templates.
The downside to this is that to use the Meraki API, you will need to develop, test, and maintain your script.
Unfortunately, this can also be a costly task, both time and money-wise.In summary, any alternative to the Meraki Templates would either be time-consuming or result in costs down the line.
To help Network Administrators make the most out of their time, Boundless Digital has designed a new concept of Configuration Templates. The Boundless FlexTemplates.
Boundless FlexTemplates works quite similarly to the Meraki Configuration Templates, with one exception.
Unlike the Meraki templates, the FlexTemplates aren’t bound to your networks. They are deployed.
This difference is key as thanks to it they provide much more flexibility when making custom changes to individual or selected networks.
Boundless FlexTemplates is powered by the Meraki Dashboard API. This gives Network Administrators access to all the possibilities the API provides without having to develop, test, or scale in-house scripts.
As a result, they can save time and money in the long run.
If your networks aren’t bound to a Meraki template, you can deploy FlexTemplates across your selected network, and then also apply individual changes.
In the same way, after deploying a FlexTemplate to your networks, you can choose to bind them to a Meraki template.
You can deploy many FlexTemplates to the same networks, progressively extending or overwriting the configuration changes.
With Boundless FlexTemplates, you can make customized changes to your individual networks in bulk, even when these are bound to a template.