Migrate Log Collectors after Failure/RMA of Non-HA Panorama

If a system failure occurs on a Panorama management server that is not deployed in a high availability (HA) configuration, use this procedure to restore the configuration on the replacement Panorama and restore access to the logs on the Dedicated Log Collectors that it manages. The allowed migration scenarios vary by Panorama management server:

Old/Failed Panorama	New/Replacement Panorama
Panorama virtual appliance	Panorama virtual appliance M-100 appliance M-500 appliance
M-100 appliance	M-100 appliance M-500 appliance
M-500 appliance	M-500 appliance

Panorama maintains a ring file that maps the segments and partitions that Dedicated Log Collectors use to store logs. An M-Series appliance in Panorama mode stores the ring file on its internal SSD; a Panorama virtual appliance stores the ring file on its internal disk. When a system failure occurs, a non-HA Panorama cannot automatically recover the ring file. Therefore, when you replace Panorama, you must restore the ring file to access the logs on the Dedicated Log Collectors.

This procedure requires that you backed up and exported your Panorama configuration before the system failure occurred.

Palo Alto Networks recommends deploying Panorama in an HA configuration. The active Panorama peer automatically synchronizes the ring file to the passive peer in an HA configuration, thereby maintaining access to logs on the Dedicated Log Collectors even if you must replace one of the peers.

Recover Logs after Panorama Failure/RMA in Non-HA Deployments
Perform initial setup of the new Panorama appliance.	( Optional; applies only to M-Series appliances ) 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 or Perform Initial Configuration of the Panorama Virtual 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). The Panorama virtual appliance does not use Eth1 or Eth2. Register Panorama. Transfer licenses as follows only if the new Panorama model is the same model as the old one. 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 appliance and click Submit. Activate a Panorama Support License. Activate a firewall management 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.
Restore the configuration from the old Panorama to the replacement Panorama.	Log in to the new Panorama and select Panorama > Setup > Operations. Click Import named Panorama configuration snapshot, Browse to the backup configuration file, and click OK. Click Load named Panorama configuration snapshot and select the file you just imported. Click Commit, set the Commit Type to Panorama, and click Commit again. Select Panorama > Managed Collectors and verify that the Connected column displays a check mark for the Dedicated Log Collector. If the Dedicated Log Collector doesn’t appear, you must reconfigure it and its Collector Group as described in Step 3. Otherwise, skip to Step 4.
Reconfigure the Dedicated Log Collector and Collector Group if they are missing on Panorama.	Access the CLI of the Dedicated Log Collector and enter the following commands to display the name of its Collector Group. Enter the command: > request fetch ring from log-collector <serial_number> The following error will display: Server error: Failed to fetch ring info from <serial_number> Enter the command: > less mp-log ms.log The following error will display: Dec04 11:07:08 Error: pan_cms_convert_resp_ring_to_file(pan_ops_cms.c:3719): Current configuration does not contain group CA-Collector-Group In this example, the error message indicates that the missing Collector Group has the name CA-Collector-Group. Configure the Collector Group and assign the Dedicated Log Collector to it. > configure # set log-collector-group <collector-group-name> # set log-collector-group <collector-group-name> logfwd-setting collector <serial-number> Commit the changes to Panorama but not to the Collector Group. # commit # exit
Fetch the ring file to restore access to the logs stored on the Dedicated Log Collector.	Access the CLI of the new Panorama. Fetch the ring file: > request fetch ring from log-collector <serial-number> For example: > request fetch ring from log-collector 009201000343 If you don’t know the serial number of the Dedicated Log Collector, log in to its CLI and enter the show system info operational command. Commit your changes to the Collector Group. > commit-all log-collector-config log-collector-group <collector-group-name>

Document:Panorama™ Administrator’s Guide

Migrate Log Collectors after Failure/RMA of Non-HA Panorama

Related Documentation

Document:Panorama™ Administrator’s Guide

Migrate Log Collectors after Failure/RMA of Non-HA Panorama

Related Documentation

Migrate Logs to a New M-Series Appliance in Log Collector Mode

Transition to a Different Panorama Platform

Migrate from an M-100 Appliance to an M-500 Appliance

Migrate Logs to a New M-Series Appliance in Panorama Mode

Troubleshoot Log Storage and Connection Issues

Move a Log Collector to a Different Collector Group

Configure a Managed Collector

Panorama Platforms

Migrate from a Panorama Virtual Appliance to an M-Series Appliance

Centralized Logging and Reporting