i attempted to migrate an HA pair to Panorama which went bad. I had only pushed to passive and when i tried to make it active, everything went down.
had to make the previously active firewall actve again, and load last save on passive to recover the passive firewall
now, after after disabling panorama setting in firewall>device>setup, i have firewall rules starting from 100, instead of 1, and commit on standby fw fails bunch of "already in use" messages during validation.
it seems the firewall has duplicate rules and objects, only thing is i cant see them to try and delete them!
You can try following
Import active fw to Panorama.
Commit to Panorama.
Export to passive device.
Load device config on passive.
Change any settings that is different in passive (mgmt ip, hostname, HA settings etc)
Commit to firewall.
If successful so far then commit to firewall from Panorama.
Did you save and export a named config backup from both the active and passive before starting the Panorama work? If so, I would disable Panorama policies, objects, templates etc, load those configs and start from scratch.
If you didn't make any manual backups, your best bet is to revert to a previous configuration version. (Device -> Setup -> Load Configuration Version) and start from scratch.
As for why it failed in the first place; it's hard to say but I would definitely follow the below instructions. It sounds as though there may have been an issue with the device config bundle stage.
thanks for responding
i do have save .xml for both firewalls. both on the firewall and on my local pc.
infact, the active firewall is fine, no duplicate rules as well as rule number starts from 1
i was able to restore HA and access to the passive firewall via revert to last saved config
i can attemp again, but the question is, how will it different from last time, is restoring via named config any different than revert to last saved config? as revert to last saved config broguht back the firewall with duplicate rules which i cant see
If you import firewall(s() into Panorama do not commit from Panorama.
If something goes bad then it is a struggle.
Disable config sync in firewalls.
Device > High Availability >General
Import config from firewall to Panorama (I guess this part is done already).
Do any changes needed.
Commit to Panorama
Push config to passive firewall.
Panorama > Setup > Operations > Export or push device config bundle
Choose firewall and click Export
Log into firewall cli.
Verify that all rules are in place (if not then just revert to running config to get back to clean state. reboot will do the trick also as pushed config is not committed).
Perform step on second fw.
Enable config sync in firewalls.
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!