Hyper V Windows 2012 and 8. Virtual LoadMaster for Microsoft Hyper V on Windows Server 2012, 2012 R2 and Windows 8. Installation Guide

(1)

Virtual LoadMaster for Microsoft Hyper‐V

on Windows Server 2012, 2012 R2 and

Windows 8

Installation Guide

VERSION: 3.0

UPDATED: SEPTEMBER 2015

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

Portions of the LoadMaster software are copyright (C) 1989, 1991 Free Software Foundation, Inc. ‐51 Franklin Street, Fifth Floor, Boston, MA 02110‐1301, USA‐ and KEMP Technologies Inc. is in full compliance of the GNU license requirements, Version 2, June 1991. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

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

3. This notice may not be removed or altered from any source distribution.

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.

Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and

6,970,933

(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 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. For instructions on Windows Server 2008 R2, refer to the Microsoft Hyper‐V – Windows 2008 R2, Installation Guide.

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

(6)

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

2.1 Download the Hyper‐V Files

The 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:

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

2. Within the Select the hypervisor platform section, select the option for Microsoft Hyper‐V.

3. Click on the Download Hyper‐V VM button.

4. Read the end user agreement.

5. To continue, select your country from the drop‐down list.

6. Click on the Agree button.

7. Download the Hyper‐V zip file.

8. Unzip the contents of the file to an accessible location within the hyper‐v environment.

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

(7)

Installing Virtual LoadMaster (VLM) using Hyper‐V Manager

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

(8)

3. Click Next.

4. Figure 2‐3: Import Virtual Machine

5. Click the Browse button and browse to where you downloaded the Hyper‐V files.

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

(9)

Figure 2‐4: Select the VLM

7. Select the VLM and click Next.

8. Select the Copy the virtual machine (create a new unique ID) option.

9. Choose your destination and hard disks.

10. Click the Import button.

11. The virtual machine should be imported and should now appear within the Virtual Machines pane in the Hyper‐V Manager.

2.3 Check the Network Adapter Settings

Before starting the VLM we must first verify that the network adapters are configured correctly.

1. Right‐click on the virtual machine you have imported within the Virtual Machines pane.

2. Click on the Settings option.

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

(10)

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

5. Click on the OK button.

6. Repeat these steps for the second network adapter.

Jumbo frames are supported for Hyper-V network synthetic drivers.

2.4 Power On the LoadMaster

Once the VLM has been deployed it can be powered on:

(11)

1. Right‐click the Virtual Machine that was imported within the Virtual Machines pane.

2. Click Start.

The VLM should begin to boot up.

3. Right‐click the VLM and select Connect to open the console window.

Figure 2‐6: IP address

4. The VLM should obtain an IP address via DHCP. Make a note of this address.

If the VLM does not obtain an IP address, or if the IP address needs to be changed, it can be manually configured in the console by following the steps in Section 3.1.

2.5 Licensing and Configuration

The LoadMaster must now be configured to operate within the network configuration.

1. In an internet browser, enter the IP address that was noted previously.

2. Ensure to enter https:// before the IP address.

3. A warning may appear regarding website security certificates. Please click the continue/ignore option.

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

(12)

Figure 2‐7: License type selection

5. Select the relevant license type.

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

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

8. The Change Password screen appears

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

Password input field.

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

11. In the screen informing that the password has changed, click the Continue button

(13)

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

13. Click on the OK button

14. The Appliance Vitals screen of the LoadMaster will appear.

Figure 2‐9: Appliance Vitals

15. Go to System Configuration > Network Setup in the main menu.

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

(14)

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

18. Click on the Set Address button

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

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

21. Click on the Set Address button

This interface is optional, depending on the network configuration.

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

23. In the Hostname configuration screen, enter the hostname into the Current Hostname

input field.

24. Click on the Set Hostname button.

25. Click on the Local DNS Configuration > DNS Configuration menu option.

(15)

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

27. Click on the Add button.

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

29. Click the Add button.

30. Click the System Configuration > Network Setup > Default Gateway menu option.

31. In the DNS configuration screen, enter the IP address of the default gateway into the

IPv4 Default Gateway Address input field.

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

33. 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 http://kemptechnologies.com/loadmaster‐

documentation page.

(16)

3 Troubleshooting

3.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 3‐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 3‐2: Enter default gateway address

3. Enter the IP address of the Default Gateway.

(17)

Troubleshooting

Figure 3‐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.

3.2 NIC Types Cannot Be Mixed

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

3.3 Static MAC Addresses Must Be Configured

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

3.4 Make this VM Highly Available Option is Greyed Out

There 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:

1. Open the Virtual Machine Manager console.

2. Right‐click the relevant Virtual Machine that you want to make highly‐available and select Migrate.

3. Select the current host from the list for migration.

4. Click Yes to the prompt asking if you want to make the Virtual Machine highly available.

5. The path can be changed if needed. Click Next.

(18)

6. Select the network and click Move.

7. Wait for the migration to complete.

3.5 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 Section 3.1

(19)

References

4 References

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

Microsoft Hyper‐V – Windows 2008 R2, Installation Guide Licensing, Feature Description

(20)

Document History

Date Change Reason for Change Version Resp.

Jan 2015 Release update Updated for 7.1‐24 release 1.6 LB

Feb 2015 Minor update Enhancement made 1.7 LB

Apr 2015 Release update Updated for 7.1‐26 release 1.8 LB

Sept 2015 Screenshot updates LoadMaster WUI reskin 3.0 KG