Install Panorama on Google Cloud Platform
How to deploy a Panorama™ virtual appliance and a virtual
Dedicated Log Collector on Google Cloud Platform (GCP).
You can now deploy Panorama™ and a Dedicated
Log Collector on Google Cloud Platform (GCP). Panorama deployed
on GCP is Bring Your Own License (BYOL), supports all deployment
modes (Panorama, Log Collector, and Management Only), and shares
the same processes and functionality as the M-Series hardware appliances. For
more information on Panorama modes, see Panorama
Models.
To deploy the Panorama virtual appliance on
GCP, you need to build a custom image. To begin this process, you
must download the Panorama
tar.gz
from
the Palo Alto Networks Customer Support portal and upload it to
a GCP storage bucket. You can then create the custom image and use
the image to deploy the Panorama virtual appliance on GCP.- Download the Panorama virtual appliance image.
- Log in to the Palo Alto Networks Support Portal.
- Selectand filter byUpdatesSoftware UpdatesPanorama Base Images.
- Download the latest version of the Panorama on GCPtar.gzimage.
- Upload the Panorama virtual appliance image to the Google Cloud Platform.
- Log in to the Google Cloud Console.
- From theProducts and Servicesmenu, selectStorage.
- ClickCreate Bucket, configure the new storage bucket and clickCreate.
- Select the storage bucket you created in the previous step, clickUpload files, and select the Panorama virtual appliance image you downloaded.
- From theProducts and Servicesmenu, select.Compute EngineImages
- ClickCreate Imageand create the Panorama virtual appliance image:
- Namethe Panorama virtual appliance image.
- In theSourcefield, selectCloud Storage filefrom the drop-down menu.
- ClickBrowseand navigate to the storage bucket where you uploaded the Panorama virtual appliance image, andSelectthe uploaded image.
- Createthe Panorama virtual appliance image.
- Configure the Panorama virtual appliance.
- From theProducts and Servicesmenu and select theCompute Engine.
- ClickCreate Instanceto begin deploying the Panorama virtual appliance.
- Add a descriptiveNameto easily identify the Panorama virtual appliance.
- Select theRegionandZonewhere you want to deploy the Panorama virtual appliance.
- Allocate theMachine TypeandCustomizethe CPU cores, memory and CPU platform. Review the Setup Prerequisites for the Panorama Virtual Appliance for minimum resource requirements.If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you configure the appliance with the required resources during initial deployment. The Panorama virtual appliance does not remain in Log Collector mode if you resize the virtual machine after you deploy it, and this results in a loss of log data.The GCP zone selection determines the CPU platforms available to you. For more information, refer to Regions and Zones for details.
- Configure the Panorama boot disk.
- For theBoot Disk, clickand select the Panorama image file you uploaded in Step 2ChangeCustom image
- Configure the boot disk size. By default the system disk is 81GB but you can increase the system disk size to 224GB.(SD-WAN only) If you plan on managing your SD-WAN deployment using this Panorama virtual appliance in Panorama mode, you must increase the system disk size to 224GB. If you plan on managing your SD-WAN deployment in Management Only mode, you must add a 2TB logging disk.
- ClickSelectto save your configuration.
- UnderIdentity and API access, selectAllow full access to all Cloud APIs.
- UnderFirewall, selectAllow HTTPS traffic.
- ExpandManagement, security, disks, networking, sole tenancy
.
- Enable access to the serial port so you can manage the Panorama virtual appliance.
- SelectManagement.
- Enter the following name-value pair as Metadata:serial-port-enable true
- Reserve a static IP address for the management interface.Reserve static internal and external IP addresses for the management interface in the event that if the Panorama virtual appliance is rebooted, your managed devices do not lose connection to the Panorama virtual appliance when the IP addresses are reassigned.For more information on how to reserve IP addresses, refer to Reserving a Static Internal IP Address and Reserving a Static External IP Address.
- SelectNetworking.
- Editthe network interface.
- Select the Panorama virtual applianceNetwork.
- Select the Panorama virtual applianceSubnetwork. Instances in the same subnetwork will communicate with each other using their internal IP addresses.
- Set thePrimary internal IPaddress.
- Ephemeral (Automatic)— Automatically assign a primary internal IP address.
- Ephemeral (Custom)—Configure a custom IP range that GCP uses to assign a primary internal IP address.
- Reserve a static internal IP address—Manually configure a static primary internal IP address.
- Set theExternal IPaddress.
- Ephemeral—Automatically assign an external IP address from a shared IP pool.
- Select an existing reserved external IP address.
- Create IP address—Reserve an external IP address.
- SetIP forwardingtoOnto allow the Panorama virtual appliance to receive packets from non-matching destinations or source IP addresses.
- Configure the SSH key. You need an SSH key to access the Panorama virtual appliance CLI to configure the administrative user password after the initial deployment.
- SelectSecurity.
- Select theBlock project-wide SSH keysbox. Only instance keys are currently supported for logging in to the Panorama virtual appliance after initial deployment.
- Paste the SSH key in the comment box. For information on the correct SSH key format and how to generate SSH keys for GCP, refer to Managing SSH keys in Metadata.When generating the SSH key, save the private key in.ppkformat. The private key is required to log in to the Panorama virtual appliance after the initial deployment before you can configure the administrative password.
- (Panorama and Log Collector mode) Add additional storage for log collection. Repeat this step as needed to add additional virtual logging disks.If you intend to use the Panorama virtual appliance in Panorama mode or as a Dedicated Log Collector, add the virtual logging disks during initial deployment. By default, the Panorama virtual appliance is in Panorama mode for the initial deployment when you meet the Panorama mode resource requirements and have added at least one virtual logging disk. Otherwise, the Panorama virtual appliance defaults to Management Only mode in which you can manage devices and Dedicated Log Collectors, and cannot collect logs locally.The Panorama virtual appliance on GCP only supports 2TB logging disks, and in total supports up to 24TB of log storage. You are unable to add a logging disk smaller than 2TB, or a logging disk with a size not divisible by the 2TB logging disk requirement. The Panorama virtual appliance partitions logging disks larger than 2TB into 2TB partitions.
- Select.DisksAdd new disk
- Enter theName.
- Expand theTypedrop-down menu and select the desired type.
- For theSource type, selectBlank disk.
- For theMode, selectRead/write.
- Select theDeletion ruleto configure whether to delete the virtual logging disk if the Panorama virtual appliance instance is deleted. To
- Set theSize (GB)of the virtual logging disk.
- Set your preferredEncryptionsolution for the data on the virtual logging disk.
- ClickDone.
- Createthe Panorama virtual appliance. The Panorama virtual appliances takes roughly 10 minutes to boot up after initial deployment.
- Configure a new administrative password for the Panorama virtual appliance.You must configure a unique administrative password before you can access the web interface of the Panorama virtual appliance. To access the CLI, use the private key to launch the Panorama virtual appliance.
- If you have an SSH service installed on your computer:
- Enter the following command to log into the Panorama virtual appliance:ssh -i<private_key.ppk>admin@<public-ip_address>
- Configure a new password using the following commands and follow the onscreen prompts:admin>configureadmin#set mgt-config users admin password
- If you have a BYOL that you need to, set the DNS server IP address so that the Panorama virtual appliance can access the Palo Alto Networks licensing server. Enter the following command to set the DNS server IP address:admin#set deviceconfig system dns-setting servers primary<ip_address>
- Commit your changes:admin#commit
- Terminate the SSH session.
- If you are using PuTTY to SSH into the Panorama virtual appliance:
- If you are using an existing key pair and have the.ppkfile available, continue to Step 11.3. If you created a new key pair or only have the.pemfile of the existing key pair, open PuTTYgen andLoadthe.pemfile.
- Save the private keyto a local accessible destination.
- Open PuTTY and selectandSSHAuthBrowsefor the.ppkfile saved in the previous step.
- SelectSessionsand enter the public IP address of the Panorama virtual appliance. ThenOpenand clickYeswhen the security prompt appears.
- Login as admin when prompted.
- Configure a new password using the following commands and follow the on screen prompts:admin>configureadmin#set mgt-config users admin password
- Set the DNS server IP address so that the Panorama virtual appliance can access the Palo Alto Networks licensing server. Enter the following command to set the DNS server IP address:admin#set deviceconfig system dns-setting servers primary<ip_address>
- Commit your changes with the command:admin#commit
- Terminate the SSH session.
- Activate the device management license and support license on the Panorama virtual appliance.
- Complete configuring the Panorama virtual appliance for your deployment needs.
- (Management Only mode) Set up a Panorama Virtual Appliance in Management Only Mode.
- (Log Collector mode) Begin at Step 6 to Switch from Panorama mode to Log Collector mode.Enter the Public IP address of the Dedicated Log Collector when you Add the Log Collector as a managed collector to the Panorama management server. You cannot specify theIP Address,Netmask, orGateway.
- (Panorama and Management Only mode) Configure a Managed Collector to add a Dedicated Log Collector to the Panorama virtual appliance. Management Only mode does not support local log collection, and requires a Dedicated Log Collector to store managed device logs.
Recommended For You
Recommended Videos
Recommended videos not found.