Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Kemp 360 Central V2.1 Release Notes

Version 2.1 of Kemp 360 Central was released in March 2019 and is a feature and bug-fix release. It contains the new features, resolved issues, and known issues described in the following subsections.

For installation prerequisites, upgrade path information, virtual machine requirements, and other details, please see the article Installing and Upgrading Kemp 360 Central.

For more information on all features described below, see the Feature Description and the rest of the Kemp 360 Central documentation in the Documentation Library.

New Features

LoadMaster Profile Enhancements (SPLA/MELA Customers Only)

Express (Quick) Workflow

A new Quick Mode for creating LoadMaster Profiles is provided that is template-based and doesn't require full manual configuration of the LoadMaster (as does the Advanced Mode provided in V2.0). You can choose from a pre-selected set of Kemp’s most popularly-downloaded Application Templates, provide the information necessary to deploy the template on a LoadMaster (or HA pair of LoadMasters), and then deploy using the automated or manual deployment methods.

Automated Deployment -- VMware ESXi

This enhancement to automated deployments extends VMware auto-deployment to support direct deployment to VMware ESXi servers. It is intended for use with standalone ESXi servers that are not managed via vCenter. To deploy an ESXi server managed via vCenter, use the existing VMware vCenter target environment instead.

Cloning LoadMaster Profiles

Adds the ability to make a simple copy (or clone) of an existing deployment, so that it can be re-used. The user selects and existing profile, supplies new LoadMaster device parameters (IP address, credentials), and the profile is copied without making any changes to the internal LoadMaster configuration (e.g., Virtual Services, SubVSs, and Real  Servers). The resulting profile is placed into a Draft state, and so must be edited to modify internal IPs and any other configuration details required before being deployed.

Deployment History

In Version 2.0, you had to open the hypervisor logs and K360C system logs to see messages associated with automated deployments. This enhancement provides a separate table in the UI that has an entry for every attempted deployment; that entry can be expanded to display all the error messages either received from the hypervisor or generated by Kemp 360 Central during an automated deployment attempt. This is separate from the Kemp 360 Central logs; i.e., the histories can be deleted from the UI without removing any messages from the logs.

MELA Activations Table Enhancements

Several improvements to the Settings and Configuration > Metered Licensing Management table have been made to make it more useful. Among them:

  • An IP Address column is added to show the address of each licensed device.
  • Tooltips are added to display device nicknames.
  • If Kemp 360 Central is in an HA configuration, the table indicates which of the HA pair units each LoadMaster was licensed against.
  • Help text is added for the Status column to explain all possible status values.
  • The table can now be sorted by any column.

Operational Notes

Upgrade to Version 2.1 Requires Version 2.0

Starting with V2.1, upgrade directly from pre-Version 2.0 releases is not allowed. If you are running Version 1.27 or an earlier release of Kemp 360 Central, you must first upgrade to Version 2.0, and then upgrade to Version 2.1.

Resolved Issues

The following are the major issues fixed in Version 2.1.




UI issues with Safari on Mac OS: Fixed UI display issues observed using Safari on some MacOS versions.


Redirect Status Inconsistent: Fixed an issue in the UI where the Monitoring page shows different status values for LoadMaster Redirect VSs at the network and device levels.


UI Navigation: Menu items can now be activated by clicking anywhere in the highlighted area, not just on the text.


Manual Poll Progress bar: Fixed issues with the progress bar not appearing after the Update button on the Monitoring page was clicked.


Virtual Service status: Fixed an issue that caused a Virtual Service with no health checks defined to show a status of ‘Unknown’, when the status should be ‘Unchecked’.


Editing a Device: Modified the Edit Device dialog so that the default Network setting is Auto-Select, similar to the Add Device dialog.


Known Issues

The following list includes the most serious known issues in the product. If you experience an issue that is not on this list, please contact Kemp Support for further information.




LoadMaster Deployments: A manually or automatically deployed LoadMaster Profile created using Quick Mode will not have a DNS server configured by default, and so operations that depend on DNS being configured (such as downloading GEO and WAF rules) will fail. The workaround is to add a DNS server to LoadMaster after it's deployed. The same issue can happen when deploying an Advanced mode profile, if the user failed to specify a DNS server in the LM WUI Emulator.


Virtual Service Naming: Do not exclusively use numeric characters in a Virtual Service name; for example, ‘12345’. This causes an error to be returned by LoadMaster and the Virtual Service will not be created.


LoadMaster Firmware Upgrade: Attempting to update the firmware on a LoadMaster to the same release that is already installed results in two messages appearing in the Kemp 360 Central UI:

The LoadMaster device ... is updating.
Loadmaster ... firmware failed to update.

As indicated by the second message, the upgrade was unsuccessful; the progress bar for the upgrade, however, remains active.


Online Licensing: In the advanced options for online licensing on the initial licensing page, setting a proxy server IP address that does not point to a working proxy server will result in an 'Incorrect username or password.' error. If you receive this error when using proxy settings to perform online licensing, confirm with your network administrator that the proxy server IP address and port you are using are correct and ensure that Kemp 360 Central is located on a network that has access to the proxy server's network.


Reporting: Special characters used in network and device names are not displayed properly in the device selection list on the Reporting page.


Logging: In the log viewer, the real server drop-down does not display ports along with the IP, so you can't choose a specific server from a group of servers running on the same device using different ports. The workaround is to use the Text search instead to search for an IP:port combination.


