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.
- 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.
- 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.
- Power off each M-100 appliance in Panorama mode.
- Log in to the M-100 appliance HA peer that you will power off.
- Select PanoramaSetupOperations, and click Shutdown 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.
- Register Panorama.
- Activate a Panorama Support License.
- 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).Perform this task on each M-500 appliance HA peer:
- Log in to the M-500 appliance and select PanoramaSetupOperations.
- Click Import named Panorama configuration snapshot, Browse to 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 click OK.
- Click Load named Panorama configuration snapshot, 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 occurred, save them to a local file. Resolve each error to ensure the migrated configuration is valid.
- Select CommitCommit to Panorama and Validate Commit. Resolve any errors before proceeding.
- Commit your 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 the Dashboard tab and, in the High Availability widget, click Sync to peer.
- In the High Availability widget, verify that the Local (primary M-500 appliance) is active, the Peer is passive, and the Running Config is synchronized.
- 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.
- Migrate Logs to a New M-Series Appliance in Log Collector Mode.
- 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 PanoramaManaged Devices,
and verify that the Device State column displays Connected for the
firewalls.At this point, the Shared Policy (device groups) and Template columns display Out of sync for the firewalls.
- Push your changes to device groups and templates:
- Select CommitPush to Devices and Edit Selections.
- Select Device Groups, select every device group, Include Device and Network Templates, and click OK.
- Push your changes.
- In the PanoramaManaged Devices page, verify that the Shared Policy and Template columns display In sync for the firewalls.
- In the active M-500 appliance, select PanoramaManaged Devices, and verify that the Device State column displays Connected for the firewalls.
Transition to a Different Panorama Model
Transition to a Different Panorama Model When your network requirements change (for example, the logging rate increases), you can migrate the Panorama management server and ...
Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
Procedure to migrate logs from a decommissioned M-Series appliance in a HA pair to a new M-Series appliance of a different model. ...
Migrate Logs to a New M-Series Appliance in Panorama Mode
Procedure to migrate logs from a decommissioned M-Series appliance, that is not in a HA pair, to a new M-Series appliance. ...
Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
Procedure to migrate logs from a decommissioned M-Series appliance in a HA pair to a new M-Series appliance of the same model. ...
Migrate from a Panorama Virtual Appliance to an M-Series Ap...
Migrate from a Panorama Virtual Appliance to an M-Series Appliance You can migrate the Panorama configuration from a Panorama virtual appliance to an M-Series appliance ...
Migrate Log Collectors after Failure/RMA of Non-HA Panorama
Migrate Log Collectors after Failure/RMA of Non-HA Panorama If a system failure occurs on a Panorama management server that is not deployed in a high ...
Troubleshoot Log Storage and Connection Issues
Troubleshoot Log Storage and Connection Issues Verify Panorama Port Usage Resolve Zero Log Storage for a Collector Group Replace a Failed Disk on an M-Series ...
Migrate Logs to a New M-Series Appliance in Log Collector M...
Migrate Logs to a New M-Series Appliance in Log Collector Mode If you need to replace an M-600, M-500, M-200 or M-100 appliance in Log ...
Migrate from an M-Series Appliance to a Panorama Virtual Ap...
Procedure to migrate from an M-Series appliance to a Panorama virtual appliance on Panorama 8.0 ...