pn do not use tempalte ,only use device group

Felixcao — Wed, 14 Dec 2022 04:31:11 GMT

The customer manages multiple sets of firewalls through panorama. Considering that the configuration of the template is not changed much in the future, the customer considers porting the configuration of the template to the local wall. If the parameters are changed, it will not be pushed through panorama.

Panorama is only responsible for pushing policies and objects. Does this bring new problems to the later operation and maintenance, or are there any special precautions?

Please put forward more suggestions or discuss, thank you.

Re: pn do not use tempalte ,only use device group

PavelK — Wed, 14 Dec 2022 10:07:48 GMT

Hello @Felixcao

thanks for the post!

I can think of a few issues and limitations.

Some of the Device Group configuration has dependency on Templates. For example Log Forwarding profile is being pushed by Device Group, but Syslog, SNMP, Email is coming from Template. If you do not use Template, you will not be able to push this configuration. The same applies to security policy, QoS, Policy Based Forwarding, Decryption. Each of these configuration is leveraging Zones and moving this from Template to local Firewall configuration will result in not being able to reference it in Device Group.

There are still some configuration under Device Group that have no dependency on Template, however not being able to use configuration from Template because it has moved from Panorama to local configuration will limit customer to only several configuration sections.

Personally, I think by this move there are more limitations than benefits.

Kind Regards

Pavel

topic Re: pn do not use tempalte ,only use device group in Panorama Discussions

pn do not use tempalte ,only use device group

Re: pn do not use tempalte ,only use device group