Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
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
Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
Convert your evaluation Panorama™ virtual appliance to
a production Panorama using VM Flex licensing.
If you have an evaluation Panorama™ virtual
appliance in Panorama mode configured with a local Log Collector,
you can convert it to a production Panorama with VM Flex licensing
by migrating the configuration from the evaluation Panorama to the production
Panorama and modifying as needed.
If a local Log Collector
is not configured, see Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector.
Logs ingested by the Log Collector on a
Panorama virtual appliance cannot be migrated.
If you need
to maintain access to the logs stored on your evaluation Panorama virtual
appliance, after you migrate the evaluation
Panorama configuration to the production Panorama, keep your
evaluation Panorama powered on to access the logs locally for the
remainder of the evaluation license lifetime. Adding the evaluation
Panorama to the production Panorama as a managed collector is not
supported.
- Plan the migration.
- Upgrade the software on the Panorama virtual appliance before you convert your evaluation Panorama virtual appliance to a production Panorama virtual appliance. Review the Compatibility Matrix for the minimum PAN-OS version required for your hypervisor. For important details about software versions, see Panorama, Log Collector, Firewall, and WildFire Version Compatibility.
- Schedule a maintenance window for the migration.
Obtain the Panorama serial number and auth code from your flexible VM-Series licensing deployment profile.- Log in to the Palo Alto Networks Customer Support Portal (CSP).Create a deployment profile that enables a Panorama virtual appliance.Provision Panorama to generate the a serial number for Panorama.Copy the Serial Number and Auth Code.Set up your production Panorama virtual appliance.
- Log in to the Palo Alto Networks CSP.Set Up the Panorama Virtual Appliance.Register the Panorama virtual appliance with the Palo Alto Networks Customer Support Portal (CSP).The Panorama serial number and authorization code you generated in the previous step.Install Content and Software Updates for Panorama.Activate the device management license on the Palo Alto Networks CSP for the production Panorama virtual appliance.
- Select AssetsDevices and locate your Panorama virtual appliance.In the Action column, click the pencil icon to edit the device licenses.Select Activate Auth-Code and enter the Authorization Code.Select Agree and Submit to activate the device management license.Export the Panorama configuration from the evaluation Panorama virtual appliance.
- Log in to the Panorama Web Interface.Select PanoramaSetupOperations.Click Export named Panorama configuration snapshot, select running-config.xml and click OK. Panorama exports the configuration to your client system as an XML file.Locate the running-config.xml file you exported and rename the XML file. This is required to import the configuration as Panorama does not support importing an XML file with the name running-config.xml.Load the Panorama configuration snapshot that you exported from the evaluation Panorama virtual appliance into the production Panorama virtual appliance.
- Log in to the Panorama Web Interface of the production Panorama virtual appliance.Select PanoramaSetupOperations.Click Import named Panorama configuration snapshot, Browse to the Panorama configuration file you exported from the Panorama virtual appliance, and click OK.Click Load named Panorama configuration snapshot, select the Name of the configuration you just imported, leave the Decryption Key blank (empty), and click OK. Panorama overwrites its current candidate configuration with the loaded configuration. Panorama displays any errors that occur when loading the configuration file.If errors occurred, save them to a local file. Resolve each error to ensure the migrated configuration is valid.Modify the configuration on the production Panorama virtual appliance.
- Select PanoramaSetupManagement.Edit the General Settings, modify the Hostname, and click OK.Edit the Management Interface Settings to configure the management IP address and click OK.The most efficient approach is to assign a new IP address to the evaluation Panorama virtual appliance and reuse its old IP address for the production Panorama virtual appliance. This ensures that the evaluation Panorama virtual appliance remains accessible and that firewalls can point to the production Panorama virtual appliance without you reconfiguring the Panorama IP address on each firewall.Remove the Log Collector configuration imported from the evaluation Panorama.
- Select PanoramaCollector Group and Delete all configured collector groups.
- Select PanoramaManaged Collectors and Delete all configured Log Collectors.
Select CommitCommit to Panorama and Commit your changes to the Panorama configuration.Reconfigure your Log Collectors and collector groups.You must add the managed collectors, collector group configuration, and log forwarding configurations you deleted in the previous step, as well as add the local Log Collector.- Configure a Managed Collector.Configure a Collector Group.Configure Log Forwarding to Panorama.Verify that the support and device management licenses are successfully activated.
- Select PanoramaLicenses and Retrieve license keys from license server.Verify the Device Management License displays the correct number of devices.Select PanoramaSupport and verify that the correct support Level and Expiry Date are displayed.Synchronize the production Panorama virtual appliance with the firewalls to resume firewall management.Complete this step during a maintenance window to minimize network disruption.
- On the production Panorama virtual appliance, select PanoramaManaged Devices and verify that the Device State column displays Connected for the firewalls.At this point, the Shared Policy (device groups) and Template columns display Out of sync for the firewalls.Push your changes to device groups and templates:
- Select CommitPush to Devices and Edit Selections.
- Select Device Groups, select every device group, Include Device and Network Templates, and click OK.
- Push your changes.
In the PanoramaManaged Devices page, verify that the Shared Policy and Template columns display In sync for the firewalls.