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 Interface Support and Logging Rates on 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 between hypervisors. 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 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.
  1. 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. Panorama on AWS and Microsoft Azure require 8.1 or later release, Google Cloud Platform (GCP) requires 8.1.1 or later release, KVM and AWS GovCloud require 8.1.2 or later release, and Hyper-V requires 8.1.3 or later release. 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.
  2. Purchase the new Panorama virtual appliance license, and migrate your subscriptions to the virtual appliance.
    1. Purchase the new Panorama virtual appliance license.
    2. Purchase the new support license and migration license.
    3. At the time you purchase the new Panorama virtual appliance license, provide your sales representative the serial number and device management auth-code of the Panorama virtual appliance you are phasing out, as well as a license migration date of your choosing. After deploying the new Panorama virtual appliance, register the appliance and activate the device management and support licenses using the migration and support auth-codes provided by Palo Alto Networks. On the migration date, the device management license on the old Panorama virtual appliance is decommissioned, and you can no longer manage devices or collect logs using the old Panorama virtual appliance. However, the support license is preserved and the Panorama appliance remains under support. You can complete the migration after the effective date, but you are unable to commit any configuration changes on the now decommissioned Panorama virtual appliance.
  3. (
    Legacy mode only
    ) On the old Panorama virtual appliance, change to Panorama mode.
    This step is required to preserve the log data, settings and log forwarding configuration of the Panorama virtual appliance. If you export the Panorama configuration while in Legacy mode, these settings are lost. You must complete Step 10 if you do not change Panorama to Panorama mode before continuing.
    Continue to the next step if the Panorama virtual appliance is already in Panorama mode.
    1. Migrate Panorama Logs to the New Log Format if you want to preserve the existing log data on the old Panorama virtual appliance.
  4. Export the Panorama configuration from the old Panorama virtual appliance.
    1. Select
      Panorama
      Setup
      Operations
      .
    2. Click
      Save named Panorama configuration snapshot
      , enter a
      Name
      to identify the configuration, and click
      OK
      .
    3. Click
      Export named Panorama configuration snapshot
      , select the
      Name
      of the configuration you just saved, and click
      OK
      . Panorama exports the configuration to your client system as an XML file.
  5. 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:
    1. On the web interface of the old Panorama virtual appliance, select
      Panorama
      Setup
      Management
      , and edit the Management Interface Settings.
    2. Enter the new
      IP Address
      and click
      OK
      .
    3. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes.
  6. Perform the initial setup of the new Panorama virtual appliance.
    1. Perform Initial Configuration of the Panorama Virtual Appliance to define the network connections required to activate licenses and install updates.
    2. Install Content and Software Updates for Panorama. Install the same versions as those on the old Panorama virtual appliance.
  7. Load the Panorama configuration snapshot that you exported from the old Panorama virtual appliance into the new Panorama virtual appliance.
    1. Log in to the Panorama Web Interface of the new Panorama virtual appliance.
    2. Select
      Panorama
      Setup
      Operations
      .
    3. Click
      Import named Panorama configuration snapshot
      ,
      Browse
      to the Panorama configuration file you exported from the Panorama virtual appliance, and click
      OK
      .
    4. 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.
    5. If errors occurred, save them to a local file. Resolve each error to ensure the migrated configuration is valid.
  8. 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.
    Multiple interface configurations are not supported for Panorama deployed on AWS, AWS GovCloud, Microsoft Azure, and GCP. You must reconfigure device management, log collection, Collector Group communication, licensing and software updates to operate over the MGT interface if migrating to one of these hypervisors.
    1. Select
      Panorama
      Setup
      Management
      .
    2. Edit the General Settings, modify the
      Hostname
      , and click
      OK
      .
    3. Edit the Management Interface Settings, modify the values as necessary, and click
      OK
      .
  9. 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.
    1. Configure a Managed Collector that is local to the Panorama virtual appliance.
    2. Configure a Collector Group for the default managed collector.
    3. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
  10. (
    Legacy mode only
    ) If you exported the Panorama configuration from a Panorama virtual appliance in Legacy mode, Configure Log Forwarding to Panorama.
  11. Synchronize the new Panorama virtual appliance with the firewalls to resume firewall management.
    Complete this step during a maintenance window to minimize network disruption.
    1. On the new Panorama virtual appliance, select
      Panorama
      Managed 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.
    2. Push your changes to device groups and templates:
      1. Select
        Commit
        Push to Devices
        and
        Edit Selections
        .
      2. Select
        Device Groups
        , select every device group,
        Include Device and Network Templates
        , and click
        OK
        .
      3. Push
        your changes.
    3. In the
      Panorama
      Managed Devices
      page, verify that the Shared Policy and Template columns display
      In sync
      for the firewalls.

Related Documentation