Download the FreeBSD 9.1 ISO image from the FreeBSD FTP site. I will use VirtualBox for the lab demostration. Install the Loab Balancer OS and HAProxy packageġ.- I created the virtual machine with two NIC's, one for the Load Balancer and other for Administration.First let start with the OS installation.ex2.- Exchange 2010 sp2 Box, Windows 2008R2, CAS, HT and Mailbox Roles.ex1.- Exchange 2010 sp2 Box, Windows 2008R2, CAS, HT and Mailbox Roles.If you need very high speeds like 10Gbps kinks, read the haproxy supported platforms documentation, they recommend using haproxy on Linux kernel 2.6.32 and above for a better performance and high speed bandwidths (above 10Gbps).įor my scenario, i used VirtualBox 4.2.16 as my virtualization platform. This might not be the best recommended option but we are not an ISP needed hundreds of thousand of connections, only need some thousand. I will use FreeBSD as Operating System for the HAProxy. Its supported by Linux, Solaris, FreeBSD and OpenBSD. This tool is used by other network products as load balancer or high availavility module. This tools is very cool, its latest stable version 1.4 was released on 7 meaning that its an active project and continues in development (v1.5-dev19). The Load Balancing tool of my choice is haproxy. Relayd looks very good, but seems that his power is to interact with OpenBSD PF which I like too, but for doing only Load Balancing, I thing its too much (I will try it in the future). Digging into Open Source solutions, I found relayd (previously hoststated). There are out there many commercial solutions like F5, BigIP or Cisco CSS, but they are expensive and cost is high for only one service needed for these products.
Exchange 2010 with WNLB is not supported by Microsoft :(. It generates a high amount of traffic and. This is a big head-each because some clients are working OK (the ones that are using the online CAS) and some are not.Īnother solution its to use Windows Network Load Balance (WNLB), a windows built-in Feature that works, but not very well, specially in virtualized environments. So clients will receive a connection error until the Browser cookie expires or DNS TTL expires on the client OS. DNS Round robin doesn't check service status so it keeps returning the failed server IP address even if its offline. This works well until one of the CAS server fails or is taked offline. On many installations of Exchange 2010, we decided to use DNS Round Robin as our Load Balancer method for the CAS services.
0 kommentar(er)
