Migrate Log Collectors after Failure/RMA of Non-HA Panorama
Table of Contents
11.1 & Later
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 Alibaba Cloud
- 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
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- 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 Alibaba Cloud
- 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
- Increase the CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- 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
- Install the Device Certificate for a Dedicated Log Collector
-
- 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-500 Appliance to an M-700 Appliance
- Migrate from an M-600 Appliance to an M-700 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 Admin Role Profile for Selective Push to Managed Firewalls
- 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
- Enable SCP Uploads for an Administrator
- Configure Tracking of Administrator Activity
-
- Add a Firewall as a Managed Device
- Change Between Panorama Management and Cloud Management
-
- 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
- Device Group Push to a Multi-VSYS Firewall
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Schedule a Configuration Push to Managed Firewalls
- Redistribute Data 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
-
- Configure a Managed Collector
- Monitor Managed Collector Health Status
- Configure Log Forwarding to Panorama
- Configure Syslog Forwarding to External Destinations
- Forward Logs to Strata Logging Service
- Verify Log Forwarding to Panorama
- Modify Log Forwarding and Buffering Defaults
- Configure Log Forwarding from Panorama to External Destinations
-
- Add Standalone WildFire Appliances to Manage with 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
-
-
- Preview, Validate, or Commit Configuration Changes
- Commit Selective Configuration Changes for Managed Devices
- Push Selective Configuration Changes to Managed Devices
- 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
- View Log Query Jobs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- View Task Success or Failure Status
- Generate a Stats Dump File for a Managed Firewall
- Recover Managed Device Connectivity to Panorama
- Restore an Expired Device Certificate
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 model:
Old/Failed Panorama | New/Replacement Panorama |
---|---|
Panorama virtual appliance |
|
M-100 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.
- Perform initial setup of the new Panorama appliance.
- Set Up the M-Series Appliance or Set Up the Panorama Virtual Appliance based on your needs. If you are setting up a new M-Series appliance, refer to the M-Series Appliance Hardware Reference Guides for instructions on how to rack mount the new M-Series appliance.
- 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 during initial configuration of the new M-Series appliance (). The Panorama virtual appliance does not support interfaces other than MGT.PanoramaSetupInterfaces
- Transfer licenses as follows only if the new Panorama appliance is the same model as the old appliance. Otherwise, you must purchase new licenses.
- Log in to the Palo Alto Networks Customer Support web site.
- Select theAssetstab and click theSpareslink.
- Click the Serial Number of the new M-Series appliance.
- ClickTransfer Licenses.
- Selectthe old appliance and clickSubmit.
- The M-500 appliance requires Panorama 7.0 or a later release. M-200 and M-600 appliances require Panorama 8.1. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
- Restore the configuration from the old Panorama to the replacement Panorama.
- Log in to the new Panorama and select.PanoramaSetupOperations
- ClickImport named Panorama configuration snapshot,Browseto the backup configuration file, and clickOK.
- ClickLoad named Panorama configuration snapshot, select theNameof the file you just imported, and clickOK.To replace an RMA Panorama, make sure youRetain Rule UUIDswhen you load the named Panorama configuration snapshot. If you do not select this option, Panorama removes all previous rule UUIDs from the configuration snapshot and assigns new UUIDs to the rules on Panorama, which means it does not retain information associated with the previous UUIDs, such as the policy rule hit count.
- SelectandCommitCommit to PanoramaCommityour changes.
- Selectand verify that the Connected column displays a check mark for the Dedicated Log Collector.PanoramaManaged CollectorsIf the Dedicated Log Collector doesn’t appear, you must reconfigure it and its Collector Group as described in the next step. Otherwise, skip the following step to Fetch the ring file to restore access to the logs stored on the Dedicated Log Collector.
- 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.logThe 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-GroupIn 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 123456789012If you don’t know the serial number of the Dedicated Log Collector, log in to its CLI and enter theshow system infooperational command.
- Commit your changes to the Collector Group.>commit-all log-collector-config log-collector-group<collector-group-name>