Select the Interface that
satellites will use for ingress access to the portal.
Specify the IP Address Type and IP
address for satellite access to the portal:
The IP address type can be IPv4 (for
IPv4 traffic only), IPv6 (for IPv6 traffic
only, or IPv4 and IPv6. Use IPv4
and IPv6 if your network supports dual stack configurations,
where IPv4 and IPv6 run at the same time.
The IP address must be compatible with the IP address type.
For example, 172.16.1/0 for IPv4 addresses
or 21DA:D3:0:2F3B for IPv6 addresses. For
dual stack configurations, enter both an IPv4 and IPv6 address.
Click OK to save changes.
Specify an SSL/TLS Service profile to use to enable the
satellite to establish an SSL/TLS connection to the portal.
On the GlobalProtect Portal Configuration
dialog, select Authentication.
Select the SSL/TLS Service Profile.
Specify an authentication profile and optional certificate
profile for authenticating satellites.
If the portal can’t validate the
serial numbers of connecting satellites, it will fall back to the
authentication profile. Therefore, before you can save the portal
configuration (by clicking OK), you must Configure
an authentication profile.
Add a
Client Authentication, and then enter a Name to
identify the configuration, select OS: Satellite to apply
the configuration to all satellites, and specify the Authentication
Profile to use to authenticate satellite devices. You
can also specify a Certificate Profile for
the portal to use to authenticate satellite devices.
Continue with defining the configurations to push to
the satellites or, if you have already created the satellite configurations,
save the portal configuration.