Migrate Logs to a New M-Series Appliance in Log Collector
When you request an RMA, use this procedure to migrate logs from a decommissioned M-Series appliance in Log Collector mode, that is not in a HA pair, to a new M-Series appliance.
If you need to replace an M-600, M-500, M-200 or M-100 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 procedure 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 a M-500 appliance).
Migrating logs by removing the logging disks from any M-Series appliance and loading them into an M-600 Panorama management server is not supported. To migrate to an M-600 appliance, set up the M-600 appliance, configure log forwarding to the new M-600 appliance and configure the M-Series appliance as a managed Log Collector until you no longer needed access to the logs stored on the M-Series appliance.
- 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-Series Appliance Hardware Reference Guides for instructions.
- When configuring interfaces, configure only the Management (MGT) interface. Switching to Log Collector mode (later in this procedure) removes the configurations for any other interfaces. If the Log Collector will use interfaces other than MGT, add them when configuring the Log Collector (see Step 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.
- Select theAssetstab and click theSpareslink.
- Click the Serial Number of the new M-Series appliance.
- ClickTransfer Licenses.
- Selectthe old M-Series appliance and clickSubmit.
- Activate a firewall management license. If you are migrating from an M-100 appliance to a M-500 appliance, enter the auth-code associated with the migration license.
- Install Content and Software Updates for Panorama. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire 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
- EnterYto 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 aCMS Loginprompt, 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>exitIf the old Log Collector used interfaces other than the MGT interface 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 ().PanoramaManaged CollectorsInterfaces
- 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-Series Appliance Hardware Reference Guides.
- 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.
- Insert the disks into the new Log Collector. For details, refer to the disk replacement procedure in the M-Series Appliance Hardware Reference Guides.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.
- Enable the disk pairs by running the following CLI command for each pair:>request system raid add<slot>force no-formatFor example:>request system raid add A1 force no-format>request system raid add A2 force no-formatTheforceandno-formatarguments are required. Theforceargument associates the disk pair with the new Log Collector. Theno-formatargument 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
- 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.
- Overwrite Panorama restriction to allow Log Collector with no disk to be added to a Collector Group:request log-migration-set-start
- 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 (). Give the new Log Collector the same priority in the firewall preference lists as the old Log Collector.PanoramaCollector GroupsDevice Log ForwardingYou cannot use the CLI 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
- Generate new keys on the new Dedicated 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.
- Delete all RSA keys on new Log Collector:request logdb update-collector-group-after-replace collector-group<collector-group-name>The process can take up to 10 minutes to completed.
- 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.
- Show the Log Collector details by running the following commands either:
Alternatively, you can run the following command on each Dedicated Log Collector:show log-collector detailConfirm that SearchEngine Status is Active.Redistribution status: noneLast commit-all: commit succeeded, current ring version 1SearchEngine status: Activemd5sum 4e5055a359f7662fab8f8c4f57e24525 updated at 2017/06/14 09:58:19
- On Panorama for all Log Collectors:show log-collector all
- 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.
- 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>
Recommended For You
Recommended videos not found.