Migrate from an M-600 Appliance to an M-700 Appliance
Table of Contents
11.1 & Later
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
- Enable SCP Uploads for an Administrator
- 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
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.
- 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.
Purchase the new M-700 appliance, and migrate your subscriptions to the new appliance.- Purchase the new M-700 appliance.Purchase the new support license and migration license.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.Export the Panorama configuration from the M-600 appliance.
- Log in to the Panorama web interface.Select PanoramaSetupOperations.Click Save named Panorama configuration snapshot, enter a Name to identify the configuration, and click OK.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.Perform the initial setup of the M-700 appliance.
- Rack mount the M-700 appliances. For more information, refer to the M-300 and M-700 Appliance Hardware Reference guide.Perform Initial Configuration of the M-Series Appliance to define the network connections required to activate licenses and install updates.Register Panorama.Activate a Panorama Support License.(FIPS-CC only) Retrieve the license key from the license server when migrating from normal mode to FIPS-CC mode.Activate a firewall management license. Use the auth-code associated with the migration license.Install Content and Software Updates for Panorama. Install the same versions as those on the M-600 appliance.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.
- Log in to the Panorama web interface of the M-700 appliance.Select PanoramaSetupOperations.Click Import named Panorama configuration snapshot.Browse for the configuration file you exported from the M-600 appliance, and click OK.Click Load named Panorama configuration snapshot, and select the Name of the configuration you just imported.Select a Decryption Key (the master key for Panorama) 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 occur, save the errors to a local file. Resolve each error to ensure the migrated configuration is valid.Review the network configuration on the M-700 appliance.
- (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.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.Ensure that all the interface configurations are set up based on your requirements for the M-700 appliance.Select CommitCommit to PanoramaValidate Commit to review and resolve any configuration issues. Commit the Panorama configuration.Generate a new device registration authentication key for managed device connectivity.
- In the Panorama web interface of the M-700 appliance, select PanoramaDevice Registration Auth Key and Add a new authentication key.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.
Click OK.Copy Auth Key and Close.After you complete the migration, connectivity to the managed firewalls is lost. Recover connectivity to the managed firewalls.- Log in to the firewall CLI.(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# exitReset the secure connection state.This command resets the managed device connection to Panorama and is irreversible.admin> request sc3 resetRestart the management server on the managed device.admin> debug software restart process management-serverAdd the device registration authentication key you copied in Step 8.admin> request authkey set <auth_key>Verify the managed device connectivity to Panorama.admin> show panorama-statusVerify that the IP address of the M-700 appliance appears and the Panorama server Connected status displays yes.After you complete the migration, connectivity to the managed log collectors is lost. Recover connectivity to the managed log collectors.
- Log in to the Dedicated Log Collector CLI.(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# exitReset the secure connection state.This command resets the managed device connection to Panorama and is irreversible.admin> request sc3 resetRestart the management server on the managed device.admin> debug software restart process management-serverAdd the device registration authentication key you copied in Step 8.admin> request authkey set <auth_key>Verify the managed device connectivity to Panorama.admin> show panorama-statusVerify that the IP address of the M-700 appliance appears and the Panorama server Connected status displays yes.Select CommitCommit to PanoramaValidate Commit to review and resolve any configuration issues. Commit the Panorama configuration.Synchronize the M-700 appliance with the managed devices.
- Select CommitPush to Devices and Edit Selections.Select all the devices under Device Groups, Templates, and Collector Groups, and click OK.Push your changes.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.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.