Configure Panorama Appliances in High Availability for Panorama
Managed Prisma Access
An overview and the task you perform to configure a Panorama Managed Prisma Access deployment in High Availability (HA).
Deploying Panorama appliances in a high availability (HA) configuration provides redundancy in case of a system or network failure and ensures that you have continuous connectivity to Prisma Access. In an HA configuration, one Panorama appliance peer is the active-primary and the other is the passive-secondary. In the event of a failover, the secondary peer becomes active and takes over the role of managing Prisma Access.
To simplify the HA set up, configure the Panorama appliances in HA after you purchase Prisma Access and Cortex Data Lake auth codes and components and associate the serial number of the primary Panorama appliance on which you plan to install the Cloud Services plugin with the auth codes, but before you Activate and Install Panorama Managed Prisma Access. However, you can also use this process to configure existing Panorama appliances that already have the plugin installed.
Whether you are just getting started with a new pair of Panorama appliances, or you have already set up your standalone Panorama appliance and completed the licensing and installation procedures, make sure to check the prerequisites before you enable HA:
- The Panorama appliance peers must be of the same form factor (hardware appliances of the same model or identical virtual appliances) and same OS version and must have the same set of licenses. The premium support license is required for Prisma Access and Cortex Data Lake.
- The serial number of the primary Panorama appliance is tied to your Prisma Access and Cortex Data Lake auth codes. If you have installed and set up the plugin on a standalone Panorama appliance, ensure that you use that Panorama appliance as the primary peer. If you need to assign this standalone peer as the secondary Panorama appliance, contact Palo Alto Networks support for assistance with transferring the license to the primary Panorama appliance peer before you continue.
If you disable HA for a Panorama pair and revert to a configuration where a single Panorama manages Prisma Access, you must re-verify your account to prevent errors when retrieving the status of Prisma Access components.
To set up your Panorama appliances in an HA configuration, complete the following steps.
- Set the primary Panorama appliance asPrimaryand the secondary Panorama appliance asSecondaryand be sure that the serial number of your primary Panorama appliance is tied to your Prisma Access and Cortex Data Lake auth codes.
- Make sure that the primary (active) and secondary (passive) Panorama appliances are synchronized and that the HA link state between them is up.
- Access theDashboardon the primary Panorama appliance and selectto display the HA widget.WidgetsSystemHigh Availability
- Sync to peer, clickYes, and wait for theRunning Configto displaySynchronized.
- Make sure that theLocalpeer isactive.
- Access theDashboardon the passive Panorama appliance and selectto display the HA widget.WidgetsSystemHigh Availability
- Verify that theRunning ConfigdisplaysSynchronized.
- Make sure that theLocalpeer ispassive.
- Install the Prisma Access components on the primary Panorama appliance.
- Log in to the primary Panorama appliance and select.PanoramaLicenses
- ClickRetrieve the license keys from license server.
- Activate and Install Panorama Managed Prisma Access, including generating a one-time password (OTP) and verifying your account.
- Check that HA is enabled.
- On the primary Panorama appliance, Access the CLI and enter the following operational command:tail follow yes mp-log plugin_cloud_services.log
- Find the following text in the log output, whereXis the serial number of the primary Panorama appliance andYis the serial number of the secondary Panorama appliance:2017-11-06 15:14:07.790 -0800 INFO: [hainfo] Sending update to CSP for HA peer serial information to https://updates.paloaltonetworks.com/licensesvc/licenseservice.asmx/PanoramaHAInfo (https://updates.paloaltonetworks.com/licensesvc/licenseservice.asmx/PanoramaHAInfo) 2017-11-06 15:14:07.791 -0800 INFO: [hainfo] Data string is primarypanoramasn=<varname>X</varname> &secondarypanoramasn=<varname>Y</varname> 2017-11-06 15:14:17.595 -0800 INFO: [hainfo] HTTP_CODE 200, RESPONSE: <?xml version="1.0" encoding="utf-8"?> <PanoramaHA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance (http://www.w3.org/2001/XMLSchema-instance)" xmlns:xsd="http://www.w3.org/2001/XMLSchema (http://www.w3.org/2001/XMLSchema)" xmlns="http://www.paloaltonetworks.com/ (http://www.paloaltonetworks.com/)"> <success>true</success> </PanoramaHA> 2017-11-06 15:14:17.596 -0800 INFO: [hainfo] Cached HA Peer's serial number <varname>Y</varname>
- Log in to the Customer Support Portal (CSP) and selectto verify that both Panorama peers are tied to your Prisma Access and Cortex Data Lake licenses.AssetsCloud Services
- Check the fields for the primary and secondary Panorama appliance.The Auth Code, Model Name, License Description, and Expiration Date fields should be the same for the primary and secondary Panorama appliance, because Palo Alto Networks has associated the Prisma Access license automatically to the secondary Panorama appliance.
- Log in to the secondary Panorama appliance and Activate and Install Panorama Managed Prisma Access.
- Commit your changes on the primary and secondary Panorama appliance.
- your changes.CommitCommit and Push
- Verify that the primary and secondary Panorama appliances are still in a synchronized state.
Recommended For You
Recommended videos not found.