Kemp 360 Central V2.4 Release Notes
Version 2.4 of Kemp 360 Central was released in October 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
Migrate SPLA (Service Provider Licenses) to Metered Licenses
Customers with Service Provider License Agreement (SPLA) LoadMasters can now re-license LoadMaster instances to use Metered Licenses from Kemp 360 Central. Re-licensing preserves the configuration of the LoadMaster but will require a reboot. LoadMaster 7.2.48 or later is required.
Ansible Automation of Virtual Service Configuration
This release of Kemp 360 Central provides support for configuration of LoadMaster Virtual Services using Ansible. Rather than using the LoadMaster API, you may now declare your complete Virtual Service configuration in an Ansible playbook and apply the configuration via Kemp 360 Central. To get started with automation using Ansible, consult the Ansible Reference Guide.
The Kemp Ansible modules and example playbooks will be made available within the next week to enable this capability.
Feature Enhancements
Subscription Widget Updated
The widget has been enhanced to indicate the 30 and 90 day count of pending expirations of LoadMaster Support Subscriptions.
Changes to password change process
When changing their password, users must now provide their old password as part of the process. This is part of an ongoing effort to increase system wide security best practices.
Improved Logfile management
Administrators may now delete device logs by date to provide better control of disk space usage.
Configurable DNS Settings
Administrators may now specify the DNS settings for Kemp 360 Central in the web interface.
Improved support for VMware vCenter folders in Auto-deployment
When deploying to a vCenter target environment, administrators can now navigate the vCenter folder tree to select the appropriate folder for the deployment.
Improved Labeling in Metered Licensing Reports
The Metered Licensing usage download zipfile now includes device nicknames in addition to device IP details in the usage and HA details CSV files.
SSH Services can now be disabled
In prior releases, SSH services were always enabled with access being granted by the administrator as required. It is now possible to completely disable SSH services on Kemp 360 Central.
Resolved Issues
The following major issues were resolved in version 2.4
|
KTS-6479 |
Fix incorrect error message on key import for Admin UI |
|
KTS-6610 |
Fix consumption of licenses by LoadMaster profiles that are not yet deployed |
|
KTS-6675 |
Fix error message when trying to relicense a trial as a trial |
|
KTS-6723 |
Network tree not expanding when in monitoring page |
|
KTS-6773 |
Fixed issue with newly updated UI certificate not being applied |
|
KTS-6790 |
Order number not mandatory for change of ownership |
|
KTS-6811 |
Certificate import tooltip now indicates support for .pfx files |
|
KTS-6820 |
Fix log error text when reporting metered licensing reporting failures |
|
KTS-6824 |
Added cancel button to the license selection dialog |
|
KTS-6891 |
Prevent setting of invalid DNS address via API |
|
KTS-6892 |
Prevent non-admin user from configuring DNS |
|
KTS-6896 |
UI changes in DNS not reflected in console interface |
|
KTS-6899 |
Fixed ping utility in console interface |
|
KTS-6923 |
Fix issue with 'Next Step' and 'Cancel' button display during manual deployment of LM |
|
KTS-6933 |
Fix issue were zero interface traffic was resulting in ‘NaN Messages’ being displayed in messages widget and empty monitoring graphs |
Known Issues introduced in this version
|
KTS-7059 |
Manual refresh (via update button) of standby member of HA pair on shared-IP failing. To refresh, you should select the primary HA member |
|
KTS-6997 |
Re-sync of Kemp 360 Central HA may have performance impact where a large number of syslog entries have to be synced. |
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-6374 |
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. |
|
KTS-4252 |
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. |
|
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 |
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. |