Virtual LoadMaster for VMware ESX, ESXi using vsphere

(1)

Virtual LoadMaster

for VMware ESX,

ESXi using vSphere

Installation Guide

VERSION: 1.15

(2)

Copyright Notices

KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster product line including software and documentation. The use of the LoadMaster Exchange appliance is subject to the license agreement. Information in this guide may be modified at any time without prior notice.

Microsoft Windows is a registered trademarks of Microsoft Corporation in the United States and other countries. All other trademarks and service marks are the property of their respective owners.

Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts

to ensure that the information presented herein are correct, but makes no warranty, express or implied, about the accuracy of this information. If any material errors or inaccuracies should occur in this document, KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective, including without limitation any direct, special, incidental or consequential damages (including without limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from any action or inaction whether or not negligent, in the compiling or in delivering or communicating or publishing this document.

Any Internet Protocol (IP) addresses, phone numbers or other data that may resemble actual contact information used in this document are not intended to be actual addresses, phone numbers or contact information. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual addressing or contact information in illustrative content is unintentional and coincidental.

Portions of this software are; copyright (c) 2004-2006 Frank Denis. All rights reserved; copyright (c) 2002 Michael Shalayeff. All rights reserved; copyright (c) 2003 Ryan McBride. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the above copyright holders..

(3)

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

(4)

1 Introduction

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 VLM is has been tested with VMware ESX 4.0, 4.1, 5.0 and 5.1, vCenter Server 5.5, VMware ESXi 4.0, 4.1, 5.0, 5.1 and 5.5 and vSphere 4.0, 5.0 and 5.5.

There are several different versions of the VLM available. Full details of the currently supported versions are available on our website: www.kemptechnologies.com.

The VMware virtual machine guest environment for the VLM, at minimum, must include:  2 x virtual CPUs (reserve 2 GHz)

 1 GB RAM  32 GB disk space

(6)

2 Best Practices

Some best practices to be aware of before deploying a LoadMaster on VMware are below:  Configure a load balancing port group for the relevant VLAN to avoid port flooding  Use the E1000 network adapter type when deploying the VLM

Figure 2-1: Security Tab

 The Security Policy Forged Transmit on the Portgroup 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.

Figure 2-2: NIC Teaming Tab

(7)

3 Installing Virtual LoadMaster (VLM) using vSphere

The following instructions describe how to install a Virtual LoadMaster on a VMware ESXi environment using the VMware vSphere client.

Download the OVF File

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.

1. Log on to http://www.KEMPtechnologies.com/try

2. Within the Select the hypervisor platform section, select the option for VMware ESX, ESXi and vSphere.

3. Click on the Download OVF button. 4. Read the end user agreement.

5. If you wish to continue, select your country from the drop-down list. 6. Click on the Agree button.

7. Download the ovf zip file.

8. Unzip the contents of the file to an accessible location.

Deploy the OVF File

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.

(8)

Figure 3-1: Source

5. Click the Next button.

6. Within the OVF Template Details screen, ensure that all the details regarding the VLM are correct.

Figure 3-2: OVF Template Details

(9)

Figure 3-3: End-User 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

Figure 3-4: Name and Location

(10)

This page is only displayed if the cluster contains a resource pool and if you hadn’t selected a resource pool within the inventory tree before initiating the deployment wizard.

Figure 3-5: Resource Pool

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.

Figure 3-6: Datastore

19. Within the disk Format screen, select whether you wish to use Thin provisioned format or Thick provisioned format

(11)

Figure 3-7: Disk Format

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.

Figure 3-8: Network Mapping

(12)

Figure 3-9: Ready to Complete

24. Click the Finish button.

Once the Finish button is clicked, the VLM is deployed.

Check the Network Adapter Settings

Before starting the VLM we must first verify that the network adapters are configured correctly. 1. Select the deployed VLM within the inventory tree.

2. Select the Inventory > Virtual Machine > Edit Settings menu option. 3. Ensure that the network adaptors are configured correctly as follows

a. Ensure that the Connect at power on: checkbox is selected b. Ensure the Adapter Type is correct.

The default, recommended adapter type is ‘E1000’ We also have support for the vmxnet3 driver. Both E1000 and vmxnet3 support Jumbo frames.

c. Ensure that the Automatic option is selected within the MAC Address section.

(13)

Figure 3-10: Edit Settings

If the network adapters are not configured correctly or if they have not been setup you can add a new network adapter by clicking the Add button.

Power On the LoadMaster

To power on the Virtual LoadMaster, follow the steps below:

(14)

Figure 3-11: Power On

2. Click the Power on the virtual machine link.

3. Select the Console tab and wait for the Virtual Machine to finish booting.

Figure 3-12: IP address

(15)

To change the IP address via the console view, follow the steps in Section 4.1.

Licensing and Configuration

You must now configure the LoadMaster to operate within your network configuration. 1. In your internet browser enter the IP address previously noted, ensure you place

’https://’ before the IP address.

2. You may get a warning regarding website security certificates. Please click on 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.

Figure 3-13: License Required

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.

(16)

Please use the following login credentials: lb100 login: bal

Password: 1fourall

7. The Change Password screen appears

8. Enter a new password for the bal user in the Password input field and retype it in the Retype Password input field.

9. The login screen appears again, enter the bal user name and the new password as defined in the previous step.

10. In the screen informing you that the password has changed, press the Continue button 11. If your machine has 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.

12. Click on the OK button

(17)

Figure 3-14: Appliance Vitals

14. Click the System Configuration menu option.

15. Click the eth0 menu option within the Interfaces section.

16. 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. 17. Click on the Set Address button

18. Click on the eth1 menu option within the Interfaces section

19. 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.

20. Click on the Set Address button

This interface is optional, depending on the network configuration.

21. Click on the Local DNS Configuration > Hostname Configuration menu option.

22. In the Hostname configuration screen, enter the hostname into the Current Hostname input field.

23. Click on the Set Hostname button.

(18)

25. 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.

26. Click on the Add button.

27. Enter the domain name that is to be prepended to requests to the DNS nameserver into the DNS NameServer input field.

28. Click on the Add button.

29. Click on the Route Management > Default Gateway menu option.

30. In the DNS configuration screen, enter the IP address of the default gateway into the IPv4 Default Gateway Address input field.

31. If you have an IPv6 Default Gateway, please enter the value in the IPv6 Default Gateway Address input field.

32. Click on 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

(19)

4 Troubleshooting

4.1 Cannot access the Web User Interface

If a connection to the WUI cannot be established, network settings can be configured via the console view.

1. Login into the VLM via the console using the settings: lb100 login: bal

Password: 1fourall

Figure 4-1: Enter IP address

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 field and press Enter on the keyboard.

Figure 4-2: Enter default gateway address

(20)

Figure 4-3: Nameserver IP addresses

4. Enter a space-separated list of nameserver IP addresses.

5. 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.

6. Contact the local KEMP Customer Services Representative for further support if needed.

Factory Reset

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 Section 4.1.

VMware Tools

The VLM does not support integration with VMware Tools.

However, the NIC device drivers that are part of VMware Tools have been integrated with the VLM which, for many users, negates the need for using VMware Tools.

Working with VMware Virtual Switches

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.

(21)

References

Unless otherwise specified, the below documents can be found at http://www.kemptechnologies.com/documentation.

(22)

Document History

Date Change Reason for Change Ver Resp

Jun 2012 Initial draft of the document Initial draft of the document 1.0 DD

Oct 2012 Added not re VMware Tools Note required 1.1 DD

Nov 2012 Updates made EULA screen update 1.2 DD

Nov 2012 Updates Made Introduction of VLM-DE product 1.3 DD

Jan 2013 Minor Updates made As per 6.0-42 updates 1.4 DD

May 2013 Updates made As per 7.0-4 updates 1.5 DD

July 2013 Minor updates Updates made 1.6 LB

July 2013 Updated made New licensing process 1.7 LB

July 2013 Minor change Added supported versions 1.8 LB

Sep 2013 Minor changes Minor release updates 1.9 LB

Sep 2013 Order of steps changed More logical order 1.10 LB

Nov 2013 Release updates Minor updates for 7.0-8e release 1.11 LB

Jan 2014 Minor update Release update 1.12 LB

Feb 2014 Release updates Updates for 7.0-12a release 1.13 LB

Feb 2014 Minor change Additional supported versions 1.14 LB

Virtual LoadMaster for VMware ESX, ESXi using vsphere