: Migrate from an M-600 Appliance to an M-700 Appliance
Focus
Focus

Migrate from an M-600 Appliance to an M-700 Appliance

Table of Contents
End-of-Life (EoL)

Migrate from an M-600 Appliance to an M-700 Appliance

Migrate the Panorama™ management server configuration from an M-600 appliance to an M-700 appliance.
This procedure describes the Panorama configuration migration from an M-600 appliance to an M-700 appliance in Panorama mode. Log migration is not supported. The M-600 appliance logging disk form factor is not supported on the M-600 and M-700 appliances.
This procedure assumes you are no longer using the M-600 appliance for device management or log collection. If you intend to continue using the M-600 appliance as log collector, you must get a device management license for the M-600 appliance. Without a device management license, you cannot use the M-600 appliance as a log collector.
You can continue to access the existing log data at a later date if you do not plan to use the M-600 appliance as a log collector. After you successfully migrate to the new M-700 appliance, power on the M-600 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-600 appliance.
Policy rule usage data is not preserved when you migrate to a different Panorama model. This indicates that all the existing policy rule usage data from the old Panorama model is no longer displayed after you migrate 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.
    • Upgrade the M-600 appliance to the latest software and content version.
    • Install the latest software and content versions on the M-700 appliance. Both the M-600 and M-700 appliances must run on the same PAN-OS version. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
    • Ensure that both the M-600 and M-700 appliances are on the same system mode.
    • Schedule a maintenance window for the migration. Firewalls can buffer logs after the M-600 appliance goes offline and then forward the logs after the M-700 appliance comes online. However, completing the migration during a maintenance window ensures that the logs do not exceed the buffer capacities and are not lost during the transition between Panorama models.
  2. Purchase the new M-700 appliance, and migrate your subscriptions to the new appliance.
    1. Purchase the new M-700 appliance.
    2. Purchase the new support license and migration license.
    3. When purchasing the new M-700 appliance, provide your sales representative with the serial number and device management auth-code of the M-700 appliance that you are phasing out, and the date when you expect your migration. After you receive the M-700 appliance, register it and activate the device management and support licenses by using the migration and support auth-codes from Palo Alto Networks. On the migration date, the device management license on the M-600 will be decommissioned, preventing you from managing devices or collecting logs using the M-600 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 will not be able to commit any configuration changes on the decommissioned M-600 appliance. Palo Alto Networks allows up to a 90 day migration grace period when migrating between M-Series appliances. Contact your Palo Alto Networks sales representative for more information about your migration.
  3. Export the Panorama configuration from the M-600 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. Perform the initial setup of the M-700 appliance.
    1. Rack mount the M-700 appliances. For more information, refer to the M-300 and M-700 Appliance Hardware Reference guide.
    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-600 appliance.
  5. Load the Panorama configuration snapshot that you exported from the M-600 appliance into the M-700 Panorama mode.
    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. Log in to the Panorama web interface of the M-700 appliance.
    2. Select PanoramaSetupOperations.
    3. Click Import named Panorama configuration snapshot.
    4. Browse for the configuration file you exported from the M-600 appliance, and click OK.
    5. Click Load named Panorama configuration snapshot, and select the Name of the configuration you just imported.
    6. Select a Decryption Key (the master key for Panorama) and click OK.
    7. Panorama overwrites its current candidate configuration with the loaded configuration. Panorama displays any errors that occur when loading the configuration file. If errors occur, save the errors to a local file. Resolve each error to ensure the migrated configuration is valid.
  6. Review the network configuration on the M-700 appliance.
    1. (Optional) Log in to the Panorama web interface of the M-600 appliance, select PanoramaSetupOperations, and click Shutdown Panorama.
      Shut down the M-600 appliance if you plan to have the same IP address on both the M-600 and M-700 appliances.
    2. Log in to the Panorama web interface of the M-700 appliance, select PanoramaSetupInterfaces, and verify the network configuration on the Management interface to ensure that the connectivity to the M-700 appliance is not disrupted post commit.
    3. Ensure that all the interface configurations are set up based on your requirements for the M-700 appliance.
  7. Select CommitCommit to PanoramaValidate Commit to review and resolve any configuration issues. Commit the Panorama configuration.
  8. Generate a new device registration authentication key for managed device connectivity.
    1. In the Panorama web interface of the M-700 appliance, select PanoramaDevice Registration Auth Key and Add a new authentication key.
    2. Configure the authentication key.
      • Name—Enter a descriptive name for the authentication key.
      • Lifetime—Enter the key lifetime to specify the duration of the validity of the authentication key.
      • Count—Enter the number of devices that will use the authentication key for connecting to Panorama.
      • Device Type—Specify whether the authentication key may be used for Firewalls, Log Collectors, or Any device.
    3. Click OK.
    4. Copy Auth Key and Close.
  9. After you complete the migration, connectivity to the managed firewalls is lost. Recover connectivity to the managed firewalls.
    1. (Optional) If the IP address of the M-700 appliance is different from the M-600 appliance, update the panorama-server IP address.
      admin> configure admin# set deviceconfig system panorama local-panorama panorama-server <panorama-ip> [panorama-server-2 <panorama-ha-peer-ip>] admin# commit admin# exit
    2. Reset the secure connection state.
      This command resets the managed device connection to Panorama and is irreversible.
      admin> request sc3 reset
    3. Restart the management server on the managed device.
      admin> debug software restart process management-server
    4. Add the device registration authentication key you copied in Step 8.
      admin> request authkey set <auth_key>
    5. Verify the managed device connectivity to Panorama.
      admin> show panorama-status
      Verify that the IP address of the M-700 appliance appears and the Panorama server Connected status displays yes.
  10. After you complete the migration, connectivity to the managed log collectors is lost. Recover connectivity to the managed log collectors.
    1. (Optional) If the IP address of the M-700 appliance is different from the M-600 appliance, update the panorama-server IP address.
      admin> configure admin # set deviceconfig system panorama-server <panorama-ip> [panorama-server-2 <panorama-ha-peer-ip>] admin# Commit admin# exit
    2. Reset the secure connection state.
      This command resets the managed device connection to Panorama and is irreversible.
      admin> request sc3 reset
    3. Restart the management server on the managed device.
      admin> debug software restart process management-server
    4. Add the device registration authentication key you copied in Step 8.
      admin> request authkey set <auth_key>
    5. Verify the managed device connectivity to Panorama.
      admin> show panorama-status
      Verify that the IP address of the M-700 appliance appears and the Panorama server Connected status displays yes.
  11. Select CommitCommit to PanoramaValidate Commit to review and resolve any configuration issues. Commit the Panorama configuration.
  12. Synchronize the M-700 appliance with the managed devices.
    1. Select CommitPush to Devices and Edit Selections.
    2. Select all the devices under Device Groups, Templates, and Collector Groups, and click OK.
    3. Push your changes.
    4. Select PanoramaManaged DevicesSummary, and verify that all the firewalls are connected. Also, verify that the shared policy and template configurations of the firewalls are In sync with Panorama.
    5. Select PanoramaManaged Collectors, and verify that the configuration status is In Sync with Panorama, and the health status is Green for all the log collectors.