Install Panorama on Oracle Cloud Infrastructure (OCI)
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
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
.pub
key 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 Palo Alto Networks Panorama image.See Upload the Panorama Virtual Appliance Image to OCI to upload and maintain your own Panorama virtual applianceCustom Imageon OCI.
- Under Image and shape, selectChange Image.
- For the Image Source, selectPartner Image.If you maintain your own Panorama virtual appliance image, selectCustom Imageinstead and select the Panorama virtual appliance image you uploaded to OCI.
- Search forPalo Alto Networks Panoramaand select (check) the image.Skip this step if you selectedCustom Imagein the previous step.PAN-OS 10.2.0 is the default PAN-OS version.
- Select Image.
- Configure the instance resources.Refer to the Setup Prerequisites for the Panorama Virtual Appliance for more information for the minimum resources required based on your Panorama usage needs.
- 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.
- 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.
- (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.
Complete configuring the Panorama virtual appliance for your deployment needs.- 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