Guys sorry for the newb question but our company just up and ordered a bunch of PA stuff.
We configure a firewall to access the Internet and connect to panorama on Ethernet 1\1.
We import the devices settings into panorama and achieve a sync.
Now we would like to create a template stack and device group and push everything in panorama back to the firwall.
So using variables we make sure that we are going to assign the proper public IP to Ethernet 1\1 (essentially overwrite the existing config of Ethernet 1\1 on the firwall with the exact same settings pushed from panorama). Every time we try this we get a commit failed Ethernet 1\1 is in use.
What are we missing, Should we not be trying to overwrite Ethernet 1\1's settings with those on panorama?
I am sure we are either doing something stupid or we are missing some aspect of a proper panorama configuration but for all my reading I still have no idea what it might be.
Thanks for any and all help
hi @LeeRRoss !
Are the firewalls already configured to be in Layer3 mode, or are they still in their factory setting?
If the latter, you'll want to remove the default v-wire configuration and commit the change on the firewall, as by default int1/1 and 1/2 are tied together and if you push only config for eth1/1 that may cause such issue
For the former, if you log on to the firewall you can check for additional details of the commit job to see if that adds more clarity to the issue
In addition to readers comments, you may also want to check out the below documentation.
It kinda makes sense that, if you already have a configuration on the firewall, then try pushing configuration from Panorama - it will fail since the configuration already exists. That's why Panorama has an option for "Push device config bundle" (step 5) which helps avoid any commit errors.
Give that a go and let us know if that works.
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!