Install Panorama on Azure
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 Azure
How to deploy a Panorama™ virtual appliance and a virtual
Dedicated Log Collector on Microsoft Azure.
You can now deploy Panorama™ and a Dedicated
Log Collector on Microsoft Azure. Panorama deployed on Azure 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.
- Log into to the Microsoft Azure portal.
- Set up the virtual network for your network needs.Whether you launch the Panorama virtual appliance in an existing virtual network or you create a new virtual network, the Panorama virtual appliance must be able to receive traffic from other instances in the virtual network and perform inbound and outbound communication between the virtual network and the internet as needed.Refer to the Microsft Azure Virtual Network documentation for more information.
- Create a Virtual Network or use an existing virtual network.
- Verify that the network and security components are appropriately defined.
- Create a NAT gateway if you want to enable only outbound internet access for the subnet to which the Panorama virtual appliance belongs.
- Create subnets. Subnets are segments of the IP address range assigned to the VNet in which you can launch Microsoft Azure 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 VNet 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 VNet to manage VNet 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 (port443) 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.
- Deploy the Panorama virtual appliance.
- In the Azure Dashboard, selectVirtual machinesandAdda new virtual machine.
- Search for Palo Alto Networks and select the latest Panorama virtual appliance image.
- Createthe Panorama virtual appliance.
- Configure the Panorama virtual appliance.
- Select your AzureSubscription.
- Select the AzureResource Groupto contain all your Azure instance resources.
- Enter aVirtual machine namefor the Panorama virtual appliance.
- Select theRegionfor the Panorama virtual appliance to be deployed in.
- Select theImageused to deploy the Panorama management server.Browse all public and private imagesto deploy the Panorama management server from the Panorama image on the Azure marketplace.
- Configure the Panorama virtual appliance size. Review the Setup Prerequisites for the Panorama Virtual Appliance for sizing 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.
- Configure the unique Panorama virtual appliance administrator credentials.You must configure a unique administrative password before you can access the web interface and CLI of the Panorama virtual appliance.
- Enter aUsernamefor the Panorama virtual appliance administrator. To ensure that your username is secure, admin is not a valid entry.
- Enter aPasswordor copy and paste anSSH public keyfor securing administrative access to the Panorama virtual appliance.
You must enable SSH key authentication if you plan to use this instance of the Panorama virtual appliance in FIPS-CC operational mode. Although you can deploy the Panorama virtual appliance using a username and password, you will be unable to authenticate using the username and password after changing the operational mode to FIPS-CC. After resetting to FIPS-CC mode, you must use the SSH key to log in and can then configure a username and password that you can use for subsequently logging in to the Panorama web interface. For details on creating the SSH key, refer to the Azure documentation. - Configure the Panorama virtual appliance instanceNetworking
- Select an existingVirtual networkor create a new virtual network.
- Configure theSubnet. The subnet is dependent on the virtual network you selected or created in the previous step. If you selected an existing virtual network, you can choose one of the subnets for the selected virtual network.
- Select an existingPublic IP addressor create a new one. This creates the management interface used to access your Panorama virtual appliance.
- Select an existingNIC network security groupor create a new security group. Network security groups control traffic to the virtual machine. Make sure that HTTPS and SSH are allowed for the Inbound rules.
- Configure the instanceManagementsettings.
- Select whether to enableAuto-shutdown. Auto-shutdown allows you to configure a daily time to automatically shut down the virtual machine that you disable auto-shutdown to avoid the possibility that a new public IP address gets assigned to the virtual machine, that logs are dropped, that logs are not or that you are unable to manage your firewalls while the Panorama virtual appliance is shut down.
- Select whether to enable bootMonitoring. Select the Diagnostic storage account if enabled. Monitoring automatically sends boot-up diagnostic logs to your Diagnostics storage account. For more information, see Overview of Monitoring in Microsoft Azure.
- Configure any other settings as needed.
- Review the summary, accept the terms of use and privacy policy, andCreatethe Panorama virtual appliance.
- Verify that you the Panorama virtual appliance has been successfully deployed.
- Selectand select the resource group containing the Panorama virtual appliance.DashboardResource Groups
- Under Settings, selectDeploymentsfor the virtual machine deployment status.It takes about 30 minutes to deploy the Panorama virtual appliance. Launching the Panorama virtual appliance may take longer depending on the resources configured for the virtual machine. Microsoft Azure does not permit the ICMP protocol to test whether it deployed successfully.If you plan to use the Panorama virtual appliance as a Dedicated Log Collector, ensure that you correctly configured the appliance the required resources. 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.
- Configure a static Public IP address.
- On the Azure portal, selectVirtual machinesand select the Panorama virtual machine.
- SelectOverviewand click thePublic IP address.
- Under Assignment, selectStaticandSavethe new IP address configuration.
- Log in to the web interface of the Panorama virtual appliance.
- On the Azure portal, inAll Resources, select the Panorama virtual appliance and view the public IP address located in the Overview section.
- Use a secure (https) connection from your web browser to log in to the Panorama virtual appliance using the public IP address.
- Enter the username and password of the Panorama virtual appliance. You are prompted with a certificate warning. Accept the certificate warning and continue to the web page.
- 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.
- Add a Virtual Disk to Panorama on Azure as needed.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.