Version 2.0 of Kemp 360 Central was released in February 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.
LoadMaster Deployments (SPLA/MELA Customers Only)
The LoadMaster Deployment feature allows you to specify settings for LoadMaster instances, and deploy LoadMasters matching those specifications in supported hypervisors, using either Automated Deployment (where the deployment is managed by Kemp 360 Central) or Manual Deployment (where you can download images from Kemp 360 Central and install them yourself).
With LoadMaster Deployments you can define LoadMaster Profiles that include all the specifications (including MELA licenses) needed to deploy a pre-configured virtual LoadMaster (VLM) image, that in turn contains completely specified and ready-to-go Virtual Service configurations.
This feature is currently targeted at Metered Licensing Agreement (MELA) and Service Provider Licensing Agreement (SPLA) customers, and so is only supported in SPLA builds of Kemp 360 Central.
Hypervisor Support for LoadMaster Deployments is limited in this first release, as follows:
- LoadMaster Deployments are supported only when Kemp 360 Central is installed in a VMware 6.0 or KVM hypervisor environment (and is therefore not supported when Kemp 360 Central is installed on AWS, Azure, Hyper-V, VirtualBox, Xen, and versions of VMware prior to v6.0).
- Note that the nested virtualization feature in the VMware or KVM hypervisor on which Kemp 360 Central is running must be enabled in order to create LoadMaster Deployments.
- When Kemp 360 Central is installed in a VMware (v6.0 or later) or KVM hypervisor environment:
- You can use automated deployment to automatically install pre-configured VLM images to VMware vCenter v6.5 (and above) configurations only.
- You can also download pre-configured, installable VLM images for manual installation on the following hypervisor platforms: Hyper-V (Gen 1 VLM images only), KVM, VirtualBox, VMware vCenter v6.0 (and above), VMware ESXi 6.0 (and above), and Xen.
- You cannot currently use LoadMaster Deployments to instantiate VLMs on either AWS or Azure.
Hypervisor support for LoadMaster Deployments will be expanded in future releases.
Improved Licensing Error Returns
The Kemp licensing server has been modified to provide specific error messages for HTTP 400 responses in the license payload sent to Central. Central currently ignores these messages and uses hard-coded messages in their place. In this release, Central has been modified to instead process the proper messages returned by the licensing server and display them to the user.
Outbound Proxy Settings
The outbound proxy functionality has been restored to the UI under Settings and Configuration > Proxy Settings. It was removed in a previous release because of several issues that have now been addressed; see the Resolved Issues list, below, for more information.
Accepting EULA on Upgrade
When upgrading to Version 2.0, you are presented an update End User License Agreement (EULA) that covers all Kemp products that you must accept before the upgrade can proceed.
The following are the major issues fixed in Version 2.0.
|In previous releases, only scheduled backups that succeeded were recorded in the system log; now, backup failures are recorded as well.|
|KTS-5795||In previous releases, no HA partner failures for Kemp 360 Central HA were not recorded in the system log. This issue has been fixed.|
|KTS-5611||On the installation Licensing form, the page is cleared after 1 minute of inactivity. This issue has been fixed.|
|KTS-5559||Fixed an issue that caused an error then setting the Statistics Retention Threshold to unlimited.|
|KTS-5457||In Version 1.27, a change was made that resulted in devices being displayed in oldest-to-youngest order (LIFO) in the network tree, rather than the youngest-to-oldest order (FIFO) used in previous releases. The V1.26 ordering (FIFO) has been restored in this release; devices are displayed in the order in which they were added to the network.|
|KTS-5410||In Version 1.27, a change was made that resulted in the persistence controls for Virtual Services no longer working. This issue has been fixed.|
|KTS-5409||Fixed an issue observed in Version 1.27 where a SubVS is shown in the 'down' state even when its associated Real Servers are 'up'.|
Fixed an issue observed in Version 1.27 where a SubVS is shown in the 'up' state even when its associated device is marked 'down'.
|KTS-5403||Fixed an issue observed in Version 1.27, where setting options on one SubVS causes the options to be set on other SubVSs as well.|
|KTS-5402||Fixed errors that occur when accessing the Restrict WUI Access page in the UI from multiple browsers simultaneously.|
|KTS-5401||Fixed the log viewer to filter Virtual Service IP addresses by selected Device IP addresses.|
|KTS-5178||Fixed heartbeat times on the HA configuration page so that they are displayed in the browser's time zone, instead of UTC.|
|Fixed an issue where invalid files uploaded to Central are not removed from the system.|
|Fixed an issue with incorrect timestamps on "last message repeated" messages in the system log.|
|The outbound proxy functionality had been fixed and restored to the UI under Settings and Configuration > Proxy Settings.|
|KTS-5012||Fixed an issue seen in the UI Offline Licensing page where providing invalid credentials results in an error requesting the user try again later; the proper error is now reported instead.|
|Email notifications associated with restricting UI access now provide information identifying the Kemp 360 Central unit that is the source of the notification.|
|KTS-4843||Fixed issues associated with lowercase and uppercase characters in login names. Login names are case-sensitive.|
|KTS-4734||Fixed issues associated with incorrect or non-informative error messages being displayed during Kemp 360 Central interactions with the licensing server.|
|KTS-4688||The offline licensing page is not auto-populating the web page with values from Kemp 360 Central. This issue has been fixed.|
|KTS-4542||Fixed issues with moving unmanaged devices to the network tree not being polled until up to one hour after initial contact. Now, the device will be polled immediately for configuration when credentials are added.|
|KTS-4538||When synchronizing a LoadMaster configuration from Kemp 360 Central, an unneeded comma may be prepended to an IP address in the LoadMaster Log Settings. This issue has been fixed.|
|KTS-4402||On some browsers, the scrollbar on the System Configuration screen may not appear at the lowest supported resolution for the Central User Interface (UI) (1366x768). This issue has been fixed.|
|KTS-4341||When viewing third-party F5 device logs in the log viewer, the real servers on the F5 device are not displayed in the search text box. This issue has been fixed.|
|KTS-4299||In the log viewer, AWS-ELB devices are not displayed in the device selection drop-down, so AWS-ELB logs cannot be viewed. This issue has been fixed.|
|KTS-3876||When the Proxy Settings for outgoing connections (Settings and Configuration > System Settings > Proxy Settings) are set or unset, internal errors can occur that may result in the new proxy settings not being used for all connections, or the old proxy settings continuing to be used. This issue has been fixed.|
|KTS-3875||LoadMaster HA Pairs: When adding a device, if any LoadMaster HA pairs are expanded in the left frame, they close while the Add a Device screen is open and expand again once you click Apply. This issue has been fixed.|
|KTS-3653||Fixed an issue on the console where the current hostname was not being shown in the display when modifying system settings.|
|KTS-3390||When Amazon Web Services (AWS) Elastic Load Balancing (ELB) devices are present in the configuration, it is possible for status information for all devices to be delayed. Status information is processed and visible in the UI on a two-minute cycle, instead of every minute. This issue has been fixed.|
|KTS-3305||Fixed issues in the task scheduler that could cause a failure when trying to create new scheduled actions with the same time and repetition values, but different execution dates, than existing scheduled actions.|
|KTS-2720||The HTTP Method field displays a blank value for HTTP/S health checks. This issue has been fixed.|
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 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.
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.
|KTS-5743||Reporting: Special characters used in network and device names are not displayed properly in the device selection list on the Reporting page.|
|KTS-5626||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.|
|KTS-4567||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.|
|KTS-4252||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 of the HA units in the pair was modified on the LoadMaster without making the same modifications on Kemp 360 Central.|
|KTS-3814||LoadMaster HA Pairs: If the two HA devices in a LoadMaster HA pair take significantly different times to poll (for example, HA1 takes one second, HA2 takes 10 seconds), the UI may report inconsistent data for up to one minute, until the next device status poll occurs.|
|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.|
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:
|KTS-3438||In the log viewer, it is possible for the user to miss-configure a Time Range (for example, set a From date later than a To date), and then select another range (for example, Last Week). If the user then tries to export the log display, the export fails because the invalid From and To dates are still checked, even though they do not apply to the Last Week selection.|
|KTS-3427||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.|
|KTS-3304||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.|
|KTS-2707||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.|
|KTS-2145||When using the VS Motion Migrate function, the virtual 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.|
|KTS-2101||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.
|PD-10051||Local License Activations: 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.|
|PD-9947||Issues with Virtual Service status returns from LoadMasters running version 22.214.171.124 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).|
|PD-9747||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 126.96.36.199 and 7.2.40 LoadMaster releases.|
|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 188.8.131.52 and 7.2.40 LoadMaster releases.|