Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Multi-Tenant LoadMaster MT_7.1.35.10 Release Notes

Multi-Tenant LoadMaster Version MT_7.1.35.10 was released in September 2021. This release contains the resolved and known issues described below.

Issues Resolved

PD-18698 User Interface: Fixed an issue that caused the UI to become unresponsive when bonding or unbonding an interface and the Try Again button is clicked.
PD-18622 API: The API has been modified to prevent deleting a bonded interface when one or more ports remain linked.
PD-15826 Interface Bonding: In previous releases, it was possible to attempt to bond interfaces on a VNF, but this would fail because all bonding must be done on the MT Host. With this release, the option to bond interfaces no longer appears in the VNF UI; if you attempt to bond interfaces on the VNF using the API, the error “Bonding not allowed for VNF” is returned.
PD-15823 User Interface: Fixed the user interface to properly display a change in link speed for bonded interfaces.
PD-15822 User Interface: Fixed an issue that caused bonded interfaces to not appear on the Home and Statistics pages.
PD-15292 Interface Bonding: Fixed an error that occurred when adding a bonded interface when there is no link.
PD-11334 Interface Bonding: On previous releases, bonding 2 interfaces may result in one of the ports being named incorrectly in the bond configuration (e.g., Eth2 and peth3, instead of Eth2 and Eth3), which causes the bond to fail (e.g., removing the cable from Eth2 doesn't cause traffic to move to Eth3). This bug has been fixed.
PD-10437 Interface Bonding: Fixed an issue that caused the eth2 interface to return an "unknown interface" error after factory reset when bonded with eth3.

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.


You cannot restore backup files on Multi-Tenant LoadMaster VNFs, if the VNFs are running version 7.1.35.x.


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.

Was this article helpful?
0 out of 0 found this helpful