Setup Prerequisites for the Panorama Virtual Appliance
Table of Contents
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-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
- Configure Tracking of Administrator Activity
-
- 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
- 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
- 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
- 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
Setup Prerequisites for the Panorama Virtual Appliance
Complete the following tasks before you Install
the Panorama Virtual Appliance:
- Use your browser to access the Palo Alto Networks Customer Support web site and Register Panorama You will need the Panorama serial number that you received in the order fulfillment email. After registering Panorama, you can access the Panorama software downloads page.
- Review the supported Panorama hypervisors to verify the hypervisor meets the minimum version requirements to deploy Panorama.
- If you will install Panorama on a VMware ESXi server, verify that the server meets the minimum requirements as listed in the System Requirements for the Panorama Virtual Appliance. These requirements apply to Panorama 5.1 and later releases. The requirements vary based on whether you will run the virtual appliance in Panorama mode or Management Only mode. For details on the modes, see Panorama Models.If you install Panorama on VMware vCloud Air, you set the system settings during installation.
Review the minimum resource requirements for deploying the Panorama
virtual appliance on Alibaba Cloud, Amazon Web Services (AWS), AWS
GovCloud, Microsoft Azure, Google Cloud Platform (GCP), Hyper-V,
KVM, Oracle Cloud Infrastructure (OCI), and VMware ESXi to ensure
that the virtual machine meets the minimum required resources for
the desired mode (Panorama, Management Only, or Log Collector).
The minimum resource requirements for the Panorama virtual appliance are
designed to help you achieve the maximum number of logs per second
(LPS) for log collection in Panorama and Log Collector mode. If
you add or remove virtual logging disks that results in a configuration
that does not meet or exceed the number of virtual logging disks
recommended (below), your LPS will be reduced.
If the minimum resource requirements are not met for Panorama
mode when you Install the Panorama Virtual Appliance, Panorama
defaults to Management Only mode for all supported public (Alibaba
Cloud, AWS, AWS GovCloud, Azure, GCP, and OCI) and private (Hyper-V,
KVM, and VMware ESXi) hypervisors. If the minimum resource requirements
are not met for Management Only mode, Panorama defaults to Maintenance
mode for all supported public hypervisors, Hyper-V, and KVM. If
the minimum resource requirements for Management Only mode are not
met when you Install Panorama on VMware, Panorama
defaults to Legacy mode.
While still supported, Legacy mode is not recommended for production environments. Additionally,
you can no longer switch Panorama to Legacy mode. For more information on supported
modes, see Panorama Models.
Requirements | Panorama Virtual Appliance in Management
Only Mode | Panorama Virtual Appliance
in Panorama Mode | Panorama Virtual Appliance in Log Collector
Mode |
---|---|---|---|
Virtual hardware version |
In
Panorama mode, the virtual appliance running on any ESXi version
supports up to 12 virtual logging disks with 2TB of log storage
each, for a total maximum capacity of 24TB. (VMware ESXi
and vCloud Air only) In Legacy mode, the virtual appliance
supports one virtual logging disk. ESXi 5.5 and later versions supports
one disk of up to 8TB. Earlier ESXi versions support one disk of
up to 2TB. | ||
(ESXi and vCloud Air only) Client computer | To install the Panorama virtual
appliance and manage its resources, you must install a VMware vSphere
Client or VMware Infrastructure Client that is compatible with your
ESXi server. | ||
System disk
|
For log storage, Panorama uses virtual logging disks instead of the
system disk or an NFS datastore.
Panorama must be initially installed with the Default system
disk size, with the option to increase the system
disk size after initial installation.
| ||
CPUs, memory, and
logging disks |
| The minimum resources below are required
to achieve the specified logging rate.
| The minimum resources below are required
to achieve the specified logging rate.
|
The first logging disk on the
Panorama virtual appliance must be 2TB in order to add additional
logging disks. If the first logging disk is smaller than 2TB, you
are unable to add additional logging disks. | |||
Minimum CPUs and memory |
| The minimum resources below
do not take LPS into consideration and are only required for the
Panorama virtual appliance to function based on the number of logging
disks added. Palo Alto Networks recommends you refer to the recommended resources above. For
larger Panorama deployments, be aware that you may be under-provisioning
your Panorama. This may lead to impacted performance and may cause Panorama
to become unresponsive depending on the number of firewalls managed,
the configuration size, the number of administrators logged in to
Panorama, and the volume of logs ingested.
| |
Log storage capacity | Panorama in Management Only mode requires
log forwarding to a Dedicated Log Collector. | 2TB to 24TB | 2TB to 24TB |
Supported Interfaces
Interfaces can be used for device management, log collection,
Collector Group communication, licensing and software updates. The
Panorama virtual appliance supports up to six interfaces (MGT and
Eth1 - Eth5).
Function | Alibaba Cloud | Amazon Web Services (AWS) and
AWS GovCloud | Microsoft Azure | Google Cloud Platform (GCP) | OCI | |
---|---|---|---|---|---|---|
Device Management | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported |
Device Log Collection | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported |
Collector Group Communication | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported | Any interface supported |
Licensing and Software Updates | MGT interface only | MGT interface only | MGT interface only | MGT interface only | MGT interface only | MGT interface only |
Function | KVM | Hyper-V | VMware (ESXi, vCloud Air) |
---|---|---|---|
Device Management | Any interface supported | Any interface supported | Any interface supported |
Device Log Collection | Any interface supported | Any interface supported | Any interface supported |
Collector Group Communication | Any interface supported | Any interface supported | Any interface supported |
Licensing and Software Updates | Any interface supported | Any interface supported | Any interface supported |