In this article series, we will understand the step by step instruction to deploy Kemp LoadMaster for Exchange Server 2013 services in multi- site (Dallas and Pittsburg) lab environment and also configure geo-redundancy between the two AD sites. Where the Kemp LoadMaster load balances the client requests( from internal and internet network) within the AD site and also routes the client request automatically to the available Exchange 2013 servers in other site when one AD site goes down.
Current LAB Setup
Current Lab is built on Microsoft Hyper-V and it is configured with two AD sites Dallas (10.10.10.0/24 network) and Pittsburg (188.8.131.52/24 network). It is also installed with domain controller on each site with the domain name happy.com. In each of the AD site, one Exchange Server 2013 (multirole) is installed and configured Database Availability Group (DAG01) between them. Below Figure 1.1 has the details of the AD sites, Domain Controller, Exchange nodes and DAG.
Figure 1.1 Exchange 2013 deployed in the lab environment.
LAB Hyper-V Virtual Network Configuration Requirement:
LoadMaster interfaces with both internal network and external/internet network. Hence, Hyper-V needs to configure with two Virtual networks: DMZ Network and Internal Network.
1. DMZ Network: Create a new DMZ Network virtual network of type External network, it should connect to the host Machine network interface card (NIC) and communicates with the external world. Make sure to select Allow management operation system to share this network adapter. The Figure 1.2 has the details of the same. Host machine NIC should be connected to the internet.
Figure 1.2 DMZ Network configuration
2. Internal Network: Create new Internal Network virtual network of type Internal Network. Internal network is isolated network which can communicate within themselves. We will configure all Exchange Servers 2013 guest machines NICs to use internal network.
Figure 1.3 Hyper-V Internal Network Configuration.
A Windows VM is configured as Router with two NICs pointing to internal network. This windows Router will route traffic between two network segment Dallas (10.10.10.x) and Pittsburg (20.20.20.x) within the internal network.
Configuring Kemp LoadMaster in the Exchange 2013 lab
In this part , we will Install and configure LoadMaster on both the AD site in Two-Arm Deployment as defined in the below Figure 1.4. With one NIC pointing the DMZ network and other NIC pointing to the internal network.
Figure 1.4 Kemp LoadMaster deployment and IP address configuration plan
Configuring LoadMaster for Dallas Network
1. Register a new Kemp ID at http://freeloadbalancer.com and download the latest version of Free Kemp loadmaster for Hyper-V
Figure 1.5 Free Kemp LoadMaster Website
2. Extract the KEMP LoadMaster Virtual Machine (VM) file on the Hyper-V server.
3. Start Hyper-V Manager and click on Import VM from the Actions menu then click on Next at the Welcome Screen.
Figure 1.6 Importing LoadMaster Virtual Machine into Hyper-V
4. At Local Folder page, Click on Browse button to specify the Kemp LoadMaster virtual machine and click Next and on Select Virtual Machine page keep the settings as default and click on Next
Figure 1.7 Specify the Folder containing virtual machine to import
5. Choose the option Copy the Virtual Machine (create a unique ID) to make of copy of the VM with the new unique ID and click Next. (This will help us to create multiple copy of the downloaded LoadMaster image)
Figure 1.8 Choose the virtual machine Import type
6. Choose folders paths to store the new copy of the LoadMaster VM and click Next.
Figure 1.9 Choose Virtual Machines files path
7. Then Choose Storage folders path for the new VM and click Next
8. Validate the Summary page and click on Finish to import the Virtual Machine (VM) into Hyper-V console.
Figure 1.10 Completing Import Wizard.
9. To identify the Dallas Load Master in the Hyper-V, rename the newly imported LoadMaster VM to DalKemp.
Figure 1.11 Renaming LoadMaster VM in Hyper-V Manager
10. To configure the virtual network on the DalKemp VM, right click on LoadMaster VM and select Settings. Select DMZ Network for the first VM-Bus network Adapter and Internal Network for the second VM-Bus network adapter and click on Apply. Below Figure 1.12 has the reference details.
Figure 1.12 Configure Network Adapter on DalKemp VM
Connecting to LoadMaster and Activating Free License
1. Boot the DalKemp LoadMaster VM from Hyper-V console
2. Post booting it displays IP Address of the Appliance (in our case it is 192.168.1.100). It is been assigned by the LAB router via External DMZ network. Since, this network is sharing the host NIC and also connected to the Lab router with DHCP Configured.
Note: The Default Username/Password: bal /1fourall
Figure 1.13 DalKemp LoadMaster connection information.
3. To configure the DalKemp LoadMaster, start Internet Explorer and connect to it using the IP address assigned – https://192.168.1.100
4. Provide the Default credentials Username/Password: bal /1fourall
5. Click on Agree to accept the End User Agreement
Figure 1.14 Accepting EULA
6. Select License Type as Free LoadMaster and click on Allow to connect back to KEMP home for license activation.
Figure 1.15 Selecting License Type
7. Use the registered KEMP ID and activate free LoadMaster license.
Figure 1.16 Activating Free LoadMaster License
8. Once activated, it will prompt to reset the default user (bal) password. Once password is changed then re-login back to the VM using new password.
Configuring LoadMaster Network Interface
1. Login to Kemp LoadMaster from Internet Explorer and under Main menu expand system configuration -> interface
2. Select eth0 (Network Interface 0) and validate IP Address – 192.168.1.100/24. It is been assigned by DHCP and we could use the same on the interface and change it if required. Make sure Use for GEO Responses and Request is checked and this interface will be used to communicate with Pittsburg LoadMaster for geo redundancy.
Figure 1.17 Configuring LoadMaster eth0 Interface
3. Select eth1 (network Interface 1) and assign the IP address 10.10.10.9/24 from the Dallas internal network segment and click on Set Address. This interface will be used to communicate with internal Exchange 2013 servers in the Dallas and Pittsburg AD sites.
Figure 1.18 Configuring LoadMaster eth1 Interface
Follow the above Instructions: Configuring LoadMaster for Dallas Network, Connecting to LoadMaster and Activating Free License, Configuring LoadMaster Network Interface to import and configure Pittsburg LoadMaster. Configure interface Eth0 with IP address 192.168.1.101/24 (Pittsburg DMZ network) and Eth1 with 184.108.40.206/24 (Pittsburg internal network) on it.
With this we are at the end of the part 1 of the article service with Exchange server 2013 installed and configured, Hyper-V networks configured and finally installed and configured LoadMaster in both the AD site. In the next part we will configure the LoadMaster for the Exchange HTTPS/ SMTP Services and validate the same.