We are trying to increase capactity at our site and have set up the pulse servers to try the servers in order.
If the first server is unavailable due to the url is down the client will try the next server.
If the first server is unavailable due to 'too many concurrent users' the client will keep trying that server and will not fail over.
How do we force the client to switch on any error?
The best way to solve this is to use Pulse vADC to balance the workload across the PCS appliances. Pulse vADC can distribute the traffic more evenly, because it can be configured to monitor the license usage on each PCS appliance, and steer traffic to appliances which have more headroom.
There is a built-in Wizard to simplify configuration with Pulse vADC, or a more detailed deployment guide on the Pulse web site. Alternatively, you can work with your local partner, or our Customer Success team to customize the policies to suit your own needs.
Deployment guide here:
Load Balancing Pulse Connect Secure with Pulse Traffic Manager Deployment Guide
Optimal Gateway Selection for Pulse Connect Secure Deployment Guide
Thanks for the reply.
I think I was expecting a more simple approach that means if the client fails to connect for any reason it would try the next server in the list. It makes no sense that if the client finds the current server full that it would keep retrying and not find the next server in the list.
I currently don't have the resources to add a new server nor are the pulse appliances at the same location on the same networks so we cannot easily cluster them. I would have hoped the client would be a little more intelligent and actually fail over on a failiure.
Pulse Client will only fallback within different URLs configured in the same connection, not between two separate connections, and that too only if the VPN server URL is not resolvable, not reachable.