Migrate from an M-100 Appliance to an M-500 Appliance
|
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, and Firewall 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 appliances.
|
|
Migrate your subscriptions to the new appliance.
|
Purchase the new support license and migration license.
Provide your sales representative the serial number of the M-100 appliance you will phase out, the auth code you received when you purchased the M-500 appliance, and the effective date for the migration. On the effective date, Palo Alto Networks will automatically apply the auth code to the serial number of the M-500 appliance, phase out support for the M-100 appliance, and trigger support for the M-500 appliance. Consult your sales representative regarding how much time is available to complete the migration after the effective date. At the end of that period, Palo Alto Networks terminates the support entitlement on the M-100 appliance; it can no longer receive software or content updates.
|
|
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
Panorama > Setup > Operations.
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
Panorama > Setup > Operations, 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
Panorama > Setup > Operations.
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.
Click
Commit
and
Validate Changes. Resolve any errors before proceeding.
Click
Commit, for the
Commit Type
select
Panorama, and click
Commit
again.
|
|
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
Panorama > Managed 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.
Click
Commit, for the
Commit Type
select
Device Group, select every device group, select the
Include Device and Network Templates
check box, and click
Commit
again.
In the
Panorama > Managed Devices
page, verify that the Shared Policy and Template columns display
In sync
for the firewalls.
|
