In case of client side network outage or ALOHA failover, users will keep on being redirected to the same server. Now, the users can point their RDP client to the VIP and get load-balanced. Server tse4 10.0.0.26:3389 weight 10 check inter 2s rise 2 fall 3 Server tse3 10.0.0.25:3389 weight 10 check inter 2s rise 2 fall 3 Server tse2 10.0.0.24:3389 weight 10 check inter 2s rise 2 fall 3 Server tse1 10.0.0.23:3389 weight 10 check inter 2s rise 2 fall 3 Stick-table type string len 32 size 10k expire 1d peers aloha # wait up to 5s for an RDP cookie in the request ![]() Configurationįind below the configuration for such infrastructure: peers aloha In order to ensure stickiness, the ALOHAs will use the RDP cookie, store it in a table where it is associated to the server serving the request.įinally, this table is shared between both ALOHAs, in order to ensure safe failover. ![]() The ALOHAs share a VIP, 10.0.0.18, on which clients will get connected. ![]() The TSE infrastructure looks like the image below:īasically, we have a couple of ALOHA load-balancer, in active/passive mode. The configuration below shows you how you can build outage-free Terminal server infrastructure with ALOHA and HAProxy. One main issue when using RDP is to be able to stick a user to a server. You need to load-balance Microsoft Terminal Services or remoteapps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |