Install Panorama on Oracle Cloud Infrastructure (OCI)
Install the Panorama virtual appliance on Oracle Cloud Infrastructure (OCI).
Create a Panorama™ virtual appliance instance on Oracle Cloud Infrastructure (OCI). An OCI instance supports a single NIC by default. You must manually upload a Panorama virtual appliance qcow2 image downloaded from the Palo Alto Networks Customer Supported Portal (CSP) to OCI to successfully install the Panorama virtual appliance on OCI.
A Panorama virtual appliance deployed on OCI 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.
A machine running a Linux operating system is required successfully install the Panorama on OCI. To successfully install Panorama on OCI, you must generate a
.pubkey using OpenSSH. Additionally, you can only use a Linux machine to log into the Panorama CLI for the initial network configuration.
Review the Setup Prerequisites for the Panorama Virtual Appliance to determine the virtual resources required for your needs. The virtual resources requirement for the Panorama virtual appliance is based on the total number of firewalls managed by the Panorama virtual appliance and the required Logs Per Second (LPS) for forwarding logs from your managed firewalls to your Log Collector.
Under-provisioning the Panorama virtual appliance will impact management performance. This includes the Panorama virtual appliance becoming slow or unresponsive depending on how under-provisioning the Panorama virtual appliance is.
- Log in to the Oracle Cloud Infrastructure console.
- Set up the Virtual Cloud Network (VCN) for your network needs.Whether you launch the Panorama virtual appliance in an existing VCN or you create a new VCN, the Panorama virtual appliance must be able to receive traffic from other instances in the VCN and perform inbound and outbound communication between the VCN and the internet as needed.Refer to the OCI VCN documentation for more information.
- Configure a VCN or use an existing VCN.
- Verify that the network and security components are appropriately defined.
- Create an internet gateway to enable internet access to the subnet of your Panorama virtual appliance. Internet access is required to install software and content updates, activate licenses, and leverage Palo Alto Networks cloud services. Otherwise, you must manually install updates and activate licenses.If the Panorama virtual appliance instance is part of a private subnet, you can configure a NAT gateway to enable only outbound internet access for the subnet.
- Create subnets. Subnets are segments of the IP address range assigned to the VCN in which you can launch OCI instances. It is recommended that the Panorama virtual appliance belong to the management subnet so that you can configure it to access the internet if needed.
- Add routes to the route table for a private subnet to ensure traffic can be routed across subnets in the VCN and from the internet if applicable.Ensure you create routes between subnets to allow communication between:
- Panorama, managed firewalls, and Log Collectors.
- (Optional) Panorama and the internet.
- Ensure that the following ingress security rules are allowed for the VCN to manage VCN traffic. The ingress traffic source for each rule is unique to your deployment topology.See Ports Used for Panorama for more information.
- Allow SSH (port22) traffic to enable access to the Panorama CLI.
- Allow HTTPS (port443and28270) traffic to enable access to the Panorama web interface.
- Allow traffic on port3978to enable communication between Panorama, manage firewalls, and managed Log Collectors. This port is also used by Log Collectors to forward logs to Panorama.
- Allow traffic on port28443to enable managed firewalls to get software and content updates from Panorama.
- SelectandComputeInstancesCreate Instance.
- Enter a descriptiveNamefor the Panorama virtual appliance image.
- Select theAvailability domain.
- Select the custom Panorama image.
- Under Image and shape, selectChange Image.
- For the Image Source, selectCustom Image.
- Select the custom Panorama image you created.
- Select Image.
- Configure the instance resources.
- Under Image and shape, selectChange Shape.
- Select the shape with number of CPUs, amount of RAM, and number of interfaces you require.
- Select Shape.
- Configure the instance Networking settings.
- For the Network,Select existing virtual cloud networkand select the VCN.
- For the Subnet,Select existing subnetand select the subnet.It is recommended to deploy the Panorama virtual appliance instance in a management subnet to safely allow internet access if needed.
- (Optional) For the Public IP Address, selectAssign a public IPv4 addressif you want to make the Panorama virtual appliance accessible from outside the VCN.
- Configure the Panorama virtual appliance instance boot volume.
- For the Boot volume,specify a custom boot volume size.
- For the Boot volume size, enter81.
- Createthe Panorama virtual appliance image.
- Log in to the Panorama virtual appliance CLI from the OCI console.
- In the OCI console, selectInstancesand select the Panorama virtual appliance instance.
- SelectConsole ConnectionandCreate Console Connection.
- SelectUpload public key files (.pub)and upload the public SSH key you generated toCreate Console Connection.
- In the Instance Details screen, expand the Console Connection options andCopy Serial Connection for Linux/Mac.
- On your Linux machine, open a terminal and paste the serial connection.
- Verify you can log in to the Panorama web interface.If you cannot log in to the Panorama web interface, review your route table and VCN security rules to ensure the correct routes and security rules are created.
- Configure a new administrative password for the Panorama virtual appliance.You must configure a unique administrative password before you can access the web interface or CLI of the Panorama virtual appliance. The new password must be a minimum of eight characters and include a minimum of one lowercase character, one uppercase character, and one number or special character.When you first log in to the Panorama CLI, you are prompted to enter theOld Passwordand theNew Passwordfor theadminuser before you can continue.
- Configure the system IP address settings for the Panorama virtual appliance.
- Configure the initial network settings for the Panorama virtual appliance.admin>configureadmin#set deviceconfig system type staticadmin#set deviceconfig system ip-address <instance-private-IP address> netmask <netmask> default-gateway <default-gateway-IP>admin#set deviceconfig system dns-setting servers primary <primary-dns-IP>admin#set deviceconfig system dns-setting servers secondary <secondary-dns-IP>admin#commitVerify you can log in to the Panorama web interface.If you cannot log in to the Panorama web interface, review your route table and VCN security rules to ensure the correct routes and security rules are created.Register the Panorama virtual appliance and activate the device management license and support licenses.
Complete configuring the Panorama virtual appliance for your deployment needs.
- (VM Flex Licensing Only) Provisioning the Panorama Virtual Appliance Serial Number.When leveraging VM Flex licensing, this step is required to generate the Panorama virtual appliance serial number needed to register the Panorama virtual appliance with the Palo Alto Networks Customer Support Portal (CSP).
- You must register the Panorama virtual appliance using the serial number provided by Palo Alto Networks in the order fulfillment email.This step is not required when leveraging VM Flex licensing as the serial number is automatically registered with the CSP when generated.
- For Panorama in Log Collector Mode.
- Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Log Collector mode.
- Begin at Step 6 to switch 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.
- For Panorama in Panorama mode.
- Adding at least one virtual logging disk is required before you can change the Panorama virtual appliance to Panorama mode.
- For Panorama in 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 VideosRecommended videos not found.