Panorama objects to be used in a local firewall config through expedition

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Panorama objects to be used in a local firewall config through expedition

L3 Networker



In a somewhat unusual case I'm trying to use objects pushed through Panorama, in a policy in expedition. Both Panorama and the firewall are linked & imported in the expedition project.

Moving the firewall policy to an all Panorama policy isn't an option here (yet). Is there a way I can use a Panorama object (already present on the firewall) and use it in local policies through expedition (or the find/replace functionality)?



L5 Sessionator

If the current FW policy is using the object, the object should appear in Expedition when importing the configuration.

This would be one of our called "ghost" objects.


We identify those objects if we see them used in the configuration but not being declared (as it is the Panorama push config the one declaring the object).

One trick would be to create a disabled rule using the object, or an object group using that object in the FW, and when importing the configuration into Expedition, those objects would show up.

We do not directly go to the Panorama configuration to see which are the objects that may have been pushed to the NGFW.

  • 1 replies
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!