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.
  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. 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.
  2. (
    Legacy mode only
    ) On the old Panorama virtual appliance, change to Panorama mode.
    This step is required to preserve the log settings (
    Panorama
    Log 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.
    1. Migrate Panorama Logs to the New Log Format if you want to preserve the existing log data on the old Panorama virtual appliance.
  3. Export the Panorama configuration from the old Panorama virtual appliance.
    1. Select
      Panorama
      Setup
      Operations
      .
    2. 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.
    3. 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
      .
  4. 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.
    1. Log in to the Panorama web interface of the old Panorama virtual appliance.
    2. In the
      Dashboard
      , copy the
      Serial #
      of the old Panorama virtual appliance located in the General Information widget.
    3. Log in to the Panorama web interface of the new Panorama virtual appliance.
    4. Add the serial number of the old Panorama virtual appliance to the new Panorama virtual appliance.
      1. Select
        Panorama
        Setup
        Management
        and edit the General Settings.
      2. Enter (paste) the
        Serial Number
        and click
        OK
        .
      3. Select
        Commit
        and
        Commit to Panorama
        .
  5. 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. (
      For maintaining access to the old Panorama virtual appliance only
      ) Register Panorama.
    3. (
      For maintaining access to the old Panorama virtual appliance only
      ) Activate a Panorama Support License.
    4. (
      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.
    5. 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.
    6. Select
      Panorama
      Plugins
      and install all plugins that were installed on the old Panorama virtual appliance.
  6. 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.
  7. (
    Prisma Access
    ) Transfer the Prisma Access license from the old Panorama virtual appliance to the new Panorama virtual appliance.
  8. 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.
    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.
  9. 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.
    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
      .
    4. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
  10. 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. 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.
    2. Configure a Managed Collector that is local to the Panorama virtual appliance.
    3. Configure a Collector Group for the default managed collector.
    4. Select
      Commit
      Commit to Panorama
      and
      Commit
      your changes to the Panorama configuration.
  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.

Recommended For You