Revert Panorama Configuration Changes
Table of Contents
10.0 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on Alibaba Cloud
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on Hyper-V
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on Alibaba Cloud
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Panorama, Log Collector, Firewall, and WildFire Version Compatibility
- Install Updates for Panorama in an HA Configuration
- Install Updates for Panorama with an Internet Connection
- Install Updates for Panorama When Not Internet-Connected
- Install Updates Automatically for Panorama without an Internet Connection
- Migrate Panorama Logs to the New Log Format
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute Data to Managed Firewalls
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- View Log Query Jobs
- Troubleshoot Commit Failures
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Downgrade from Panorama 10.0
End-of-Life (EoL)
Revert Panorama Configuration Changes
When you revert changes, you are replacing
settings in the current candidate configuration with settings from
another configuration. Reverting changes is useful when you want
to undo changes to multiple settings as a single operation instead
of manually reconfiguring each setting.
You can revert pending
changes that were made to the Panorama configuration since the last
commit. You can revert all pending changes on Panorama or select
specific device groups, templates, or template stacks. Panorama
provides the option to filter the pending changes by administrator
or location. The locations can be specific device groups, templates,
Collector Groups, Log Collectors, shared settings, or the Panorama
management server. If you saved a snapshot file for a candidate
configuration that is earlier than the current running configuration
(see Save
and Export Panorama and Firewall Configurations), you can
also revert to that candidate configuration snapshot. Reverting
to a snapshot enables you to restore a candidate configuration that
existed before the last commit. Panorama automatically saves a new
version of the running configuration whenever you commit changes
and you can restore any of those versions.
Reverting a Panorama
management server configuration requires a full commit and must
be performed by a superuser.
Full commits are required when performing certain Panorama operations,
such as reverting and loading a Panorama configuration, and are
not supported for custom Admin Role profiles.
- Revert to the current Panorama running
configuration (file named running-config.xml).This operation undoes changes you made to the candidate configuration since the last commit.
- To revert all the changes that all administrators made, perform one of the following steps:
- Select PanoramaSetupOperations, Revert to running Panorama configuration, and click Yes to confirm the operation.
- Log in to Panorama with an administrative account that is assigned the Superuser role or an Admin Role profile with the Commit For Other Admins privilege enabled. Then select ConfigRevert Changes, select Revert All Changes, and Revert.
- To revert only specific changes to the candidate configuration:
- Log in to Panorama with an administrative account that has the role privileges required to revert the desired changes.The privileges that control commit operations also control revert operations.
- Select ConfigRevert Changes.
- Select Revert Changes Made By.
- To filter the Revert Scope by administrator, click <administrator-name>, select the administrators, and click OK.
- To filter the Revert Scope by location, clear any locations that you want to exclude.
- Revert the changes.
- To revert specific device group, template, or template stack changes to the running configuration:
- Select PanoramaSetupOperations, Revert to running Panorama configuration, and Select Device Group & Templates.
- Select the specific device groups, templates, or template stacks to revert.
- Click OK to confirm the operation.
- (Optional) Select CommitCommit to Panorama and Commit your changes to overwrite the running configuration.
- Revert to the default snapshot (.snapshots.xml)
of the Panorama candidate configuration.
- To revert all the changes that all administrators made:
- Select PanoramaSetupOperations and Revert to last saved Panorama configuration.
- Click Yes to confirm the operation.
- (Optional) Select CommitCommit to Panorama and Commit your changes to overwrite the running configuration with the snapshot.
- To revert specific device group, template, or template stack changes to the running configuration:
- Select PanoramaSetupOperations, Revert to last saved Panorama configuration, and Select Device Group & Templates.
- Select the specific device groups, templates, or template stacks to revert.
- Click OK to confirm the operation.
- (Optional) To overwrite the running configuration, select CommitCommit to Panorama and Commit your changes with the snapshot.
- Revert to a previous version of the running configuration
that is stored on Panorama.
- To revert all changes that administrators made:
- Select PanoramaSetupOperations, Load Panorama configuration version, and Select Device Group & Templates.
- Select a configuration Version and click OK.
- (Optional) To overwrite the running configuration with the version you just restored, select CommitCommit to Panorama and Commit your changes.
- To revert specific device group, template, or template changes to the running configuration:
- Select PanoramaSetupOperations, Load Panorama configuration version, and select a configuration version Name.
- Select Device Group & Templates and select the specific device groups, templates, or template stacks to revert.
- Click OK to confirm the operation.
- (Optional) To overwrite the running configuration with the snapshot, select CommitCommit to Panorama and Commit your changes.
- Revert to one of the following:
- Custom-named version of the Panorama running configuration that you previously imported.
- Custom-named Panorama candidate configuration snapshot (instead of the default snapshot).
- Select PanoramaSetupOperations, Load named Panorama configuration snapshot, and select the Name of the configuration file you just imported.
- (Optional) Load Shared Objects or Load Shared Policies to load all shared objects or policies. You can load all shared objects and policies, as well as load all objects and policies configured in the device groups and templates you specify in the next step.
- (Optional) Select Device Group & Templates, and select the specific device group, template, or template stack configurations to load. Skip this step if you want to revert the entire Panorama configuration.
- Click OK to confirm the operation.
- (Optional) To overwrite the running configuration with the snapshot, select CommitCommit to Panorama and Commit your changes.
- Restore a Panorama running or candidate configuration
that you previously exported to an external host.
- Select PanoramaSetupOperations, Import named Panorama configuration snapshot, Browse to the configuration file on the external host, and click OK.
- Load named Panorama configuration snapshot and select the Name of the configuration file you just imported.
- (Optional) Load Shared Objects or Load Shared Policies to load all shared objects or policies. You can load all shared objects and policies, as well as load all objects and or policies configured in the device groups and templates you specify in the next step.
- (Optional) Select Device Group & Templates and select the specific device group, template, or template stack configurations to load. Skip this step if you want to revert the entire Panorama configuration.
- Click OK to confirm the operation.
- (Optional) To overwrite the running configuration with the snapshot you just imported, select CommitCommit to Panorama and Commit your changes.