Migrate from a Panorama Virtual Appliance to an M-Series
You can migrate the Panorama configuration from a Panorama virtual appliance to an M-Series appliance in Panorama mode. However, you cannot migrate the logs because the log format on the Panorama virtual appliance is incompatible with that on M-Series appliances. Therefore, if you want to maintain access to the old logs stored on the Panorama virtual appliance, you must continue running the Panorama virtual appliance after the migration. The M-Series appliance will collect the new logs that firewalls forward after the migration. After the pre-migration logs expire or become irrelevant due to aging, you can shut down the Panorama virtual appliance.
Legacy mode is no longer supported in PAN-OS 8.1 or later releases. If the old Panorama virtual appliance is in Legacy mode, you must change Panorama to Panorama mode before migrating to the new hypervisor in order to preserve the log settings and Log Collector forwarding configurations. Importing the configuration of the old Panorama in Legacy mode to a new Panorama in Panorama mode causes all log and log forwarding settings to be removed.
You cannot migrate logs between hypervisors. Therefore, if you want to maintain access to the logs stored on the old Panorama virtual appliance, you must continue running the old Panorama virtual appliance after the migration and add it as a managed Log Collector on the new Panorama virtual appliance. This allows the new Panorama virtual appliance to collect the new logs that firewalls forward after the migration, while maintaining access to the old log data. After the pre-migration logs expire or become irrelevant due to aging, you can shut down the Panorama virtual appliance.
If you store firewall logs on Dedicated Log Collectors (M-Series appliances in Log Collector mode) instead of on the Panorama virtual appliance, you can maintain access to the logs by migrating the Dedicated Log Collectors to the M-Series appliance in Panorama mode.
- Plan the migration.
- Upgrade the software on the Panorama virtual appliance before the migration if the M-Series appliance requires a later release of the current software (the M-500 appliance requires Panorama 7.0 or a later release. The M-600 and M-200 appliances require Panorama 8.1 or later release). 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 Panorama virtual appliance goes offline and then forward the logs after the M-Series 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.
- Consider whether to maintain access to the Panorama virtual appliance after the migration to access existing logs. The most efficient approach is to assign a new IP address to the Panorama virtual appliance and reuse its old IP address for the M-Series appliance. This ensures that the Panorama virtual appliance remains accessible and that firewalls can point to the M-Series appliance without you reconfiguring the Panorama IP address on each firewall.
- Purchase the new M-Series appliance, and migrate your subscriptions to the new appliance.
- Purchase the new M-Series appliance.
- Purchase the new support license and migration license.
- At the time you purchase the new M-Series appliance, provide your sales representative the serial number and device management auth-code of the Panorama virtual appliance you are phasing out, as well as a license migration date of your choosing. On receipt of your M-Series 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 Panorama virtual appliance is decommissioned, and you can no longer manage devices or collect logs using the Panorama virtual 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 Panorama virtual appliance.
- (Legacy mode only) On the old Panorama virtual appliance, change to Panorama mode.This step is required to preserve the log data, settings and log forwarding configuration of the Panorama virtual appliance. If you export the Panorama configuration while in Legacy mode, these settings are lost. You must complete Step 9 if you do not change Panorama to Panorama mode before continuing.Continue to the next step if the Panorama virtual appliance is already in Panorama or Management Only mode.
- Migrate Panorama Logs to the New Log Format if you want to preserve the existing log data on the old Panorama virtual appliance.
- Export the Panorama configuration from the Panorama virtual appliance.
- Log in to the Panorama virtual 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 the Panorama virtual appliance if you won’t need to access to it after the migration or assign a new IP address to its management (MGT) interface if you will need access to it.To power off the Panorama virtual appliance, see the documentation for your VMware product.To change the IP address on the Panorama virtual appliance:
- Select, and edit the Management Interface Settings.PanoramaSetupManagement
- Enter the newIP Addressand clickOK.
- SelectandCommitCommit to PanoramaCommityour changes.
- Perform the initial setup of the M-Series appliance.
- Rack mount the M-Series appliance. Refer to the M-Series 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/Retrieve a Firewall Management License on the M-Series Appliance. Use the auth-code associated with the migration license.
- Install Content and Software Updates for Panorama. Install the same versions as those on the Panorama virtual appliance.
- Load the Panorama configuration snapshot that you exported from the Panorama virtual appliance into the M-Series 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.
- On the M-Series appliance, select.PanoramaSetupOperations
- ClickImport named Panorama configuration snapshot,Browseto the Panorama configuration file you exported from the Panorama virtual 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.
- Modify the configuration on the M-Series appliance.Required if the M-Series appliance will use different values than the Panorama virtual appliance. If you will maintain access to the Panorama virtual appliance to access its logs, use a different hostname and IP address for the M-Series appliance.
- Edit the General Settings, modify theHostname, and clickOK.
- Edit the Management Interface Settings, modify the values as necessary, and clickOK.
- Add the default managed collector and Collector Group back to the M-Series appliance.
- Synchronize the M-Series appliance with the firewalls to resume firewall management.Complete this step during a maintenance window to minimize network disruption.
- On the M-Series appliance, selectand 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.
Recommended For You
Recommended videos not found.