Staged Firmware upgrade for Templated Networks

[amabt]

We are evaluating options to bring our devices that are all in a Full stack template to the latest stable firmware with hundreds of networks.

Since we are using template this means when an upgrade is applied to the template all devices atatched to it are going to be upgraded in one hit. If there is an uncaught test case then we potentialy has many sites that we have to deal with at the same time.

How do we best stage rollout so that only a subset of sites in the template network are upgraded at any one time to minimise any impacts?

I can't see any option here. Removing devices from the template is not a viable option here.

Seeking everyone input on how you are doiing it?

Thanks.

[Brash · Accepted solution]

The best way in my opinion:

Have a few sites which run as pilots and are not bound to the template.

Use these sites to perform large config changes and run newer firmware to validate before applying to the template.

Best practices doc for reference: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/...

[RaphaelL]

Unbound the network from the template.

We have over 2K networks and yes we are using templates on most of the sites. We always test the firmware in a lab , then we do a pilot with a couple sites that are unbound from the template , then we do a massive rollout

Easy as that !

[RaphaelL]

You can also ask support to PIN the firmware from a network bound to a template. Do that for a couple sites if you don't want to unbind them

[amabt]

Thanks all. We currently only have Hub sites not in template.

Looks like we are going to have to unbound some sites from the Template and use them as test sites going forward.