Load Balancer Solutions¶
Load balancers may be added to a Cloud Access Software deployment to distribute system and to optimize performance by distributing PCoIP connections across several CAS Connectors.
Using Load Balancing for On-Premises Deployments¶
The following diagram outlines a load balancing scenario for a Cloud Access Software deployment with Cloud Access Manager integration.
Load balancers must support both HTTP and sticky sessions (jsessionid). During the session establishment phase, the CAS Connector passes it's
ExternalRoutableIP configuration value to the PCoIP Client. After the session has been established, the PCoIP Client uses the provided IP address to communicate directly with the CAS Connector. TCP Ports 443/60443 can be opened for session establishment.
Teradici recommends using TCP 60443 for internal connections. It is not mandatory for TCP 60443 to be opened to the public network.
ExternalRoutableIP must point to the CAS Connector
ExternalRoutableIP setting is configured to point to the load balancer instead of the CAS Connector, the load balancer may direct the PCoIP Client to the incorrect CAS Connector on the wrong server and the PCoIP Client will not be able to establish a session.
CAS Connector Public IP Addresses
In the above configuration, each CAS Connector must have a unique public IP address and it must be routable externally for port 4172.
Load Balancer Session Planning¶
The number of users allocated per individual CAS Connector varies according to user type and considerations such as display topology and resolution. At present, the throughput of PCoIP traffic through an individual CAS Connector is limited to approximately 400 Mbps. As an example, a typical 1080p VDI workloads demanding less than 5 Mbps per session would allow in excess of 80 concurrent sessions per CAS Connector instance. In contrast, a 4K/UHD video editorial user or VFX artist may require upward of 50 Mbps on average, limiting each CAS Connector instance to less than 10 concurrent sessions.