Expedition Merge and Generate XML not working

cancel
Showing results for 
Search instead for 
Did you mean: 

Expedition Merge and Generate XML not working

L1 Bithead

Hi, 

 

After trying and failing on Expedition 1.0.95 with no luck I have now deleted my VM and downloaded and updated to 1.0.107.

 

Whenever I migrate (tried Cisco, Checkpoint and Juniper), I click export, drag the elements into the base config, press merge then generate xml. I'm left with what looks like the original base config instead of a xml output.

All the migrated work is lost.

 

What is the sequence from when I am ready to generate an xml?

 

By the way the configs and base config are fine as I've used them before in the Migration Tool 3.3.15

 

Thanks

20 REPLIES 20

It is the case for both the XML and the ZIP for me. When I open up the XML, it looks like 1 line from each section has been imported. For example, eth1/1 was created but not the rest of the interfaces. The first gateway and ipsec objects are in the XML but not the full list I am expecting. Same with security rules, only the first line is shown in the XML. I assume expedition is hitting some kind of error in each section and skipping to the next section.

Hi,

 

Would it be possible to export this project having issues and send it to fwmigrate at paloaltonetworks dot com for further research?

We have not experienced this issue, and it may be a corner case that we would like to study to address it.

 

Best,

Sorry about the delay.

 

I blew the VM back in October as Palo Alto now have a higher version to download. I'm on 1.0.107 now, which I belive was a fresh download then one update.

 

So far it seems to be ok but I've only tested it with 1 Cisco config (the exact same one it wouldn't work with before) and one Checkpoint.

 

What version are you on?

You are the best 🙂

hey i have the same problem!!

how did u download the earlier version..

i cant do nothing now 

 

someone?

expedition.PNG

 how did u downlload this version 1.0.107??

i have the same problem

We are already in version 1.1.35.

 

Make sure that you are always running the latest version

I am having the same problem after pressing merge, it comes back blank as well.  It appears everything is stuck as pending.  I am on version 1.35 and another consultant we have is on .36 and seems to be having the same issue.

Looks like the bug is still there (although not for me). I'm afraid I have no answer other than a brand new VM with a newer version that Palo Alto made available.
Are no Palo engineers monitoring these threads anymore?

Hi, yes we are here. Are you in 1.1.38? is still there the problem? if yes, please send us an email to fwmigrate at paloaltonetworks dot com and we can schedule a zoom session to see what's going on!

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!