Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Multi-Tenant LoadMaster MT_7.1.35.6 Release Notes

Refer to the sections below for details about firmware version MT_7.1.35.6. This was released on 5th December 2018. 

Feature Enhancements

  • Previously, there was no Redundant Array of Independent Disks (RAID) monitoring facility available for LoadMaster Multi-Tenant hosts that supported disk RAID configurations. Now, on a LoadMaster Multi-Tenant host that supports RAID configurations, in the Debug Options screen on the LoadMaster WUI, there are options to display the RAID controller and RAID disk information. Status information in relation to RAID events is also available in the LoadMaster message logs and using Syslog.

Issues Resolved


Addressed a further critical vulnerability (CVE-2018-9091) in the Multi-Tenant LoadMaster Operating System (MT-LMOS) related to Session Management that could, in certain circumstances, allow an unauthorized, remote attacker to bypass security protections, and gain access to sensitive system data, thereby compromising the system. This vulnerability was partially addressed in

The expanded scope of this vulnerability covers exploitation through the use of insecure Web User Interface (WUI) endpoints associated with historical graphs and licensing. These vulnerabilities have been addressed in this release. Further information can be found here: Mitigation For Remote Access Execution Vulnerability.


Previously, the LoadMaster Virtual Network Function (VNF) always used the default Port and Interface for the IP address hyperlink on Status of Installed VNFs.

Now, the hyperlink displays the correct IP address and Port (other than the default 443) on the VNF Status page.


Previously, a user with just User Administration privileges was not able to add\modify\delete other users on the system.

Now, the correct permissions are assigned, and a user with these permissions can administer other users on the system.


Previously, VLAN IDs were referenced using their HEX identifiers or the equivalent integer value. In cases where multiple VLANs were configured, this led to difficulty identifying the appropriate VLAN IDs.

 Now, VLAN IDs are easily identified throughout the WUI with the IDs set during configuration.


 Previously, RADIUS-based users did not get the correct Web User Interface (WUI) administration permissions when WUI Session Management was enabled.

Now, the correct user permissions are assigned.

Known Issues


High Availability (HA) on the Multi-Tenant LoadMaster does not work with LoadMaster VNF firmware versions LTS 7.1.35.x and V7.2.36.x.


The following error message appears if no local users are configured on the Multi-Tenant host WUI: '_RO_USERS: No such file or directory'. There is no functional impact relating to this error.


You cannot update the license of a Multi-Tenant LoadMaster VNF.


Users cannot apply a WUI certificate using the RESTful API or WUI.


Bonded VNF interfaces are not removed correctly after a VNF Factory Reset operation.


You cannot restore backup files on Multi-Tenant LoadMaster VNFs.


There are some issues when bonding more than two interfaces on a Multi-Tenant host.


The operation of the AutoStart button for Instantiated VNFs could be made clearer.


There is a limit to the VNF size of the max number of cores of a single CPU on a multi-core platform. For example, a dual CPU system with 6 cores per CPU, the max size that can be configured for a single VNF is 6 cores.


Some user permissions that are available for selection are not valid for a user on a Multi-Tenant LoadMaster.


Unable to download the backup file via the RESTful API if Session Management is enabled.


With Session Management enabled, the Test AAA for User functionality for the RADIUS user does not work and displays an “Authentication failed” message.


Characters allowed in the VNF name during creation are invalid when the name is modified.