Kemp 360 Central V2.10 Release Notes

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

The V2.10 patch may be applied to any V2.0 or later version of Kemp 360 Central.

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.

New Features

Certificate Usage Reporting

When viewing the detail of a certificate, you can now view the LoadMaster devices where the selected certificate has been deployed using configuration management.

System Health Check

A health check of system components and service reachability is now performed daily and any issues identified are notified by email. This email is only sent if an issue is detected and requires configuration of SMTP services.

Create a new LoadMaster when deploying an application

When deploying an Application Profile, you can now create a new LoadMaster instance rather than deploying to an existing LoadMaster. The newly defined Loadmaster can be deployed automatically to VMware and KVM environments or manually to any supported platform or cloud.

ESP deployment support via Automation

Identity and access management settings (ESP) on LoadMaster can now be configured via automation tools such as Ansible using the Kemp 360 Central API.

Enhancements

Configuration Management Performance

The configuration management deployment process has been optimized to deliver up to a 50% reduction in the time taken to deploy an Application Profile.

General Usability

  • When renaming an Application Profile, Server Pool or Rule, the description may also be changed during the rename process.
  • Rules can now be cloned to create new rules based on existing rules.
  • Redeployment of an Application Profile now pre-fills deployment parameters with values from the last successful deployment of the profile to that LoadMaster.
  • Improved usability and visual indicators in Application Profile deployment workflow

Resolved Issues

KTS-8581

Fix incorrect message on metered licensing report

KTS-8593

Fix local license connectivity check interval

KTS-8650

Add logging of status email delivery failures

KTS-8653

Fix display of HA LoadMaster instances in licensing report

 

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.

 

KTS-3857

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.

KTS-3837

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.

KTS-3812

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.

KTS-3721

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.

KTS-3304

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

PD-11560

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.

PD-10051

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.

PD-9947

Virtual Service Status: Issues with Virtual Service status returns from LoadMasters running version 7.1.35.4 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.

PD-9747

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 7.1.35.4 and 7.2.40.

PD-9373

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

PD-9383
PD-9569

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 7.1.35.4 and 7.2.40.

Was this article helpful?

0 out of 0 found this helpful

Comments