Verify Panorama Port Usage
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
Verify Panorama Port Usage
To ensure that Panorama can communicate with managed
firewalls, Log Collectors, and WildFire appliances and appliance
clusters, and its high availability (HA) peer, use the following
table to verify the ports that you must open on your network. Panorama
uses TCP protocol for port communications.
By default, Panorama uses the management (MGT) interface to manage devices
(firewalls, Log Collectors, and WildFire appliances and appliance
clusters), collect logs, communicate with Collector Groups, and
deploy software and content updates to devices. However, you can
optionally assign the log collection and Collector Group communication
functions to the Eth1 or Eth2 interfaces on an M-700, M-600, M-500,
M-300, or M-200 appliance running Panorama 6.1 through 7.1. If the
appliance runs Panorama 8.0 or a later release, you can assign any
function to the Eth1, Eth2, Eth3, Eth4, or Eth5 interfaces on the
M-700, M-600, M-500, M-300, or M-200 appliance. The ports listed
in the following table apply regardless of which function you assign
to which interface. For example, if you assign log collection to
MGT and assign Collector Group communication to Eth2, then MGT will
use port 3978 and Eth2 will use port 28270. (The Panorama virtual
appliance can only use the MGT interface for all these functions.)
Communicating Systems
& Direction of Connection Establishment | Ports Used in Panorama 5.x | Ports Used in Panorama 6.x
to 7.x | Ports Used in Panorama
8.x and later | Description |
---|---|---|---|---|
Panorama and Panorama (HA) Direction:
Each peer initiates its own connection to the other | 28 | 28 | 28 | For HA connectivity and synchronization
if encryption is enabled. Used for communication between Log
Collectors in a Collector Group for log distribution. |
Panorama and Panorama (HA) Direction:
Each peer initiates its own connection to the other | 28769 and 28260 (5.1) 28769 and 49160 (5.0) | 28260 and 28769 | 28260 and 28769 | For HA connectivity and synchronization
if encryption is not enabled. |
Panorama and managed firewalls Direction:
Initiated by the firewall | 3978 | 3978 | 3978 | A bi-directional connection where the logs are
forwarded from the firewall to Panorama; and configuration changes
are pushed from Panorama to the managed firewalls. Context switching commands
are sent over the same connection. |
Panorama and Log Collector Direction:
Initiated by the Log Collector | 3978 | 3978 | 3978 | For management and log collection/reporting. Used
for communication between the local Log Collector on a Panorama
in Panorama mode, and for communicating with Log Collectors in a
distributed log collection deployment. |
Panorama and managed devices (firewalls,
Log Collectors, and WildFire appliances and appliance clusters) Direction:
| 3978 | 3978 | 28443 | Devices running PAN-OS 8.x or later releases
use port 28443 to retrieve software and content update files from Panorama. Devices
running 7.x or earlier releases do not retrieve update files from Panorama;
Panorama pushes the update files to the devices over port 3978. Support
for Panorama management of WildFire appliances and appliance clusters
requires PAN-OS 8.0.1 or later installed on the managed WildFire
appliances. We recommend that Panorama runs 8.0.1 or later to manage
WildFire appliances and appliance clusters. |
Log Collector to Log Collector Direction:
Each Log Collector initiates a connection to the other Log Collectors
in the Collector Group | 49190 | 28270 | 28270 | For distributing blocks and
all binary data between Log Collectors. |
Panorama to Strata Logging Service | NA | NA | 444 Version 8.0.5 and later. | For setting up a secure communication channel with the Strata Logging Service . The managed firewalls use port 3978 to
communicate with Strata Logging Service . |