Expedition can merge multiple configurations, and you can also merge it manually if you're comfortable working with XML (heck, you could even merge it directly on the firewall if you wanted to). If you aren't comfortable working with XML, expedition is going to be the most "user friendly" way of doing so easily.
As for the migration itself, once you have the configuration built out you'll just want to manually go through and verify that everything actually is how it should be. Personally, when doing this sort of migration I like to take the time to go through everything and verify that I'm not moving over unused objects or rulebase entries that don't actually need to exist anymore. Use it to do a bit of "housekeeping" if you will.
Thanks for quick response , manually merging would be huge time consuming also could be error prone as we have total 20 nos vsys configuration from diff set of HA setup , many common setting, named policy like LACP bonding , zone, etc. Does Expedition tell if there is duplicate/shadow/override configuration while merging two configuration.
Is there any ways to do inplace migration with less downtime where in one shot , we can do all instances migrated to new setup?
Also thinking about in parallel migration , apart from time constrain is there any other risk is involve while planning to do batch wise vsys movement.?
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!