- Get Started
- News & Events
- Collaboration
- Education Services
- Technologies
- Next-Generation Firewall
- GlobalProtect
- Threat Prevention Services
- Endpoint Protection
- SSL Decryption
- App-ID
- Content-ID
- User-ID
- 5G
- IoT Security
- Cloud Identity Engine
- Panorama
Network Security
- Prisma Access
- Prisma Cloud
- Prisma SD-WAN
- CN-Series
- VM-Series:
- OCI
- Alibaba
- AWS
- GCP
- Azure
Cloud Security
- Cortex XDR
- Cortex XSOAR
- Cortex Data Lake
- Cortex Xpanse
Security Operations
- Resources
- COVID-19 Response Center
device group changes not survive panorama reboot
- LIVEcommunity
- Collaboration
- Discussions
- General Topics
- device group changes not survive panorama reboot
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
device group changes not survive panorama reboot
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
05-28-2014 01:33 AM
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?
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
05-28-2014 01:34 AM
it happaned to me twice two days of work whrere wasted
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
05-29-2014 03:18 PM
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.
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
06-02-2014 02:14 PM
Which version of Panorama are you currently running?
- Mark as New
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report This Content
06-05-2014 12:43 AM
yes i also prefer committing panorama and then committing the devices.
as i asked Paloalto there is a feature request for this issue
- How to upgrade software in firewalls when firewalls are managed by panorama in Panorama Discussions
- Pushing GlobalProtect Linux Clients in GlobalProtect Discussions
- Auth failed after Global Protect cert renew in GlobalProtect Discussions
- Connection HTTPS / HTTP and SSH not working in General Topics
- After changing exiting object name at panorama, got commit failed message in General Topics
Show your appreciation!
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!
