If you need to replace an M-Series appliance in Panorama mode (Panorama management server), you can migrate the logs it collected from firewalls by moving its RAID disks to a new M-Series appliance, but only if Panorama is deployed in a high availability (HA) configuration. Moving the disks enables you to recover logs after a system failure on the M-Series appliance or to migrate logs as part of a hardware upgrade (from an M-100 appliance to an M-500 appliance).
This migration procedure covers the following scenarios:
Both Panorama HA peers have managed collectors that belong to a single Collector Group. For details, see Figure: Multiple Default Log Collectors Per Collector Group. Both Panorama HA peers have a managed collector and each is assigned to a separate Collector Group. For details, see Figure: Single Default Log Collector Per Collector Group.
Migrate Logs to a New M-Series Appliance in Panorama Mode
Forward any logs on the SSD of the old M-Series appliance to an external destination if you want to preserve them. The SSD stores only the System and Config logs that Panorama and Log Collectors generate. You cannot move the SSD between M-Series appliances. Configure Log Forwarding from Panorama to External Destinations.
Export the Panorama configuration from the decommissioned M-Series appliance in Panorama mode. Log in to the Panorama 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.
Remove the RAID disks from the old M-Series appliance. Power off the old 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-100 or M-500 Appliance Hardware Reference Guide.
Perform initial setup of the new 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. If the old M-Series appliance used the Eth1 and Eth2 interfaces for log collection and Collector Group communication, you must define those interfaces during initial configuration of the new M-Series appliance ( Panorama > Setup > Management). Register Panorama. Transfer licenses as follows only if the new M-Series appliance is the same hardware model as the old M-Series appliance. Otherwise, you must purchase new licenses. Log in to the Palo Alto Networks Customer Support web site. Select the Assets tab and click the Spares link. Click the Serial Number of the new M-Series appliance. Click Transfer Licenses. Select the old M-Series appliance and click Submit. Activate a Panorama Support License. Activate a firewall management license. If you are migrating from an M-100 appliance to an M-500 appliance, enter the auth-code associated with the migration license. Install Content and Software Updates for Panorama. 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. Set the HA priority. The new M-Series appliance must have the same priority as the HA peer you are replacing.
Load the Panorama configuration snapshot that you exported from the decommissioned M-Series appliance into the new M-Series appliance in Panorama mode. Log in to the new M-Series appliance and select Panorama > Setup > Operations. Click Import named Panorama configuration snapshot, Browse to the configuration file you exported from the decommissioned M-Series 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. Select Commit > Commit to Panorama and Validate Commit. Resolve any errors before proceeding. Commit your changes to the Panorama configuration.
Insert the RAID disks in to the new M-Series appliance. Power off the new M-Series appliance by pressing the Power button until the system shuts down. Insert the disks into the new M-Series appliance. For details, refer to the disk replacement procedure in the M-100 or M-500 Appliance Hardware Reference Guide. The disk carriers of the M-100 appliance are incompatible with those of the M-500 appliance. Therefore, when migrating between these hardware models, you must unscrew each disk from its old carrier and insert the disk in the new carrier before inserting the disk in the new appliance. You must maintain the disk pair association. Although you can place a disk pair from slot A1/A2 on the old appliance into slot B1/B2 on the new appliance, you must keep the disks together in the same slot; otherwise, Panorama might not restore the data successfully. Power on the new M-Series appliance by pressing the Power button.
Copy log file data from the to the new M-Series appliance. Contact Palo Alto Networks Support to copy log file data from the decommissioned M-Series appliance to the new M-Series appliance and restart the mgmtsrvr process.
Prepare the disks for migration. 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. Enable the disk pairs by running the following CLI command for each pair: > request system raid add <slot> force no-format For example: > request system raid add A1 force no-format > request system raid add A2 force no-format The force and no-format arguments are required. The force argument associates the disk pair with the new appliance. The no-format argument 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 Synchronize the configuration of the M-Series appliance HA peers. > request high-availability sync-to-remote running-config
Configure the local Log Collector on the new M-Series appliance. For all steps with commands that require a serial number, you must type the entire serial number; pressing the Tab key won’t complete a partial serial number. Don’t enable the disks on the new M-Series appliance at this point. When you successfully migrate the logs, Panorama automatically enables the disks. Configure the local Log Collector as a managed collector using the Panorama web interface or using the following CLI commands: > configure # set log-collector <log-collector_SN> deviceconfig system hostname <log-collector-hostname> # exit Verify that the local Log Collector is connected to Panorama and that the status of its disk pairs is present/available. > show log-collector serial-number <log-collector_SN> The disk pairs will display as disabled at this stage of the restoration process. Commit your changes to Panorama. Don’t commit the changes to the Collector Group just yet. > configure # commit
Migrate the logs. You must use the Panorama CLI for this step, not the web interface. You must assign the local Log Collector of the new M-Series appliance to the Collector Group that contains the local Log Collector of the old M-Series appliance. Add the new local Log Collector as a member of the Collector Group and commit your changes to Panorama. # set log-collector-group <collector_group_name> logfwd-setting collectors <SN_managed_collector> # commit # exit The old local Log Collector still appears in the list of members, because you didn’t yet delete it from the configuration. For each disk pair, migrate the logs to the new appliance. > request log-migration from <old_LC_serial_number> old-disk-pair <log_disk_pair> to <new_LC_serial_number> new-disk-pair <log_disk_pair> For example: > request log-migration from 003001000010 old-disk-pair A to 00300100038 new-disk-pair A Commit the changes to Panorama. > configure # commit
Reconfigure the Collector Group. Use the web interface to assign the new Log Collector to the firewalls that forward logs ( Panorama > Collector Groups > Device Log Forwarding). Give the new Log Collector the same priority in the firewall preference lists as the old Log Collector. You use the web interface to perform this step because no CLI command can change the priority assignments of firewall preference lists. Delete the old Log Collector from the Collector Group. # delete log-collector-group <group_name> logfwd-setting collectors <old_LC_serial_number> For example: # delete log-collector-group DC-Collector-Group logfwd-setting collectors 003001000010 Delete the old Log Collector from the Panorama configuration and commit your changes to Panorama. # delete log-collector <old_LC_serial_number> # commit # exit Commit the Collector Group changes so that the managed firewalls can send logs to the new Log Collector. > commit-all log-collector-config log-collector-group <collector_group_name> For example: > commit-all log-collector-config log-collector-group DC-Collector-Group

Related Documentation