Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Kemp 360 Central V2.3.1 Release Notes

Version 2.3.1 of Kemp 360 Central was released in August 2019 and is a bug-fix release. 

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


Patch upgrade and initial installation to this version will take over 10 minutes due to internal system libraries that have been upgraded. 

Resolved Issues

The following issue observed in the previous release that is resolved in this release.


Installation: The Console Administration Interface is now available to manually configure the network settings of Kemp 360 Central if your network does not have a DHCP server configured.


Known Issues introduced in previous versions

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




Kemp Id: Passwords with special characters are not supported and will return an error when licensing or using the Change of Ownership feature.


Change of Ownership: It is not possible to change the ownership of Kemp 360 Central from the UI without a valid Order or Contract Id. Please contact Kemp Support to complete this process if you do not have an Order or Contract Id.


Security Scanner results: Some security scanners report SSH weak cipher vulnerabilities with SSH Server CBC Mode Ciphers and SSH Weak MAC Algorithms Enabled. These issues are not considered critical or exploitable and will be fixed in next release.


Browser Compatibility: Due to changes made on LMOS version 7.2.47 for the Auto adding of Metered Licensed LoadMasters to Kemp 360 Central, Kemp 360 Central running on IE and Edge browsers does not function correctly with this version of LMOS. Chrome and Firefox function correctly.


Statistics: In some cases, LoadMaster interface statistics report over 120%.


LoadMaster Deployments: An available LoadMaster license will be consumed once a LoadMaster profile is created. In certain cases, especially with a limited number of available LoadMaster licenses, for example a Metered Licensing Trial of Kemp 360 Central, all available licenses can be consumed by LoadMaster Profiles, even if they are not deployed. 


Metered Licensing Trial: If an attempt is made to re-license a non-expired metered licensed trial without an order or contract Id an incorrect message is displayed stating that the License attempt was successful, however no changes are made to the current license.


Backup and Diagnostic Access: If a backup archive is created while SSH diagnostic access is enabled, and that archive is restored, SSH access will appear to be enabled in the UI on the restored system; however, it is not actually enabled and an attempt to log in to the diagnostic shell via SSH will fail. To work around this issue, click the Revoke Access button to clear the SSH access form and enable access again.


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

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.


Known Issues introduced in prior version 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 LoadMaster Operating System (LMOS) version 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 has been addressed in 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 issue has been addressed in LMOS version 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 has been addressed in LMOS versions and 7.2.40.


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 has been addressed in LMOS version 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 has been addressed in LMOS versions and 7.2.40.