Save Candidate Configurations
Select ConfigSave Changes at the top right of the firewall or Panorama web interface to save a new snapshot file of the candidate configuration or to overwrite an existing configuration file. If the firewall or Panorama reboots before you commit your changes, you can then revert the candidate configuration to the saved snapshot to restore changes you made after the last commit. To revert to the snapshot, select DeviceSetupOperations and Load named configuration snapshot. If you don’t revert to the snapshot after a reboot, the candidate configuration will be the same as the last committed configuration (the running configuration).
You can filter which configuration changes to save based on administrator or location. The location can be specific virtual systems, shared policies and objects, or shared device and network settings.
You should periodically save your changes so that you don’t lose them if the firewall or Panorama reboots.
Saving your changes to the candidate configuration does not activate those changes; you must Commit Changes to activate them.
The Save Changes dialog displays the options described in the following table:
Save All Changes
Saves all changes for which you have administrative privileges (default). You cannot manually filter the scope of the configuration changes that the firewall saves when you select this option. Instead, the administrator role assigned to the account you used to log in determines the save scope:
If you have implemented access domains, the firewall automatically applies those domains to filter the save scope (see Device > Access Domain). Regardless of your administrative role, the firewall saves only the configuration changes in the access domains assigned to your account.
Save Changes Made By
Filters the scope of the configuration changes the firewall saves. The administrative role assigned to the account you used to log in determines your filtering options:
Filter the save scope as follows:
If you have implemented access domains, the firewall automatically filters the save scope based on those domains (see Device > Access Domain). Regardless of your administrative role and your filtering choices, the save scope includes only the configuration changes in the access domains assigned to your account.
Lists the locations that have changes to save. Whether the list includes all changes or a subset of the changes depends on several factors, as described for the Save All Changes and Save Changes Made By options. The locations can be any of the following:
This column categorizes the locations where the changes were made:
Include in Save
(Partial save only)
Enables you to select the changes you want to save. By default, all changes within the Save Scope are selected. This column displays only after you choose to Save Changes Made By specific administrators.
There might be dependencies that affect the changes you include in a save. For example, if you add an object and another administrator then edits that object, you cannot save the change for the other administrator without also saving your own change.
Group by Location Type
Groups the list of configuration changes in the Save Scope by Location Type.
Enables you to compare the configurations you selected in the Save Scope to the running configuration. The preview window uses color coding to indicate which changes are additions (green), modifications (yellow), or deletions (red).
To help you match the changes to sections of the web interface, you can configure the preview window to display Lines of Context before and after each change. These lines are from the files of the candidate and running configurations that you are comparing.
Because the preview results display in a new window, your browser must allow pop-up windows. If the preview window does not open, refer to your browser documentation for the steps to unblock pop-up windows.
Lists the individual settings for which you are saving changes. The Change Summary list displays the following information for each setting:
Optionally, you can Group By column name (such as Type).
Saves the selected changes to a configuration snapshot file:
Save and Export Firewall Configurations
Save and Export Firewall Configurations Saving a backup of the candidate configuration to persistent storage on the firewall enables you to later revert to that ...
Revert Panorama Configuration Changes
Revert Panorama Configuration Changes Revert operations replace settings in the current candidate configuration with settings from another configuration. Reverting changes is useful when you want ...
Revert Changes Select Config Revert Changes at the top right of the firewall or Panorama web interface to undo changes made to the candidate configuration ...
Revert Firewall Configuration Changes
Revert Firewall Configuration Changes Revert operations replace settings in the current candidate configuration with settings from another configuration. Reverting changes is useful when you want ...
Save and Export Panorama and Firewall Configurations
Save and Export Panorama and Firewall Configurations Saving a backup of the candidate configuration to persistent storage on Panorama enables you to later restore that ...
Commit Changes Click Commit at the top right of the web interface and specify an operation for pending changes to the firewall configuration: commit (activate), ...
Panorama Commit Operations
Panorama Commit Operations Click Commit at the top right of the web interface and select an operation for pending changes to the Panorama configuration and ...
Preview, Validate, or Commit Configuration Changes
Preview, Validate, or Commit Configuration Changes You can perform Panorama Commit, Validation, and Preview Operations on pending changes to the Panorama configuration and then push ...
Commit, Validate, and Preview Firewall Configuration Change...
Commit, Validate, and Preview Firewall Configuration Changes A commit is the process of activating pending changes to the firewall configuration. You can filter pending changes ...