This document describes the installation of the KEMP Virtual LoadMaster (VLM) within a Microsoft Hyper-V environment. The VLM has been tested with Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and Windows 8. The instructions in this installation guide are for Windows Server 2012, Windows Server 2012 R2 and Windows 8.
The KEMP Virtual LoadMaster in other words (Virtual Load Balancer) is a version of the KEMP LoadMaster that runs as a virtual machine within a hypervisor and can provide all the features and functions of a hardware-based LoadMaster.
There are several different versions of the VLM available. Full details of the currently supported versions are available on KEMP website: .
The Microsoft Hyper-V virtual machine guest environment for the VLM, at minimum, must include:
- 2 x virtual processors
- 2 GB RAM
- 32 GB virtual hard disk capacity
There may be maximum configuration limits imposed by Hyper-V such as maximum RAM per VM, Virtual NICs per VM etc. For further details regarding the configuration limits imposed by Microsoft Hyper-V, please refer to the relevant Microsoft Hyper-V documentation.
Installing Virtual LoadMaster (VLM) using Hyper-V Manager:The following instructions describe how to install a Virtual LoadMaster on a Hyper-V environment using the Hyper-V Manager.
Download the Hyper-V FilesThe VLM is packaged within a .vhd file for ease of deployment. This file can be freely downloaded from KEMP Technologies for a 30 day evaluation period. To download the VLM please follow the instructions below:
- Log on to
- Within the Select the hypervisor platform section, select the option for Microsoft Hyper-V.
- Click on the Download Hyper-V VM button.
- Read the end user agreement.
- To continue, select your country from the drop-down list.
- Click on the Agree button.
- Download the Hyper-V zip file.
- Unzip the contents of the file to an accessible location within the hyper-v environment.
Importing the VLM:To import the VLM we use the Import Virtual Machine function within the Hyper-V Manager.
1. Open the Hyper-V Manager and select the relevant server node in the left panel.
Figure 2‑1: Hyper-V Manager
2. Click the Import Virtual Machine menu option in the panel on the right.
Figure 2‑2: Import Virtual Machine
3. Click Next.
4. Click the Browse button and browse to where you downloaded the Hyper-V files.
5. Select the LoadMaster VLM folder (under the top-level folder LoadMaster-VLM-n.n-nn-HYPERV, where n.n-nn is the build number) and click the Select Folder button.
Figure 2‑4: Select the VLM
6. Select the VLM and click Next.
7. Select the Copy the virtual machine (create a new unique ID) option.
8. Choose your destination and hard disks.
9. Click the Import button.
10. The virtual machine should be imported and should now appear within the Virtual Machines pane in
the Hyper-V Manager.
Check the Network Adapter Settings:Before starting the VLM we must first verify that the network adapters are configured correctly.
- Right-click on the virtual machine you have imported within the Virtual Machines pane.
- Click on the Settings option.
- Click on the Network Adapter or Legacy Network Adapter option within the Hardware list.
KEMP recommend selecting the Network Adapter option as it provides much higher performance and less load on the host.
- Ensure that the network adapter is configured correctly.
- Ensure that the network adapter is connected to the correct virtual network.
- Expand the Network Adapter menu and Select the Static option within the MAC address section and enter the relevant MAC address.
- Ensure that the Enable spoofing of MAC addresses checkbox is selected.
Figure 2‑5: Network Adapter settings
- Click on the OK button.
- Repeat these steps for the second network adapter.
Jumbo frames are supported for Hyper-V network synthetic drivers.
Power On the LoadMaster:Once the VLM has been deployed it can be powered on:
- Right-click the Virtual Machine that was imported within the Virtual Machines pane.
- Click Start.
The VLM should begin to boot up.
- Right-click the VLM and select Connect to open the console window.
Figure 2‑6: IP address
- The VLM should obtain an IP address via DHCP. Make a note of this address.
Licensing and Configuration:The LoadMaster must now be configured to operate within the network configuration.
- In an internet browser, enter the IP address that was noted previously.
- Ensure to enter https:// before the IP address.
- A warning may appear regarding website security certificates. Please click the continue/ignore option.
- The LoadMaster End User License Agreement screen appears.
Please read the license agreement and, if willing to accept the conditions therein, click the Agree button to proceed.
Figure 2‑7: License type selection
- Select the relevant license type.
- A section will then appear asking if you are OK with the LoadMaster regularly contacting KEMP to check for updates and other information. Click the relevant button to proceed.Figure 2‑8: License Required
- If using the Online licensing method, fill out the fields and click License Now.
If you are starting with a trial license, there is no need to enter an Order ID. If you are starting with a permanent license, enter the KEMP Order ID# if this was provided to you.
If using the Offline Licensing method, select Offline Licensing, obtain the license text, paste it into the License field and click Apply License.
- The Change Password screen appears.
- Enter a password for the bal user in the Password input field and retype it in the Retype Password input field.
- The login screen appears again, enter the bal user name and the new password as defined in the previous step.
- In the screen informing that the password has changed, click the Continue button
- If the machine has shipped with a temporary license, a warning will appear informing that a temporary license has been installed on the machine and for how long the license is valid.
- Click on the OK button
- The Appliance Vitals screen of the LoadMaster will appear.
Figure 2‑9: Appliance Vitals
- Go toSystem Configuration > Network Setup in the main menu.
- Click the eth0 menu option within the Interfaces section.
- In the Network Interface 0 screen, enter the IP address of the eth0 interface, the network facing interface of the LoadMaster, in the Interface Address input field.
- Click on the Set Address button
- Click on the eth1 menu option within the Interfaces section
- In the Network Interface 1 screen, enter the IP address of the eth1 interface, the farm-side interface of the LoadMaster, in the Interface Address input field.
- Click on the Set Address button
This interface is optional, depending on the network configuration.
- Click on the Local DNS Configuration > Hostname Configuration menu option.
- In the Hostname configuration screen, enter the hostname into the Current Hostname input field.
- Click on the Set Hostname button.
- Click on the Local DNS Configuration > DNS Configuration menu option.
- In the DNS configuration screen, enter the IP address(es) of the DNS Server(s) which will be used to resolve names locally on the LoadMaster into the DNS NameServer input field.
- Click on the Add button.
- Enter the domain name that is to be prepended to requests to the DNS nameserver into the DNS NameServer input field.
- Click the Add button.
- Click the System Configuration > Network Setup > Default Gateway menu option.
- In the DNS configuration screen, enter the IP address of the default gateway into the IPv4 Default Gateway Address input field.
- If you have an IPv6 Default Gateway, please enter the value in the IPv6 Default Gateway Address input field.
- Click the Set IPv4 Default Gateway button.
Cannot access the Web User InterfaceIf a connection to the WUI cannot be established, network settings can be configured via the console view.
- Login into the VLM via the console using the settings:
lb100 login: bal
Figure 3‑1: Enter IP address
- Enter the IP address of the eth0 interface, the network-facing interface of the LoadMaster, in the input field within the Network Side Interface Address field and press Enter on the keyboard.
Figure 3‑2: Enter default gateway address
- Enter the IP address of the Default Gateway.
Figure 3‑3: Nameserver IP addresses
- Enter a space-separated list of nameserver IP addresses.
- A message will appear asking to continue licensing via the WUI. Try to access the IP address via a web browser. Ensure to enter https:// before the IP address.
- Contact the local KEMP Customer Services Representative for further support if needed.
NIC Types Cannot Be MixedIf you add new Network Adapters to a VLM then they must be of the same Adapter Type as those already configured on the VLM.
If you install a Network Adapters with a different Adapter Type as those already configured on the VLM the VLM will not recognize the new interface.
Static MAC Addresses Must Be ConfiguredIn case you move a VLM system to a different Virtual Machine, ensure that the MAC addresses of the Virtual Machine’s NICs stay the same. It is recommended to configure static MAC addresses for all NICs within Virtual Machines.
For further information on configuring static MAC addresses, please refer to the relevant Hyper-V documentation.
Make this VM Highly Available Option is Greyed OutThere is an option in the Virtual Machine Manager called Make this VM highly available. This option is set when the Virtual Machine is placed on a host. Therefore, the option will be greyed out, even when the Virtual Machine is not running. There is a way to work around this problem without having to delete and re-create the Virtual Machine. The Virtual Machine can be migrated. Follow the steps below to do this:
- Open the Virtual Machine Manager console.
- Right-click the relevant Virtual Machine that you want to make highly-available and select Migrate.
- Select the current host from the list for migration.
- Click Yes to the prompt asking if you want to make the Virtual Machine highly available.
- The path can be changed if needed. Click Next.
- Select the network and click Move.
- Wait for the migration to complete.
Factory Reset:If you perform a factory reset on the VLM, all configuration data, including the VLM’s IP address is deleted. During the subsequent reboot the VLM attempts to obtain an IP address via DHCP. If the VLM is on a different subnet to the DHCP server then an IP address will not be obtained and the IP address is set to the default 192.168.1.101.
The VLM may not be accessible using this address. If this is the case then you must run through the quick setup via the console as described in above step.