Migrate from an M-Series Appliance to a Panorama Virtual 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-Series Appliance to a Panorama Virtual Appliance
Procedure to migrate from an M-Series appliance to a
Panorama virtual appliance on Panorama 10.0.
You can migrate the Panorama
configuration from an M-100, M-200, M-300, M-500, M-600, M-700 appliance
to a Panorama virtual appliance in Panorama mode. However, you cannot
migrate the logs because the log format on the M-Series appliances
is incompatible with that on the Panorama virtual appliances. Therefore,
if you want to maintain access to the old logs stored on the M-Series
appliance, you must continue running the M-Series appliance as a
Dedicated Log Collector after the migration and add it to the Panorama
virtual appliance as a managed collector.
If your Panorama management server is part of a high availability configuration, you must deploy
a second Panorama virtual appliance of the same hypervisor or cloud environment, and
purchase the required device management and support licenses. See Panorama HA
Prerequisites for a full list of HA requirements.
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 M-Series appliance to PAN-OS 11.1 or later release before the migrating to the Panorama virtual appliance. To upgrade Panorama, see Install Content and Software Updates for Panorama. 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-Series appliance goes offline and then forward the logs after the Panorama virtual appliance comes online, completing the migration during a maintenance window minimizes the risk that logs will exceed the buffer capacities during the transition to a different Panorama model.
- Purchase management and support licenses for the new Panorama virtual appliance.
- Contact your sales representative to purchase the new device management and support licenses.
- Provide your sales representative the serial number of the M-Series appliance you to plan phase out, the serial number and support auth code you received when you purchased the new Panorama virtual appliance, and the date when you expect your migration from the old device to the new virtual appliance to be completed. Before the migration date, register the serial number and activate support auth code on the new virtual appliance so that you can begin your migration. The capacity auth code on the old M-Series appliance is automatically removed on the expected migration completion date you provided.
- Perform the initial setup of the Panorama virtual appliance.
- Perform Initial Configuration of the Panorama Virtual Appliance to define the network connections required to activate licenses and install updates.
- Install Content and Software Updates for Panorama. Install the same versions as those on the M-Series appliance.
- Edit the M-Series appliance Panorama interface configuration to only use the management interface.The Panorama virtual appliance supports only the management interface for device management and log collection.
- Log in to the Panorama Web Interface of the M-Series appliance.
- Select.PanoramaSetupManagement
- Edit the General Settings, modify theHostname, and clickOK.
- SelectInterfacesand edit theManagementinterface to enable the required services.
- Disable services for the remaining interfaces.
- Select.CommitCommit to Panorama
- Add the IP address of the new Panorama virtual appliance.On the M-Series appliance, add the Public IP address of the Panorama virtual appliance as the second Panorama Server to manage devices from the new Panorama management server. If the Panorama virtual appliance is deployed on Alibaba Cloud, AWS, Azure, GCP, or OCI, use the public IP address.
- Select.DeviceSetup
- In the Template context drop-down, select the template or template stack containing the Panorama server configuration.
- Edit the Panorama Settings.
- Enter the Panorama virtual appliance public IP address and clickOK.
- Select.CommitCommit and Push
- Export the configuration from the M-Series 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. Save the configuration to a location external to the Panorama appliance.
- Power off the M-Series appliance or assign a new IP address to the management (MGT) interface.If the M-Series appliance is in Panorama mode and has logs stored on the local Log Collector that you need access on the new Panorama virtual appliance, you must change the IP address on the M-Series appliance in order to add it to the Panorama virtual appliance as a managed Log Collector.
- To Power off the M-Series appliance:
- Log in to the Panorama web interface.
- Select, and under Device Operations,PanoramaSetupOperationsShutdown Panorama. ClickYesto confirm the shutdown.
- To change the IP address on the M-Series appliance:
- Log in to the Panorama web interface.
- Select, and edit the Management Interface Settings.PanoramaSetupManagement
- Enter the newIP Addressand clickOK.
- SelectandCommitCommit to PanoramaCommityour changes.
- Load the Panorama configuration snapshot that you exported from the M-Series appliance into the Panorama virtual appliance.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.
- Log in to the Panorama web interface of the Panorama virtual appliance, and select.PanoramaSetupOperations
- ClickImport named Panorama configuration snapshot,Browseto the Panorama configuration file you exported from the M-Series appliance, 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. The configuration has been loaded once the commit is successful. - Change the M-Series appliance to Log Collector mode to preserve existing log data.Logging data is erased if you change to Log Collector mode while the logging disks are still inserted in the M-Series appliance. Logging disks must be removed before changing mode to avoid log data loss.Generating the metadata for each disk pair rebuilds the indexes. Therefore, depending on the data size, this process can take a long time to complete. To expedite the process, you can launch multiple CLI sessions and run the metadata regeneration command in each session to complete the process simultaneously for every pair. For details, see Regenerate Metadata for M-Series Appliance RAID Pairs.
- Remove the RAID disks from the old M-Series appliance.
- Power off the M-Series appliance by pressing the Power button until the system shuts down.
- Remove the disk pairs. For details, refer to the disk replacement procedure in the M-Series Appliance Hardware Reference Guides.
- Power on the M-Series appliance by pressing the Power button.
- Configure anadminsuperuser administrator account.If anadminadministrator account already is already created, continue to the next step.Anadminaccount with superuser privileges must be created before you switch to Log Collector mode or you lose access to the M-Series appliance after switching modes.
- Log in to the Panorama CLI on the old M-Series appliance.
- Switch from Panorama mode to Log Collector mode.
- Switch to Log Collector mode by entering the following command:>request system system-mode logger
- EnterYto confirm the mode change. The M-Series appliance reboots. If the reboot process terminates your terminal emulation software session, reconnect to the M-Series appliance to see the Panorama login prompt.If you see aCMS Loginprompt, this means the Log Collector has not finished rebooting. Press Enter at the prompt without typing a username or password.
- Log back in to the CLI.
- Verify that the switch to Log Collector mode succeeded:>show system info | match system-modeIf the mode change succeeded, the output displays:>system-mode: logger
- Insert the disks back into the old M-Series appliance. For details, refer to the disk replacement procedure in the M-Series Appliance Hardware Reference Guides.You must maintain the disk pair association. Although you can place a disk pair from slot A1/A2 on the into slot B1/B2, you must keep the disks together in the same slot; otherwise, Panorama might not restore the data successfully.
- Enable the disk pairs by running the following CLI command for each pair:>request system raid add<slot>force no-formatFor example:>request system raid add A1 force no-format>request system raid add A2 force no-formatTheforceandno-formatarguments are required. Theforceargument associates the disk pair with the new appliance. Theno-formatargument prevents reformatting of the drives and retains the logs stored on the disks.
- Generate the metadata for each disk pair.>request metadata-regenerate slot<slot_number>For example:>request metadata-regenerate slot 1
- Enable connectivity between the Log Collector and Panorama management server.Enter the following commands at the Log Collector CLI, where<IPaddress1>is for the MGT interface of the solitary (non-HA) or active (HA) Panorama and<IPaddress2>is for the MGT interface of the passive (HA) Panorama, if applicable.>configure#set deviceconfig system panorama-server#<IPaddress1>panorama-server-2<IPaddress2>commit#exit
- 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 Panorama virtual appliance with the firewalls to resume firewall management.Complete this step during a maintenance window to minimize network disruption.
- On the Panorama virtual appliance, selectand verify that the Device State column displays the firewalls asPanoramaManaged DevicesConnected.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, andInclude Device and Network Templates.
- SelectCollector Groups, select every collector group, and clickOK.
- Pushyour changes.
- In thepage, verify that the Shared Policy and Template columns displayPanoramaManaged DevicesIn syncfor the firewalls.
- (HA only)Set up the Panorama HA peer.If the Panorama management servers are in a high availability configuration, perform the steps below on the HA peer.
- (HA only) Modify the Panorama virtual appliance HA peer configuration.
- On an HA peer, Log in to the Panorama Web Interface, selectand edit thePanoramaHigh AvailabilitySetup.
- In thePeer HA IP Addressfield, enter the new IP address of the HA peer and clickOK.
- SelectandCommitCommit to PanoramaCommityour change
- Repeat these steps on the other peer in the HA peer.
- (HA only) Synchronize the Panorama peers.
- Access theDashboardon one of the HA peers and selectto display the HA widget.WidgetsSystemHigh Availability
- Sync to peer, clickYes, and wait for theRunning Configto displaySynchronized.
- Access theDashboardon the remaining HA peer and selectto display the HA widget.WidgetsSystemHigh Availability
- Verify that theRunning ConfigdisplaysSynchronized.
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.