The LoadMaster has rebooted.

This can be as a result of a system problem or possible power supply issues. Being informed about these reboots allow you to investigate the root cause and determine if there are any future risks to application delivery.

Example scenario: The following text describes an example scenario where a LoadMaster reboot may occur. A power surge results in a brief loss of power to the LoadMaster. While redundant power supply kicked in, the power surge did result in a brief loss of power and a reboot of the device.

Like all software appliances, factors such as excessive traffic volumes or software errors can result in performance issues or unexpected reboots. High Availability (HA) can ensure that reboots of a LoadMaster has minimal impact on application service. For further details on HA, refer to the HA Feature Description.

In any case, it is important to investigate and diagnose any such issues. With the right investigation and diagnosis these issues can be easily identified and prevented. Some checks you can perform if there appears to be any performance issues or unexpected restarts of the LoadMaster device are as follows:
  • Determine CPU and Network Metrics: One of the first things to check are CPU and network metrics. These should provide an indication of whether the LoadMaster is operating within healthy boundaries and can also point to potential issues if present. For further details, refer to the following Knowledge Base article: How to View the LoadMaster's Metrics and Connection Statistics.
  • Identify processes running on the LoadMaster: When there are issues, it may be useful to identify all processes running on the LoadMaster because this may point to unexpected processes consuming resources. For instructions on how to do this, refer to the following Knowledge Base article: How to Determine Processes that are Running on the Kemp LoadMaster.
  • LoadMaster Resource Utilization: All hardware and software LoadMasters have finite resources. It is useful to understand the different aspects of application delivery and how these might impact LoadMaster performance. For further details, refer to the Resource Utilization Technical Note.