KEMP 360 Release Notes


1Installing and Upgrading KEMP 360 Central

First-time installation of KEMP 360 Central is supported on a number of platforms. In addition to reading these Release Notes, please also read and follow the Installation Guide for your platform, available from the KEMP Documentation Library. Expand the KEMP 360 link at the top left of the library contents and then click on the installation guide for your platform.

Upgrading directly to the latest version of KEMP 360 Central is supported from Version 1.9 or a later release only. For details on the upgrade path to the current release, please see the section Upgrade Path to the Latest Release on page 2.

If you are running a release of KEMP 360 Central earlier than Version 1.9, please contact KEMP support to upgrade to Version 1.9 before attempting to upgrade to the latest release:

To update KEMP 360 Central to the latest firmware version, click the Settings and Configuration icon (the gear icon) at the bottom-left corner of the UI and then click Firmware Management.

1.1Before You Begin

The following are requirements and recommendations for installing and using KEMP 360 Central:

  • Before attempting to add a LoadMaster to KEMP 360 Central, ensure that the LoadMaster is running Version 7.1.34 of the LMOS software, or a later release.
  • Any device that you want to add to KEMP 360 Central must be located on a network that can be reached from the KEMP 360 Central instance.
  • The person performing a fresh install or upgrade of KEMP 360 Central should be familiar with network administration best practices within their organization and possess an intermediate level of general network and system administration knowledge.
  • For the best user experience, KEMP recommends using Google Chrome to access the KEMP 360 Central UI. Other browsers -- Firefox, Safari, Edge, and Internet Explorer -- are also supported.
  • If any of the LoadMasters you are adding to KEMP 360 are configured into a High Availability (HA) configuration, please see the additional configuration notes in the section Monitoring LoadMaster HA from KEMP 360 on page 2.
  • Please read the following section below before installing or upgrading:

This document applies to KEMP 360 Central. For documentation on configuring LoadMaster, LMOS release notes, information on LMOS backup archive content, or other LoadMaster-specific issues, please refer to the LoadMaster documentation from the KEMP Documentation Library.

1.2Monitoring LoadMaster HA from KEMP 360

When adding LoadMaster devices that are configured into a High Availability (HA) configuration to KEMP 360, please observe the guidelines below that apply to your configuration:

  • Most customers will deploy an image of KEMP 360 Central that is not enabled for Service Provider Licensing Agreements (SPLA), Metered Licensing Agreements (MELA), or the Activation Server Local (ASL) feature. If you are a deploying such an image, do the following for each HA pair you want to monitor with KEMP 360 Central:
  1. Add one device for the HA pair using the HA Shared IP Address. This will allow you to monitor and manage Virtual Services and other load balancing resources as well as the common configuration settings between the two HA LoadMasters.
  2. Do not add additional devices to KEMP 360 using the local IP addresses of the two LoadMasters in the HA pair. This causes duplicate logs to be synchronized to KEMP 360 and will have a negative impact on KEMP 360 performance, while providing no additional visibility into the configuration nor any additional settings that are not presented and kept in sync by the two LoadMasters via the HA Shared IP address.
  3. To ensure that you are getting email alerts for both HA units (regardless of which is the current master), configure email alerts on both LoadMasters.
  4. To edit settings that are local to each LoadMaster (e.g., interface settings, licensing), log into the LoadMaster units using the IP address of each LoadMaster in the HA pair.
  • Otherwise, if you have deployed a SPLA-enabled image of KEMP 360 Central and are also deploying LoadMasters under MELA using ASL, do the following for each HA pair you want to monitor with KEMP 360 Central:
  1. Add two devices using the IP addresses of the individual LoadMasters in the HA pair. This is required so that each LoadMaster can report activity to KEMP 360 Central.
  2. Do not add a device using the HA Shared IP Address for the HA pair. This causes duplicate logs and statistics to be synchronized to KEMP 360 Central, which will report duplicate information on system activity. This may impact system performance.
  3. To edit settings that are common to the HA pair (e.g., Virtual Services, Real Servers), log into the LoadMaster WUI using the HA Shared IP address for the HA pair.

