Log Message: Cannot build symbol table - disabling symbol lookups

This is a normal bootup message that occurs on LoadMasters

Can I use offline licensing with a Free LoadMaster?

No, part of the requirements of using a free LoadMaster is that it is connected to the internet

“Please keep in mind that the licensing steps vary for the Free LoadMaster, such as the fact that online licensing is the only available licensing method. Refer to the next section for instructions on how to license the Free LoadMaster.”

https://support.kemptechnologies.com/hc/en-us/articles/204427785

Log Message: L7: Connection timed out (x.x.x.x:p->y.y.y.y:p-><nodest>)[0] (waiting for initial client request)

"Waiting for initial client request" occurs when the client connects but does not send any data. The client in question is x.x.x.x, the VS is y.y.y.y, the third address is the RS. In this case, the RS has not been selected, since there has been no data from the client that can be used to determine which to select.

What is the recommended firmware?

Kemp recommends upgrading to the LTS

Log Message: L7: Connection timed out (x.x.x.x:p->y.y.y.y:p->z.z.z.z:p)[0] (unconnected)

"Unconnected" timeouts are a result of connection attempts which were not completed to the real server. LoadMaster has determined which real server should take the connection and has initiated a TCP connection to the server, however the server did not respond. This may be due to a failed real server which has not been marked as failed by the healthcheck. It could also be caused by a very slow response time.

Can I upgrade from firmware X to the current GA firmware?

Please see tde table below for tde firmware update patd

Firmware Upgrade to        
5.1.X 5.1-74 -> 6.0-42-> 7.0-10I -> 7.1.35.6 (LTS) -> 7.2.44 (GA)
6.0.X 6.0-42-> 7.0-10I -> 7.1.35.6 (LTS) -> 7.2.44 (GA)
7.0.X 7.0-10I -> 7.1.35.6 (LTS) -> 7.2.44 (GA)
7.1.X 7.1.35.6 (LTS) -> 7.2.44 (GA)
7.2.X 7.2.44 (GA)

32-bit systems can only upgrade to LTS
see below for list of 32-bit models

GEO firmware versions??

Log Message: L7: Connection timed out (x.x.x.x:p->y.y.y.y:p->z.z.z.z:p)[0] (connected)

"Connected" timeouts indicate that the connection to the real server has been established and that data may have been transferred. The connection was disconnected because the idle timeout has been reached. This type of timeout is normal and is mostly the result of clients simply abandoning the connection.

The default for the timeout is 660s. This timeout can be found in System Configuration > Miscellaneous Options > L7 Configuration. The 'L7 Connection Timeout (secs)' is the global value for this timer. If it is set to 0, it will use the default value. This value can be overridden by the 'Idle Connection Timeout' in each virtual service.

Does my LoadMaster support the latest firmware?

Check the list below,

If the unit is 32-bit you can only upgrade as far as LTS

If the unit is not on the list below, please check our End of life cycle

32-bit Systems 64-bit Systems
LM-GEO 5.1-74 ->
6.0.X LM-X3
LM-2200 LM-X15
  LM-2400
  LM-2600
  LM-3000
  LM-3400
  LM-3600
  LM-4000
  LM-5000
  LM-5300
  LM-5400
  LM-5600
  LM-8000
  LM-8020
  LM-8020M
   
  VLM-GEO
  VLM-1000
  VLM-200
  VLM-2000
  VLM-3000
  VLM-5000
  VLM-10G
   
  Bare Metal
  AWS
  Azure

Log Message: L7: Real Server Connect attempt failed (x.x.x.x:p->y.y.y.y:p)

This message indicates that the server was unreachable for client connections even though the healthcheck is passing. This can be due to several factors. Most likely the healthcheck is not operating at a high enough level, the healthcheck considers the server up whereas in reality the server is not ready to accept connections. This can also happen if the server has just gone down and the healthcheck has not yet failed.

