Deploy Panorama M-Series Appliances with Local Log Collectors
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
Deploy Panorama M-Series Appliances with Local Log Collectors
The following figures illustrate Panorama in a centralized log collection deployment. In these
examples, the Panorama management server comprises two M-Series appliances in
Panorama mode that are deployed in an active/passive high availability (HA)
configuration. The firewalls send logs to the predefined (default) local Log
Collector on each Panorama M-Series appliance.
If you assign more than one Log Collector to a Collector Group, see Caveats for a
Collector Group with Multiple Log Collectors to understand the
requirements, risks, and recommended mitigations.
After implementing this deployment, if the logging rate exceeds the
qualified maximum, Palo Alto Networks recommends that you add Dedicated Log
Collectors (M-Series appliances in Log Collector mode) as described in the Deploy Panorama with Dedicated Log
Collectors documentation. For more information about the qualified
maximum logging rates, see Logging Rates for
M-Series appliances and System Requirements for
Panorama Virtual Appliances. Such an expansion might require reassigning
firewalls from the local Log Collectors to Dedicated Log Collectors.
Perform
the following steps to deploy Panorama with local Log Collectors.
Skip any steps you have already performed (for example, the initial
setup).
- Perform the initial setup of each M-Series appliance.
- Rack mount the M-Series appliance. Refer to the M-Series Hardware Reference Guides for instructions.Perform Initial Configuration of the M-Series Appliance.Palo Alto Networks recommends reserving the management (MGT) interface for administrative access to Panorama and dedicating separate M-Series Appliance Interfaces to other Panorama services.Configure each array. This task is required to make the RAID disks available for logging. Optionally, you can add disks to Increase Storage on the M-Series Appliance.Register Panorama and Install Licenses.Install Content and Software Updates for Panorama.Set Up HA on Panorama.Perform the following steps to prepare Panorama for log collection.
- Connect to the primary Panorama in one of the following ways:
- Attach a serial cable from your computer to the Console port on the primary Panorama. Then use terminal emulation software (9600-8-N-1) to connect.
- Use terminal emulation software such as PuTTY to open an SSH session to the IP address that you specified for the MGT interface of the primary Panorama during initial configuration.
Log in to the CLI when prompted. Use the default admin account and the password that you specified during initial configuration.Enable the primary Panorama to connect to the secondary Panorama by entering the following command, where <IPaddress2> represents the MGT interface of the secondary Panorama:> configure # set deviceconfig system panorama-server <IPaddress2> # commit
Log in to the CLI of the secondary Panorama.Enable the secondary Panorama to connect to the primary Panorama by entering the following command, where <IPaddress1> represents the MGT interface of the primary Panorama:> configure # set deviceconfig system panorama-server <IPaddress1> # commit # exit
In the CLI of the secondary Panorama, enter the following command to display the serial number, and then record it:> show system info | match serial
You need the serial number to add the Log Collector of the secondary Panorama as a managed collector to the primary Panorama.Edit the Log Collector that is local to the primary Panorama.Use the web interface of the primary Panorama to perform these steps:- Select PanoramaManaged Collectors and select the default (local) Log Collector.Select Disks and Add each logging disk pair.Click OK to save your changes.Configure the Log Collector that is local to the secondary Panorama.Panorama treats this Log Collector as remote because it’s not local to the primary Panorama. Therefore you must manually add it on the primary Panorama.Use the web interface of the primary Panorama to Configure a Managed Collector:
- Select PanoramaManaged Collectors and Add the Log Collector.Enter the serial number (Collector S/N) you recorded for the Log Collector of the secondary Panorama.Enter the IP address or FQDN of the primary and secondary Panorama HA peers in the Panorama Server IP field and Panorama Server IP 2 field respectively.Both of these fields are required.Select Interfaces and configure each interface that the Log Collector will use. The Management interface is required. Perform the following steps for each interface:
- Click the interface name.
- Configure one or both of the following field sets based on the IP protocols of your network.IPv4—IP Address, Netmask, and Default GatewayIPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway
- (Management interface only) Select SNMP if you will use an SNMP manager to monitor Log Collector statistics.Using SNMP requires additional steps besides configuring the Log Collector (see Monitor Panorama and Log Collector Statistics Using SNMP).
- Click OK to save your changes to the interface.
Click OK to save your changes to the Log Collector.Select CommitCommit to Panorama and Commit your changes.This step is required before you can enable logging disks.Edit the Log Collector by clicking its name.Select Disks, Add each RAID disk pair, and click OK.Select CommitCommit to Panorama and Commit your changes.Add a Firewall as a Managed Device.Use the web interface of the primary Panorama to perform this task for each firewall that will forward logs to the Log Collectors.Edit the default Collector Group that is predefined on the primary Panorama.Use the web interface of the primary Panorama to Configure a Collector Group:- Select PanoramaCollector Groups and edit the default Collector Group.Add the local Log Collector of the secondary Panorama to the Collector Group Members list if you are adding multiple Log Collectors to a single Collector group. By default, the list displays the local Log Collector of the primary Panorama because it is pre-assigned to the default Collector Group.In any single Collector Group, all the Log Collectors must run on the same Panorama model: all M-700 appliances, all M-600 appliances, all M-500 appliances, all M-300 appliances, all M-200 appliances, or all Panorama virtual appliances.(Best Practice) Enable log redundancy across collectors if you add multiple Log Collectors to a single Collector group. This option requires each Log Collector to have the same number of logging disks.(Optional) Select Monitoring and configure the settings if you will use SNMP to monitor Log Collector statistics and traps.Select Device Log Forwarding and configure the Log Forwarding Preferences list. This list defines which firewalls forward logs to which Log Collectors. Assign firewalls according to the number of Log Collectors in this Collector Group:
- Single—Assign the firewalls that will forward logs to the local Log Collector of the primary Panorama, as illustrated in Single Local Log Collector Per Collector Group.
- Multiple—Assign each firewall to both Log Collectors for redundancy. When you configure the preferences, make Log Collector 1 the first priority for half the firewalls and make Log Collector 2 the first priority for the other half, as illustrated in Multiple Local Log Collectors Per Collector Group.
Click OK to save your changes.Configure a Collector Group that contains the Log Collector of the secondary Panorama.Required if each Collector Group has only one Log Collector.Use the web interface of the primary Panorama to Configure a Collector Group:- Select PanoramaCollector Groups and Add the Collector Group.Enter a Name to identify the Collector Group.Add the local Log Collector of the secondary Panorama to the Collector Group Members list.(Optional) Select Monitoring and configure the settings if you will use an SNMP manager to monitor Log Collector statistics and traps.Select Device Log Forwarding and Add an entry to the Log Forwarding Preferences list:
- Modify the Devices list, select the firewalls that will forward logs to the local Log Collector of the secondary Panorama (see Single Local Log Collector Per Collector Group), and click OK.
- Add the local Log Collector of the secondary Panorama to the Collectors list and click OK.
Click OK to save your changes.Commit and push your changes to the Panorama configuration and the Collector Groups.In the web interface of the primary Panorama, select CommitCommit and Push and then Commit and Push your changes to Panorama and the Collector Groups you added.Manually fail over so that the secondary Panorama becomes active.Use the web interface of the primary Panorama to perform the following steps:- Select PanoramaHigh Availability.Click Suspend local Panorama in the Operational Commands section.On the secondary Panorama, configure the network settings of the Log Collector that is local to the primary Panorama.Use the web interface of the secondary Panorama to perform the following steps:
- In the Panorama web interface, select PanoramaManaged Collectors and select the Log Collector that is local to the primary Panorama.Enter the IP address or FQDN of the primary and secondary Panorama HA peers in the Panorama Server IP field and Panorama Server IP 2 field respectively.Both of these fields are required.Select Interfaces, click Management, and complete one or both of the following field sets (based on the IP protocols of your network) with the MGT interface values of the primary Panorama:
- IPv4—IP Address, Netmask, and Default Gateway
- IPv6—IPv6 Address/Prefix Length and Default IPv6 Gateway
Click OK to save your changes.Select CommitCommit and Push and then Commit and Push your changes to Panorama and the Collector Groups you added.Manually fail back so that the primary Panorama becomes active.Use the web interface of the secondary Panorama to perform the following steps:- Select PanoramaHigh Availability.Click Suspend local Panorama in the Operational Commands section.Configure log forwarding from firewalls to Panorama.Use the web interface of the primary Panorama to:
- Configure Log Forwarding to Panorama.Verify Log Forwarding to Panorama.(Optional) Configure Log Forwarding from Panorama to External Destinations.You can assign separate external server profiles to each Panorama HA peer. For example, you might want each peer to forward logs to a different syslog server. To make each Panorama peer forward logs to different external services, log in to the web interface of each peer, select PanoramaCollector Groups, select the Collector Group, select Collector Log Forwarding, assign the server profiles, and click OK.