To support the environment outlined above, a number of Virtual Services need to be defined on the LoadMaster. The table below outlines example details that would need to be configured on the LoadMaster.

VIP

Real Server(s)

Purpose

10.154.11.31:443 (TCP)

10.154.201.2

10.154.201.3

Balance the initial SSL connection from the client between the View Connection/Security server instances

10.154.11.32:443 (TCP)

10.154.201.2

Accept load-balanced client connections on HTTPS

10.154.11.32:4172 (TCP)

10.154.201.2

PCoIP connections can be over UDP or TCP. These Virtual Services forward connections to the View Connection Server.

10.154.11.32:4172 (UDP)

10.154.201.2

10.154.11.32:8443 (TCP)

10.154.201.2

Blast is the View via a browser protocol which we deliver on port 8443

10.154.11.33:443 (TCP)

10.154.201.3

Second View instance of the above services

10.154.11.33:4172 (TCP)

10.154.201.3

10.154.11.33:4172 (UDP)

10.154.201.3

10.154.11.33:8443 (TCP)

10.154.201.3

HTTPS is being offered on three Virtual Services in the configuration above. Each of these will require a certificate and associated private key for the Fully Qualified Domain Name (FQDN) of the VIP. In the example, we are using a wildcard certificate (*.viewlab.net) on all of the Virtual Services supporting HTTPS.