Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

LoadMaster Release Notes

Refer to the sections below for details about firmware version This was released on 17th November 2016.

New Features

The following features were added to the release:

  • Unified Capabilities Approved Product List (UC APL) updates
  • The following Virtual Service application configuration templates were published:
    • IBM Domino
    • RabbitMQ
    • Epic Medical Systems
    • Pearson PowerSchool
    • vSphere Platform Service Controllers (PSC)
    • Apache Tomcat
    • Apache HTTP
    • Horizon View 7.0
    • Microsoft IIS
  • LoadMaster kernel update
  • Additional Dell support
  • Security Assertion Markup Language (SAML)-based authentication Proof of Concept (PoC)
  • License type selection
  • Digital signing of PowerShell Application Program Interface (API) module
  • Certificate-based authentication added for the PowerShell API module

Feature Enhancements

  • Enhanced special character handling for form-based Edge Security Pack (ESP) logins.
  • Active File Transfer Protocol (FTP) traffic is being Network Address Translated (NATed) to the expected IP address.
  • Updated the OpenSSL version to 1.0.2j.
  • Updated the BIND version on the LoadMaster to 9.10.4-P3 to mitigate against the CVE-2015-5722 and CVE-2015-5986 vulnerabilities.
  • Support added for Dell Broadwell hardware.
  • Enhancements made to the debug checks performed when licensing fails.
  • On newly created Virtual Services, transparency is disabled and Subnet Originating Requests is enabled by default.
  • Improvements made to eliminate the possibility of having duplicate High Availability (HA) Virtual IDs.
  • Three days after deploying a LoadMaster for Amazon Web Services (AWS), you are prompted to type your KEMP ID and password to activate your support subscription.
  • Lightweight Directory Access Protocol (LDAP) health checks added.
  • A header value can be copied into a custom header.
  • Support added for the ModSecurity JavaScript Object Notation (JSON) log format.
  • It is possible to configure the check port for the DNS health check type in the Web User Interface (WUI).
  • SSL certificates, SSO settings and associated settings are now synchronized between cloud-based HA pairs.
  • Added an API command to check the previous firmware version.
  • The showiface API command now lists all interfaces if an interface is not specified.
  • A number of diagnostic commands added to the PowerShell API module.

Issues Resolved


The newest USB drivers for keyboards are supported.


Fixed an issue that was causing the LoadMaster to crash in a specific scenario.


Fixed some issues relating to the GEO proximity Selection Criteria.


Subnet Originating Requests are now respected when the LoadMaster is using a “Sorry” Server.


Fixed an issue that was displaying incorrect Real Server statistics.


It is possible to assign multiple Web Application Firewall (WAF) rules to a Virtual Service using the API.


Fixed an issue with the Real Server icons.


Fixed an issue that caused a reboot loop on Hyper-V with the Intel Skylake processor.


A notification is displayed when the GEO cluster limit is reached.


Fixed an issue with historical graphs.


Fixed an issue with cloud HA synchronization.


Fixed an issue that was causing GEO partner updates to fail.


Stopped a spurious log message from appearing.


Rectified a truncation issue with LinOTP-2 factor PIN.


Fixed an issue that prevented exported templates from working when Detect Malicious Requests is enabled.


Fixed an issue that was causing the health check status to show as unchecked in Azure HA units (even though the health check probe was working correctly).


Fixed an issue that locked out some LoadMaster users when using HA and session management.


Fixed an issue that prevented wildcard UDP Virtual Services from NATing the return traffic as expected.


Fixed an issue that prevented ciphers being selected in the Microsoft Edge and Internet Explorer browsers.


Fixed an issue that was causing the LoadMaster to enter passive mode after rebooting three times without the LoadMaster being up for more than five minutes.


Made improvements to the boot log to make it easier to read.


Improved RADIUS challenge-OTP handling.


It is possible to set the Checked Port using the API.


It is possible to set the Persistence Mode to none using the PowerShell API.


Fixed an issue that required the port to be specified when running the Enable-SecAPIAccess and Disable-SecAPIAccess commands.


Fixed an issue that prevented the netsonsole parameter from being set using the PowerShell API.


Fixed an issue preventing certain values from being unset using the Set-SecRemoteAccess PowerShell API command.


Corrected the API command for WAF commercial rule updates and installations.


Fixed an issue preventing a custom rule data file from being uploaded using the RESTful API.


It is possible to enable the Require SNI hostname flag using API commands.


Fixed a misspelling in a RESTful API command.


Improved error handling for API commands relating to GEO maps.


It is possible to set the GEO location of “everywhere” using the API.


The checker address can be set using the API.

Known Issues


A critical vulnerability (CVE-2018-9091) in the LoadMaster Operating System (LMOS) related to Session Management could allow an unauthorized, remote attacker to bypass security protections, gain system privileges, and execute elevated commands such as ls, ps, cat, and so on, thereby compromising the system. Through this remote execution, in certain cases, exposure of sensitive system data such as certificates, private keys, and other information may be possible.

Further information can be found here: Mitigation For Remote Access Execution Vulnerability.


Proximity and Location Based scheduling do not work with IPv6 source addresses.


Application of SNORT rules does not work.


LoadMaster VNF HA does not work on LoadMaster versions 7.1.35.n and 7.2.36.n. It does work om LoadMaster version 7.2.37 and above.


Issue with configuration corruption causes some GEO features not to function.


ESP SubVS connection logging is not showing Real Servers.


The MTU size is getting reset to 1500 when bonding interfaces together.


There are some issues relating to IPv6 routing.


Some JavaScript appearing in the LoadMaster warn logs is being executed by the browser.


There are some issues with content rules matching multiple requests on the same connection.


It is not possible to manage admin certificates from the individual IP addresses of a HA pair.


The vRealize Operations Manager Adapter setup fails if the API is disabled.


When using the vRealize Operations Manager, the management port must be set to 443 otherwise it fails.


The WUI help text says it is possible to set the L7 Connection Drain Time to 0 but this is not possible. Valid values range between 60 and 86400.


There is some unnecessary output from the Get-NetworkDNSConfiguration API command.


In some cases, after upgrading the LoadMaster firmware from version 7.1.35 to a newer firmware version, historical graphs may not display. To fix this, reset the statistic counters (System Configuration > Logging Options > System Log Files > Debug Options > Reset Statistics).


The API commands to reset the CPU and network graphs do not work.