Generated config file does not contain the expected data after merging

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Generated config file does not contain the expected data after merging

L2 Linker

Hi,

 

I upgraded Expedition tool to 1.2.102 and encountered a symptom I hadn't experienced before. I'm about to migrate an ASA config to a Palo Alto config, and everything seems to be going fine until generating the merged configuration. All the merged data is visible on the Expedition surface, but after generating the files, it contains only the base config. Do you have any suggestions for what might be causing this issue?

Regards,

Mihaly

2 REPLIES 2

L4 Transporter

Hi @mkukucska 

Please could you confirm you executed all steps defined in the above video

https://www.youtube.com/watch?v=RMHfO4MA0jw&list=PLD6FJ8WNiIqVez8EBeoyRsnQcKTA5FuZ-&index=8

Also could you check the file /tmp/error for any error output.

Thanks,

David

Hi,

 

Thank you for reflecting my issue. However, this was caused by improper input files. Even though the merging seemed to be succesfull, generating the new config did not work with those two config files, I was working with. I tried with another one, and everything is working with this one.

 

Regards,

Mihaly

  • 114 Views
  • 2 replies
  • 0 Likes
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!