Migrate from a Panorama Virtual Appliance to an M-Series Appliance
|
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). For important details about software versions, see
Panorama, Log Collector, and Firewall 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 appliances.
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.
|
|
Migrate your subscriptions to the new appliance.
|
Purchase the new support license and migration license.
Provide your sales representative the serial number of the Panorama virtual appliance you will phase out, the auth code you received when you purchased the new M-Series 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-Series appliance, phase out support for the Panorama virtual appliance, and trigger support for the M-Series 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 Panorama virtual appliance, after which it can no longer receive software or content updates.
|
|
Export the Panorama configuration from the Panorama virtual appliance.
|
Log in to the Panorama virtual 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 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
Panorama > Setup > Management, and edit the Management Interface Settings.
Enter the new
IP Address
and click
OK.
Click
Commit, for the
Commit Type
select
Panorama, and click
Commit
again.
|
|
Perform the initial setup of the M-Series appliance.
|
Rack mount the M-Series appliance. Refer to the
M-100 or 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/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.
|
On the M-Series appliance, select
Panorama > Setup > Operations.
Click
Import named Panorama configuration snapshot,
Browse
to the Panorama configuration file you exported from the Panorama virtual appliance, 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.
|
|
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.
|
Select
Panorama > Setup > Management.
Edit the General Settings, modify the
Hostname, and click
OK.
Edit the Management Interface Settings, modify the values as necessary, and click
OK.
|
|
Add the
default managed collector and Collector Group
back to the M-Series appliance.
Loading the configuration from the Panorama virtual appliance (
Step 6) removes the default managed collector and Collector Group that are predefined on each M-Series appliance.
|
Configure a Managed Collector
that is local to the M-Series appliance.
Configure a Collector Group
for the default managed collector.
Click
Commit, for the
Commit Type
select
Panorama, and click
Commit
again.
|
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, 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.
|
