Deploy Panorama Virtual 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 Virtual Appliances with Local Log Collectors
You can configure firewalls to send logs to
a Log Collector that runs locally on a Panorama virtual appliance
in Panorama mode. In a high availability (HA) configuration, each
Panorama HA peer can have a local Log Collector. You can assign
the local Log Collectors on the HA peers to the same Collector Group
or to separate Collector Groups, as illustrated in the following
figures. Refer to the Setup Prerequisites for the Panorama Virtual Appliance to review
the supported logs per second when deploying the Panorama virtual
appliance with local Log Collectors in a VMware virtual infrastructure.
If you will 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.
Single Log Collector Per Collector Group
![](/content/dam/techdocs/en_US/dita/_graphics/11-1/panorama/Log_Collection_VAs_Local_LCs_Separate_CGs.png)
Multiple Log Collectors Per Collector Group
![](/content/dam/techdocs/en_US/dita/_graphics/11-1/panorama/Log_Collection_VAs_Local_LCs_Shared_CGs.png)
Perform
the following steps to deploy Panorama with local Log Collectors.
Skip any steps you have already performed (such as the initial setup).
- Perform the initial setup of each Panorama virtual appliance.
- Install the Panorama Virtual Appliance. You must configure the following resources to ensure the virtual appliance starts in Panorama mode:
- System disk with exactly 81GB of storage.
- CPUs and memory that are sufficient for the quantity of logs that Panorama will receive and store.
- Virtual logging disk with 2–24TB of storage.
Panorama automatically divides the new disk into 2TB partitions, each of which will function as a separate virtual disk.
- Set up the Panorama virtual appliances in an HA configuration.
- Add a Log Collector that is local to the primary Panorama.On the primary Panorama:
- Record the Panorama serial number.
- Access the Panorama web interface.
- SelectDashboardand record theSerial #in the General Information section.
- Add the Log Collector as a managed collector.
- SelectandPanoramaManaged CollectorsAdda new Log Collector.
- In theGeneralsettings, enter the serial number (Collector S/N) you recorded for Panorama.
- ClickOKto save your changes.
- Select.CommitCommit to PanoramaThis step is required before you can add the virtual logging disks.
- Add the virtual logging disks.
- Selectand edit the Log Collector by clicking its name.PanoramaManaged CollectorsThe Log Collector name has the same value as the hostname of the primary Panorama.
- SelectDisksandAddthe virtual logging disks.
- ClickOKto save your changes.
- Select.CommitCommit to Panorama
- Add a Log Collector that is local to the secondary Panorama.Panorama treats this Log Collector as remote because it does not run locally on the primary Panorama.
- Record the serial number of the secondary Panorama.
- Access the web interface of the secondary Panorama.
- SelectDashboardand record theSerial #in the General Information section.
- Access the web interface of the primary Panorama.
- SelectandPanoramaManaged CollectorsAddthe Log Collector.
- In theGeneralsettings, enter the serial number (Collector S/N) you recorded for the secondary Panorama.
- Enter the IP address or FQDN of the primary and secondary Panorama HA peers in thePanorama Server IPfield andPanorama Server IP 2field respectively.Both of these fields are required.
- ClickOKto save your changes to the Log Collector.
- SelectandCommitCommit to PanoramaCommityour changes.This step is required before you can add the virtual logging disks.
- Edit the Log Collector by clicking its name.The Log Collector name has the same value as the hostname of the secondary Panorama.
- SelectDisks,Addthe virtual logging disks, and clickOK.
- SelectandCommitCommit to PanoramaCommityour changes.
- Use the primary Panorama to perform this task for each firewall that will forward logs to the Log Collectors.
- Configure the Collector Group.Perform this step once if you will assign both Log Collectors to the same Collector Group. Otherwise, configure a Collector Group for each Log Collector.On the primary Panorama:
- SelectandPanoramaCollector GroupsAdda Collector Group.
- Addone or both Log Collectors as Collector Group Members.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 collectorsif you add multiple Log Collectors to a single Collector group. This option requires each Log Collector to have the same number of virtual logging disks.Enabling redundancy doubles the amount of logs and log processing traffic in a Collector Group. If necessary, Expand Log Storage Capacity on the Panorama Virtual Appliance.
- SelectDevice Log Forwardingand 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 Log Collector that is local to the primary Panorama, as illustrated in Single Log Collector Per Collector Group.
- Multiple—Assign each firewall to both Log Collectors for redundancy. When you configure the preference list, 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 Log Collectors Per Collector Group.
- ClickOKto save your changes.
- Selectand thenCommitCommit and PushCommit and Pushyour changes to Panorama and the Collector Groups you added.
- Trigger failover on the primary Panorama so that the secondary Panorama becomes active.On the primary Panorama:
- Select.PanoramaHigh Availability
- ClickSuspend local Panoramain the Operational Commands section.
- Configure the connection from the secondary Panorama to the Log Collector that is local to the primary Panorama.On the secondary Panorama:
- In the Panorama web interface, selectand select the Log Collector that is local to the primary Panorama.PanoramaManaged Collectors
- Enter the IP address or FQDN of the primary and secondary Panorama HA peers in thePanorama Server IPfield andPanorama Server IP 2field respectively.Both of these fields are required.
- ClickOKto save your changes.
- Selectand thenCommitCommit and PushCommit and Pushyour changes to Panorama and the Collector Groups.
- Restore HA functionality on the primary Panorama.
- Log in to the Panorama web interface of the primary Panorama.
- Select.PanoramaHigh Availability
- Make local Panorama functional for high availability.
- Trigger fail-back on the secondary Panorama so that the primary Panorama becomes active.On the secondary Panorama:
- Select.PanoramaHigh Availability
- ClickSuspend local Panoramain the Operational Commands section.
- Make local Panorama functional for high availabilityto restore HA functionality to the secondary Panorama.
- In theDashboard, verify in the High Availability widget that the secondary Panorama issecondary-passive.
- Log in to the Panorama web interface of the primary Panorama and in theDashboard, verify in the High Availability widget that the primary Panorama isprimary-active.
- Configure log forwarding from the firewalls to Panorama.On the primary Panorama to: