Expedition won't export Set commands

[PaulMurphy]

Hi,

I have just got through the import-import-merge-remove invalid-dedupe with a Checkpoint source to an existing Panorama config.

At the very last step I do the export and I get xml and pretty xml - which contain the new policy but the Set command file is empty. Am I missing something?

Paul

[Edited to remove separate upgrade issue]

[azuniga]

Hello @PaulMurphy 

I confirmed internally yes the set command part is a bug we are looking into but have no fix for yet.

[MNagel]

That bug stopped us cold on a major consolidation/migration project
early this year.  We were told we needed to wait for 2.0.

[azuniga]

Hello @MNagel 

Why are you not able to use the xml commands created through the export section? You could always load them into your firewall and perform a load config partial.

[MNagel]

While it may have been possible, the migration we were doing at the time
was MUCH simpler to do with set commands and some scripting to pull
sections under migration into Panorama via the CLI.  I have used partial
XML imports for other processes (address objects and such), but the
rulebase updates just were going to be too painful with XML.

[azuniga]

Hello @MNagel 

As an alternative have you thought about using the API push and allowing the configuration to sit within the pre-commit until your change window? Or just have what you want pushed over the API instead of using the set commands?