In a wildcard service, these messages mean that a connection to your wildcard service was attempted but was not able to connect because the real server rejected the request. This can happen when a client tries to access a service which does not exist on the real server; LoadMaster accepts the connection and attempts to forward it, but the server refuses it and thus LoadMaster closes the initial client connection. These are normal noise for a wildcard service.

How to upgrade firmware?

Step 1) Back up the LoadMaster

KEMP recommends taking a backup of the LoadMaster as a restore point which can be used if needed. To back up the LoadMaster, go to System Configuration > System Administration > Backup/Restore. Click Create Backup File.

Certificates need to be backed up separately. For instructions on how to back up certificates refer to the following article: How do I back up certificates?. Alternately, you can take a snapshot of the virtual machine if you have a Virtual LoadMaster.

Step 2) Download the patch

  • Log into the KEMP Support Center.
  • Click Downloads.
  • Select the appropriate LoadMaster type/model.
  • Download the appropriate firmware release.

Step 3) Install the patch (Start on Standby unit if in HA)

  • In the WUI, go to System Configuration > System Administration > Update Software.
  • Click Choose File.
  • Browse to and select the patch file.
  • Click Update Machine.
  • Follow the prompts to apply the patch.

Step 3.5) If the update fails due to "License disallows further software updates" please refer to this article:

(https://support.kemptechnologies.com/hc/en-us/articles/115003486286-License-Disallows-Any-Further-Software-Updates)

Step 4) Reboot

You will be prompted to reboot the LoadMaster. Please do so.

Step 5) Clear the browser cache

After patching, if there are any problems using the WUI, please clear the browser cache and restart the browser.

Step 6) Repeat the process for the partner unit (if applicable)

LoadMaster Highly Available (HA) pairs require each unit be patched separately. Following this process will achieve the least amount of down time since once one fail-over is required. The overall process is as follows:

  • Patch the Standby unit via the individual IP address.
  • Reboot the upgraded unit.
  • Check to ensure the patched unit is back online (try to access the LoadMaster administrative IP address, which usually the eth0 IP address).
  • Now the patch the active unit.
  • Reboot the upgraded unit.

Log Message: "Timeout waiting for data"

Connected, but server took too long to send back any data.

License Disallows Any Further Software Updates?

This error refers to the current license on the unit. You can update the firmware on the LoadMaster if the unit is in support but will need to update the license first

If support has been renewed recently, the unit may have the old support date. In this scenario, you must update the license on the unit using the online or offline licensing method.

If the LoadMaster has access to the internet:

Access the LoadMaster Web User Interface (WUI).
Navigate to System Configuration > System Administration > Update License.
Select Online Licensing and enter your KEMP ID and password.
Click Update License.

Alternatively, if the LoadMaster does not have internet access you can use the offline method:

Navigate to System Configuration > System Administration > Update License.
Select Offline Licensing and click the Get License link.
Enter your KEMP ID and password (leave the Order ID field blank).
Upon completion, the license will be emailed to you.
Copy and paste the License, from start to finish, into the License box.
Click Update License.

For further information, refer to the Licensing Feature Description

“Patch is not for this CPU architecture.”
this error is displayed when you try to apply a 64-bit firmware on a 32-bit system or 64-bit firmware on a 32-bit firmware

Please confirm that the model supports 64-bit firmware

“Cannot update: Software update currently in progress”
This error is displayed when you try to update the firmware, but the process was interrupted rebooting the unit clears this error

Log Message: "Timeout waiting for connection"

Probably only seen when checking "remote" machines, or if machine has just failed (ARP still valid).

Log Message: "Connection Failed - unreachable host"

There is no route to the host, machine is probably down, or a network failure.

Log Message: "Connection Failed - server unavailable"

Machine is available but the application is not running (connection refused).

Log Message: "Connection Failed - Failed SSL negotiation"

TCP connection ok, but the SSL_connect failed.