11-07-2024 07:35 AM - edited 11-07-2024 07:35 AM
Hi @DJ_1924 ,
The global server load balancing method mentioned by @jpomachagua can be done if site2 also has the portal configured with the same FQDN.
Another approach to automatic failover (no manual selection) can be done with 1 portal and 2 gateways. Site1 will have both gateways (site1 and site2) configured in the portal. You can use the GlobalProtect gateway selection process to have everyone use site1 gateway. If the portal ever goes down, the clients will automatically connect to the site2 gateway using the cached portal configuration.
https://knowledgebase.paloaltonetworks.com/kCSArticleDetail?id=kA10g000000ClVz
There was a cool 3rd party document on this configuration that has since been deleted. It also said that the portal client configuration Save User Credentials had to be enabled for this redundancy to work. That is how i configured and tested this HA for a client. It worked great. If it doesn't work without that setting, you could try that.
Thanks,
Tom
