Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Multi-Tenant LoadMaster MT_7.1.35.9 Release Notes

Multi-Tenant LoadMaster Version MT_7.1.35.9 was released in October 2019. This is a feature and bug fix release, as described in the sections below.

New Features

Support for Specifying a RADIUS NAS ID for RADIUS Authentication

When using RADIUS-based authentication to log into MT via the WUI or API, you can now specify a RADIUS NAS-Identifier (or NAS ID) to send to the RADIUS server. By default, the NAS ID is set to the MT system hostname, but can be changed to any custom string. This identifier is primarily used on the RADIUS server to select the policy to apply to an incoming request, and often follows a site-specific format.

Issues Resolved


Shutdown: On an LM-5610, shutting down MT from the WUI or API, reboots the unit instead of performing a shutdown. This issue has been fixed.


Offline Licensing: If an MT unit's license was updated using the offline method, the "Update License" button in the VNF WUI for all VNFs instantiated on the MT unit remained disabled. This bug has been fixed. The "Update License" button is now clickable and works as expected when an MT license is updated.


Interface Speeds and the stats() API: The stats() API displays incorrect speeds for any interface that is configured but on which no link is detected. This issue has been fixed so that the API displays the correct and appropriate speed for an interface regardless of the link status.


Memory Values and the createinstance() API: Previously, when using the createinstance() API, the max memory value that can be specified is 8192, regardless of the system's actual memory capacity. This has been addressed by modifying the API to present the max memory value appropriate for the MT host, and will present the same values that appear in the WUI.


Adding a VNF: Creating a VNF via the WUI with an invalid name displayed an error message that was different than the API. This issue has been addressed by modifying the WUI to display the same message as the API.


EULA API: Viewing/accepting the EULA via the readeula() API results in an error; the response is not displayed, and the EULA can't be viewed via the API after it's accepted. This has been fixed so that users can view/accept the EULA via the API without any errors being seen, and the API used to view the EULA can be used after the EULA is accepted.


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, if the VNFs are running version 7.1.35.x.


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.