topic Add Palo alto HA (existing config) in Panorama. Doubts.. in General Topics

Add Palo alto HA (existing config) in Panorama. Doubts..

BigPalo — Fri, 05 Sep 2025 06:24:40 GMT

Hi,

I need to add a cluster A/P FWs in Panorama. I was checking this useful link: https://www.mbtechtalker.com/migrate-a-ha-pair-of-pan-firewalls-to-panorama-management-2/ and videos on internet.

I have everything under control, but I'm a little concerned about if its necessary in any point to enable the "force template value" option at some point to do a commit, as it could affect the HA or MGMT interface. I would like to HA config and each MGMT interface stay in local FW config (not template)

In one of the step it's suggested that the HA configuration be removed from the templates that will be included in the panorama, but after that, i dont know if the commit should be launch with "force template value" marked or not.

Thanks

Re: Add Palo alto HA (existing config) in Panorama. Doubts..

reaper — Fri, 05 Sep 2025 08:11:29 GMT

if you make sure the management and HA config is removed from the template, you will not overwrite it locally

after the "export or push device config bundle" all local settings that appear in the template will automatically be overwritten with the template, so normally you shouldnt need to push a config with 'force template values' enabled

Re: Add Palo alto HA (existing config) in Panorama. Doubts..

BigPalo — Fri, 05 Sep 2025 12:25:25 GMT

Thanks reaper as usual. In the previous link the HA config in the template is deteled but not the MGMT interface. i dont know if MGMT will never overrite and thats why there is not any action on the template.

Re: Add Palo alto HA (existing config) in Panorama. Doubts..

reaper — Tue, 09 Sep 2025 09:14:48 GMT

any thing that is included in the template will be pushed to the device

That's where the force template comes in: an existing thing will not be overwritten by a template unless you force template values. a non-existing thing will be created by the template

any thing that's not included in a template will remain local