The KEMP Virtual LoadMaster 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.
This document describes the installation of the Virtual LoadMaster (VLM) within a VMware ESX or ESXi hypervisor environment.
The Virtual LoadMaster is VMware ready. The VLM is has been tested with VMware ESX 4.0, 4.1, 5.0, and 5.1, vCenter Server 5.5 and 6.0, VMware ESXi 4.0, 4.1, 5.0, 5.1, 5.5 and 6.0, and vSphere 4.0, 5.0, 5.5 and 6.0.
The VMware virtual machine guest environment for the VLM, at minimum, must include:
2 x virtual CPUs (reserve 2 GHz)
2 GB RAM
16 GB disk space (sparse where possible)
There may be maximum configuration limits imposed by VMware such as maximum RAM per VM, Virtual NICs per VM and so on. For further details regarding the configuration limits imposed by VMware, please refer to the relevant VMware documentation.
Some best practices to be aware of before deploying a LoadMaster on VMware are below:
Configure an existing or new load balancing port group for the relevant VLAN to avoid port flooding
Use the VMXNET3 network adapter type when deploying the VLM
When using High Availability (HA): The Security Policy Forged Transmit on the port group should be set to Accept. Ensure this is forced (hard coded) on the port group as any changes to the vSwitch will affect all port groups by default.
When using HA and the LoadMasters are on different hosts: To prevent the transmission of RARP packets from being sent every time a Virtual Machine is powered on, set the Notify Switches option to No.
The following instructions describe how to install a Virtual LoadMaster on a VMware ESXi environment using the VMware vSphere client.
The VLM is packaged with an .ovf 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 following instructions.
2. Click the Download Now button.
3. Within the Select your hypervisor section, select the option for VMware (OVF).
4. Select your country from the drop-down list provided.
5. Read the End User License Agreement.
6. To proceed with the download, ensure the I agree to the End User License Agreement terms check box is ticked.
7. Click the Download button.
8. Unzip the contents of the file to an accessible location.
To deploy the VLM we initiate a Deploy OVF Template wizard which gathers all the information required to correctly deploy the VLM.
1. Open the VMware vSphere client.
2. Select the correct Resource Pool within which you wish to install the VLM.
3. Select the File > Deploy OVF Template menu option, this initiates the Deploy OVF Template wizard.
4. Within the Source screen, click on the Browse button and select the downloaded file.
5. Click Next.
6. Within the OVF Template Details screen, ensure that all the details regarding the VLM are correct.
7. Click Next.
8. Within the End User License Agreement screen, read the KEMP Technologies SOFTWARE LICENSE AGREEMENT.
9. If you wish to continue with the installation, you must accept the end-user license agreement by clicking the Accept button.
10. When the Accept button has been clicked the Next button will become available.
11. Click the Next button.
12. In the Name and Location field, enter a name for the VLM into the Name field.
The name can be up to 80 characters long. It should be unique within the virtual machine folder. Names are case sensitive.
13. If required, select the folder location within the inventory where the VLM will reside
14. Click Next.
15. Within the Resource Pool screen, select the resource pool where the VLM will run.
This page is only displayed if the cluster contains a resource pool and if you had not selected a resource pool within the inventory tree before initiating the deployment wizard.
16. Click the Next button
17. Within the Datastore screen, select the datastore in which you wish to store the VLM.
You may only select from preconfigured datastores within this screen.
18. Click Next.
19. Within the disk Format screen, select whether you wish to use Thin provisioned format or Thick provisioned format
KEMP recommends you using the Thick provisioned format option. The estimated disk usage is approximately 32 GB.
20. Click Next.
21. Within the Network Mapping screen, select which networks in the inventory should be used for the VLM.
Select the network mapping for Network and Farm by right-clicking the Destination Network column and choosing the relevant preconfigured network from the drop-down list.
22. Click Next.
23. Within the Ready to Complete screen, ensure that all the details are correct.
24. Click the Finish button.
Once the Finish button is clicked, the VLM is deployed.
Please verify that the Virtual Machine settings are configured with the recommended values:
2 x virtual processors
2 GB RAM
16 GB virtual hard disk capacity (sparse where possible)
To power on the Virtual LoadMaster, follow the steps below:
1. In the left panel of the client, select the LoadMaster Virtual Machine.
2. Click the Power on the virtual machine link.
3. Select the Console tab and wait for the Virtual Machine to finish booting.
4. When the Virtual Machine finishes booting, a screen similar to the one above appears which will show the IP address. Take note of this as you will need it to access the LoadMaster Web User Interface (WUI).
To change the IP address using the console view, follow the steps in the Configuring the LoadMaster via the Console section.
The LoadMaster must now be configured to operate within the network configuration.
1. In an internet browser, enter the IP address that was previously noted.
Ensure to enter https:// before the IP address.
2. A warning may appear regarding website security certificates. Please click the continue/ignore option.
3. The LoadMaster End User License Agreement screen appears.
Please read the license agreement and, if you are willing to accept the conditions therein, click on the Agree button to proceed.
4. A screen 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.
5. 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.
For detailed instructions on how to register for a KEMP ID and license the LoadMaster, refer to the Licensing, Feature Description on the KEMP Documentation Page.
6. If you entered an Order ID, a screen appears that provides a list of available licenses for that order ID, in addition to any licenses registered for the KEMP ID based on the LoadMaster platform type. Select the license type you want to apply to this LoadMaster.
If the license type you want is not displayed, please contact your KEMP representative.
7. Click Continue.
8. The login screen appears, enter the bal user name and the password.
9. In the screen informing you that the password has changed, press the Continue button
10. If your machine has shipped with a temporary license you should get a warning informing you that a temporary license has been installed on your machine and for how long the license is valid.
Click OK .
11. You should now connect to the Home screen of the LoadMaster.
12. Go to System Configuration > Network Setup in the main menu.
13. Click the eth0 menu option within the Interfaces section.
14. 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.
15. Click the Set Address button
16. Click the eth1 menu option within the Interfaces section
17. 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.
18. Click on the Set Address button
This interface is optional, depending on the network configuration.
19. Click on the Local DNS Configuration > Hostname Configuration menu option.
20. In the Hostname configuration screen, enter the hostname into the Current Hostname input field.
21. Click the Set Hostname button.
22. Click the Local DNS Configuration > DNS Configuration menu option.
23. In the DNS configuration screen, enter the IP address(es) of the DNS Server(s) which is used to resolve names locally on the LoadMaster into the DNS NameServer input field.
24. Click the Add button.
25. Enter the domain name that is to be prepended to requests to the DNS nameserver into the DNS NameServer input field.
26. Click the Add button.
27. Click the System Configuration > Network Setup > Default Gateway menu option.
28. 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.
29. Click the Set IPv4 Default Gateway button.
The LoadMaster is now fully installed and ready to be used. For further information on how to configure and implement the Virtual LoadMaster, please refer to the LoadMaster documentation which can be downloaded from the page.
If the LoadMaster does not automatically obtain an IP address using DHCP, or if the user prefers to configure the LoadMaster via the console, then the following configuration steps must be completed before starting the LoadMaster.
1. Login into the LoadMaster via the console using the settings
- lb100 login: bal
- Password: 1fourall
2. 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 dialog box.
3. Press OK.
4. Enter the IP address of the default gateway in the input field of the Default Gateway dialog box.
5. Press OK.
6. Once these are set, a prompt will appear asking to connect to the web interface at the newly configured IP address. In an internet browser enter the IP address of the eth0 entered in Step 2.
Ensure to enter https:// before the IP address.
7. A warning may appear regarding website security certificates. Please click the continue/ignore option.
8. The LoadMaster End User License Agreement screen appears.
9. Please read the license agreement and, if willing to accept the conditions therein, click on the Agree button to proceed.
10. 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.
11. Click OK.
12. The Appliance Vitals screen of the LoadMaster should appear.
The LoadMaster is now fully installed and ready to be used. For further information on how to configure and implement the Virtual LoadMaster, please refer to the LoadMaster documentation which can be found here: https://kemptechnologies.com/documentation.
If you perform a factory reset on your 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 the Configuring the LoadMaster via the Console section.
The VLM supports integration with VMware Tools. For more information, please refer to the VMware Tools Add-On Package, Feature Description.
When working with VMware Virtual Switches within your configuration, please ensure that the value of the Forged Transmit Blocking option is Accept. If this optionâ€™s value is Reject, the LoadMaster is prevented from sending traffic as it appears to come from nodes on the network other than the LoadMaster.
Please refer to your VMware documentation for further details on how to configure the VMware Virtual Switch.
Reason for Change
|Jan 2017||Release update||7.2.37 release||8.0||LB|
|Mar 2017||Release update||7.2.38 release||9.0||LB|