Because the GlobalProtect configuration that the portal delivers to the satellites includes the list of gateways the satellite can connect to, it is a good idea to configure the gateways before configuring the portal.
After you have completed the
Prerequisite Tasks, configure each GlobalProtect gateway to participate in the LSVPN as follows:
Configure the Gateway for LSVPN
Add a gateway.
Network > GlobalProtect > Gateways
screen, enter a
for the gateway. The gateway name should have no spaces and, as a best practice, should include the location or other descriptive information to help users and administrators identify the gateway.
) Select the virtual system to which this gateway belongs from the
Specify the network information that enables satellite devices to connect to the gateway.
If you haven’t created the network interface for the gateway, see
Create Interfaces and Zones for the LSVPN for instructions.
that satellites will use for ingress access to the gateway.
for gateway access.
Click OK to save changes.
On the GlobalProtect Gateway Configuration dialog, select Authentication and then configure any of the following:
To secure communication between the gateway and the satellites, select the
SSL/TLS Service Profile
for the gateway.
To specify the authentication profile to use to authenticate satellites,
a Client Authentication. Then, enter a
to identify the configuration, select
to apply the configuration to all satellites, and specify the
to use to authenticate the satellite. You can also select a
for the gateway to use to authenticate satellite devices attempting to establish tunnels.
Configure the tunnel parameters and enable tunneling.
On the GlobalProtect Gateway Configuration dialog, select
Satellite > Tunnel Settings.
check box to enable tunneling.
you defined to terminate VPN tunnels established by the GlobalProtect satellites when you performed the task to
Create Interfaces and Zones for the LSVPN.
) If you want to preserve the Type of Service (ToS) information in the encapsulated packets, select
If there are multiple sessions inside the tunnel (each with a different TOS value), copying the TOS header can cause the IPSec packets to arrive out of order.
) Enable tunnel monitoring.
Tunnel monitoring enables satellites to monitor its gateway tunnel connection, allowing it to failover to a backup gateway if the connection fails. Failover to another gateway is the only type of tunnel monitoring profile supported with LSVPN.
address the satellites should use to determine if the gateway is active. Alternatively, if you configured an IP address for the tunnel interface, you can leave this field blank and the tunnel monitor will instead use the tunnel interface to determine if the connection is active.
Tunnel Monitor Profile
drop-down (this is the only supported tunnel monitor profile for LSVPN).
Select the IPSec Crypto profile to use when establishing tunnel connections.
The profile specifies the type of IPSec encryption and the authentication method for securing the data that will traverse the tunnel. Because both tunnel endpoints in an LSVPN are trusted firewalls within your organization, you can typically use the default (predefined) profile, which uses ESP as the IPSec protocol, group2 for the DH group, AES-128-CBC for encryption, and SHA-1 for authentication.
IPSec Crypto Profile
to use the predefined profile or select
New IPSec Crypto Profile
to define a new profile. For details on the authentication and encryption options, see
Define IPSec Crypto Profiles.
Configure the network settings to assign the satellites during establishment of the IPSec tunnel.
You can also configure the satellite to push the DNS settings to its local clients by configuring a DHCP server on the firewall hosting the satellite. In this configuration, the satellite will push DNS settings it learns from the gateway to the DHCP clients.
On the GlobalProtect Gateway Configuration dialog, select
Satellite > Network Settings.
) If clients local to the satellite need to resolve FQDNs on the corporate network, configure the gateway to push DNS settings to the satellites in one of the following ways:
If the gateway has an interface that is configured as a DHCP client, you can set the
to that interface and assign the same settings received by the DHCP client to GlobalProtect satellites. You can also inherit the DNS suffix from the same source.
Manually define the
Secondary DNS, and
settings to push to the satellites.
To specify the
of addresses to assign the tunnel interface on the satellites when the VPN is established, click
and then specify the IP address range(s) to use.
To define what destination subnets to route through the tunnel click
area and then enter the routes as follows:
If you want to route all traffic from the satellites through the tunnel, leave this field blank. Note that in this case, all traffic except traffic destined for the local subnet will be tunneled to the gateway.
To route only some traffic through the gateway (called
), specify the destination subnets that must be tunneled. In this case, the satellite will route traffic that is not destined for a specified access route using its own routing table. For example, you may choose to only tunnel traffic destined for your corporate network, and use the local satellite to safely enable Internet access.
If you want to enable routing between satellites, enter the summary route for the network protected by each satellite.
) Define what routes, if any, the gateway will accept from satellites.
By default, the gateway will not add any routes satellites advertise to its routing table. If you do not want the gateway to accept routes from satellites, you do not need to complete this step.
To enable the gateway to accept routes advertised by satellites, select
Satellite > Route Filter.
Accept published routes
To filter which of the routes advertised by the satellites to add to the gateway routing table, click
and then define the subnets to include. For example, if all the satellites are configured with subnet 192.168.x.0/24 on the LAN side, configuring a permitted route of 192.168.0.0/16 to enable the gateway to only accept routes from the satellite if it is in the 192.168.0.0/16 subnet.
Save the gateway configuration.
to save the settings and close the GlobalProtect Gateway Configuration dialog.