topic Re: Merge result with empty files in Expedition Discussions

Merge result with empty files

minow — Wed, 27 Jun 2018 06:23:14 GMT

hey

i am finishing the merge stage of the configuration and than download the generated files but they contains only the following lines

the "set" file is empty

the "xml" file has only those lines

===========================

<?xml version="1.0"?>
<?xml version="1.0"?>

===========================

API commands generation also files. one time i have manage to see "error" on the progress bar but nothing informative.

thanks

Re: Merge result with empty files

minow — Wed, 27 Jun 2018 06:52:36 GMT

i have tried merge the configuration "part by part" it looks like i get empty only after i merge the Polices .

all other are merge fine:

1) network

2) VR

3) Objects

4) Zones

how can i figure out what is the issue ?

thanks

Re: Merge result with empty files

alestevez — Wed, 27 Jun 2018 13:39:39 GMT

Can u please confirm the version of Expedition you have? If you are not in 1.0.93 please upgrade and try it again. Thanks

Re: Merge result with empty files

minow — Wed, 27 Jun 2018 17:10:22 GMT

hey

i was on 1.0.84

after the update i am now on version 1.0.94

the merge action complete and i get a non-empty file however

the PA does not accept to load the xml file since it is malformed.

when opening it on notepad++ it looks like the XML structure is bad, the file is not orgenized and the end is trimed in one of the rules in the security rulebae

please advise

thanks

Re: Merge result with empty files

alestevez — Wed, 27 Jun 2018 18:14:04 GMT

maybe you send us the config file to fwmigrate at paloaltonetworks dot com for review?

Re: Merge result with empty files

minow — Thu, 28 Jun 2018 06:38:58 GMT

found the issue with the Trimed configuration it caused by a non english charachters.

i think it will be a good choice to put some "Alert" on the import stage to identify if non supported charachters exist on the imported configuration.

i have imported policy from 2 different source files and it looks like i have conflicts in the rule names with the base config.

the "<entry name="Rule ID 2">" and a lot more exist twice on the security poilcy, one from the base config on the first migrated FW to the PA , and one is from the new config from the currently migrated FW

thanks