KEMP Metered Licensing (MELA) allows the creation of an application delivery fabric that contains LoadMaster Application Delivery Controller (ADC) instances that are licensed for metered usage. If you are deploying a trial, the number of LoadMaster ADC instances is limited to 20 and will stay active for 60 days. Full support is available during the trial period.
If you are deploying a metered licensing subscription, MELA licenses as many LoadMaster instances as required and charges monthly in arrears based on measured usage.
The application delivery fabric consists of two components â€“ the KEMP 360 Central instance for licensing/management and the individual ADC instances. Licenses may be issued to ADC instances on any supported platform from a single KEMP 360 Central.
|Platform||KEMP 360 Central||LoadMaster|
|Amazon Web Services (AWS)||Y||Y|
A KEMP 360 Central instance is required to license the LoadMaster ADCs and to provide monitoring and management and can be deployed on any supported platform.
LoadMaster instances may be deployed on any platform that can communicate with the KEMP 360 Central instance.
- To license KEMP 360 Central for MELA, you need a KEMP ID and an Order ID. The Order ID is either:
- Your Contract ID if you have purchased a subscription
- The Product Key if you registered for a trial
- A supported hypervisor or cloud platform
- Bi-directional communication between KEMP 360 Central and managed LoadMaster instances over TCP/443 (TCP/8443 for Azure/AWS)
- Syslog traffic from LoadMaster to KEMP 360 Central over UDP/514 (optional)
- KEMP 360 Central to have Simple Mail Transfer Protocol (SMTP) communication to a local SMTP server over TCP/25. This is optional if no notifications are required and MELA reporting is through HTTPs to ALSI (KEMP licensing and reporting services)
- KEMP 360 Central to have access to a DNS resolver over TCP/UDP/53
- KEMP 360 Central to have access to ALSI through TCP/443
- LoadMaster instances can be accessed through a routable network or through a network address translation (NAT) device
Virtual Machine Requirements
Note that with Version 1.25.2, the default minimum Virtual Machine provisioning requirements for new installs have been updated as follows:
|Resource||V1.24 and earlier firmware||V1.25.2 and later firmware|
|CPU||Two cores||Four cores|
|RAM||4 GB||8 GB|
|Disk Storage||40 GB||250 GB|
Upgrades to Version 1.25.2 and later releases will not update existing Virtual Machine resources. To modify your current Virtual Machine configuration to conform to the above minimum values, contact KEMP Support.
The following steps should be followed to deploy an operational MELA environment.
KEMP 360 Central and LoadMaster are delivered as Virtual Machine (VM) images for hypervisor platforms and are available in the cloud marketplaces for Amazon Web Services (AWS) and Azure.
Application Delivery Fabric requires a special build of both KEMP 360 Central and LoadMaster. If deploying from cloud marketplaces (AWS/Azure), select the SPLA/MELA options. For all other platforms, the images can be downloaded from the following locations:
The platform-specific deployment guides for KEMP 360 Central are available on the KEMP Support site. The only deviation from these guides for MELA is as follows:
- If you are deploying in AWS/Azure, ensure you have the correct MELA image by selecting the metered licensing product in the cloud marketplaces
- When you encounter the licensing screen, enter the Order ID, which is either the Contract ID provided by KEMP or the Product Key provided during trial registration
The following KEMP 360 Central Deployment Guides are available on the KEMP Support site:
When presented with the licensing screen during installation, enter the Order ID along with your KEMP ID credentials. This licenses the KEMP 360 Central instance as a MELA licensing and reporting server.
After licensing, set the password for the admin user. The admin user is the default user on KEMP 360 Central and has all privileges. Additional user entities can be created with role-based access.
Once licensed, you are requested to input details on LoadMasters to be added. As no MELA licensed LoadMasters are deployed, this stage can be skipped.
You are also prompted for an SMTP relay to deliver alerts by email. This can be configured at this stage or skipped for later configuration.
There are a number of system settings on KEMP 360 Central that are optional. Full details on configuration is available in the KEMP 360 Central Feature Description document on the KEMP Support site.
|NTP Time Server||An NTP server is not mandatory. Using an external time server ensures that the system time on KEMP 360 Central (and LoadMaster instances) is correct and synchronized with the wider infrastructure.|
|SMTP Relay||An SMTP relay is not mandatory. If configured, notifications may be set by email and email may be used to deliver usage data to KEMP.|
|Role Based Access||In addition to the default admin user, other users and groups can be added and configured for role-based access.|
|Scheduled Reporting||The system can autogenerate reports and deliver them by email. An SMTP relay is required for this feature.|
Your KEMP 360 Central system is now ready to license metered LoadMaster instances.
LoadMaster instances can be deployed on Hyper-V, VMware, XEN, KVM, and VirtualBox hypervisors and on the Azure and AWS public clouds. A KEMP 360 Central MELA server can license LoadMasters on any platform as long as there is IP connectivity between the LoadMaster and KEMP 360 Central.
The hypervisor versions can be downloaded from https://kemptechnologies.com/spla-download and the Azure and AWS versions are available in the respective marketplaces as License Agreement Based LoadMaster (MELA/SPLA).
In the Azure MarketPlace, select License Agreement Based LoadMaster (MELA/SPLA) from the dropdown list under Plans + Pricing.
In the AWS Marketplace, select License Agreement Based LoadMaster for AWS (MELA).
Guidelines on how to deploy LoadMaster for each platform are available in the KEMP Resource Library.
- LoadMaster Installation Guide for Hyper-V
- LoadMaster Installation Guide for VMware (ESX, ESXi, and vSphere)
- LoadMaster Installation Guide for KVM
- LoadMaster Installation Guide for XEN
- LoadMaster Installation Guide for Oracle VirtualBox
- LoadMaster for Azure Feature Description
- LoadMaster for AWS Feature Description
For metered licensing, the LoadMaster license is provided by KEMP 360 Central.
Ensure you select KEMP 360 Central Licensing as the license method (select Local Activation for pre 7.2.43 releases). Selection of any other licensing method may result in a non-metered license being assigned.
You are now prompted for the Host and Port of the KEMP 360 Central instance deployed earlier.
When KEMP 360 Central Licensing is selected, a screen (similar to the one above) appears. If this screen does not appear, you are not using the correct version of the LoadMaster. Contact a KEMP representative if this is the case.
1. Type the IP address or FQDN of KEMP 360 Central in the Host text box.
2. Type the Port to access KEMP 360 Central on in the Port text box.
3. Click Activate.
The LoadMaster contacts the KEMP 360 Central server on the IP address and port specified and requests a license.
In addition to providing licensing, LoadMaster instances can be managed by KEMP 360 Central. Newly licensed LoadMasters are not added to the management domain by default and must be manually configured for management as follows.
Newly licensed LoadMasters are listed in the KEMP 360 Central UI in the networks list and can be identified by the icon below.
To add the LoadMaster for management, select the LoadMaster and click the edit icon in the bottom left of the screen.
This prompts for the LoadMaster credentials and optionally allows a nickname to be assigned.
For Azure and AWS LoadMasters, the port must be set to 8443.
Once added, the KEMP 360 Central system can monitor and manage the LoadMaster.
Client traffic is decrypted/encrypted on the LoadMaster and passed unencrypted to the application servers on port 80. It is assumed that the LoadMaster is configured with a single IP address in the guidelines below.
1. Login to the LoadMaster UI by opening a https session (port 443 default/8443 on Azure/AWS) on the LoadMaster IP address. The default username is bal and the password is what was set earlier when the LoadMaster was provisioned.
2. In the navigation menu, select Virtual Services and the Add New option.
3. Set the Virtual Address to the IP address of the LoadMaster instance.
4. Set the port to 443 because you want to handle SSL traffic.
5. Type a service name (optional) and click Add this Virtual Service.
6. Expand the SSL Properties section.
7. Select the SSL Acceleration Enabled check box. The LoadMaster generates a self-signed certificate for the SSL service that can be replaced with a trusted certificate if required.
8. Add the web application servers. With LoadMaster, the application servers are referred to as Real Servers.
9. In the Real Servers section, select Add New.
10. Specify the Real Server IP address and port. The other settings may be left as default.
11. Repeat for each Real Server you want to add.
You should now be able to send traffic through the load balancer on port 443, which is then forwarded to the Real Servers. For further guidance on configuring service options, consult the KEMP guide to configuring an SSL virtual service. Detailed documentation on LoadMaster configuration and features is available from the KEMP Resource Library.
The LoadMaster instances licensed under MELA have no license limits on performance and are only limited by the underlying infrastructure. This provides the capability to scale within a single instance, which may be sufficient for many environments. LoadMaster instances may also be clustered to provide scale-out capability. With clustering, multiple LoadMaster instances operate in parallel to deliver virtual services with individual instances being able to scale to the maximum capability of the underlying infrastructure. Additional cluster members may be added or removed on demand to provide the desired capacity.
To evaluate scaling using clustering, consult the LoadMaster Clustering documentation.
Within the KEMP 360 application delivery fabric, ADC instances may be deployed, managed, and licensed across multiple hypervisors and clouds from a single KEMP 360 Central providing a single unified view of all ADC resources regardless of location.
A quick way to evaluate this multi-platform support is to deploy a LoadMaster instance on desktop-based hypervisor or on a public cloud such as Azure or AWS. When deploying on cloud platforms, the LoadMaster instance is behind a network address translation (NAT) and has a public IP and a private IP. Use the Public IP when adding the LoadMaster instance to KEMP 360 Central.
Within KEMP 360 Central, all ADC resources, across all platforms, are available and may be monitored and managed.
A key to flexible application delivery is the ability to move (or clone) services between ADCs. KEMP 360 Central can take a Virtual Service configuration for an application and move it to another ADC. To move (or clone) a Virtual Service, follow these steps:
1. Click the Network and Device Administration icon (cloud icon) on the left.
2. Select Service Configuration.
3. Select the relevant ADC on the left.
4. Click the VS Motion Migrate icon for the Virtual Service you want to migrate.
5. Select the target ADC.
6. Enter the IP address and port of the target ADC.
7. Click Copy to clone the service on the target ADC then click Move to remove the service from the source ADC and create it in the target ADC.
KEMP 360 Central is KEMPâ€™s management and monitoring platform, which also acts as the licensing and metering service for MELA. LoadMaster ADCs under MELA may be monitored and managed from KEMP 360 Central. The Global Dashboard provides a snapshot of the health and status of the application delivery fabric.
The widgets on the Global Dashboard provide a quick view of the status and link to the underlying detail.
- Device Health â€“ Status of the ADC instance
- Local Licenses - Number of ADC instances licensed for MELA
- Non-Local Licensing â€“ Status on perpetual and subscription licenses
- Top Utilization â€“ List of busiest ADC instances
- Log Summary â€“ Breakdown of ADC log events by status
- VS Status â€“ Summary of Virtual Service status
- Real Server Status â€“ Summary of the application server status
- Administratively Disabled â€“ Displays the number of Real Servers and Virtual Services that are administratively disabled
- Active Connections - Displays the total number of active connections for all managed devices
- WAF Statistics - Displays the number of configured WAF services and the number of alerts and events in the past 24 hours
For resilience, ADC instances are normally deployed as High Availability (HA) pairs. With LoadMaster HA, one instance is active while the other is in standby. In the event of a failure, the standby instance assumes the active role resulting in no service disruption.
To configure high availability on LoadMaster, consult the High Availability documentation.
With metered licensing, HA is essentially free because the HA pair is considered a single unit for billing purposes. Usage traffic is reported separately for both units. Evaluation of HA capabilities is as simple as turning off the primary LoadMaster, which automatically promotes the secondary LoadMaster as the active ADC.
This document was last updated on 25 July 2018.