GlobalProtect Multiple Gateway Configuration

In the GlobalProtect Multiple Gateway Topology below, a second external gateway is added to the configuration. In this topology, you must configure an additional firewall to host the second GlobalProtect gateway. When you add the client configurations to be deployed by the portal, you can also specify different gateways for different client configurations or allow access to all gateways.
GlobalProtect Multiple Gateway Topology
gp-multi-gw.png
If a client configuration contains more than one gateway, the app attempts to connect to all gateways listed in its client configuration. The app uses priority and response time to determine the gateway to which it will connect. The app only connects to a lower priority gateway if the response time for the higher priority gateway is greater than the average response time across all gateways. For more information, see Gateway Priority in a Multiple Gateway Configuration.
  1. Create Interfaces and Zones for GlobalProtect.
    In this configuration, you must set up interfaces on each firewall hosting a gateway.
    Use the default virtual router for all interface configurations to avoid having to create inter-zone routing.
    On the firewall hosting the portal/gateway (gw1):
    • Select NetworkInterfacesEthernet, and then select ethernet1/2.
    • Configure ethernet1/2 as a Layer 3 interface with an IP address of 198.51.100.42, and then assign it to the l3-untrustSecurity Zone and the defaultVirtual Router.
    • Create a DNS “A” record that maps IP address 198.51.100.42 to gp1.acme.com.
    • Select NetworkInterfacesTunnel, and then Add the tunnel.2 interface. Add the interface to a new Security Zone called corp-vpn. Assign it to the defaultVirtual Router.
    • Enable User Identification on the corp-vpn zone.
    On the firewall hosting the second gateway (gw2):
    • Select NetworkInterfacesEthernet, and then select ethernet1/5.
    • Configure ethernet1/5 as a Layer 3 interface with an IP address of 192.0.2.4, and then assign it to the l3-untrustSecurity Zone and the defaultVirtual Router.
    • Create a DNS “A” record that maps IP address 192.0.2.4 to gp2.acme.com.
    • Select NetworkInterfacesTunnel, and then Add the tunnel.1 interface. Add the interface to a new Security Zone called corp-vpn. Assign it to the default Virtual Router.
    • Enable User Identification on the corp-vpn zone.
  2. Purchase and install a GlobalProtect subscription on each gateway if your end-users will be using the GlobalProtect app on their mobile endpoints or if you plan on using the HIP-enabled security policy.
    After you purchase the GlobalProtect subscription and receive your activation code, install the license on the firewall hosting the portal, as follows:
    1. Select DeviceLicenses.
    2. Select Activate feature using authorization code.
    3. When prompted, enter the Authorization Code, and then click OK.
    4. Verify that the license was activated successfully:
      Gateway_license.png
  3. On each firewall hosting a GlobalProtect gateway, create security policies.
    This configuration requires policy rules to enable traffic flow between the corp-vpn zone and the l3-trust zone to provide access to your internal resources (PoliciesSecurity).
  4. Use the following recommendations to obtain server certificates for each interface hosting your GlobalProtect portal and GlobalProtect gateways:
    On each firewall hosting a portal/gateway or gateway, select DeviceCertificate ManagementCertificates to manage certificates as follows:
    • Obtain a server certificate for the interface hosting portal/gw1. Because the portal and the gateway are on the same interface, you must use the same server certificate. The CN of the certificate must match the FQDN, gp1.acme.com. To enable endpoints to connect to the portal without receiving certificate errors, use a server certificate from a public CA.
    • Obtain a server certificate for the interface hosting gw2. Because this interface hosts only a gateway, you can use a self-signed certificate. The CN of the certificate must match the FQDN, gp2.acme.com.
  5. Define how you will authenticate users to the portal and the gateways.
    You can use any combination of certificate profiles and/or authentication profiles as necessary to ensure the security of your portal and gateways. Portals and individual gateways can also use different authentication schemes. See the following sections for step-by-step instructions:
    You must then reference the certificate profile and/or authentication profiles that you define in the portal and gateway configurations.
  6. Configure a GlobalProtect Gateway.
    The following example shows the configuration for gp1 and gp2, as seen in GlobalProtect Multiple Gateway Topology.
    On the firewall hosting gp1, select NetworkGlobalProtectGateways. Configure the gateway settings as follows:
    Interfaceethernet1/2
    IP Address198.51.100.42
    Server CertificateGP1-server-cert.pem issued by GoDaddy
    Tunnel Interfacetunnel.2
    IP Pool10.31.32.3 - 10.31.32.118
    On the firewall hosting gp2, select NetworkGlobalProtectGateways. Configure the gateway settings as follows:
    Interfaceethernet1/2
    IP Address192.0.2.4
    Server Certificateself-signed certificate, GP2-server-cert.pem
    Tunnel Interfacetunnel.1
    IP Pool10.31.33.3 - 10.31.33.118
  7. Configure the GlobalProtect Portals.
    Select NetworkGlobalProtectPortals. Configure the portal settings as follow:
    1. Set Up Access to the GlobalProtect Portal:
      Interfaceethernet1/2
      IP Address198.51.100.42
      Server CertificateGP1-server-cert.pem issued by GoDaddy
    2. Define the GlobalProtect Agent Configurations:
      The number of client configurations you create depends on your specific access requirements, including whether you require user/group-based policy and/or HIP-enabled policy enforcement.
  8. Deploy the GlobalProtect Agent Software.
    Select DeviceGlobalProtect Client.
    In this example, follow the procedure to Host App Updates on the Portal.
  9. Save the GlobalProtect configuration.
    Commit the configuration on the firewall hosting the portal and gateway(s).

Related Documentation