If you need to replace an M-Series appliance in Log Collector mode (Dedicated Log Collector), you can migrate the logs it collected from firewalls by moving its RAID disks to a new M-Series appliance. This 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 procedure applies whether the Panorama management server that manages the Dedicated Log Collector is a Panorama virtual appliance or an M-Series appliance in Panorama mode.
Migrate Logs to a New M-Series Appliance in Log Collector Mode
Perform initial setup of the new M-Series appliance that will be a Dedicated Log Collector. 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. When configuring interfaces, configure only the Management (MGT) interface. Switching to Log Collector mode later in this procedure removes any Eth1 and Eth2 interface configurations. If the Log Collector will use Eth1 and Eth2, add them when setting up the Log Collector later in this procedure. 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. Switch from Panorama mode to Log Collector mode: Access the Log Collector CLI and switch to Log Collector mode: > request system system-mode logger Enter Y to confirm the mode change. The M-Series appliance reboots. If the reboot process terminates your terminal emulation software session, reconnect to the M-Series appliance to display the Panorama login prompt. If you see a CMS Login prompt, press Enter without typing a username or password. Use the Log Collector CLI to enable connectivity between the Log Collector and Panorama management server. <IPaddress1 is for the MGT interface of the primary Panorama and <IPaddress2> is for the MGT interface of the secondary Panorama. > configure # set deviceconfig system panorama-server <IPaddress1> panorama-server-2 <IPaddress2> # commit # exit
On the Panorama management server, add the new Log Collector as a managed collector. 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. Configure the Log Collector as a managed collector using the Panorama web interface or using the following CLI commands: > configure # set log-collector <LC_serial_number> deviceconfig system hostname <LC_hostname> # exit If the old Log Collector used the Eth1 and Eth2 interfaces for log collection and Collector Group communication, you must define those interfaces on the new Log Collector when you configure it as a managed collector ( Panorama > Managed Collectors > Eth1 and Eth2). Verify that the 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 # exit
Remove the RAID disks from the old Log Collector. Power off the old Log Collector 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.
Insert the RAID disks in to the new Log Collector. Power off the new Log Collector by pressing the Power button until the system shuts down. Insert the disks into the new Log Collector. 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 Log Collector 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 configd 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 Log Collector. 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
Migrate the logs. You must use the Panorama CLI for this step, not the web interface. You must assign the new Log Collector to the Collector Group that contains the old Log Collector. Assign the new Log Collector to the Collector Group and commit your changes to Panorama. > configure # set log-collector-group <collector_group_name> logfwd-setting collectors <new_LC_serial_number> # commit # exit For each disk pair, migrate the logs from the old Log Collector to the new Log Collector and attach the disk pair to the new Log Collector. > 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
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. > configure # 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