Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 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-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.- Plan the migration.
- Upgrade the software on the M-100 or M-500 appliance to a supported PAN-OS release. Review the Palo Alto Network Compatibility Matrix for the minimum supported PAN-OS version.See the Palo Alto Networks End-of-Life Summary for a list of currently supported PAN-OS versions. 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 M-100 or M-500 appliance goes offline and then forward the logs after the M-200 or M-600 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 Panorama models.
- Purchase the new M-200 or M-600 appliance, and migrate your subscriptions to the new appliance.
- Purchase the new M-200 or M-600 appliance.
- Purchase the new support license and migration license.
- 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.
- 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.
- Select.PanoramaSetupOperations
- ClickSave named Panorama configuration snapshot, enter aNameto identify the configuration, and clickOK.
- ClickExport named Panorama configuration snapshot, select theNameof the configuration you just saved, and clickOK. Panorama exports the configuration to your client system as an XML file.
- In the Panorama web interface of the M-100 or M-500 appliance HA peer that you will power off, selectandPanoramaSetupOperationsShutdown Panorama.(HA configuration) Repeat this step for both M-100 or M-500 appliance HA peers.
- 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.
- Rack mount the M-500 appliances. Refer to the M-200 and M-600 Appliance Hardware Reference Guide for instructions.
- Perform Initial Configuration of the M-Series Appliance to define the network connections required to activate licenses and install updates.
- (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-100 or M-500 appliance.
- (Dedicated Log Collector only) Set Up the M-Series Appliance as a Log Collector.
- 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 PanoramaPolicyruleCreationandModifieddates 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.TheCreationandModifiedfor 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.
- Select.PanoramaSetupOperations
- ClickImport named Panorama configuration snapshot.
- Browsefor 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 clickOK.
- Load named Panorama configuration snapshotand select theNameof the configuration you just imported.
- 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.
- SelectandCommitCommit to PanoramaValidate Commit. Resolve any errors before proceeding.
- Commityour changes to the Panorama configuration.
- Synchronize the configuration between the M-200 or M-600 appliance HA peers in Panorama mode.
- In the Panorama web interface of the active M-200 or M-600 appliance, select theDashboard.
- In the High Availability widget, clickSync to peer.
- In the High Availability widget, verify that theLocal(Primary M-200 appliance) isactive, thePeeris passive, and theRunning Configissynchronized.
- 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.
- 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.
- In the active M-200 or M-600 appliance, select, and verify that the Device State column displaysPanoramaManaged DevicesConnectedfor the firewalls.At this point, the Shared Policy (device groups) and Template columns displayOut of Syncfor the firewalls.
- Push your changes to device groups and templates:
- SelectandCommitPush to DevicesEdit Selections.
- SelectDevice Groups, select every device group,Include Device and Network Templates, and clickOK.
- Pushyour changes.
- In thepage, verify that the Shared Policy and Template columns displayPanoramaManaged DevicesIn syncfor 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.