Building Windows Terminal Service Cluster using LVS
In the configuration example, we will have a LVS/DR cluster of three Windows Terminal servers. The virtual IP address of load balancer is 172.18.1.10. The ip addresses of three servers are 172.18.1.11, 172.18.1.12 and 172.18.1.13 respectively. The Windows Terminal servers need some configuration to avoid the ARP issues in LVS/DR clusters.
We use the following ipvsadm commands to setup IPVS rules:
ipvsadm -A -t 172.18.1.10:3389 -s wlc ipvsadm -a -t 172.18.1.10:3389 -r 172.18.1.11 -m -w 100 ipvsadm -a -t 172.18.1.10:3389 -r 172.18.1.12 -m -w 100 ipvsadm -a -t 172.18.1.10:3389 -r 172.18.1.13 -m -w 100
Then, use any computer not belong to this cluster, and access the Windows Terminal Service at 172.18.1.10, and see whether it works or not. "ipvsadm -Ln" can be used to list the IPVS table, and "ipvsadm -Lcn" can be used to list the IPVS connections.
Once the basic cluster configuration works, we can consider to use cluster management software to add reliability and availability into the web cluster system.
- Session Directory and Load Balancing Using Terminal Server
|"Building Windows Terminal Service Cluster using LVS" is an LVS Example related stub. You can help LVSKB by expanding it|