Missing Security Zone in Export XML Expedition Cisco ASA to PA Template

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

Missing Security Zone in Export XML Expedition Cisco ASA to PA Template

L1 Bithead

Hello everyone,

I imported the configuration from Cisco ASA to PA-460 by following the tutorial from https://www.youtube.com/watch?v=-gbQ-YcgoPs&list=PLD6FJ8WNiIqVez8EBeoyRsnQcKTA5FuZ-. Everything went well except for the Security Zone section which was not exported in the XML file. Can somebody help me?

1 accepted solution

Accepted Solutions

Hi @M.Danuarta 

I can confirm it is a bug on version 1.2.96 and it is fixed in 1.2.97 (ETA 21/OCT).

The issue is happening when migrating to a FW. The default template for the zone is not properly set and that causes Zones are not exported in the XML/API and set commands file.

Thanks for pointing this out,

Best

View solution in original post

7 REPLIES 7

L4 Transporter

Hi @M.Danuarta 

Could you check you moved also the zones while doing the drag and drop on the export section. Please see above image as an example.

Also reach out to fwmigrate@paloaltonetworks.com to get in touch with the team and if needed jump into a call.

Thanks!

Hello @dpuigdomenec ,

Thanks for the response, yes I have done that but it's okay because I have found a solution by using an older version of Expedition which is 1.2.93.

Maybe bug in 1.2.96?

Hi @M.Danuarta It could be a bug in 1.2.96. I will test in my lab and publish here my results. Thanks!

Hi @M.Danuarta I have verified with merging a ciscoasa config and panorama config in Expedition v1.2.96 and export it out as xml file, I was able to see all the zones are showing in the xml file. I suspect could be when you drag and drop the zone folder from left to right , you drop it to the DG folder instead of template->Device->vsys1  like the solution mentioned in below article:

 

https://live.paloaltonetworks.com/t5/expedition-discussions/drag-and-drop-source-configuration-to-ba...

 

if you need further helps, please contact fwmigrate@paloaltonetworks.com. Thank you!

Hello @lychiang , thanks for trying to help
But in the project I'm working on it's a direct migration to the firewall not through panorama. I have followed the tutorial from this video https://www.youtube.com/watch?v=RMHfO4MA0jw&ab_channel=PaloAltoNetworksLIVEcommunity and the result is still the zone is not exported to xml.

But i want to try through panorama too to see if it works

Ah yes, it turns out that if it is through the panorama configuration file, the zone is exported properly. But I still can't migrate directly to the firewall config.

Hi @M.Danuarta 

I can confirm it is a bug on version 1.2.96 and it is fixed in 1.2.97 (ETA 21/OCT).

The issue is happening when migrating to a FW. The default template for the zone is not properly set and that causes Zones are not exported in the XML/API and set commands file.

Thanks for pointing this out,

Best

  • 1 accepted solution
  • 1313 Views
  • 7 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!