Upgrade Log Collectors When Panorama Is Not Internet-Connected
Table of Contents
10.0 (EoL)
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 Hyper-V
- Add a Virtual Disk to Panorama on KVM
- 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 Hyper-V
- Increase CPUs and Memory for Panorama on KVM
- Increase 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
-
- Panorama, Log Collector, Firewall, and WildFire Version Compatibility
- Install Updates for Panorama in an HA Configuration
- Install Updates for Panorama with an Internet Connection
- Install Updates for Panorama When Not Internet-Connected
- Install Updates Automatically for Panorama without an Internet Connection
- Migrate Panorama Logs to the New Log Format
-
- 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-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 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
-
- Add a Firewall as a Managed Device
-
- 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
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute Data to Managed Firewalls
-
- 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
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- 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 Commit Failures
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Downgrade from Panorama 10.0
End-of-Life (EoL)
Upgrade Log Collectors When Panorama Is Not Internet-Connected
Upgrade Log Collector software to PAN-OS® 10.0 and install
content updates using Panorama™ when Panorama is not connected to
the internet.
For a list of software or content updates
you can install on Log Collectors, see Supported
Updates.
If you are upgrading from PAN-OS 8.1, PAN-OS®
9.0 introduced a new log data format for local and Dedicated Log
Collectors. On your upgrade path to PAN-OS 10.0, existing log data
is automatically migrated to the new format when you upgrade to PAN-OS
9.0. During reformatting, log data is not visible in the ACC or Monitor tabs. Additionally,
new log data is not forwarded to Log Collectors until reformatting
is complete. While the reformatting takes place, new logs are written
to the firewall system disk and after the procedure is successfully
completed, the new logs are forwarded to the appropriate Log Collector.
You
must upgrade all Log Collectors in a collector group at the same
time to avoid losing log data loss. No log forwarding or log collection
occurs if the Log Collectors in a collector group are not all running
the same PAN-OS version. Additionally, the log data for the Log
Collectors in the collector group is not visible in the ACC or Monitor tabs
until all Log Collectors are running the same PAN-OS version. For example,
if you have three Log Collectors in a collector group and you upgrade
two of the Log Collectors, then no logs are forwarded to any Log
Collectors in the collector group.
Palo Alto Networks recommends
that you upgrade Log Collectors during a maintenance window. Due
to log format migration, the entire upgrade procedure takes an additional
number of hours depending on the amount of log data on the local
and Dedicated Log Collectors.
- Before you upgrade Log Collectors, ensure that
you are running the appropriate Panorama™ software release on the
Panorama management server.Palo Alto Networks® highly recommends that Panorama and Log Collectors run the same Panorama software release and that Panorama, Log Collectors, and all managed firewalls run the same content release version. For important software and content compatibility details, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.Panorama must be running the same (or later) software release as Log Collectors but must have the same or an earlier content release version:
- Software release version—If your Panorama management server is not already running the same or a later software release than the release to which you intend to update Log Collectors, then you must install the same or a later Panorama release on Panorama (see Install Content and Software Updates for Panorama) before you update any Log Collectors.
- Content release version—For content release versions, you should ensure that all Log Collectors are running the latest content release version or, at minimum, running a later version than you will install or that is running on Panorama; if not, then first update managed firewalls (using Panorama) and then update Log Collectors before you update the content release version on the Panorama management server (see Install Content and Software Updates for Panorama).
To check the software and content versions:- Panorama management server—To determine which software and content versions are running on the Panorama management server, log in to the Panorama web interface and go to General Information settings (Dashboard).
- Log Collectors—To determine which software and content versions are running on Log Collectors, log in to the CLI of each Log Collector and run the show system info command.
- Determine the Upgrade Path to
PAN-OS 10.0.You cannot skip the installation of any feature release versions in the path from the currently running PAN-OS version to PAN-OS 10.0. Review the known issues and changes to default behavior in the Release Notes and upgrade/downgrade considerations in the New Features Guide for each release through which you pass as part of your upgrade path.If upgrading more than one Log Collector, streamline the process by determining the upgrade paths for all Log Collectors you intend to upgrade before you start downloading images.
- Download the latest content and software updates to a
host that can connect and upload the files to Panorama either over
SCP or HTTPS.
- Use a host with internet access to log in to the Palo Alto Networks Customer Support web site.
- Download content updates:
- Click Dynamic Updates in the Resources section.
- Download the desired content updates and save the files to the host. Perform this step for each content type you will update.
- Download software updates:
- Return to the main page of the Palo Alto Networks® Customer Support website and click Software Updates in the Resources section.
- Review the Download column to determine which version to install. The update package filenames for M-Series appliances begin with “Panorama_m” followed by the release number. For example, to upgrade an M-Series appliance to Panorama 10.0.0, download the Panorama_m-10.0.0 image.You can quickly locate Panorama images by selecting Panorama M Images (for M-Series appliances) from the Filter By drop-down.
- Click the appropriate filename and save the file to the host.
- Install the latest content updates.If you need to install content updates, you must do so before you install software updates. Additionally, install content updates on firewalls first and then on Log Collectors before you update the content release version on Panorama.Install the Applications or Applications and Threats update first and then install any other updates (Antivirus, WildFire®, or URL Filtering) as needed, one at a time, and in any sequence.Regardless whether your subscription includes both Applications and Threats content, Panorama installs and needs only the Applications content. For details, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
- Log in to the Panorama Web Interface.
- Select PanoramaDevice DeploymentDynamic Updates.
- Click Upload, select the update Type, Browse to the appropriate content update file on the host, and click OK.
- Click Install From File, select the update Type, and select the File Name of the update you just uploaded.
- Select the Log Collectors.
- Click OK to start the installation.
- Repeat these steps for each content update.
- Upgrade the Log Collector to the PAN-OS releases along
your upgrade path to PAN-OS 10.0.If upgrading more than one Log Collector, streamline the process by determining the upgrade paths for all Log Collectors you intend to upgrade before you start downloading images.
- Upgrade Log Collectors When Panorama is Not Internet-Connected to PAN-OS 8.1.
- Upgrade Log Collectors When Panorama
is Not Internet-Connected to PAN-OS 9.0.PAN-OS 9.0 introduced a new log format. Logs are automatically migrated to the new format after you successfully upgrade the Log Collector to PAN-OS 9.0.Do not continue on your upgrade path until you verify the automatic log migration completed successfully.
- Upgrade Log Collectors When Panorama is Not Internet-Connected to PAN-OS 9.1.
- Upgrade the Log Collector to PAN-OS 10.0.
- Select PanoramaDevice DeploymentSoftware.
- Click Upload, Browse to the appropriate software update file on the host, and click OK.
- Click Install in the Action column for the release you just uploaded.
- Select the Log Collectors to upgrade.
- Select one of the following depending on your needs:
- Upload only to device (do not install).
- Reboot device after install.
- Click OK to start the upload or installation.
- Verify the software and content versions that are installed
on each Log Collector.Log in to the Log Collector CLI and enter the show system info operational command. The output will resemble the following:
sw-version: 10.0.0 app-version: 8270-6076 app-release-date: 2020/05/08 18:21:51