In future releases, a more seamless interface between KEMP 360 and HA LoadMasters will be provided.

1.3Getting Help

If you experience issues when installing or upgrading to this release of KEMP 360 Central that can’t be resolved by consulting this document or the installation guides available from the Documentation Library, please visit the Support Web Portal to look for help from our user community, access KEMP’s Knowledge Base, or submit a support request.

To submit a support request via the Support Portal, please have your KEMP ID and password handy. After you file a request, a KEMP Support Engineer will get in touch with you promptly.

2Version 1.15

Version 1.15 of KEMP 360 Central was released in May 2017 and contains the new features, resolved issues, and known issues described in the following subsections.

2.1New Features

Device Assessment Reports

The new Settings and Configuration > Reporting page allows you to print ad-hoc and scheduled reports for selected devices. The reports contain a graphic and tabular summary of the devices’ performance over the time period selected for the report.

The report is created as a PDF file and can either be downloaded directly or sent by email to a specified list of recipients.

Previously scheduled reports are tracked in the UI and can be modified.

Unmanaged Devices Node

In previous releases, devices added to KEMP 360 Central that could not be successfully contacted were added to the bottom of the network tree, outside of any network. A new node to contain these devices, name Unmanaged Devices, now appears at the top of the network tree. If there are no unmanaged devices, the node does not appear.

Once KEMP 360 Central successfully logs into an unmanaged device, it is moved out of the Unmanaged Devices node and placed in the appropriate network based on its IP address.

Device Icon Legend

A legend describing all the icons used in the network tree has been added to the bottom of the left frame, to the right of the controls uses to add, delete, and edit networks and devices.

2.2Issues Resolved




Made a number of minor updates throughout the UI to improve usability and consistency.


Fixed issues that prevented adding a LoadMaster with a password containing special characters (e.g. "#"). Also see the section Known Issues.


Fixed issues in the MELA management UI where a report date in the future could be selected, resulting in an error when a report is created.


Fixed issues observed displaying the Dashboard with a reduced screen width.


The Tiered Subscription UI has been enhanced to allow the user to sort the table of licenses by either IP Address (default) or Expiration Date. Only data for active LoadMasters is displayed; if the LoadMaster is down or has never been contacted, no licensing information is displayed for that unit.


Upgrading the KEMP 360 Central firmware can no longer be performed by downloading an online image using the UI. The online upgrade option has been removed from the Firmware Management page. Instead, download the image from the KEMP Support Site to your local system and use the Firmware Management controls to upload the image to KEMP 360 Central for installation. The table will be updated automatically as device availability changes over time.


Fixed a timeout issue where a newly added LoadMaster can be erroneously marked as unreachable when it is first added, even though the device is available and responsive.


Fixed issues where a failure to retrieve licensing information from a LoadMaster would result in that LoadMaster being treated as down by KEMP 360 Central.


Fixed an issue that resulted in basic authentication credentials being included in debug log messages.

2.3Known Issues

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 more information on that issue.




Most special characters supported in LoadMaster passwords are supported in V1.15 and later releases. However, because of an issue in the LoadMaster API, quotes and spaces in LoadMaster passwords can cause authentication from KEMP 360 Central to fail -- while they work without issue when logging directly into the LoadMaster WUI. Until this issue is addressed in the LoadMaster API, you should log in to 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.


When selecting a backup file for restore on a managed device, the UI only displays the last 20 archives created.


In some cases, adding a LoadMaster to KEMP360 Central and activating/licensing it using the ASL Server functionality may result in a certificate authentication failure. If this occurs, please contact KEMP support for further assistance.


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


Configuring a Layer 7 specific parameter on a Layer 4 VS should both enable Layer 7 services on the VS and set the new parameter value. Instead, only Layer 7 is enabled; the Layer 7 specific parameter is not set to the value specified.


Any user with write access is able to change credentials for the admin account.


