LoadMaster for Azure (VM Depot)

 

1Introduction

This document is intended to provide an overview of LoadMaster for Azure and to introduce some basic aspects of LoadMaster functionality.

1.1Load Balancing in Microsoft Azure

Before we create a LoadMaster Virtual Machine (VM) in Azure, it is important to understand the traffic flow so that VMs in Microsoft Azure can be configured appropriately.

Microsoft Azure Infrastructure as a Service (IaaS) deployments accept traffic only on published endpoints. Any request to access Microsoft Azure workloads passes through the default load balancing layer of the Microsoft Azure platform. Figure 11 depicts the default deployment without the use of a KEMP LoadMaster in Azure.

Figure 1‑1: Microsoft Azure Load Balancer

Any workload being published consists of a cloud service, which represents a single VM or multiple VMs. When a VM is created, if a cloud service exists, you have an option to connect the VM to an existing cloud service. As more VMs are connected to an existing VM (and thus to an existing Cloud Service), the built-in Microsoft Azure load balancer distributes connections when creating a load-balanced endpoint.

If you wish to use LoadMaster for Azure for your deployment, the following steps must be completed:

  1. The LoadMaster for Azure needs to be deployed first, creating the required cloud service.
  2. All the VMs that need to be load balanced using the LoadMaster can then be created and must be connected to the existing LoadMaster VM to create the required grouping.
  3. Finally, when creating endpoints, we cannot use theLoad-Balance traffic on an existing endpoint option in Azure as we do not want to use the Microsoft Azure Load Balancer to load balance incoming connections.

Figure 12 depicts the flow when LoadMaster for Azure is deployed:

Figure 1‑2: LoadMaster for Azure

Notice that VM1, VM2 and VM3 in this example are grouped into a single cloud service and the endpoint for published Virtual Services will be created only on the LoadMaster VM. By doing this, we receive all load balanced traffic on the LoadMaster VM and the logic of load balancing incoming connections will be applied as per the configured Virtual Service on the LoadMaster for a given workload.

Also notice that VM1, VM2 and VM2 will not have any endpoints as they are not going to be published directly to the internet.

There may be exceptions to this rule for connections that require direct connectivity to the VM such as Remote Desktop Connections to Windows Server OS.

1.2Known Issues/Limitations

There are a couple of known issues/limitations to be aware of:

  • LoadMaster in Azure cannot be assigned to more than one network interface.

Dual-arm configurations are not possible due to this limitation.

  • All Virtual Services in Azure share a single IP address for a given LoadMaster deployment. You cannot publish more than one serviceon the same port for the same LoadMaster since additional IP addresses are not available.
  • If the services are HTTP or HTTPS services, content switching features included in the LoadMaster can be leveraged to publish multiple workloads sharing the same port.
  • Transparency is not possible in the Azure LoadMaster. Transparency must be disabled in the Virtual Service settings on the LoadMaster.

 

2Installation Prerequisites

2.1Prerequisites

To support LoadMaster for Azure, the following are required:

  • An active subscription of Microsoft Azure Virtual Machines
  • A client computer running Windows 7 or newer
  • Internet Explorer 9 or newer

2.2Importing the LoadMaster Image from VMDepot

Before deploying LoadMaster for Azure, you must create a reusable LoadMaster image within your Azure subscription. Follow the steps outlined below to create a LoadMaster image from VMdepot:

  1. Log in to the Azure Management Portal:https://manage.windowsazure.com
  2. Select Virtual Machinesin the navigation pane.
  3. Select the Images tab fromthe resulting page.
  4. Click theBrowse VM Depot option at the bottom of the page.
  5. From the Choose an Image dialog, select the KEMP LoadMaster for Azure RTM image.
  6. Click Next.
  7. Select the desired image region and storage account associated with the selected image region for your Azure subscription.
  8. Click Complete. This will initiate a copy of the LoadMaster image from VMDepot to your Azure subscription. Follow the next steps after the copy completes successfully.Upon successful completion, the newly created LoadMaster image will show the status Pending Registration.
  9. Click Register at the bottom of the page, provide a desired image name and click OK. Upon successful registration the image status will change to Available.

3Creating a LoadMaster VM in Azure

Please ensure that the prerequisites documented in the earlier section are met and an image for LoadMaster for Azure is created as outlined in Section 2.

3.1Creating a LoadMaster for Azure VM

