device group changes not survive panorama reboot

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

device group changes not survive panorama reboot

L1 Bithead


is anyone else experience that is you are doing changes in device group / template and only commit on the devices (not panorama) then if panorama reboot it does not save your changes and any audit logs?


L1 Bithead

it happaned to me twice two days of work whrere wasted

L7 Applicator

The candidate config will only be in memory unless you save it as a named config or commit the config.

you can rollback the config pretty easily after commit.

So I would always commit Panorama first then the devices.  If you need to back out the change use the rollback on Panorama and commit both again.

Steve Puluka BSEET - IP Architect - DQE Communications (Metro Ethernet/ISP)
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center

L4 Transporter

Which version of Panorama are you currently running?

yes i also prefer committing panorama and then committing the devices.

as i asked Paloalto there is a feature request for this issue

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!