Best Practices for Templates
We have 260 firewalls and we’re going to be adding another 100 by the time we are done. Our templates are a nightmare (think spaghetti code). My initial draft looks like this:
Global (or Admin) template
Regional template
Global Protect (firewall specific)
High Availability (firewall specific)
Management template
Network template (firewall specific)
I‘m afraid we may have many Network templates and template stacks for each firewall.
We do a lot of configuration on the firewalls themselves and many of them have zones that they don’t need. This has caused us some headaches and we‘ve had to get creative.
Is this normal or is there a better way to do this?
288 Views
I think it largely depends on what your environment looks like. We have a "common" template where most things set up on the "device" tab are the same across all firewalls and then we have site specific templates. We combine those into site stacks.
Basically anyways.