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.
If you need to replace an M-500 or M-100 appliance deployed in high availability (HA) configuration in Panorama mode (Panorama management server) with the same M-Series appliance as the M-Series appliance being replaced, you can migrate the logs it collected from firewalls by moving its RAID disks to the new M-Series appliance. Moving the disks enables you to recover logs after a system failure on the M-Series appliance.
This migration procedure covers the following scenarios:
Panorama HA Peer with Collector Group
Log_Collection_Default_Single_LC.png
  1. 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 the System and Config logs that Panorama and Log Collectors generate. You cannot move the SSD between M-Series appliances.
  2. Remove the RAID disks from the old M-Series appliance.
    1. Power off the old M-Series appliance by pressing the Power button until the system shuts down.
    2. Remove the disk pairs. For details, refer to the disk replacement procedure in the M-100 or M-500 Appliance Hardware Reference Guide.
  3. Perform initial setup of the new M-Series appliance.
    1. Rack mount the M-Series appliance. Refer to the M-100 or M-500 Appliance Hardware Reference Guide for instructions.
    2. Purchase and activate the Panorama support license or transfer licenses as follows only if the new M-Series appliance is the same hardware model as the old M-Series appliance. If the new M-Series appliance is a different model than the old M-Series appliance, you must purchase new licenses.
      1. Select the
        Assets
        tab and click the
        Spares
        link.
      2. Click the Serial Number of the new M-Series appliance.
      3. Click
        Transfer Licenses
        .
      4. Select
        the old M-Series appliance and click
        Submit
        .
    3. 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.
    4. Perform any additional configuration changes as needed.
      If the old M-Series appliance used interfaces other than the MGT interface for Panorama services (such as log collection), you must define those interfaces on the new M-Series appliance (
      Panorama
      Setup
      Interfaces
      ).
    5. Set Up HA on Panorama. The new M-Series appliance must have the same priority as the HA peer you are replacing.
  4. 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.
  5. If the M-Series appliance was part of a Collector Group, verify that the decommissioned M-Series appliance serial number is still part of the correct Collector Group:
    debug log-collector-group show name <Log CollectorGroup name>
    If the decommissioned M-Series appliance serial number is no longer a part of the correct Collector Group, then the Tech Support folders were incorrectly copied in Step 4. Contact Palo Alto Networks Customer Support again to copy the Tech Support folders to the correct location.
  6. 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.
    1. 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.
    2. Generate the metadata for each disk pair.
      >
      request metadata-regenerate slot
      <slot_number>
      For example:
      >
      request metadata-regenerate slot 1
    3. Synchronize the configuration of the M-Series appliance HA peers.
      >
      request high-availability sync-to-remote running-config
  7. 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.
    1. 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
    2. Commit your changes to Panorama. Don’t commit the changes to the Collector Group just yet.
      >
      configure
      #
      commit
    3. 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.
  8. Add a Log Collector with no disks to a Collector Group.
    From this point, only commits that are required to complete the migration process on Panorama and the Log Collectors. Hold off making any other changes.
    1. Overwrite Panorama restriction to allow Log Collector with no disk to be added to a Collector Group:
      requestlog-migration-set-start
  9. Migrate the logs.
    1. 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 haven’t deleted it from the configuration.
    2. 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
    3. Commit the changes to Panorama.
      >
      configure
      #
      commit
  10. Reconfigure the Collector Group.
    1. 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 cannot use the CLI change the priority assignments of firewall preference lists.
    2. 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
    3. Delete the old Log Collector from the Panorama configuration and commit your changes to Panorama.
      #
      delete log-collector
      <old_LC_serial_number>
      #
      commit
      #
      exit
    4. 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
  11. Generate new keys on the new Log Collector.
    This command is required in order to add the new Log Collector to the Collector Group and should only be run for the Collector Group of the Log Collector being replaced. This step deletes the existing RSA keys and allows Panorama to create new RSA keys.
    1. Delete all RSA keys on the new Log Collector:
      request logdb update-collector-group-after-replacecollector-group
      <collector-group-name>
      The process can take up to 10 minutes to completed.
  12. Confirm that SearchEngine Status is Active for all Log Collectors in the Collector Group.
    Do not continue until SearchEngine Status is Active for all Log Collectors in the Collector Group. This will result in purging of logs from the Log Collector being replaced.
    1. Show the Log Collector details by running the following commands either:
      • On Panorama for all Log Collectors:
        show log-collector all
      Alternatively, you can run the following command on each Dedicated Log Collector:
      show log-collector detail
    2. Confirm that SearchEngine Status is Active.
      Redistribution status: none
      Last commit-all: commit succeeded, current ring version 1
      SearchEngine status: Active
      md5sum 4e5055a359f7662fab8f8c4f57e24525 updated at 2017/06/14 09:58:19
  13. On the new Log Collector, replace previous Log Collector serial number with the new Log Collector serial number.
    You must replace the old Log Collector serial number with the new Log Collector serial number so that the new Log Collector will not run in to purging issues, resulting in the Log Collector being unable to purge old data from the migrated logs when necessary.
    1. Replace old Log Collector serial number with new Log Collector serial number:
      request log-migration-update-logger from
      <old-log-collector-serial-number>
      to
      <new-log-collector-serial-number>

Related Documentation