Network Interface not pushed from Panorama

[FarzanaMustafa]

Hello,

We need to add an extra IP Range to route out one of the existing sub interfaces on the Palo Alto firewall.

The change has been committed and pushed in Panorama but is not showing on the firewall.

Both using version 8.1.3

Firewall network interface:

Panorama network interface with the change circle in red:

How do we push this change to the firewall or do we have to replicate the change on the firewalls?

Any documentation on this?

Thanks in advance!

[BPry]

@FarzanaMustafa,

If the commit and push had finished completely are you positive you made the change to the right template? 

[dstjames]

I would check that it committed successfully. I remember when I first started using panorama I thought since I did not get an error that it committed and pushed correctly even though if you go in and check it my have failed for some reason. 

[AlexSieber · Accepted solution]

The green/yellow gear symbols behind the interface on your firewall screenshot indicates that you have an override active on the firewall. This means that the interface is configured locally and overwrites the config pushed from panorama.

You can disable the override on the firewall itself - there is an option to revert in the task line below the interfaces.

Furthermore you can force template values from panorama - but this will affect all overrides! 

In both cases be very careful and check that the template configuration on panorama matches the local configuration of ther firewall - or you will run into trouble!

[MP18]

when you say  

force template values from panorama - but this will affect all overrides! 

does you mean this will override any local config on firewall to new values pushed from the panorama?

[AlexSieber]

yes this is the case, any part of local configuration that also exists in the panorama template will be overwritten.

Local configuration parts that do not exist in the template will remain unchanged, they do not get deleted.

[CDCT-Security]

...And if none of the above suggestions is your fix, and it's more like you have AE interfaces with subinterfaces, currently overriding Panorama-pushed, and then you are ready to revert those to Panorama-pushed, you may very well end up with an error similar to above... *The undocumented solution is, after verifying that your Panorama version of the interface configs (and corresponding VRs and zones) is correct, to manually delete (via CLI on firewall) the subinterfaces and then the corresponding AE, and then Panorama-pushed will show appear with all green cogs.