Cannot set VS persistence to ‘none’; setting remains unchanged on LoadMaster.


Cannot unset a Health Check port on a VS or SubVS.


When using VS motion, the virtual IP address and port to use for the new VS is not automatically updated when you select a LoadMaster from the ‘Target’ drop-down box. You must update the address manually to an available IP address on a network accessible to the target LoadMaster.


Setting the ‘Alternate IP Address’ does not work on UDP services.


Setting a health check URL with query parameters may not be synchronized properly on LoadMaster.


Cannot communicate with a LoadMaster when the ‘Admin Login Method’ is changed to ‘Password or Client Certificate’.


Adding a UDP protocol VS on pre-7.1.35 LoadMaster can result in spurious errors; the VS is created on the target LoadMaster.

3Version 1.14

Version 1.14 of KEMP 360 Central was released in March 2017 and contains the new features, resolved issues, and known issues described in the following subsections.

3.1LMOS Version Support

With Version 1.14, KEMP360 Central is officially supports managing LoadMasters running LMOS Version 7.1.34, or a later release. Earlier releases can still be managed with KEMP360 Central, but for full support you should upgrade to at least Version 7.1.34. Note that older LMOS releases will experience the following operational limitations:

  • LMOS releases prior to 7.1.34 do not report network interface information & statistics. Because of these and other limitations present in LMOS, KEMP360 Central will perform optimally in a configuration of 50 devices or fewer running releases prior to 7.1.34.
  • In addition, LMOS releases prior to 7.1.30b report fewer overall statistics.

3.2System Sizing Limitations

In general, KEMP360 Central version 1.14 will work optimally with a configuration of up to 75 managed devices (whether they are LoadMaster or third-party ADCs, or a mix). The maximum number of managed devices that can be monitored with good UI performance also depends on the number of underlying resources (Virtual Services, SubVSs, and Real Servers) being monitored on each ADC, which is limited in this release to up to 1425 resources total across all managed devices. If concurrent users log in to KEMP360 Central, system performance will be affected and users will see increased rendering times in the UI. System scalability will be improved in subsequent releases.

The above limitations assume that all LoadMasters are running version 7.1.34 of the LMOS software, or a later version. See the section LMOS Version Support, above.

3.3New Features

KEMP 360 Central High Availability

Version 1.14 contains a beta release of High Availability (HA) for KEMP 360 Central. With this release, the following functionality is provided:

  • Two instances of KEMP 360 Central can be configured into an HA pair, using the controls located under Settings and Configuration > HA Configuration in the user interface.
  • With respect to failover, the two KEMP360 Central HA instances participate in a Master/Slave relationship:
    • One system is designated the Preferred Master unit, and this unit should be configured first. Whatever configuration exists on this unit when it is configured into HA mode will be propagated to the other unit (the Preferred Slave).
    • If the Preferred Master unit becomes unavailable, the Slave unit assumes the Master role.
    • Once the Preferred Master is available again, it will automatically re-assume the Master role (i.e., fail-back to the Master role, and the other unit will assume the Slave role again).
  • With respect to the data managed by KEMP360 central, the two units cooperate as follows:
    • Configuration changes made on either KEMP360 Central instance are reflected in the configuration and communicated to the other host.
    • Both of the KEMP360 HA instances collect system logs from managed devices. Therefore, each LoadMaster in the configuration will have both KEMP360 Central HA units as syslog targets.
    • Only the Master unit collects and generates statistics; the Master unit periodically forwards statistics to the Slave unit.

Please note that when configuring two KEMP360 Central instances into HA mode in this release, both units need to have at least one network defined for the initial synchronization to complete successfully.

Remember: Once the two units are initialized into HA mode, the configuration of the Preferred Master will be propagated to the Preferred Slave, and the Preferred Slave’s configuration will be overwritten. After initial synchronization has completed changes will be propagated in both directions.

LoadMaster Licensing & Tiered Subscriptions Summary

