Use these instructions to install a new Panorama virtual appliance on a VMware ESXi server. If you are upgrading your existing Panorama virtual appliance, skip to
Install Content and Software Updates for Panorama.
Install Panorama on an ESXi Server
Download the Panorama base image Open Virtual Appliance (OVA) file.
Launch the VMware vSphere Client and connect to the VMware server.
Select
File > Deploy OVF Template.
Browse
to select the Panorama OVA file and click
Next.
Confirm that the product name and description match the downloaded version, and click
Next.
Enter a descriptive name for the Panorama virtual appliance, and click
Next.
Select a
Datastore Location
on which to install the Panorama image, and click
Next.
Regardless of the disk size, Panorama uses approximately 11GB for log storage. Increasing the disk size doesn’t increase the log storage capacity. To
Expand Log Storage Capacity on the Panorama Virtual Appliance, you must add another virtual disk or set up access to a Network File System (NFS) datastore.
Select your preferred
Disk Provisioning
disk format, and click
Next.
Consider your business needs when selecting the disk provisioning format. For more information, regarding the disk provisioning performance considerations, refer to the VMware Thick vs Thin Disks and All Flash Arrays
document, or additional VMware documentation.
Specify which networks in the inventory to use for the Panorama virtual appliance.
Confirm the selected options and click
Finish
to start the installation process.
When the installation completes, right-click the Panorama virtual appliance and
Edit Settings
as follows:
Select the
Hardware
tab and allocate
Memory
based on how many firewalls Panorama will manage:
1–10 firewalls: 4GB
11–50 firewalls: 8GB
51–1,000 firewalls: 16GB
Set the
SCSI Controller
to
LSI Logic Parallel.
Click
OK
to save your changes.
Power on the Panorama virtual appliance.
In the vSphere Client, right-click the Panorama virtual appliance and select
Power > Power On.
When the Panorama virtual appliance boots, the installation process is complete. You are then ready to
Perform Initial Configuration of the Panorama Virtual Appliance.
Install Panorama in vCloud Air
Use these instructions to install a new Panorama virtual appliance in VMware vCloud Air. If you are upgrading a Panorama virtual appliance deployed in vCloud Air, skip to
Install Content and Software Updates for Panorama.
Install Panorama in vCloud Air
Download the Panorama base image Open Virtual Appliance (OVA) file.
Import the Panorama image to the vCloud Air catalog.
For details on these steps, refer to the OVF Tool User’s Guide.
Install the OVF Tool on your client system.
Access the client system CLI.
Navigate to the OVF Tool directory.For example:
C:\Program Files\VMware\VMware OVF Tool
Convert the OVA file to an OVF package:ovftool.exe
<OVA-file-pathname>
<OVF-file-pathname>
Use a browser to access the vCloud Air web console, select your
Virtual Private Cloud OnDemand
location, and record the browser URL. You will use the URL information to complete the next step. The URL format is: https://<virtual-cloud-location>.vchs.vmware.com/compute/cloud/org/<vCloud-account-number>/#/catalogVAppTemplateList?catalog=<catalog-ID>.
Import the OVF package, using the information from the vCloud Air URL to complete the <virtual-cloud-location>, <vCloud-account-number>, and <catalog-ID> variables. The other variables are your vCloud Air username and domain <user>@<domain>, a virtual data center
<datacenter>, and a vCloud Air template
<template>.
ovftool.exe -st="OVF" "
<OVF-file-pathname>
" "vcloud://
<user>@<domain>:password@
<virtual-cloud-location>.vchs.vmware.com?vdc=
<datacenter>&org=
<vCloud-account-number>&vappTemplate=
<template>.ovf&catalog=default-catalog"
Install Panorama.
Access the vCloud Air web console and select your
Virtual Private Cloud OnDemand
region.
Create a Panorama virtual machine. For the steps, refer to Add a Virtual Machine from a Template
in the vCloud Air Documentation Center. Configure the
CPU,
Memory
and
Storage
as follows:
Set the
CPU
and
Memory
based on how many firewalls Panorama will manage:
1-10 firewalls—4 CPUs and 4GB memory
11-50 firewalls—8 CPUs and 8GB memory
50-1,000 firewalls—8 CPUs and 16GB memory
Set the
Storage
to at least 52GB. For better logging and reporting performance, select the
SSD-Accelerated
option.
Panorama uses approximately 11GB for log storage. Increasing the disk size doesn’t increase the log storage capacity. To increase the log storage capacity,
Add a Virtual Disk to Panorama in vCloud Air.
Create vCloud Air NAT rules on the gateway to allow inbound and outbound traffic for the Panorama virtual appliance.
Refer to Add a NAT Rule
in the vCloud Air Documentation Center for the detailed instructions:
Add a NAT rule that allows Panorama to receive traffic from the firewalls and allows administrators to access Panorama.
Add a NAT rule that allows Panorama to retrieve updates from the Palo Alto Networks update server and to access the firewalls.
Create a vCloud Air firewall rule to allow inbound traffic on the Panorama virtual appliance.
Outbound traffic is allowed by default.
Refer to Add a Firewall Rule
in the vCloud Air Documentation Center for the detailed instructions.
Power on the Panorama virtual appliance if it isn’t already on.
Support for VMware Tools on the Panorama Virtual Appliance
VMware Tools is bundled with the software image (ovf) for the Panorama virtual appliance. The support for VMware Tools allows you to use the vSphere environment— vCloud Director and vCenter server—for the following:
View the IP address assigned to the Panorama management interface.
View resource utilization metrics on hard disk, memory, and CPU. You can use these metrics to enable alarms or actions on the vCenter server or vCloud Director.
Graceful shutdown and restart of Panorama using the power off function on the vCenter server or vCloud Director.
Enables a heartbeat mechanism between the vCenter server and Panorama for verifying that Panorama is functioning, or if the firewall/Panorama is rebooting. If the firewall goes into maintenance mode, heartbeats are disabled so that the vCenter server does not shut down the firewall. Disabling heartbeats allows the firewall to stay operational in maintenance mode when it cannot not send heartbeats to the vCenter server.