: Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
Focus
Focus

Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance

Table of Contents

Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance

Migrate the Panorama™ management server configuration from an M-100 or M-500 appliance to an M-200 appliance or M-600 appliance.
This procedure describes the Panorama configuration migration for the following M-Series appliances in Panorama mode (Panorama management server):
  • M-100 appliance to an M-200 or M-600 appliance.
    Log migration is not supported. The M-100 appliance logging disk form factor is not supported on the M-200 and M-600 appliances.
  • M-500 appliance to an M-200 or M-600 appliance.
    Log migration is not supported. The M-500 appliance logging disk form factor is not supported on the M-200 and M-600 appliances.
Additionally, all the Log Collectors in a Collector Group must be the same Panorama model. For example, if you want to add the local Log Collector on the new M-200 appliance to a Collector Group, the target Collector Group must contain only M-200 appliances. The same is true for the local Log Collector for an M-600 appliance.
This procedure assumes you are no longer using the M-100 or M-500 appliance for device management or log collection. If you plan on using the decommissioned M-100 or M-500 appliance as a Dedicated Log Collector, a device management license is required on the M-100 or M-500 appliance. Without a device management license, you are unable to use the M-100 or M-500 as a Dedicated Log Collector.
You may still access existing log data at a later date if you do not plan on using the M-100 or M-500 appliance as a Dedicated Log Collector. After you have successfully migrate to the new M-Series appliance, power on the M-100 or M-500 appliance to query and generate reports from the Panorama web interface of the decommissioned M-Series appliance. Palo Alto Networks recommends reviewing the log retention policy before decommissioning the M-100 or M-500 appliance.
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.
  1. Plan the migration.
  2. Purchase the new M-200 or M-600 appliance, and migrate your subscriptions to the new appliance.
    1. Purchase the new M-200 or M-600 appliance.
    2. Purchase the new support license and migration license.
    3. At the time you purchase the new M-200 or M-600 appliance, provide your sales representative the serial number and device management auth-code of the M-100 or M-500 appliance you are phasing out, as well as a license migration date of your choosing. On receipt of your M-200 or M-600 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 M-100 or M-500 is decommissioned, and you can no longer manage devices or collect logs using the M-100 or M-500 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 M-100 or M-500 appliance.
      Palo Alto Networks allows up to a 90 day migration grace period when migrating between M-Series appliances. Please contact your Palo Alto Networks sales representative for more information regarding your migration.
  3. Export the Panorama configuration from each M-100 or M-500 appliance in Panorama mode.
    (HA configuration) Perform this step on each M-100 or M-500 appliance HA peer. Keep track of the HA priority (Primary or Secondary) of the M-100 or M-500 appliance.
    1. Select PanoramaSetupOperations.
    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.
  4. In the Panorama web interface of the M-100 or M-500 appliance HA peer that you will power off, select PanoramaSetupOperations and Shutdown Panorama.
    (HA configuration) Repeat this step for both M-100 or M-500 appliance HA peers.
  5. Perform the initial setup of the M-200 or M-600 appliance.
    (HA configuration) Repeat this step for both M-200 or M-600 appliance HA peers.
    1. Rack mount the M-500 appliances. Refer to the M-200 and M-600 Appliance Hardware Reference Guide for instructions.
    2. Perform Initial Configuration of the M-Series Appliance to define the network connections required to activate licenses and install updates.
    3. (FIPS-CC only) Retrieve the license key from the license server when migrating from normal mode to FIPS-CC mode.
    4. Activate a firewall management license. 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 M-100 or M-500 appliance.
    6. (Dedicated Log Collector only) Set Up the M-Series Appliance as a Log Collector.
  6. Load the Panorama configuration snapshot that you exported from each M-100 or M-500 appliance into each M-200 or M-600 appliance in Panorama mode.
    (HA configuration) Repeat this step for both M-200 or M-600 appliances HA peers.
    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 universally 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. Select PanoramaSetupOperations.
    2. Click Import named Panorama configuration snapshot.
    3. Browse for the configuration file you exported from the M-100 or M-500 appliance that has the same HA priority (Primary or Secondary) as the M-200 or M-600 appliance will have and click OK.
    4. Load named Panorama configuration snapshot and select the Name of the configuration you just imported.
    5. Select a Decryption Key (the master key for Panorama) and click OK.
    6. 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.
    7. Select CommitCommit to Panorama and Validate Commit. Resolve any errors before proceeding.
    8. Commit your changes to the Panorama configuration.
  7. Synchronize the configuration between the M-200 or M-600 appliance HA peers in Panorama mode.
    1. In the Panorama web interface of the active M-200 or M-600 appliance, select the Dashboard.
    2. In the High Availability widget, click Sync to peer.
    3. In the High Availability widget, verify that the Local (Primary M-200 appliance) is active, the Peer is passive, and the Running Config is synchronized.
  8. 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.
  9. Synchronize the active M-200 or M-600 appliance in Panorama mode with the firewalls to resume firewall management.
    Complete this step during a maintenance window to minimize network disruption.
    1. In the active M-200 or M-600 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.
    2. Push your changes to device groups and templates:
      1. Select CommitPush 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 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.