Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Multi-Tenant LoadMaster MT_7.1.35.8 Release Notes

Multi-Tenant LoadMaster MT Version MT_7.1.35.8 was released in May 2019. This release contains the resolved and known issues described below.

Issues Resolved

PD-13155 Fixed an issue where the WUI and API support different sets of special characters for the LoadMaster tenant (a.k.a. Virtual Network Function or VNF) system name.
Both the WUI and the API now support the same set of special characters for the VNF name: ^ a-z A-Z 0-9 _ . @ * $ / ; [ ].
PD-13098 In previous releases, a spurious text string appears while modifying the eth0 address on a LoadMaster MT system. This issue has been fixed. 
PD-10194 In previous releases, the Update License option is never made available on tenant LoadMasters, so it was not possible to re-license the tenant LoadMaster when the MT Host LoadMaster's license is updated. This issue has been addressed -- once the MT host license has been updated, the Update License button will appear on tenant LoadMasters indicating that a new license is available. Clicking this button will apply the new license to the tenant, which will require a tenant reboot.


Known Issues


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


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


Users are unable to download the backup file via the RESTful API if Session Management is enabled.


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


There is a limit to the VNF size of the maximum 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.


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


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


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


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


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


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.


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.