Kemp 360 Central V2.13 Release Notes
Version 2.13 of Kemp 360 Central was released in February 2022 and is an enhancement release. It contains the new enhancements, and known issues described in the following subsections.
It is not possible to upgrade to version 2.13 directly, you must first upgrade to 2.12 then take a backup.
2.13 can only be freshly deployed given the significant system upgrades. 2.13 will only accept backups from 2.12.
The backup does not restore metrics, please ensure you understand the requirements and limitations before proceeding.
Any MELA or Pooled customers, please work with our support team to migrate the licensing and specific steps.
For installation prerequisites, upgrade path information, virtual machine requirements, and other details, please see the article Installing and Upgrading Kemp 360 Central.
Please note that the browser cache for Kemp 360 Central should be cleared as some components from earlier versions may impact operation of this latest version.
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.
No new features added.
Major Security Footprint Upgrade
We have updated our base operating system to the current Ubuntu LTS to address many security risks we have identified. Along with the base OS upgrade we have upgraded a number of internal libraries. In addition to the updating, we have removed many internal libraries that were no longer in use.
WAF Event and Statistics now properly show data when utilizing WAF functionality on Virtual Services.
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.
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
Known Issues Introduced In Prior Versions 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.
Metered Licensing 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.
Metered 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 188.8.131.52 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 184.108.40.206 and 7.2.40.
Metered LoadMaster HA Units Lose Connectivity: This issue occurs in 7.2.38 and causes Metered 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
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 220.127.116.11 and 7.2.40.