Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

  1. Kemp Support
  2. Documentation
  3. Kemp 360 Central
  4. Release Notes

KEMP 360 Central V1.27 Release Notes

Updated: 

Version 1.27 of KEMP 360 Central was released in September 2018 and is a feature and bug-fix release. It contains the new features, resolved issues, and known issues described in the following subsections.

For details on installing and upgrading KEMP 360 Central, refer to https://support.kemptechnologies.com/hc/en-us/articles/360019736312

New Features

Restricting UI Access to Specific IP Addresses

A new ‘whitelisting’ capability has been added that allows the administrator to specify the source IP addresses and subnets from which UI access will be allowed:

  • By default, the system allows access from any IP address that has a route to KEMP 360 Central – as in previous releases.
  • Using controls found under Settings and Configuration > UI Access Control, you can limit UI access to specific IP addresses, or use CIDR notation to limit access to a range of IP addresses.
  • As a lockout protection mechanism, the IP address from which the UI is being accessed to modify the whitelist is always added to the whitelist, even if it is not specified by the user.
  • The whitelist applies to UI access only. API access to KEMP 360 Central remains open to any network that has a route to KEMP 360 Central, as in previous releases. This is required to support API access from all managed devices.

LoadMaster Certificate Backup

The Backup and Restore capability now supports creating a backup archive of the SSL certificates installed on a LoadMaster, and restoring those certificates to a LoadMaster:

  • When creating a backup archive, the user is now prompted to back up the system configuration only, the SSL certificates only, or both.
  • When selecting a backup archive to restore to a LoadMaster, the list now indicates whether an archive contains the system configuration only, certificates only, or both.
  • When choosing an archive that has both configuration and certificates, you can choose to restore either configuration or certificates, or both.
  • Any backup archive can be downloaded to your local system from KEMP 360 Central in a ZIP file, which will contain a configuration archive, a certificate archive, or both. These can be extracted from the ZIP file and applied to a LoadMaster outside of KEMP 360 Central, using either the LoadMaster WUI or the LMOS API.
    • Note that the ability to upload backup archives from your local system to KEMP 360 Central remains as in previous releases: that is, you can upload a configuration-only archive and it will be recognized by the system. Certificate archives and combined configuration and certificate archives, however, will be accepted by the UI/API and uploaded to the system, but it will produce an error when applied to a LoadMaster.

UI Performance Improvements

The UI has been enhanced to provide better overall performance under a variety of workloads, and to reduce response times for all data queries.

Statistics Gathering Performance Improvements

The process used to poll managed devices for statistics gathering has been enhanced to provide better overall performance and more efficient management of polling activities, especially in larger configurations.

System Capacity Enhancements

With Version 1.27, system capacity has been increased as follows:

  • The maximum number of managed devices has been increased to 600 devices.
  • The maximum number of managed resources (Virtual Services, SubVSs, Real Servers) has been increased to 18000.

Issues Resolved

The following are the major issues observed in previous releases that are resolved in this release.

ID

Description

KTS-5168

Fixed an issue that could cause a blank UI page to be displayed after the system is upgraded and rebooted.

KTS-5127

Addressed an issue on installation and licensing where the licensing page gets reset and form data is lost when the License Now button is clicked.

KTS-4517

Modified dashboard behavior so that SubVSs are not counted in either the administratively disabled service widget or virtual service status widget – only Virtual Services (VSs) are counted.

KTS-4273

Fixed an issue where a rebooting device is still shown as ‘up’ in the left frame after a reboot is requested; the icon now changes immediately to show the system is rebooting.

KTS-3695

Enhanced the network tree search facility to search on full or partial network and device nicknames (in addition to the current IP address search).

KTS-3587

Fixed an issue where disabling a Real Server on LoadMaster does not get correctly reflected on KEMP 360 Central.

KTS-3537

Modified dashboard behavior so that real servers under an administratively disabled VS are also shown as disabled.

KTS-2720

Fixed an issue where the HTTP Method field displays a blank value for HTTP/S health checks even when there is actual data to display.

KTS-2837

Fixed issues in the dashboard where a disabled VS is shown as ‘down’.

 

Known Issues

The following list includes the most serious known issues in the product. If you experience an issue that is not on this list, contact KEMP Support for further information.

ID

Description

KTS-6939

MELA Reporting: An issue exists that causes the Kemp 360 Central system to report usage figures as packets instead of bytes. This leads to the MELA report being calculated incorrectly.

KTS-5059

KTS-3876

The outbound proxy functionality (Settings and Configuration > Proxy Settings) is broken and does not work. It has been removed and will be provided again in a future release.

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

