What Settings Don’t Sync in Active/Active HA?

You must configure all management settings individually on each firewall, including:

You must activate the Virtual Systems license on each firewall in the pair to increase the number of virtual systems beyond the base number provided by default on PA-3200 Series, PA-5200 Series, and PA-7000 Series firewalls.

You must also enable Multi Virtual System Capability on each firewall (DeviceSetupManagementGeneral Settings).

Set the following Panorama settings on each firewall (DeviceSetupManagementPanorama Settings).

With software updates, you can either download and install them separately on each firewall, or download them on one peer and sync the update to the other peer. You must install the update on each peer (DeviceSoftware).

With GlobalProtect app updates, you can either download and install them separately on each firewall, or download them to one peer and sync the update to the other peer. You must activate separately on each peer (DeviceGlobalProtect Client).

With content updates, you can either download and install them separately on each firewall, or download them on one peer and sync the update to the other peer. You must install the update on each peer (DeviceDynamic Updates).

All Ethernet interface configuration settings sync except for the IP address (NetworkInterfaceEthernet).

All Loopback interface configuration settings sync except for the IP address (NetworkInterfaceLoopback).

All Tunnel interface configuration settings sync except for the IP address (NetworkInterfaceTunnel).

Each peer must have a unique LACP System ID in an active/active deployment (NetworkInterfaceEthernetAdd Aggregate GroupSystem Priority).

All VLAN interface configuration settings sync except for the IP address (NetworkInterfaceVLAN).

Virtual router configuration synchronizes only if you have enabled VR Sync (DeviceHigh AvailabilityActive/Active ConfigPacket Forwarding). Whether or not to do this depends on your network design, including whether you have asymmetric routing.

IPSec tunnel configuration synchronization is dependent on whether you have configured the Virtual Addresses to use Floating IP addresses (DeviceHigh AvailabilityActive/Active ConfigVirtual Address). If you have configured a floating IP address, these settings sync automatically. Otherwise, you must configure these settings independently on each peer.

GlobalProtect portal configuration synchronization is dependent on whether you have configured the Virtual Addresses to use Floating IP addresses (NetworkGlobalProtectPortals). If you have configured a floating IP address, the GlobalProtect portal configuration settings sync automatically. Otherwise, you must configure the portal settings independently on each peer.

GlobalProtect gateway configuration synchronization is dependent on whether you have configured the Virtual Addresses to use Floating IP addresses (NetworkGlobalProtectGateways). If you have configured a floating IP address, the GlobalProtect gateway configuration settings sync automatically. Otherwise, you must configure the gateway settings independently on each peer.

QoS configuration synchronizes only if you have enabled QoS Sync (DeviceHigh AvailabilityActive/Active ConfigPacket Forwarding). You might choose not to sync QoS setting if, for example, you have different bandwidth on each link or different latency through your service providers.

No LLDP state or individual firewall data is synchronized in an active/active configuration (NetworkNetwork ProfilesLLDP).

No BFD configuration or BFD session data is synchronized in an active/active configuration (NetworkNetwork ProfilesBFD Profile).

IKE gateway configuration synchronization is dependent on whether you have configured the Virtual Addresses to use floating IP addresses (NetworkIKE Gateways). If you have configured a floating IP address, the IKE gateway configuration settings sync automatically. Otherwise, you must configure the IKE gateway settings independently on each peer.

The master key must be identical on each firewall in the HA pair, but you must manually enter it on each firewall (DeviceMaster Key and Diagnostics).

Before changing the master key, you must disable config sync on both peers (DeviceHigh AvailabilityGeneralSetup and clear the Enable Config Sync check box) and then re-enable it after you change the keys.

Log data, reports, and dashboard data and settings (column display, widgets) are not synced between peers. Report configuration settings, however, are synced.

Rule usage data, such as hit count, Created, and Modified Dates, are not synced between peers. You need to log in to the each firewall to view the policy rule hit count data for each firewall or use Panorama to view information on the HA firewall peers.

Certificates used for device management or for syslog communication over SSL don’t synchronize with an HA peer.

SSL/TLS Service Profile for Device Management doesn’t synchronize with an HA peer.