KEMP360 Central has been updated to provide a summary of LoadMaster traditional and tiered subscription licensing, so that KEMP360 Central administrators can quickly identify LoadMasters that are approaching or have passed a license-related expiration date.

A new Global Dashboard application, Non-Local Licenses and Subscriptions, reports the number of LoadMasters that have licenses or subscriptions that have expired or that are about to expire in 7, 30, or 60 days. These LoadMasters have been licensed using either legacy licenses or the latest tiered subscription based licenses. [Note: licenses activated via the KEMP360 Central Activation Server Local (ASL) feature are reported in a separate Local Licensing dashboard application.]

Clicking on Non-Local Licenses and Subscriptions opens a new Licensing table on the All Networks > System Configuration page. This table lists the IP Address, Name, License or Subscription, and Expiration date for all managed LoadMasters. If a license or subscription is expired, it is displayed in red text.

LoadMasters with legacy licenses will have one entry in the table. LoadMasters licensed with tiered subscription based licenses will have one entry for the license type (Standard, Enterprise, or Enterprise +) and additional entries for each subscription.

3.4Issues Resolved




Improved UI performance through a number of internal changes. See System Sizing Limitationson page 2 for sizing recommendations.


Improved usability of the default state of the backup and restore configuration page.


Fixed an issue in System Configuration where choosing Rebooting Selected reboots all devices instead.


Fixed issues that caused the Monitoring page network traffic graphs to display larger values than expected, either in the graph or in the tooltips for specific data points.


Improved usability of the UI by displaying a progress bar when a large amount of data is being loaded.


Fixed a configuration issue that occurred when setting the persistence method to none.


Fixed an issue in the UI Monitoring page where, in large configurations, messages reporting LoadMasters coming online repeatedly appear.


Fixed a UI issue where clicking the Reboot All button in the UI did not reboot any devices.


Fixed UI rendering issues when listing templates with long names.


Fixed an issue in the Add a Device page where the Network field is not properly pre-populated with the currently selected network.


Fixed a UI issue where clicking the Delete SubVS button does not delete the SubVS.


Modified the date format used in various graphs and tables found under Settings and Configuration > Metered Licensing Management to consistently use the Year-Month-Day format.


SSL TPS and Connections graphs under certain circumstances display a -1 value on the Y-axis, instead of or below the 0 value.

4Version 1.12

Version 1.12 of KEMP 360 Central was released in January 2017 and contains the new features, resolved issues, and known issues described in the following subsections.

4.1New Features

Log Viewer Enhancements

Click the Global Repository icon at the bottom-left corner of the UI to display the Logging page. From this page, you can search all the logs collected from all the devices that are managed by KEMP 360 and have been configured to send logs to KEMP 360. [LoadMaster, F5, NGINX, and HAProxy devices all support remote syslog; LoadMaster is configured automatically from KEMP 360 while the other devices must be configured manually.]

On the left, the time period for the log search can be set. Controls at right allow you to filter the logs for the selected time period by several new criteria:

  • Text: Type in a simple text string (this was the only criteria supported in the previous release).
  • Log Severity: Use the slider control to range of log message severities that you want to see in the search results.
  • Device IP: To filter for a single IP address, select from a list of IP addresses for all devices managed by KEMP 360. The IP addresses are organized by device type (LoadMaster, F5, NGINX, HAProxy) then by IP address. If you select a device type, then only entries from all devices of that type will be searched (e.g., all LoadMasters or all F5 devices).
  • Virtual Service IP: Select from a list of IP addresses for all virtual services managed by KEMP 360.
  • Real Server IP: Select from a list of IP addresses for all real servers managed by KEMP 360.

Global Dashboard

A new global dashboard is added that displays key information such as device, infrastructure and application health in separate panes with clear indicators. The data presented includes:

  • Device Health
  • Top 3 utilization
  • Local License Allocation
  • Log Summary
  • Virtual Service Status
  • Real Server Status
  • Administratively Disabled Services and Servers
  • WAF Statistics Summary
  • Active Connections Summary

