Install Guide

The TTL eld is displayed only if you have selected Advanced View in the View menu of the DNS Server.
The load balancing is now congured for ThreadX devices and you can use the your WDM Management Servers to manage a large number
of ThreadX devices.
Conguring load balancing for ThreadX 5.x devices
When WDM is used to manage ThreadX 5.x devices in a large enterprise environment, a single Teradici Device Proxy Server which is used
to manage ThreadX 5x devices from WDM cannot scale up to manage more than 18 thousand devices. There could be problems or delays
in client check-ins, schedule execution, and/or real-time command execution.
Load balancing helps resolve these problems to a great extent. In this setup, you can install and run multiple instances of Teradici Device
Proxy Servers on dierent systems and balance the load between them using a proxy as described below.
The components of the load balancer are as follows:
Teradici Device Proxy Server
HA Proxy Server
WDM uses the HAProxy hosted on the Ubuntu server 16.04.1 LTS to perform load balancing between the Teradici Device Proxy servers.
HAProxy is a load balancer proxy that can also provide HA based on how it is congured. It is a popular open source software for TCP/
HTTP Load Balancer, and proxying solution which can be run on Linux. The most common use is to improve the performance and reliability
of a server environment by distributing the workload across multiple servers.
This section describes how to set up and congure load balancing of the HA Proxy Server.
Steps to create DNS_SRV Record:
Firmware 5.x uses a DNS_SRV record in addition to the text record that contains the thumbprint of the SSL certicate to use in the
management console.
WDM 5.7.3 supports Teradici 5.x rmware with comprehensive features.
1 The rst record required is a DNS_SRV record for _pcoip-bootstrap. The record must point to the name of the Teradici Device Proxy
(HAProxy).
Figure 40. DNS_SRV record for _pcoip-bootstrap
2 The second record required is an A record pointing to the name used in the Host oering this service eld.
80
Conguring load balancing