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
backup (see Revert Panorama Configuration Changes).
Additionally, Panorama allows you to save and export the device
group, template, and template stack configurations that you specify.
This is useful for preserving changes that would otherwise be lost
if a system event or administrator action causes Panorama to reboot.
After rebooting, Panorama automatically reverts to the current version
of the running configuration, which Panorama stores in a file named
running-config.xml
.
Saving backups is also useful if you want to revert to a Panorama configuration
that is earlier than the current running configuration. Panorama
does not automatically save the candidate configuration to persistent
storage. You must manually save the candidate configuration as a
default snapshot file (.snapshot.xml
) or as
a custom-named snapshot file. Panorama stores the snapshot file
locally but you can export it to an external host.You
don’t have to save a configuration backup to revert the changes
made since the last commit or reboot; just select (see Revert Panorama Configuration Changes).
Config
Revert Changes
Palo
Alto Networks recommends that you back up any important configurations
to an external host.
- Save changes to the candidate configuration.
- To overwrite the default snapshot file (.snapshot.xml) with all the changes that all administrators made, perform one of the following steps:
- SelectandPanoramaSetupOperationsSave candidate Panorama configuration.
- Log in to Panorama with an administrative account that is assigned the Superuser role or an Admin Role profile with theSave For Other Adminsprivilege enabled. Then selectat the top of the web interface, selectConfigSave ChangesSave All ChangesandSave.
- To overwrite the default snapshot (.snapshot.xml) with changes made by administrators to specific device group, template, or template stack configurations:
- Select,PanoramaSetupOperationsSave candidate Panorama configuration, andSelect Device Group & Templates.
- Select the specific device groups, templates, or template stacks to revert.
- ClickOKto confirm the operation.
- (Optional) SelectandCommitCommit to PanoramaCommityour changes to overwrite the running configuration with the snapshot.
- To create a snapshot that includes all the changes that all administrators made but without overwriting the default snapshot file:
- SelectandPanoramaSetupOperationsSave named Panorama configuration snapshot.
- Specify theNameof a new or existing configuration file.
- ClickOKandClose.
- To save only specific changes to the candidate configuration without overwriting any part of the default snapshot file:
- Log in to Panorama with an administrative account that has the role privileges required to save the desired changes.
- Selectat the top of the web interface.ConfigSave Changes
- SelectSave Changes Made By.
- To filter the Save Scope by administrator, click<, select the administrators, and clickadministrator-name>OK.
- To filter the Save Scope by location, clear any locations that you want to exclude. The locations can be specific device groups, templates, Collector Groups, Log Collectors, shared settings, or the Panorama management server.
- ClickSave, specify theNameof a new or existing configuration file, and clickOK.
- To save a specific device group, template, or template stack configuration:
- Select,PanoramaSetupOperationsSave named Panorama configuration snapshot, andSelect Device Group & Templates.
- Select the specific device groups, templates, or template stacks to save.
- ClickOKto confirm the operation.
- Export a candidate or running configuration to a host external to Panorama or to a firewall.You can schedule daily exports to an SCP or FTP server (see Schedule Export of Configuration Files) or export configurations on demand. To export on demand, selectand select one of the following options:PanoramaSetupOperations
- Export named Panorama configuration snapshot—Export the current running configuration, a named candidate configuration snapshot, or a previously imported configuration (candidate or running). Panorama exports the configuration as an XML file with theNameyou specify.Select Device Group & Templatesto specify the device group, template, or template stack configurations to export.
- Export Panorama configuration version—Select aVersionof the running configuration to export as an XML file.Select Device Group & Templatesto specify the device group, template, or template stack configurations to export as an XML file.
- Export Panorama and devices config bundle—Generate and export the latest version of the running configuration backup of Panorama and of each managed firewall. To automate the process of creating and exporting the configuration bundle daily to a Secure Copy (SCP) or FTP server, see Schedule Export of Configuration Files.
- Export or push device config bundle—After you import a firewall configuration into Panorama, Panorama creates a firewall configuration bundle named <firewall_name>_import.tgz, in which all local policies and objects are removed. You can thenExport or push device config bundleto perform one of the following actions:
- Push & Committhe configuration bundle to the firewall to remove any local configuration from it, enabling you to manage the firewall from Panorama.
- Exportthe configuration to the firewall without loading it. When you are ready to load the configuration, log in to the firewall CLI and run the configuration mode commandload device-state. This command cleans the firewall in the same way as thePush & Commitoption.
The full procedure to Transition a Firewall to Panorama Management requires additional steps.
Recommended For You
Recommended Videos
Recommended videos not found.