Question about Scheduled Device Config export of Azure FW from Panorama - 01005602

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.

Question about Scheduled Device Config export of Azure FW from Panorama - 01005602

L1 Bithead



Scheduled Device Config export is only exporting local running config from the managed devices(same as export config snapshot done from device) and not panorama pushed policies,objects and network templates. While this may appear as an expected behavior per below docs



However, there are four VM Azure firewalls for which the config-bundle export has BOTH local + panorama-pushed config (analogous to .merged-runningconfig.xml).  


Can you please help me on if it is expected behavior and ascertain the reason why the inconsistency is observed.


Case number is 01005602




L5 Sessionator
This is a Panorama function so this should go in the Panorama section of the live community. Despite the firewall being VM series the function of you are utilizing relates to Panorama usage. This section is for specific challenges related to AWS and Azure. Thanks
  • 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!