First Time User Login Experience Improvements

When logging into a newly deployed KEMP 360, the system now prompts you automatically to add your first LoadMaster device. You can add one or more LoadMasters, optionally populating the KEMP 360 Central SMTP (email) parameters from the LoadMaster being added.

Add Device Workflow and Network Tree Organization

The workflow for adding any device (LoadMasters and 3rd-party devices) now locates your device by default in the network with the smallest address space that contains the IP address you specified for the device. If the device cannot be successfully contacted upon adding it to KEMP 360, the device is located at the bottom of the network tree, and will be moved to its appropriate location in the tree once the unit has been contacted and its configuration read by KEMP 360.

After the device is added, the default device location in the network hierarchy can be changed by the administrator by editing the device configuration. The device will remain in that location until the administrator specifically modifies it.

KEMP 360 Backup and Restore

Click the Settings and Configuration icon at the bottom-left corner of the UI and then click Backup & Restore to display the Backup and Restore control panes. The backup archive created contains a complete copy of the current running configuration, including all managed devices, services, networks, and KEMP 360 settings. The backup archive is encrypted and password-protected, and is saved locally to the system from which you launched the KEMP 360 Central user interface.

Similarly, the restore facility allows you to upload a previously created KEMP 360 backup archive from your local system and overwrite the current KEMP 360 configuration using the information in the archive.

The backup and restore facility is intended for disaster recovery – the device on which a backup archive is restored is expected to be equivalent to the device on which the archive was created with respect to network configuration and licensing. Other restrictions apply to restore operations when:

  • Restoring an archive created on a unit other than the one on which the archive was created.
  • Restoring an archive to a newly provisioned device while the device on which the archive was created is still active.
  • Restoring an archive that employs local licensing from a KEMP 360 ASL Activation Server.

For more information, see the backup and restore documentation in the KEMP 360 Central Feature Description.

4.2Issues Resolved




Fixed an issue where requesting status from a LoadMaster running a release prior to 7.1.32 causes KEMP 360 to stop requesting status from all devices.


Fixed an issue with graphs where a device becomes unavailable, but related graphs continue to display the last data values received from the device.


Fixed an issue displaying multiple subnetworks on network Monitoring pages.


Fixed a shell command injection issue in the UI.


Fixed an issue that caused the graph of locally licensed LoadMasters in the MELA report to omit valid activations.


Fixed an issue with VS Motion where KEMP 360 returns an error message even though copying the virtual service succeeded.


Fixed an issue where a LoadMaster is successfully added to KEMP 360 but its virtual services are not instantiated.


Fixed an issue with access control groups where adding a group member resets group resources.


Fixed an issue where editing permission group details failed under certain circumstances.


Fixed an issue where adding, editing, or deleting a service or real server appears to succeed, but actually fails and causes the target LoadMaster to become inaccessible from KEMP 360.


Fixed an issue where editing a Real Server port instead adds another Real Server to the system, and the existing server is disabled.


Fixed a problem with VS motion where the user is unable to edit the VS alternate address before copying the VS, possibly resulting in duplicate IP addresses on the target unit.


Several issues related to wildcard ports on Virtual Services were present in previous releases:

  • A wildcard port specified when adding or modifying a VS returned an error.
  • An existing VS on a LoadMaster added to KEMP 360 would not be instantiated on KEMP 360.

These issues have been fixed.


Fixed an API issue where deleting a network without specifying an ID deletes all networks within the system.


In previous releases, when editing an Access Control user group, the tree of resources (managed devices and services) displayed in the Edit Group pane shows the IP address of the resource. In this release, the display now shows the resource Nickname, if one exists; otherwise, it displays the resource IP address.


Usability: Modified the default scheduling period for rebooting a device from ‘Daily’ to ‘None’.


The UI-has been enhanced to include persistence in the settings for UDP protocol virtual services.

5Version 1.9

Refer to the sections below for details about the KEMP 360 Central version 1.9 features. Version 1.9 was released on 29th September 2016.

