Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

GEO Release Notes

GEO Version is a feature enhancement and bug-fix update released in August 2019. Please read the sections below before installing or upgrading. 

Feature Enhancements

The following feature enhancements have been implemented.

Serial Console for Public Cloud Platforms

Serial console support has been enhanced so that you can now connect to the LoadMaster serial console in public clouds, such as AWS and Azure. This allows access to all console interface capabilities, including resetting the password for the administrative login (bal).

Issues Resolved

The following issues have been resolved in this release:


Licensing: In previous releases, if a password for a Kemp ID contained a "`" (backtick) character GEO would fail to get a license from the Kemp licensing server. This issue has been fixed so that licensing is successful in this case.


Security: Fixed a potential security vulnerability where javascript could be added to the MOTD via the API. This is now not permitted.


Security: Fixed a potential security vulnerability where a script could be uploaded to the MOTD via the API. This is now not permitted.


GEO: Fixed an issue that caused updates to GEO partners to fail.


Security: In previous releases, it was possible to discover a GEO's private IP address via the API if someone knew only the public IP address. Now, the private IP address is no longer seen in the API response, nor is it seen in the WUI unless a user has logged in.


API: Fixed an issue with the 'lscpi' API that caused an 'xmlParseEntityRef' error to be returned instead of a proper response.


LDAP: In previous releases, configuring multiple LDAP servers on the LDAP Endpoint caused WUI Authentication to fail; however, it works if a single server is specified. This issue has been fixed.


Networking: Changes made to the Bonding mode (e.g., from 802.3ad to Active-Backup) reverted back to the previous value. This issue has been fixed.


Browser Support: In previous releases, the WUI Certificate doesn't have a SAN (Server Alternate Name) value, and this causes a certificate error in the Chrome and Firefox browsers. This issue has been fixed by adding a SAN to the certificate.


SMTP: In previous releases, setting the SMTP Server to "" on port 587 does not work. This issue has been fixed, so that "" on port 587 with STARTTLS can now be used.


GEO: Fixed an issue that could cause the following spurious error to appear: "GEO_ACL_Automatic_Update: feature is not enabled and/or support is expired. Please contact Kemp support.".


GEO: Fixed an issue that caused segmentation faults on GEO partners.


SSL Certificates: Fixed an error that occurred when a user tries to upload a 4096 byte SSH Private Key via the API.


Licensing: Fixed a licensing related issue on the Azure platform that could cause intermittent failures when attempting to contact the Kemp licensing server.


Licensing: Fixed an issue where the LoadMaster configuration does not get cleared after a "Kill_License" is performed via the LMOS API or licensing server.


SSL Certificates: Fixed an issue where 'Elliptic Curve Cryptography' (ECC) certificates in PFX format can't be uploaded.


Licensing: Fixed an issue that caused a spurious message to be displayed when "Kill License" is initiated from WUI.


Networking / SSL Errors: In previous releases, all client SSL messages are written to the LoadMaster logs, which can result in spurious client alert messages appearing in the logs. To address this issue, a new parameter setting has been added to the WUI under System Configuration > Miscellaneous Options > Network Options labelled Log SSL errors. This is set by default to log "Fatal errors only", which will suppress client errors and spurious messages from appearing in the log. You can also set this parameter to display client errors (but not spurious messages), or to return to the behavior in previous releases where no messages are suppressed.


GEO: Fixed an issue that could cause a 'readremote' failure to appear in the log, followed by a GEO Cluster check failure.


Kernel: Fixed an issue that caused spurious kernel call trace warnings to appear in the log.


GEO: In previous releases, when configuring a Cluster for an FQDN, the Mapping Menu parameter returns an error if a Virtual Service whose name contains a left or right bracket character ('[' or ']') is selected from the drop-down. This issue has been fixed.


RADIUS: In previous releases, the Use Local Account only if AAA Fails option may not work as designed when a RADIUS server and a backup RADIUS server are configured, and no response is received from the backup server. This issue has been fixed.


Licensing: In previous releases, the "readeula" REST API does not work after licensing (except when deployed on AWS). This has been fixed to work properly on all cloud, virtual and hardware models.


API: In previous releases, the LMOS 'stats' and 'listconfig' APIs show an incorrect interface speed when there is no link detected. This issue has been fixed so that the correct speed ('0') is displayed.


GEO: In previous releases, with cluster checking set to 'Remote LM', clusters may not appear on the partner device, or may have invalid entries. This issue has been fixed.


Known Issues

The following known issues appeared in the Release Notes for the previous release.


Networking: A Hyper-V VLM won't boot when a 4th NIC is added.


Downgrade: If an Azure VLM is downgraded to the LTS firmware release (7.1.35.x), the WUI may display in the top right-hand corner that the VLM is a Hyper-V VLM. This indicates that the Azure VLM Add-On Package must be added to the system to provide full Azure VLM functionality. If this occurs, please contact Kemp Support to get the required add-on package.


RADIUS / IPv6: IPv6 is not supported by the current RADIUS implementation in the LoadMaster for both WUI Authorization and ESP Authentication.


Networking: Azure LoadMasters are not translating the additional network address between the Master and Slave correctly.


WUI: The WUI is not accessible on NIC-1 from a non-local subnet.


GEO: If a GEO FQDN is configured with All Available as the Selection Criteria, IP addresses are returned even if the cluster is disabled.


GEO: DNS TCP requests from unknown sources are not supported.


GEO: Location Based failover does not work as expected.


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