When a LoadMaster has been licensed by Central, the user must edit the device definition and add the device’s credentials. Once the credentials are added, however, the device configuration is not automatically polled – the user has to wait until the next configuration poll occurs to see any config data for the device. That could be up to one hour later. Instead, the device should be polled immediately for configuration when credentials are added.

KTS-4541

It is possible, after a series of deletions and additions, for statistics for a deleted LoadMaster to be attributed to a LoadMaster created after the deletion occurred. This is due to ID reuse on the LoadMaster. While this has no impact on aggregate statistics reporting, it does mean that statistics attributed to a new device may have timestamps showing a date and/or time before that device was added to KEMP 360 Central.

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). The workaround is to use a higher resolution, or close the collapsible menus so the scrollbar is not needed.

KTS-4341

In the log viewer, AWS-ELB devices are not displayed in the device selection drop-down, so AWS-ELB logs cannot be viewed.

KTS-4299

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.

KTS-3876

When KEMP 360 Central's 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. The workaround is to reboot the system after modifying the Proxy Settings.

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 is a cosmetic issue only.

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

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

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

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

The HTTP Method field displays a blank value for HTTP/S health checks.

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.

ID

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

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

PD-9383

PD-9398

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

 

Appendix: Quick Start for Monitoring LoadMaster HA

In Version 1.19, a new device type (LoadMaster HA Pair) has been added to help you more effectively monitor the high availability (HA) services hosted on LoadMasters configured into HA pairs. This section will tell you what you need to know to get started using it.

If you are upgrading to V1.19 (or a later release) from a release prior to V1.19, see the section See the KEMP 360 Central Feature Description on our website for additional feature documentation.

for advice on how to modify your current configuration to use LoadMaster HA Pair devices.

Prerequisites

Before you create a LoadMaster HA Pair device ensure that:

  1. The two LoadMaster HA mode units participating in the HA pair have already been added to Central as LoadMaster type devices.
  2. The two LoadMasters are available (up) and communicating successfully with Central – their icons must be green or blue in the network tree.
  3. You have available the IP addresses and ports of the two HA mode LoadMasters, as well as the shared IP address and port used by the HA configuration.

Creating a LoadMaster HA Pair

After you ensure the prerequisites in the previous section are complete, do the following to configure two HA mode LoadMasters into a LoadMaster HA Pair:

  1. Click on the Network and Device Administration icon at left.
  2. Click on the + icon at lower left to open the Add a Device screen.
  3. Enter or select the parameters shown in the table below:
    Parameter

    Description

    Device Type

    Select LoadMaster HA Pair.

    HA Shared IP : Port

    Enter the IP address and port of the HA shared IP address used by the HA LoadMasters.

    Nickname

    (Optional) A name for the device that will appear in the network tree at left and elsewhere in the UI.

    Username
    Password

    The username and password for the HA configuration. This username and password combination must be defined on both LoadMasters.

    HA1 IP : Port

    Select the LoadMaster configured as HA1 in the LoadMaster WUI’s HA Configuration page.

    HA2 IP : Port

    Select the LoadMaster configured as HA2 in the LoadMaster WUI’s HA Configuration page.
  4. Click Apply.

The Shared IP Address (or Nickname, if you supplied one) will now appear in the appropriate place in the network tree at left, with the two HA mode LoadMasters organized underneath, as shown in the example below.

Untitled.png

Please note the following:

      • Most monitoring and service configuration is available by clicking on the Shared IP Address (or Nickname) device in the left frame. In the screen shot above, the shared IP device is 10.35.26.205.
      • The Monitoring page for the shared IP device shows consolidated status across the HA pair.
      • System configuration options specific to each of the LoadMasters are available by clicking on the icons underneath the shared device.
      • See the section for a list of LoadMaster HA Pair issues and workarounds.

See the KEMP 360 Central Feature Description on our website for additional feature documentation.

Possible Adjustments After Upgrade from a Version Before 1.19

If you are upgrading from a release previous to V1.19 to V1.19 or a later release, you may need to adjust your current device list to take advantage of the new LoadMaster HA Pair device type introduced in V1.19. Specifically:

      1. If you have added a device using the HA Shared IP for a pair of LoadMasters configured into an HA pair, then you must remove that device from Central before you can configure the LoadMaster HA Pair device. If you do not, then you’ll get an error that the shared IP address already exists when trying to add the LoadMaster HA Pair device. The workaround is to remove the device using the HA Shared IP and try again.
      2. If you have not already created two Central devices for the individual HA LoadMasters in the pair, then you must add them to Central before you can configure the LoadMaster HA Pair device.

Comments

In this document