Migrate Logs to a New M-Series Appliance in Log Collector Mode
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute User-ID Information to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Configure Basic WildFire Appliance Settings on Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Restore an Expired Device Certificate
- Downgrade from Panorama 9.1
End-of-Life (EoL)
Migrate Logs to a New M-Series Appliance in Log Collector Mode
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 an 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.
- 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 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).
- Register Panorama.
- 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.
- 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 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. 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
- 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 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). - Commit your changes to Panorama. Don’t commit the changes to the
Collector Group just yet.
> configure # commit # exit
- 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.
- Configure the Log Collector as a managed
collector using the Panorama web interface or using
the following CLI commands:
- 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-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
- Insert the disks into the new Log Collector.
For details, refer to the disk replacement procedure in the M-Series
Appliance Hardware Reference Guides.
- 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.
- Access the Panorama CLI.
- 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
- Assign the new Log Collector to the Collector
Group and commit your changes to Panorama.
- Reconfigure the Collector Group.
- Use the web interface to assign the new Log Collector to the firewalls that
forward logs (PanoramaCollector GroupsDevice 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.
- 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
- Use the web interface to assign the new Log Collector to the firewalls that
forward logs (PanoramaCollector GroupsDevice Log Forwarding). Give
the new Log Collector the same priority in the firewall preference lists
as the old Log Collector.
- 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.
- Access the Panorama CLI.
- 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.
- Access the Panorama CLI.
- 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- 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
- 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.- Access the Log Collector CLI.
- 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>