5.1New Features

  1. Local Authorization and User Access

This enables KEMP 360 Central users to be created with specific permissions to enable access to device management functions. Users can further be added to groups to aid control and access to the available device management functionality.

  1. Log Rendering

There is a new log display and filter functionality available in the KEMP 360 Central User Interface (UI).

  1. F5 BIG-IP Support

It is now possible to add/edit/remove F5 BIG-IP devices and visualize key traffic metrics and statistics from within the KEMP 360 Central UI.

5.2Feature Enhancement

  1. Virtual Service heat maps have been removed.

5.3Issues Resolved




Fixed a UI issue where some input fields were not displaying correctly in Firefox.


Fixed an issue that was preventing the menus from expanding on the Welcome on Board screen on some occasions.


Fixed an issue with hover text on Firefox.


Fixed an issue that was preventing a Virtual Service with a Real Server from being deleted after a second Virtual Service was added.


Fixed an issue relating to the LoadMaster password field.


Fixed an issue that was preventing a network from being deleted if LoadMasters and Virtual Services were present in that network.


Fixed a synchronization issue between KEMP 360 Central and LoadMasters relating to health checks.


Added a progress bar to the initial licensing screen.


Fixed an issue that was causing the spinner to appear indefinitely after clicking the Apply button when editing the SMTP settings.


Fixed an Application Program Interface (API) issue relating to editing reports.


Made improvements to the user change password field behavior.

6Version 1.8

Refer to the sections below for details about the KEMP 360 Central version 1.8 features.

6.1New Features

  1. Virtual Service Motion

Provides customers the ability to migrate Virtual Services between LoadMaster devices that are being managed within KEMP 360 Central.

  1. Real Server Health Checks

Enhancing the Virtual Service configuration to facilitate LoadMaster Real Server Health Check configuration.

  1. AWS ELB

It is now possible to add/edit/remove AWS Elastic Load Balancing (ELB) and visualize key traffic metrics and statistics from the KEMP 360 Central User Interface (UI).

6.2Feature Enhancements

  1. Enhancing the licensing capabilities to allow KEMP 360 Central be licensed using a condensed format licensing string for closed network environments.
  2. Providing the ability to allow KEMP 360 Central access to the internet using HTTP(S) proxy.
  3. Provision of confirmation step on device reboot.

7Version 1.7

Refer to the sections below for details about the KEMP 360 Central version 1.7 features.

7.1New Features

  1. System Updates

Providing the ability to perform an online (or offline) update of KEMP 360 Central firmware.

7.2Feature Enhancements

  1. Enhancing the licensing capabilities to allow KEMP 360 Central to be licensed offline.

8Version 1.6

Refer to the sections below for details about the KEMP 360 Central version 1.6 features.

8.1New Features

  1. Cert. based integration to LoadMaster

Enhanced integration with LoadMaster devices to use certificates.

Note: Only available with LoadMaster v7.1.35 releases and above.

  1. SSH Access Control

Allowing SSH access to KEMP 360 Central to assist with issue diagnosis and resolution

  1. MELA Licensing

Providing alternative consumption models for KEMP customer base to facilitate flexibility in deploying large volumes of Virtual LoadMasters whilst maintaining control over their total cost.

8.2Feature Enhancements

There are no feature enhancements as part of this release.

9Version 1.5

Refer to the sections below for details about the KEMP 360 Central version 1.5 features.

9.1New Features

  1. HAProxy

It is now possible to add/edit/remove HAProxy devices and visualize key traffic metrics and statistics from the KEMP 360 Central UI.

  1. NGINX

It is now possible to add/edit/remove HAProxy devices and visualize key traffic metrics and statistics from KEMP 360 Central UI.

  1. Public Cloud Certification

KEMP 360 Central has been certified in both Azure and AWS.

9.2Feature Enhancements

  1. Checksums are now available (MD5/SHA) to ensure that all deliverables can be verified by customers

10Version 1.4