Unmanage Devices: An unmanaged device is not polled immediately upon first contact from Kemp 360 Central. This means that some operations on such a device (for example, VS Motion Migrate) cannot be performed until the first time the device is polled for configuration (which occurs every 60 minutes), or until you manually poll the device using the Update button on the device's Monitoring page.


Virtual Service Wildcard Addresses: If a Virtual Service uses a wildcard (*) IP address, you cannot add Real Servers to the Virtual Service from Kemp 360 Central. The workaround is to add them using the LoadMaster UI; they are then displayed in the Kemp 360 Central UI.


LoadMaster HA Pairs: In the Log Viewer, the Virtual Service and Real Server search boxes do not display Virtual Services and Real Servers for the HA nodes. The workaround is to use the Text search box instead.


LoadMaster HA Pairs: If the shared IP address for a LoadMaster HA pair cannot be contacted, both HA units show their status as "Standby". You must restore access to the shared IP address from Kemp 360 Central to correct this issue. Possible causes are that the network of the shared IP address is unreachable or that the authentication parameters on one or both of the HA units in the pair was modified on the LoadMaster without making the same modifications on Kemp 360 Central.


LoadMaster HA Pairs: When setting up Role Based Access Control (RBAC) for a user on LoadMasters configured in HA mode, ensure to assign the same level of access to all three devices in the LoadMaster HA pair; the HA1 device, the HA2 device, and the shared IP device. This is not enforced by the UI.


LoadMaster HA Pairs: If a LoadMaster HA unit configured in a LoadMaster HA pair is moved to "standalone" mode in the LoadMaster WUI, the effect on status reporting for that device in the Kemp 360 Central UI depends on the LoadMaster Operating System (LMOS) release:

  • If the now standalone mode device is running on LMOS release 7.2.37 or later, that unit's device in Kemp 360 Central always shows as "down" in the Kemp 360 Central UI.
  • If the now standalone mode device is running an LMOS release earlier than 7.2.37, the unit always shows its HA status as "Standby", even when it is "Active". The only indication you get that there is a problem is that the now standalone unit will never assume the "Active" role, even when the other unit is unavailable.


Network Level System Configuration Tabs: Errors can occur when selecting multiple devices in the System Reboot, Templates, Update LoadMaster Firmware, and Backup/Restore menus in the System Configuration tab at the network level. If you experience these errors, use the System Configuration tab at the device level instead.


RBAC: If you create a user, give it full write permissions, and add it as a member of a custom user group - any device that user adds is not visible to that user in the network tree. The workaround is to specifically add the new device to the custom group.


Virtual Service Configuration: Configuring a Layer 7 specific parameter on a Layer 4 Virtual Service should both enable Layer 7 services on the Virtual Service and set the new parameter value. Instead, only Layer 7 is enabled; the Layer 7 specific parameter is not set to the value specified.


VS Motion: When using the VS Motion Migrate function, the IP address and port for the new Virtual Service is not automatically updated when you select a LoadMaster from the Target drop-down list. You must update the address manually to an available IP address on a network accessible to the target LoadMaster.


UDP Virtual Services: Setting the alternate IP address does not work on UDP services.


Known Issues with Specific LoadMaster Releases

The following table lists all issues in Kemp 360 Central that occur only with specific LoadMaster releases. If there is a fix for the issue, the release containing the fix is listed in the description.




MELA LoadMaster HA Units Failover Every 5 Minutes: LoadMaster HA Pairs fail over every 5 minutes. This issue has been addressed in LMOS 7.2.43.


MELA Licensing: When re-activating a previously activated LoadMaster, it is not possible to choose a license on the LoadMaster that is above the previously-selected license in the menu. This issue is addressed in LoadMaster Operating System (LMOS) version 7.2.41.


Virtual Service Status: Issues with Virtual Service status returns from LoadMasters running version can result in incorrect Virtual Service health statuses being displayed in the Kemp 360 Central UI. This can occur when either Virtual Service status is requested from the LoadMaster, or when the Virtual Service is modified (if the issue is not already present). In the latter case, the issue should correct itself on the next UI status update (within a minute). This will be addressed in LMOS 7.2.46.


Lost Contact with LoadMaster HA Standby Unit: When monitoring two LoadMasters that are configured in an HA pair, and certificate authentication is in use, it is possible for Kemp 360 Central to lose contact with the standby (passive) LoadMaster. The recommended workaround is to reboot the standby LoadMaster. This has no effect on traffic through the HA pair (because this is the standby unit) and certificate-based authentication with Kemp 360 Central should be restored after the reboot. An alternative workaround is to edit the LoadMaster HA devices on Kemp 360 Central and switch the authentication setting from certificate to basic authentication. This issue is addressed in the and 7.2.40 LoadMaster releases.


MELA LoadMaster HA Units Lose Connectivity: This issue occurs in 7.2.38 and causes MELA LoadMaster HA units to lose network connectivity. A reboot results in the same problem recurring. This issue is fixed in LMOS 7.2.39. Also see PD-11560, above.


Special Characters in LoadMaster Passwords: Most special characters supported in LoadMaster passwords are supported in V1.15 and later releases of Kemp 360 Central. However, because of an issue in the LoadMaster Application Program Interface (API), quotes and spaces in LoadMaster passwords can cause authentication from Kemp 360 Central to fail. However, they work without issue when logging directly into the LoadMaster WUI. As a workaround, you should log into the LoadMaster and update the password for the login that you supply to Kemp 360 Central so that it does not contain any spaces or quotes. Then, add the device to Kemp 360 Central. This issue is addressed in the and 7.2.40 LoadMaster releases.