Perform Initial Configuration of the Panorama Virtual Appliance
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
Perform Initial Configuration of the Panorama Virtual Appliance
Based on your Panorama model, use the Alibaba Cloud Console, AWS, Azure, GCP,
or OCI web interface, KVM Virtual
Machine Manager, Hyper-V Manager, VMware vSphere Client, or vCloud
Air web console to set up network access to the Panorama virtual
appliance. By default, the Panorama virtual appliance is deployed
in Panorama mode. For unified reporting, consider using Greenwich
Mean Time (GMT) or Coordinated Universal Time (UTC) as the uniform
time zone across Panorama and all the managed firewalls and Log
Collectors.
- Gather the required information from your network administrator.Collect the following information for the management (MGT) interface:
- IP address for the management (MGT) interfaceThe default management interface IP address is 192.168.1.1. if you do not configure the management interface as described when you install the Panorama virtual appliance.
- Netmask
- Default gateway
- DNS server IP addressTo complete the configuration of the MGT interface, you must specify the IP address, netmask (for IPv4) or prefix length (for IPv6), and default gateway. If you omit settings (such as the default gateway), you can access Panorama only through the console port for future configuration changes. As a best practice, always commit a complete MGT interface configuration.
- Access the console of the Panorama virtual appliance.Panorama uses the MGT interface for management traffic, high availability synchronization, log collection, and communication within Collector Groups.Starting with PAN-OS 9.0.4, the defaultadmincredentials are no longer supported. When you first install the Panorama virtual appliance, you are required to log in to the Panorama CLI to configure a uniqueadminpassword.If this is the first time you are logging in to the Panorama CLI, you are prompted to enter theOld Passwordand theNew Passwordfor theadminuser before you can continue with the initial configuration of the Panorama virtual appliance.
- Access the console.On an ESXi server:
- Launch the VMware vSphere Client.
- Select theConsoletab for the Panorama virtual appliance and press enter to access the login screen.
On vCloud Air:- Access the vCloud Air web console and select yourVirtual Private Cloud OnDemandregion.
- Select theVirtual Machinestab, right-click the Panorama virtual machine, and selectOpen In Console.
- Enter your username and password to log in (default is admin for both).On Alibaba Cloud, AWS, Azure, GCP, KVM, Hyper-V, and OCI:
- Configure the network access settings for the MGT interface.Panorama uses the MGT interface for management traffic, high availability synchronization, log collection, and communication within Collector Groups.
- Enter the following commands, where<Panorama-IP>is the IP address you want to assign to the Panorama management interface,<netmask>is the subnet mask,<gateway-IP>is the IP address of the network gateway, and<DNS-IP>is the IP address of the DNS server:>configure#set deviceconfig system ip-address#<Panorama-IP>netmask<netmask>default-gateway<gateway-IP>dns-setting servers primary<DNS-IP>commit#exit
- Troubleshoot Connectivity to Network Resources to verify network access to external services required for firewall management, such as the default gateway, DNS server, and the Palo Alto Networks Update Server, as shown in the following example:
- Configure the general settings.
- Using a secure connection (HTTPS) from a web browser, log in to the Panorama web interface using the IP address and password you assigned to the management interface (https://<IP address>).
- Selectand edit the General Settings.PanoramaSetupManagement
- Enter aHostnamefor the server and enter the networkDomainname. The domain name is just a label; Panorama doesn’t use it to join the domain.
- Align the clock on Panorama and the managed firewalls to use the sameTime Zone, for example GMT or UTC. If you plan to use theStrata Logging Service, you must configure NTP so that Panorama can stay in sync with theStrata Logging Service.Timestamps are recorded when Panorama receives the logs and the managed firewalls generate the logs. Aligning the time zones on Panorama and the firewalls ensures that the timestamps are synchronized and the process of querying logs and generating reports on Panorama is harmonious.
- Enter theLatitudeandLongitudeto enable accurate placement of the Panorama management server on the world map.
- Enter theSerial Numberyou received in the order fulfillment email.
- ClickOKto save your changes.
- (Optional) Modify the management interface settings.To configure connectivity to Panorama using an IPv6 IP address, you must configure both an IPv4 and IPv6 to successfully configure Panorama using an IPv6 IP address. Panorama does not support configuring the management interface with only an IPv6 IP address.
- Selectand clickPanoramaSetupInterfacesManagement.
- If your firewalls connect to the Panorama management server using a public IP address that is translated to a private IP address (NAT), enter the public IP in thePublic IP Addressfield, and the private IP in theIP Addressfield to push both addresses to your firewalls.
- Select which Network Connectivity Services to allow on the interface (such asSSHaccess).Don’t selectTelnetorHTTP. These services use plaintext and are less secure than the other services.
- ClickOKto save your changes to the interface.
- Commit your configuration changes.SelectandCommitCommit to PanoramaCommityour changes.
- Next steps...
- (Best Practice) Replace the default certificate that Panorama uses to secure HTTPS traffic over the management (MGT) interface.