Refer to the sections below for details about the KEMP 360 Central version 1.4 features.

10.1New Features

  1. Virtual Service management

It is now possible to perform some Virtual Service management tasks, such as adding, removing and viewing basic properties.

  1. Virtual Service monitoring

Virtual Service status is now displayed.

  1. Usage files

KEMP 360 Central now gathers usage statistics which can be exported.

  1. Scheduling

It is now possible to schedule activities, such as reboots, firmware updates and backups.

10.2Feature Enhancements

  1. It is now possible to configure the network options using the KEMP 360 Central console.
  2. It is now possible to add, modify and delete SubVSs using KEMP 360 Central.
  3. Enhancements have been made to the User Interface (UI).
  4. Tooltip text has been added.
  5. Security enhancements have been implemented.
  6. Improvements have been made to the monitoring graphs.
  7. Several styling enhancements have been made.
  8. Navigation improvements have been made.
  9. The Open WUI link is now hidden for the read_only user.
  10. A date selector has been added to the metrics data download option.
  11. A pop-up message now appears before updating the KEMP 360 Central software asking if you want to continue with the update.
  12. A warning pop-up message now appears if a LoadMaster with a firmware version older than 7.1-30b is being added.

11Upgrade Path to the Latest Release

The KEMP 360 Central firmware version is available on the About page, displayed by clicking on the question mark button on the bottom-left of the UI.

The following graphic summarizes the path that you need to follow to upgrade currently deployed KEMP 360 instances to the latest release.


Upgrade Path


Upgrade to V1.9 only. Contact KEMP Support to upgrade.


Upgrade to V1.9 only. Contact KEMP Support to upgrade.


Upgrade to V1.9 only (see the following section).


Upgrade to V1.9 only (see the following section).


Upgrade to latest release supported. Customers running a v1.9 image earlier than v1.9.0.1403 must upgrade to v1.9.0.1403 before upgrading to a later release.


Upgrade to latest release supported.


Latest release.

11.1Upgrading from Versions 1.7 and 1.8 to Version 1.9

This section tells you how to upgrade from KEMP 360 Central Versions 1.7 and v1.8 to Version 1.9. Customers running Version 1.6 and below should contact KEMP support for upgrade instructions.

  1. Contact KEMP support for the location of the KEMP 360 Central v1.9.0.1403 patch and download the patch to the local system from which you access the KEMP 360 user interface.
  2. Open the KEMP 360 Central UI and click the gear icon (Settings and Configuration) in the bottom-left corner.
  3. Click Firmware Management.
  4. Click Select Firmware.
  5. Browse to and select the KEMP 360 Central v1.9.0.1403 patch from your local system.
  6. Click Upload & Install.
  7. A message appears asking if you want to proceed with the update. Click Continue to proceed.
  8. After the update, KEMP 360 Central reboots.

Once the above is complete, you can use the UI to upgrade to the latest firmware release.

Document History



Reason for Change



Jan 2016

Initial document

Version 1.1 release



Jan 2016

Minor change

Updated Copyright Notice



Feb 2016

Release updates

Version 1.2 release



Apr 2016

Release updates

Version 1.4 release



Aug 2016

Release updates

Version 1.8 release



Sep 2016

Release updates

Version 1.9 release



Jan 2017

Release Updates

Version 1.12 release



Mar 2017

Release Updates

Version 1.14 release



Apr 2017

Updated Section 1.2

Added MELA-specific guidelines



May 2017

Release Updates

Version 1.15 release



Was this article helpful?

0 out of 0 found this helpful



Hi guys,

we have v1.9.0.1403 installed, but updating is not possible.
Error message is: "Oops! Firmware already exists, you can only upload one version of firmware at a time"

Anybody else experiencing this issue?


Naseer Husein


Just tested this in my lab and I was able to reproduce the issue. If you do not extract the zip file it will throw the error you are seeing.

When I extracted the zip file and just selected the PATCH, I was able to update central without a problem. If you have further issues with this please open up a support case and we can troubleshoot this further.