GlobalProtect
Gateway Priority in a Multiple Gateway Configuration
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
9.1 (EoL)
- 10.1 & Later
- 9.1 (EoL)
-
-
-
- Deploy App Settings in the Windows Registry
- Deploy App Settings from Msiexec
- Deploy Scripts Using the Windows Registry
- Deploy Scripts Using Msiexec
- SSO Wrapping for Third-Party Credential Providers on Windows Endpoints
- Enable SSO Wrapping for Third-Party Credentials with the Windows Registry
- Enable SSO Wrapping for Third-Party Credentials with the Windows Installer
-
- Mobile Device Management Overview
- Set Up the MDM Integration With GlobalProtect
- Qualified MDM Vendors
-
- Remote Access VPN (Authentication Profile)
- Remote Access VPN (Certificate Profile)
- Remote Access VPN with Two-Factor Authentication
- Always On VPN Configuration
- Remote Access VPN with Pre-Logon
- GlobalProtect Multiple Gateway Configuration
- GlobalProtect for Internal HIP Checking and User-Based Access
- Mixed Internal and External Gateway Configuration
- Captive Portal and Enforce GlobalProtect for Network Access
-
-
- End User Experience
- Management and Logging in Panorama
-
- View a Graphical Display of GlobalProtect User Activity in PAN-OS
- View All GlobalProtect Logs on a Dedicated Page in PAN-OS
- Event Descriptions for the GlobalProtect Logs in PAN-OS
- Filter GlobalProtect Logs for Gateway Latency in PAN-OS
- Restrict Access to GlobalProtect Logs in PAN-OS
- Forward GlobalProtect Logs to an External Service in PAN-OS
- Configure Custom Reports for GlobalProtect in PAN-OS
- Monitoring and High Availability
-
- About GlobalProtect Cipher Selection
- Cipher Exchange Between the GlobalProtect App and Gateway
-
- Reference: GlobalProtect App Cryptographic Functions
-
- Reference: TLS Ciphers Supported by GlobalProtect Apps on macOS Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Windows 10 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Windows 7 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Android 6.0.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on iOS 10.2.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Chromebooks
- Ciphers Used to Set Up IPsec Tunnels
- SSL APIs
-
6.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
-
- Download and Install the GlobalProtect App for Windows
- Use Connect Before Logon
- Use Single Sign-On for Smart Card Authentication
- Use the GlobalProtect App for Windows
- Report an Issue From the GlobalProtect App for Windows
- Disconnect the GlobalProtect App for Windows
- Uninstall the GlobalProtect App for Windows
- Fix a Microsoft Installer Conflict
-
- Download and Install the GlobalProtect App for macOS
- Use the GlobalProtect App for macOS
- Report an Issue From the GlobalProtect App for macOS
- Disconnect the GlobalProtect App for macOS
- Uninstall the GlobalProtect App for macOS
- Remove the GlobalProtect Enforcer Kernel Extension
- Enable the GlobalProtect App for macOS to Use Client Certificates for Authentication
-
6.1
- 6.1
- 6.0
- 5.1
-
6.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
End-of-Life (EoL)
Gateway Priority in a Multiple Gateway Configuration
To enable secure access for your mobile workforce no
matter where they are located, you can strategically deploy additional
Palo Alto Networks next-generation firewalls and configure them
as GlobalProtect gateways. To determine the preferred gateway to
which your apps connect, add the gateways to a portal agent configuration,
and then assign each gateway a connection priority. See Define
the GlobalProtect Agent Configurations.
If a GlobalProtect portal agent configuration contains more than
one gateway, the app attempts to communicate with all gateways listed
in its agent configuration. The app uses the priority and response
time to determine the gateway to which to connect. With GlobalProtect
app 4.0.2 and earlier releases, the app connects to a lower priority
gateway only if the response time for the higher priority gateway
is greater than the average response time across all gateways.
For example, consider the following response times for gw1 and
gw2:
Name | Priority | Response Time |
---|---|---|
gw1 | Highest | 80 ms |
gw2 | High | 25 ms |
The app determines that the response time for the gateway with
the highest priority (higher number) is greater than the average response
time for both gateways (52.5 ms) and, as a result, connects to gw2.
In this example, the app did not connect to gw1 even though it had
a higher priority because a response time of 80 ms was higher than
the average for both.
Now consider the following response times for gw1, gw2, and a
third gateway, gw3:
Name | Priority | Response Time |
---|---|---|
gw1 | Highest | 30 ms |
gw2 | High | 25 ms |
gw3 | Medium | 50 ms |
In this example, the average response time for all gateways is
35 ms. The app would then evaluate which gateways responded faster
than the average response time and see that gw1 and gw2 both had
faster response times. The app would then connect to whichever gateway
had the highest priority. In this example, the app connects to gw1
because gw1 has the highest priority of all the gateways with response
times below the average.
In addition to gateway priority, you can add one or more source
regions to an external gateway configuration. GlobalProtect recognizes
the source region and only allows uses to connect to gateways that
are configured for that region. Regarding gateway selection, source
region is considered first, then the gateway priority.
In GlobalProtect app 4.0.3 and later releases, the GlobalProtect
app prioritizes the gateways assigned highest, high, and medium priority
ahead of gateways assigned a low or lowest priority regardless of
response time. The GlobalProtect app then appends any gateways assigned
a low or lowest priority to the list of gateways. This ensures that
the app first attempts to connect to the gateways that you configure
with a higher priority.