Migrate a Panorama Virtual Appliance to a Different Hypervisor
Table of Contents
11.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 KVM
- Add a Virtual Disk to Panorama on Hyper-V
- 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 KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase the 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
- Install the Device Certificate for a Dedicated Log Collector
-
- 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-500 Appliance to an M-700 Appliance
- Migrate from an M-600 Appliance to an M-700 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 Admin Role Profile for Selective Push to Managed Firewalls
- 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
- Configure Tracking of Administrator Activity
-
- Add a Firewall as a Managed Device
- Change Between Panorama Management and Cloud Management
-
- 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
- Device Group Push to a Multi-VSYS Firewall
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Schedule a Configuration Push to Managed Firewalls
- Redistribute Data to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Configure a Managed Collector
- Monitor Managed Collector Health Status
- Configure Log Forwarding to Panorama
- Configure Syslog Forwarding to External Destinations
- Forward Logs to Strata Logging Service
- Verify Log Forwarding to Panorama
- Modify Log Forwarding and Buffering Defaults
- Configure Log Forwarding from Panorama to External Destinations
-
- 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
-
-
- Preview, Validate, or Commit Configuration Changes
- Commit Selective Configuration Changes for Managed Devices
- Push Selective Configuration Changes to Managed Devices
- 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 Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- View Task Success or Failure Status
- Generate a Stats Dump File for a Managed Firewall
- Recover Managed Device Connectivity to Panorama
- Restore an Expired Device Certificate
End-of-Life (EoL)
Migrate a Panorama Virtual Appliance to a Different Hypervisor
Migrate the Panorama™ virtual appliance configuration
from a supported hypervisor to another supported hypervisor.
Migrate the Panorama configuration of a Panorama
virtual appliance from one supported hypervisor to another supported
hypervisor in Management Only mode or Panorama mode. Before migrating
to the Panorama virtual appliance to a new hypervisor, review the Panorama Models to ensure
that the new hypervisor you are migrating to is supported. Additionally,
if your Panorama configuration has multiple interfaces configuration
for device management includes multiple interfaces for device management,
log collection, Collector Group communication, licensing and software
updates, review Setup Prerequisites for the Panorama Virtual Appliance to verify
that the hypervisor you are migrating to supports multiple interfaces.
Legacy
mode is no longer supported in PAN-OS 8.1 or later releases. If
the old Panorama virtual appliance is in Legacy mode, you must change
Panorama to Panorama mode before migrating to the new hypervisor
in order to preserve the log settings and Log Collector forwarding
configurations. Importing the configuration of the old Panorama
in Legacy mode to a new Panorama in Panorama mode causes all log
and log forwarding settings to be removed.
You cannot migrate
logs from Panorama virtual appliance. Therefore, if you want to maintain
access to the logs stored on the old Panorama virtual appliance,
you must continue running the old Panorama virtual appliance in Log Collector mode after
the migration and add it as a managed Log Collector on the new Panorama
virtual appliance. This allows the new Panorama virtual appliance
to collect the new logs that firewalls forward after the migration,
while maintaining access to the old log data. After the pre-migration
logs expire or become irrelevant due to aging, you can shut down
the Panorama virtual appliance.
If you
store firewall logs on Dedicated Log Collectors (Panorama virtual
appliance in Log Collector mode) instead of on the Panorama virtual
appliance, you can maintain access to the logs by migrating the Dedicated
Log Collectors to the new Panorama virtual appliance in Panorama
mode.
Policy rule usage data is not preserved when you
transition to a different Panorama model. This means that all existing policy
rule usage data from the old Panorama is no longer displayed after a successful
migration to a new Panorama model. After a successful migration, Panorama begins
tracking policy rule usage data based on the date the migration was completed.
For example, the Created date displays the date the
migration was completed.
- Plan the migration.
- Upgrade the software on the Panorama virtual appliance before the migration if the new Panorama virtual appliance requires a later release of the current software. For the minimum PAN-OS version for each hypervisor, see Panorama Hypervisor Support. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
- Schedule a maintenance window for the migration. Although firewalls can buffer logs after the Panorama virtual appliance goes offline and then forward the logs after the new Panorama virtual appliance comes online, completing the migration during a maintenance window minimizes the risk that logs will exceed the buffer capacities and be lost during the transition between hypervisors.
- Consider whether to maintain access to the old Panorama virtual appliance after the migration to access existing logs. The most efficient approach is to assign a new IP address to the old Panorama virtual appliance and reuse its old IP address for the Panorama virtual appliance. This ensures that the old Panorama virtual appliance remains accessible and that firewalls can point to the new Panorama virtual appliance without you reconfiguring the Panorama IP address on each firewall.If you to intend to maintain access to the old Panorama virtual appliance, you must purchase a new device management license and support license for the new Panorama virtual appliance before you can complete the migration successfully.
(Legacy mode only) On the old Panorama virtual appliance, Set up a Panorama Virtual Appliance in Panorama Mode.This step is required to preserve the log settings (PanoramaLog Settings) on the old Panorama virtual appliance. If you export the Panorama configuration while in Legacy mode, these settings are lost.Continue to the next step if the Panorama virtual appliance is already in Panorama or Management Only mode.Export the Panorama configuration from the old Panorama virtual appliance.- Log in to the Panorama Web Interface.Select PanoramaSetupOperations.Click Export named Panorama configuration snapshot, select running-config.xml and click OK. Panorama exports the configuration to your client system as an XML file.Locate the running-config.xml file you exported and rename the XML file. This is required to import the configuration as Panorama does not support importing an XML file with the name running-config.xml.Install the Panorama virtual appliance.Migrate the serial number of the old Panorama virtual appliance to the new Panorama virtual appliance.This step is required to migrate all subscriptions and the device management license tied to the Panorama serial number and only if you intend to shut down the old Panorama virtual appliance. If you do intend on maintaining access to the old Panorama virtual appliance, continue to the next step.You have up to 90 days to shut down the old Panorama virtual appliance. Running multiple Panorama virtual appliances with the same serial number violates the EULA.
- Log in to the Panorama web interface of the old Panorama virtual appliance.In the Dashboard, copy the Serial # of the old Panorama virtual appliance located in the General Information widget.Log in to the Panorama web interface of the new Panorama virtual appliance.Add the serial number of the old Panorama virtual appliance to the new Panorama virtual appliance.
- Select PanoramaSetupManagement and edit the General Settings.
- Enter (paste) the Serial Number and click OK.
- Select Commit and Commit to Panorama.
Perform the initial setup of the new Panorama virtual appliance.- Perform Initial Configuration of the Panorama Virtual Appliance to define the network connections required to activate licenses and install updates.(For maintaining access to the old Panorama virtual appliance only) Register Panorama.(For maintaining access to the old Panorama virtual appliance only) Activate a Panorama Support License.(For maintaining access to the old Panorama virtual appliance only) Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected. Use the auth-code associated with the migration license.Install Content and Software Updates for Panorama. Install the same versions as those on the old Panorama virtual appliance.This step is required before loading configuration from the old Panorama virtual appliance. Ensure that all required content updates are installed to avoid security outages.Select PanoramaPlugins and install all plugins that were installed on the old Panorama virtual appliance.Power off the old Panorama virtual appliance if you won’t need to access to it after the migration or assign a new IP address to its management (MGT) interface if you will need access to it.To power off the Panorama virtual appliance, see the supported documentation for the hypervisor on which the old Panorama virtual appliance has been deployed.To change the IP address on the Panorama virtual appliance:
- On the web interface of the old Panorama virtual appliance, select PanoramaSetupManagement, and edit the Management Interface Settings.Enter the new IP Address and click OK.Select CommitCommit to Panorama and Commit your changes.(Prisma Access) Transfer the Prisma Access license from the old Panorama virtual appliance to the new Panorama virtual appliance.Load the Panorama configuration snapshot that you exported from the old Panorama virtual appliance into the new Panorama virtual appliance.The Panorama Policy rule Creation and Modified dates are updated to reflect the date you commit the imported Panorama configuration on the new Panorama. The universially unique identifier (UUID) for each policy rule persists when you migrate the Panorama configuration.The Creation and Modified for managed firewalls are not impacted when you monitor policy rule usage for a managed firewall because this data is stored locally on the managed firewall and not on Panorama.
- Log in to the Panorama Web Interface of the new Panorama virtual appliance.Select PanoramaSetupOperations.Click Import named Panorama configuration snapshot, Browse to the Panorama configuration file you exported from the Panorama virtual appliance, and click OK.Click Load named Panorama configuration snapshot, select the Name of the configuration you just imported, leave the Decryption Key blank (empty), and click OK. Panorama overwrites its current candidate configuration with the loaded configuration. Panorama displays any errors that occur when loading the configuration file.If errors occurred, save them to a local file. Resolve each error to ensure the migrated configuration is valid.Modify the configuration on the new Panorama virtual appliance.Required if the new Panorama virtual appliance will use different values than the old Panorama virtual appliance. If you will maintain access to the old Panorama virtual appliance to access its logs, use a different hostname and IP address for the new Panorama virtual appliance.
- Select PanoramaSetupManagement.Edit the General Settings, modify the Hostname, and click OK.Edit the Management Interface Settings, modify the values as necessary, and click OK.Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.Add the default managed collector and Collector Group to the new Panorama virtual appliance.Loading the configuration from the old Panorama virtual appliance (Step 7) removes the default managed collector and Collector Group that are predefined on each Panorama virtual appliance in Panorama mode.
- To maintain access to logs stored on the old Panorama virtual appliance, change to Log Collector mode and add the Dedicated Log Collector to the new Panorama virtual appliance.Configure a Managed Collector that is local to the Panorama virtual appliance.Configure a Collector Group for the default managed collector.Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.Recover Managed Device Connectivity to Panorama for managed firewalls and Dedicated Log Collectors added using the device registration authentication key.This is required when transitioning from one Panorama model to another.Synchronize the new Panorama virtual appliance with the firewalls to resume firewall management.Complete this step during a maintenance window to minimize network disruption.
- On the new Panorama virtual appliance, select PanoramaManaged Devices and verify that the Device State column displays Connected for the firewalls.At this point, the Shared Policy (device groups) and Template columns display Out of sync for the firewalls.Push your changes to device groups and templates:
- Select CommitPush to Devices and Edit Selections.
- Select Device Groups, select every device group, Include Device and Network Templates, and click OK.
- Push your changes.
In the PanoramaManaged Devices page, verify that the Shared Policy and Template columns display In sync for the firewalls.After you migrate to a different Panorama model, if there are connectivity issues between Panorama and the managed firewalls, recover the connectivity of the managed devices to Panorama to resolve the issues.