The steps in this document reflect the steps in VM Depot. For steps in the Azure Marketplace (http://portal.azure.com), refer to the LoadMaster for Azure (Marketplace).

The following procedure describes how to set up LoadMaster for Azure from the image created earlier:

  1. From the Azure Management Portal, clickNew.
  2. Navigate toCompute > Virtual Machine> From Galleryin the resulting menu structure.
  3. Click From Gallery. This will open theCreate a Virtual Machinedialog.
  1. Click theMy Imagessection.
  2. Select the LoadMaster for Azure image you created earlier.
  3. Click Nextto proceed to the next step.
  4. In the resulting dialog, provide details to create the VM. The details required to create new VM are:
  1. Virtual Machine Name: Provide a unique name for VM identification
  2. Size: Choose from the available VM sizes to fit your needs

Please contact KEMP for assistance with sizing.

  1. New User Name:This will not be used by LoadMaster for Azure. Provide a name of your choice.
  2. Authentication:This will not be used by LoadMaster for Azure. Provide a password of your choice. Do not use the SSH Key option for authentication.
  1. Click Nextto proceed to the next step.
  2. Click Create a new cloud service.
  3. Provide a unique cloud service DNS name. This will become your endpoint. This is the name that will be used to access the LoadMaster WUI.
  4. Make appropriate selections for Region/Affinity Group/Virtual Network, Virtual Network Subnets and Availability Set to meet your requirements.
  5. Click Next.

Since the LoadMaster is a Linux VM (as identified by the image created earlier), Azure will list SSH as a default endpoint. The LoadMaster uses Web UI for management. You will need to create an endpoint for TCP port 8443.

  1. Click theEnter or Select a Valuedropdown.
  2. Select HTTPS from the list.
  3. Change the Public and Private ports from 443 to 8443.
  4. Change the name to any desired name, for exampleManagement.
  5. Click Next to start the creation of LoadMaster for Azure VM.

The creation of a VM may take a few minutes or more depending on the Azure portal’s responsiveness and other factors. Ensure that the VM is created without any errors. Resolve any errors if needed.

3.2Licensing and Initial Configuration

The following procedure will help you set up LoadMaster for Azure by ensuring appropriate licensing and basic configuration before you can create a Virtual Service and publish the required workloads:

  1. Using a supported web browser, navigate to https://<cloudserviceurl>:8443.

Substitute cloudserviceurl with the cloud service DNS name you created in previous section.

  1. Take the appropriate steps to acknowledge notification about the self-signed certificate in order to proceed.
  2. Before using the LoadMaster, it must be licensed. For instructions on how to license the LoadMaster, refer to the Licensing, Feature Description.

Online Licensing is the only available method of licensing for Azure. Also, Azure licenses are automatically issued as permanent – there are no trial licenses.

  1. The LoadMaster requires you to login before you can proceed any further. Provide the default usernamebaland password1fourallto proceed. You will be required to change the default password soon after.
  2. Immediately after providing initial login information, you will be presented with the End User License Agreement (EULA). You must accept the EULA to proceed further. ClickAgreeto accept the EULA.
  3. After accepting the EULA, you will be presented with a password change screen. Provide a secure password of your choice. ClickSet Passwordto commit changes. The new password is effective immediately.
  4. On the password notification screen, clickContinue.
  5. The LoadMaster will require you to authenticate with a new password. Enter balin the user field and the new password in the password field. ClickOkto proceed.
  6. After successful authentication, you will be presented with the main menu and home screen of the LoadMaster.

Before you can create Virtual Services, you should create VMs that you will be load balancing through LoadMaster for Azure. The following section will provide some details on this topic.

4Creating VMs and Virtual Service Endpoints

While creating VMs is fundamentally not very different from what we covered in Section 3, we need to make sure that the VMs that need to be load balanced by LoadMaster for Azure are not stand-alone VMs. The following procedure provides an overview of creating a connected virtual machine.

4.1Creating a Connected VM

To create a connected VM, follow the steps below:

  1. From the Azure Management Portal, click New.
  2. Navigate to Compute > Virtual Machine > From Gallery in the resulting menu structure.
  3. Click From Gallery. This will open the Create a Virtual Machine dialog.
  1. Choose an image or disk from the resulting dialog to create the required VM.
  2. Click Nextto proceed to the next step.
  3. In the resulting dialog, provide details to create the VM. The details required to create the new VM are:
  1. Virtual Machine Name:Provide a unique name for VM identification
  1. Size:Choose from available VM sizes to fit your needs
  2. New User Name: Provide a desired username
  3. Authentication: Provide a desired password
  1. Click Nextto proceed to the next step.
  2. It is important that you select Connect to an Existing Virtual Machine here. Select the LoadMaster for Azure VM that was created in Section 3 earlier.
  3. Make the appropriate selections for Storage Account, Region/Affinity Group/Virtual Network, and Virtual Network Subnets to meet your requirements.
  4. Click Next.
  5. Make the appropriate selection for Availability Set to meet your requirements.
  6. Click Next to start creation of the VM.

Create more VMs if needed and then proceed to the next step to create a Virtual Service.

4.2Creating a Virtual Service Endpoint

For each service that needs to be published (i.e. a website on TCP port 80 or a web service using SSL on TCP port 443), the corresponding endpoint needs to be created. Since we need to use the LoadMaster as the end point for connections from clients, we need to make sure we create the endpoint on the LoadMaster VM we created earlier and not for VMs that are being load balanced.

The following steps describe how to create an endpoint:

  1. From the Microsoft Azure management portal, go to theVirtual Machines section and select the LoadMaster for Azure VM created earlier.
  1. Select theEndpoints tab.
  2. Click Add to create a new endpoint.
  3. Select Add Endpoint in the resulting dialog.

It is important that you do not create a load-balance traffic on an existing endpoint here. We need to use the LoadMaster as load balancing mechanism, not the Azure load balancer.

  1. Click Next.
  2. In resulting dialog, provide the following information:
  1. Name: Name to identify service being published
  1. Protocol: Protocol being published (TCP or UDP)
  2. Public Port: The port that the client will connect to
  3. Private Port: The port that the LoadMaster will listen on (this usually is same as the port that the load balanced server is listening on)
  1. Click Nextto start the creation of the endpoint.

By creating a Virtual Service endpoint, Microsoft Azure starts accepting and passing traffic for a given endpoint to the VM it is configured for. This will enable the LoadMaster to receive traffic intended for the Virtual Service. A Virtual Service must be created on the LoadMaster in order to start distributing traffic to servers being load balanced for a given Virtual Service. Section 5 outlines the steps to create a Virtual Service.

5Creating Virtual Services

The following steps describe how to create a Virtual Service on the LoadMaster for Azure.

  1. Using a supported web browser, navigate to https://<cloudserviceurl>:8443. Substitute cloudserviceurl with the cloud service DNS name you created in Section3.2.
  1. Take the appropriate steps to acknowledge notification about the self-signed certificate to proceed further.

The certificate used by the WUI will take the public name used by Azure/AWS.

  1. Login using the usernamebaland password that you created earlier in Section 3.2.
  2. From the main menu, expand theVirtual Servicessection and clickAdd New.
  3. In theVirtual Service parameters section, provide the following details:
  1. Virtual Address: In Microsoft Azure, currently only one IP address can be assigned to a VM, limiting the LoadMaster to a single IP. To create a Virtual Service, you must use the internal IP address of the LoadMaster VM. You can find the internal IP address from the VM’s dashboard page.
  2. Port: This must be the same port asthe Private Portdefined while creating the endpoint in earlier section.
  1. Service Name: While optional, service name helps identify the purpose of the Virtual Service being created
  2. Protocol: This must be the same as the protocol selected during creation of the endpoint in the earlier section.
  1. Click theAdd this Virtual Servicebutton.
  2. Expand the Standard Options section.

Figure 5‑1: Standard Options

  1. Remove the tick from the Transparency check box.

Virtual Services in the LoadMaster for Azure must be non-transparent.

  1. Configure the remaining virtual parameters as necessary. Use the KEMP LoadMaster guides from the Product Documentation section located on the KEMP Technologies website: http://kemptechnologies.com/loadmaster-documentation
  2. Add VMs being load balanced in theReal Serverssection of the Virtual Service.

Repeat the steps above as necessary to create more Virtual Services on LoadMaster for Azure.

6References

While the instructions above provide a basic overview of how to deploy and configure LoadMaster for Azure, it is not designed to be a comprehensive guide to configure every possible workload. This section identifies some of many guides published on our resources section of our website. Unless otherwise specified, the following documents can be found at

: http://kemptechnologies.com/loadmaster-documentation

.

LoadMaster for Azure (Marketplace) KEMP LoadMaster, Product Overview Web User Interface (WUI), Configuration Guide CLI, Interface Description RESTful API, Interface Description Virtual Services and Templates, Feature Description SubVSs, Feature Description SSL Accelerated Services, Feature Description Port Following, Feature Description Content Rules, Feature Description ESP, Feature Description Quickstart Guide Licensing, Feature Description

You can find more documentation here: http://kemptechnologies.com/loadmaster-documentation

You can engage in community discussions on forums at: http://forums.kemptechnologies.com/

Document History

Date

Change

Reason for Change

Ver.

Resp.

Sep 2014

Release updates

Updates for 7.1-20 release

1.10

LB

Feb 2015

Minor changes

Added references

1.11

LB

Sep 2015

Release updates

Updates for 7.1-30 release

3.0

LB

Was this article helpful?

0 out of 0 found this helpful

Comments