There are various methods of distributing traffic among a cluster or group of servers. The traffic distribution is based on a load balancing algorithm or scheduling method. The scheduling are applied on a per Virtual service basis. Here is a list of the methods:
This is a known behavior when the scheduling method is set to Least Connections. Using this scheduler LoadMaster will send new connections to the server which has the least connections which are actively sending data. If the overall level of traffic is not great enough to ensure that a baseline of activity is happening at every moment, there may be a skewing of traffic to the first server.
Information about Adaptive Scheduling can be found on our documentation page. Contained in the zip file is the Windows executable file, details about configuring the Windows agent as well as details about Adaptive Scheduling in general. You can also find example scripts for Linux and other platforms in the LoadMaster Configuration Guide in Appendix H.
Port following is set when two services need to share persistence records. Typically this is done for HTTP and HTTPS services so users maintain a server session regardless of whether they connect securely. This is explained in our manual in Section 4.6 and 16.7. Port Following does have several requirements:
One requirement is that you will have to run a web service on the server. Whether IIS, apache, etc., you will need a web service running on the server in-order to run adaptive agent. There is a list of steps to configure this feature on your server and you can find these setting and documentation at: https://www.kemptechnologies.com/documentation
This can be accomplished by selecting Fixed Weighting for your Scheduling Method within your virtual service. This will allow clients to only connect to the highest available weighted Real Server. If the preferred Real Server becomes unavailable, the next highest available weighted Real Server will be selected. All weights of the Real servers must be different. To modify a specific server's associated weight, in the WUI: