Migrate from an M-100 Appliance to an M-500 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 Appliance to an M-500 Appliance
You can migrate the Panorama configuration
and firewall logs from an M-100 appliance to an M-500 appliance
in Panorama mode (Panorama management server). You can also migrate
the firewall logs from an M-100 appliance to an M-500 appliance
in Log Collector mode (Dedicated Log Collector). Because all the
Log Collectors in a Collector Group must be the same Panorama model,
you must migrate all or none of the M-100 appliances in any Collector
Group.
In the following procedure, the Panorama management
server is deployed in an active/passive high availability (HA) configuration,
you will migrate both the configuration and logs, and the M-500
appliances will reuse the IP addresses from the M-100 appliances.
This procedure assumes you are no longer
using the M-100 for device management or log collection. If you
plan on using the decommissioned M-100 appliance as a Dedicated
Log Collector, a device management license is required on the M-100.
Without a device management license, you are unable to use the M-100 as
a Dedicated Log Collector.
If you do not plan on using the
M-100 appliance as a Dedicated Log Collector, but the M-100 appliance
contains log data that you must access at a later date, you may still
query and generate reports using the existing log data. Palo Alto
Networks recommends reviewing the log retention policy before decommissioning
the M-100 appliance.
If you will
migrate only the logs and not the Panorama configuration, perform the
task Migrate
Logs to a New M-Series Appliance in Log Collector Mode or Migrate
Logs to a New M-Series Appliance in Panorama Mode.
If
you will migrate to a new Panorama management server that is not
deployed in an HA configuration and the new Panorama must access
logs on existing Dedicated Log Collectors, perform the task Migrate
Log Collectors after Failure/RMA of Non-HA Panorama.
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 appliance if its current release is earlier than 7.0; the M-500 appliance requires Panorama 7.0 or a later release. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
- Forward the System and Config logs that Panorama and Log Collectors generate to an external destination before the migration if you want to preserve those logs. The M-Series appliance in Panorama mode stores these log types on its SSD, which you cannot move between models. You can move only the RAID drives, which store firewall logs.
- Schedule a maintenance window for the migration. Although firewalls can buffer logs after the M-100 appliance goes offline and then forward the logs after the M-500 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-500 appliance, and migrate your subscriptions to the new appliance.
- Purchase the new M-500 appliance.
- Purchase the new support license and migration license.
- At the time you purchase the new M-500 appliance, provide your sales representative the serial number and device management auth-code of the M-100 appliance you are phasing out, as well as a license migration date of your choosing. On receipt of your M-500 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 is decommissioned, and you can no longer manage devices or collect logs using the M-100 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 appliance.
- Export the Panorama configuration from each M-100 appliance in Panorama mode.Perform this task on each M-100 appliance HA peer:
- Log in to the M-100 appliance and 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.
- Power off each M-100 appliance in Panorama mode.
- Log in to the M-100 appliance HA peer that you will power off.
- Select, and clickPanoramaSetupOperationsShutdown Panorama.
- Perform the initial setup of each M-500 appliance.
- Rack mount the M-500 appliances. Refer to the M-500 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.
- 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 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 appliance into each M-500 appliance in Panorama mode (both HA peers).The PanoramaPolicyruleCreationandModifieddates 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.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.Perform this task on each M-500 appliance HA peer:
- Log in to the M-500 appliance and select.PanoramaSetupOperations
- ClickImport named Panorama configuration snapshot,Browseto the configuration file you exported from the M-100 appliance that has the same HA priority (primary or secondary) as the M-500 appliance will have, and clickOK.
- ClickLoad named Panorama configuration snapshot, select theNameof the configuration you just imported, select aDecryption Key(the master key for Panorama), and clickOK. 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-500 appliance HA peers in Panorama mode.
- On the active M-500 appliance, select theDashboardtab and, in the High Availability widget, clickSync to peer.
- In the High Availability widget, verify that theLocal(primary M-500 appliance) isactive, thePeeris passive, and theRunning Configissynchronized.
- Move the RAID drives from each M-100 appliance to its replacement M-500 appliance to migrate the logs collected from firewalls.In the following tasks, skip any steps that you already completed on the M-500 appliance.
- Migrate Logs to a New M-Series Appliance in Panorama Mode. Migrate logs from the M-100 appliance only if it uses a default managed collector for log collection.
- 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-500 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-500 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.