Migrate a Firewall to Panorama Management
When you import a firewall configuration,
Panorama automatically creates a template to contain the imported
network and device settings. To contain the imported policies and
objects, Panorama automatically creates one device group for each
firewall or one device group for each virtual system (vsys) in a
multi-vsys firewall.
When you perform the following steps,
Panorama imports the entire firewall configuration. Alternatively,
you can Load
a Partial Firewall Configuration into Panorama.
Panorama
can import configurations from firewalls that run PAN-OS 5.0 or
later releases and can push configurations to those firewalls. The
exception is that Panorama 6.1 and later releases cannot push configurations
to firewalls running PAN-OS 6.0.0 through 6.0.3.
Panorama
can import configurations from firewalls that are already managed
devices but only if they are not already assigned to device groups
or templates.
- Plan the migration.See the checklist in Plan the Transition to Panorama Management.
- Add the firewall as a managed device.
- Log in to Panorama, selectand clickPanoramaManaged DevicesSummaryAdd.
- Enter the serial number of the firewall and clickOK.If you will import multiple firewall configurations, enter the serial number of each one on a separate line. Optionally, you can copy and paste the serial numbers from a Microsoft Excel worksheet.
- SelectandCommitCommit to PanoramaCommityour changes.
- Set up a connection from the firewall to Panorama.
- Log in to the firewall, select, and edit the Panorama Settings.DeviceSetup
- In thePanorama Serversfields, enter the IP addresses of the Panorama management server.
- ClickOKandCommit.
- Import the firewall configuration into Panorama.If you later decide to re-import a firewall configuration, first remove the firewall device groups and template to which it is a member. If the device group and template names are the same as the firewall hostname, then you can delete the device group and template before re-importing the firewall configuration or use theDevice Group Name Prefixfields to define new names for the device group and template created by the re-import. Additionally, firewalls don’t lose logs when you remove them from device groups or templates.
- From Panorama, select, clickPanoramaSetupOperationsImport device configuration to Panorama, and select theDevice.Panorama can’t import a configuration from a firewall that is assigned to an existing device group or template.
- (Optional) Edit theTemplate Name. The default value is the firewall name. You can’t use the name of an existing template or template stack.
- (Optional) Edit theDevice Groupnames. For a multi-vsys firewall, each device group has a vsys name by default, so add a character string as a Device Group Name Prefix for all the device groups. Otherwise, the default value is the firewall name. You can’t use the names of existing device groups.TheImport devices' shared objects into Panorama's shared contextcheck box is selected by default, which means Panorama compares imports objects that belong to the Shared location in the firewall to Shared in Panorama. If an imported object is not in the Shared context of the firewall, it is applied to each device group being imported. If you clear the check box, Panorama copies will not compare imported objects, and apply all shared firewall objects into device groups being imported instead of Shared. This could create duplicate objects, so selecting the check box is a best practice in most cases. To understand the consequences of importing shared or duplicate objects into Panorama, see Plan how to manage shared settings.
- Select aRule Import Locationfor the imported policy rules:Pre RulebaseorPost Rulebase. Regardless of your selection, Panorama imports default security rules (intrazone-default and interzone-default) into the post-rulebase.If Panorama has a rule with the same name as a firewall rule that you import, Panorama displays both rules. Delete one of the rules before performing a Panorama commit to prevent a commit error.
- ClickOK. Panorama displays the import status, result, details about your selections, details about what was imported, and any warnings. ClickClose.
- SelectandCommitCommit to PanoramaCommityour changes.
- Push the configuration from Panorama to the newly added device.To prevent duplicate rule or object names, push the device group configuration from Panorama to the firewall to avoid commit errors.This step is required to successfully migrate firewall management to the Panorama management server. Failure to perform this step successfully causes configuration errors and commit failures.
- Log in to the Panorama Web Interface and selectand clickPanoramaSetupOperationsExport or push device config bundle.
- ClickExport or push device config bundle, select theDevicefrom the drop-down menu, and clickOK.
- Select theDevicefrom which you imported the configuration, clickOK, and clickPush & Commit. Panorama pushes the bundle and initiates a commit on the firewall.
- ClickCloseafter the push has committed successfully.
- Launch the Web Interface of the firewall and ensure that the configuration has been successfully committed. If not,Committhe changes locally on the firewall.
- On the Panorama web interface, Select, and verify that the device group and template stack are in sync for the passive firewall. Verify policy rules, objects and network settings on the passive firewall match the active firewall. On the firewall web interface, verify that configuration objects display a green cog (PanoramaManaged DevicesSummary
), signifying that the configuration object is pushed from Panorama.
- SelectandCommitCommit to PanoramaCommityour changes.
- Fine-tune the imported configuration.
- In Panorama, select, select thePanoramaConfig AuditRunning configandCandidate configfor the comparison, clickGo, and review the output.
- Update the device group and template configurations as needed based on the configuration audit and any warnings that Panorama displayed after the import. For example:
- Delete redundant objects and policy rules.
- Move firewalls to different device groups or templates.
- Move a device group that Panorama created during the import to a different parent device group: Select, select the device group you want to move, select a newPanoramaDevice GroupsParent Device Group, and clickOK.
- Push the firewall configuration bundle to the firewall to remove all policy rules and objects from its local configuration.This step is necessary to prevent duplicate rule or object names, which would cause commit errors when you push the device group configuration from Panorama to the firewall in the next step.
- In Panorama, selectandCommitCommit to PanoramaCommityour changes.
- Selectand clickPanoramaSetupOperationsExport or push device config bundle.
- Select theDevicefrom which you imported the configuration, clickOK, and clickPush & Commit. Panorama pushes the bundle and initiates a commit on the firewall.
- Push the device group and template configurations to complete the transition to centralized management.If you are migrating multiple firewalls, perform all the preceding steps—including this one—for each firewall before continuing.
- SelectandCommitCommit and PushEdit Selectionsin the Push Scope.
- SelectDevice Groupsand select the device groups that contain the imported firewall configurations.
- SelectMerge with Device Candidate Config,Include Device and Network Templates, andForce Template Values.
- ClickOKto save your changes to the Push Scope.
- Commit and Pushyour changes.
- Consolidate all the imported firewall configurations.This step is required if you are migrating multiple firewalls.
- After importing all the firewall configurations, update the device groups and templates as needed to eliminate redundancy and streamline configuration management: see Fine-tune the imported configuration. (You don’t need to push firewall configuration bundles again.)
- Configure any firewall-specific settings.If the firewalls will have local zones, you must create them before performing a device group or template commit; Panorama can’t poll the firewalls for zone name or zone configuration. If you will use local firewall rules, ensure their names are unique (not duplicated in Panorama). If necessary, you can Override a Template or Template Stack Value with a firewall-specific value.
- Commit and push your changes:
- SelectandCommitCommit and PushEdit Selectionsin the Push Scope.
- SelectDevice Groups, select the device groups you changed, andInclude Device and Network Templates.
- ClickOKto save your changes to the Push Scope.
- Commit and Pushyour changes.
- Perform your post-migration test plan.Perform the verification tasks that you devised during the migration planning to confirm that the firewalls work as efficiently with the Panorama-pushed configuration as they did with their original local configuration: see Create a post-migration test plan.
Recommended For You
Recommended Videos
Recommended videos not found.