Subatomic policy API strips out source and destination addresses

Reply
Not applicable

Subatomic policy API strips out source and destination addresses

We are trying to convert some CheckPoint policies into a Panorama device that already has the full address and service objects loaded on it (from previous imports).  But when we generate the security API calls as subatomic, it seems to strip out the address objects from the rules.  We don't want to copy over the address objects again as they have been modified on Panorama with changes that we don't get from the CheckPoint import.  Why is the tool stripping the address objects?  I could see if it sent a non-existent address name that the rule would fail, but all the rules are passing, just with nothing useful in them except the service objects.

Tags (2)
Highlighted
L7 Applicator

Re: Subatomic policy API strips out source and destination addresses

Hi,

Its hard to figure it out, can you send some screenshots or even the configs to fwmigrate@paloaltonetworks.com? then we can check. If not, please can you add here some screenshots or add more information regarding the workflow you are following here?

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 Live Community as a whole!

The Live Community thanks you for your participation!