Load-Balancing a Pulse Connect Secure Service
This chapter describes how to configure the Traffic Manager to load-balance VPN connections to a Pulse Connect Secure (PCS) service. It also describes how to configure the Traffic Manager to provide optimal gateway selection and dynamic failover when deploying multiple geographically-located PCS clusters.
Overview of a PCS Load Balancing Configuration
You can configure the Traffic Manager to distribute incoming user VPN sessions across a set of PCS instances. The Traffic Manager additionally monitors the health of your PCS instances, and provides load-balancing and failover functionality across your PCS deployment.
To simplify operation, the Traffic Manager provides a wizard -“Load-balance Pulse Connect Secure”- that automatically creates Traffic Manager service configuration based on the details that you provide.
ATTENTION
The wizard does not perform any configuration outside of the Traffic Manager. Before running the wizard, make sure you have a fully-configured set of PCS instances. These instances might be clustered in an active/active configuration, or might share configuration through some other means. For more information, see the Pulse Connect Secure documentation available from the Ivanti website (www.ivanti.com).
To use the wizard, make sure you have the following information:
•An identifying name for the new service.
•A previously-created Traffic IP group containing all IP addresses that the new service should listen on.
•The UDP port number you want the Traffic Manager to use (where ESP mode is configured on your PCS instances).
Images and references in this guide assume the default value of 4500.
•The hostnames or IP addresses of your PCS instances.
In addition, decide whether you want the Traffic Manager to perform the following functions:
•Redirect HTTP requests to HTTPS.
•Use IP transparency.
Before you run the wizard, make sure you do not have any existing services using port 443 or the selected UDP port on the Traffic IP addresses you want to use.