Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Check Point R80+ policy auto-zoning on import partially works

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

Check Point R80+ policy auto-zoning on import partially works

L2 Linker

Currently working on migration from CP R80.20 to PA 9.0.X. and having issues with auto-zoning during the import process using the show policy package java app method.

Only the Application Layer section of the Security policy has auto-zoning applied. The Network Layer has no Zones applied. 

Interfaces and Zones are created correctly from netstat output however they only appear in the Application Layer Template which is why no Zones are applied to the Network Layer Security policy.  Expedition version is 1.1.69.3.

 

The older API method works when only exporting the Network Layer however in the newer version there is no java app parameter that allows excluding the Application Layer.  Sadly I need to use the latest version for this Customer's migration.

 

Thanks

Ben

5 REPLIES 5

L4 Transporter

Hello,

 

I believe the routing file is used for the auto-zoning feature, which it sounds like you are adding during the import of the checkpoint configuration. If it is still not working with that can you try to upgrade your expedition client to 1.1.76.1 (newest version) and see if there are any changes in your import?

 

If you still see no changes in the behavior please email us at fwmigrate@paloaltonetworks.com so we can attempt to recreate your issue and assist you in trouble-shooting it.

Thanks Azuniga, I will arrange for the customer to upgrade Expedition and let you know how it goes.

L2 Linker

Hi Azuniga,

 

Unfortunately upgrading to 1.1.76.1 has not resolved the issue.

Any assistance would be greatly appreciated.

 

Thanks

Ben

L2 Linker

Hi Azuniga,

If you do try and replicate, please note the export is from a Multi-Domain Management and VSX Gateway deployment.  

I am specifying the correct Domain (-d) and Package (-k) parameters during export so these virtualization mechanisms shouldn't be relevant however I thought it would best for completeness.

Thanks

Ben

L5 Sessionator

We may be applying the autozone on the first policy (which may be in your case the Application Layer), and missing your Security policy.

 

We will take a look into it

  • 4825 Views
  • 5 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!