Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

GEO Release Notes

Refer to the sections below for details about firmware version This was released on 21st February 2018.

Issues Resolved


Previously, on occasions the GEO zone serial is not refreshed, causing a spurious "Zone may fail to transfer to slaves" log message.
Now, the log level for these messages have been changed from ERROR to INFO. These messages do not affect functionality.


Previously, if an FQDN with a wildcard and another FQDN belonging to the same domain is configured, in some scenarios GEO can pick up the wildcard FQDN instead of the correct FQDN.
Now, GEO picks up the correct FQDN even if the configuration has a wildcard FQDN.


Previously, GEO returns sites that are down if the Selection Criteria is set to All Available.
Now, only sites with a status of "up" are returned.


Previously, the New-GeoCluster command returns an invalid error, when you try to add a GEO cluster that already exists with the same name and IP address.
Now, for the same scenario, the New-GeoCluster command returns a proper error message: Cluster already defined. Name/IP must be unique.


Previously, the removecountry API command error message had a typo (countries was spelled counries).
Now, the typo in the removecountry API command error message is fixed.


Previously, the showcluster and showfqdn API commands displayed location parameter values in degrees, but the showip API command displayed the values in seconds.
Now, the showfqdn, listfqdns, showip, listops, showcluster, and listclusters API commands display the values in seconds.


 Previously, the showfqdn API command displayed the Failtime value in seconds, but it is set in minutes.
 Now, the showfqdn API command displays the Failtime value in minutes.

Known Issues


A critical vulnerability (CVE-2018-9091) in the Multi-Tenant LoadMaster Operating System (MT-LMOS) related to Session Management could allow an unauthorized, remote attacker to bypass security protections, gain system privileges, and execute elevated commands such as ls, ps, cat, and so on, thereby compromising the system. Through this remote execution, in certain cases, exposure of sensitive system data such as certificates, private keys, and other information may be possible.

Further information can be found here: Mitigation For Remote Access Execution Vulnerability.


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


An issue with configuration corruption is causing some GEO features to not function.


GEO does not support DNS TCP requests from unknown sources.


Proximity and Location Based scheduling do no work with IPv6 source addresses.


Location Based failover does not work as expected.