Load Balancing Citrix Delivery Controllers via a Load Balancer necessity?
At one of my projects we were discussing the high level design decisions and one of the discussion topics were setting-up the Delivery Controllers high available and redundant. During the talk we discussed the necessity of using Load Balancer appliances in front of the Delivery Controller. Based on that talk I thought it was a good idea to write an article about this topic including my opinion.
Logically we need to start which communication streams are being used to the Delivery Controllers which should be taken into account. Communicating to the delivery controller has three communication streams.
- Virtual Delivery Agent (VDA) communication
- StoreFront communication Application enumeration/ICA file creation (XML broker)
- NetScaler (and StoreFront) STA communication
Let’s dig deeper in each communication stream.
The first stream is all communication between the Delivery Controller and the VDA. Each VDA communicates with one of the Delivery Controllers. At the discovery process the connection will be set-up with one of the delivery controllers. Before XenApp 7/XenDesktop .x it was a best practice to set-up a specific A record with a general name, which was configured into the VDA software. To make this option reliable a load balancer appliance was being used to distribute the VDA to a specific delivery controller.
Read the entire article here, VanBragt.Net Virtualization – Load Balancing Citrix Delivery Controllers via a Load Balancer necessity?
via the amazing Wilco van Bragt.