The KEMP VLM-200 virtual load balancer
- You can request a 30 day trial license.
- The default username and password were provided by KEMP in an email.
Now I'm in and can start the configuration.
This is where you would configure the IP address of the first network interface (eth0):
I'll make the IP address 10.0.0.27 with a /8 or 255.0.0.0 subnet mask.
This is the IP address I will use from now on to access and configure the virtual load balancer.
Note: the connection uses HTTPS (port 443) so remember to type the URL like this:
If you are prompted about the web site's certificate not being trusted, you can ignore the warning - at least for the time being.
Templates for Exchange 2010
We then browse to the downloaded template and import:
Now we have the following templates to work with:
Yes, that may be difficult to read. So I'll indicate the names of the templates here:
- Exchange 2010 HTTPS: for access methods using HTTPS (autodiscover, OWA, Outlook Anywhere, ActiveSync, EWS, ECP).
- Exchange 2010 HTTPS Offloaded: same as above except SSL connections terminate at the load balancer, Essentially, the load balancer manages SSL encryption of client connections and can, optionally, re-encrypt connections to the Exchange servers.
- Exchange 2010 MAPI: these are Outlook connections.
- Exchange 2010 SMTP: this is mail traffic to and from the Hub Transport servers (that may also hold other roles as well).
- Direct client access and hub transport traffic to the appropriate load balancer IP address (some services may have a distinct IP address) either with the IP address itself or via DNS. In particular, we want to point the CAS Array DNS record to an IP address of the load balancer. Incoming SMTP traffic should also be directed to the load balancer.
- Configure the services themselves (HTTPS access, MAPI access, SMTP traffic). We can do this manually or use the templates mentioned earlier. I will use the templates. At this time, we will designate the Exchange 2010 servers to which the load balancer will forward client access connections and SMTP traffic
Hub Transport (SMTP)
- The MX records points to the A record.
- The A record points to the external IP address of my firewall.
10.0.0.28? Not 10.0.0.27?
- The virtual (IP) address is 10.0.0.28.
- The port is 25 (for SMTP - with TCP for the protocol).
- The service name is optional but I'll call it "SMTP - HT role".
- Among the templates imported previously, I'll select the "Exchange 2010 SMTP" template.
Client Access (Outlook - MAPI)
As for Outlook, we need to adjust the DNS record for the CAS Array. Until now, that DNS record pointed to EX13-1, one of the Exchange 2010 servers, at IP address 10.0.0.23. I need to change the record so it points to the load balancer:
Note: why not port 135? I'm not sure. If I recall correctly, that is how the template configured the service.
You can also register at the KEMP website to access documentation and watch instructional videos.