device group changes not survive panorama reboot

[netcomsupp]

hey

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?

[netcomsupp]

it happaned to me twice two days of work whrere wasted

[pulukas]

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.

[jcostello]

Which version of Panorama are you currently running?

[netcomsupp]

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

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