Panorama Theory- Understanding Templates, Device Groups & Firewalls

Showing results for 
Search instead for 
Did you mean: 

Panorama Theory- Understanding Templates, Device Groups & Firewalls

L3 Networker
I am trying to get a clear general understanding of Panorama managed Firewalls & how they work with templates, template stacks and device groups. Can someone please correct and or add to my current understanding as I explain in a scenario below? I did take the free training and know that variables can be configured within Panorama but ask that you avoid using variables in your advice to my questions because right now I feel they are hindering my general understanding of how to best manage firewalls at scale....

In my current understanding, created templates & their configs within them, by default only get configured on the Firewalls assigned to them? If a different firewall must have a different security and nat policy, with different inside & outside addresses, that could easily & effectively be accomplished by creating a separate template, with the addresses specific to that site configured within the security & nat policies? In this scenario both firewalls assigned to the separate templates would only have the configuration of the template they are assigned to when looking locally on each firewall?

Pertaining to the scenario above...

Since both firewalls require different security & nat policies as well as interface IP's, this could easily be achieved by not only creating separate templates with differences in configuration but by also creating different device groups, also differing in configuration and assigning each firewall to a separate group which would have the site specific interface addresses and objects within them? The separate device group configurations would not have the site specific configs crossing over into the other device group and when looking locally on each separate firewall you would only see the configs from the device group its connected to in Panorama, not both device groups?

In summary, each firewall could have its own dedicated template, template stacks & device group which would not cross over into each other in Panorama or when looking locally on each firewall. This is an effective way to manage each separate firewall using Panorama and will eliminate the chances of misconfiguring other firewalls by mistake when needing to make changes to only a single specific firewall?

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!