Search The Hostwinds Guides Knowledge Base

Creating A Load Balancer

Share This Article [TheChamp-Sharing]

This guide is intended for Hostwinds Clients to help create a Load Balancer through the Cloud Control Panel. These steps are intended for Hostwinds clients who have access to the Cloud Control Panel and would like to quickly and easily create a Load Balancer.

Create a Load Balancer

Step One: Login to your Cloud Portal

Step Two: Navigate to Network => Load Balancers to access your Load Balancer Panel

Cloud Control Network Load Balancers Menu Location

Step Three: Click Create => Load Balancer in the upper right to begin the steps

Cloud Control Create Load Balancer Location

Step Four: Clicking that will bring you to a page where you can decide the details for the Load Balancer. Such as specifying any Health checks, Traffic Rules, as well as Backend Servers

Cloud Control Network Load Balancers Add A Load Balancer Default
  1. Here you can enter in the Name for the load balancer. This is used to identify the Load Balancer from within your Cloud Portal.
  2. You can also select the Data center Location that the Load Balancer is created in.
  3. With the Traffic Rules you can set, what happens to traffic depending on the Ports that are accessed on the Load Balancer. The available options to choose from are HTTP, HTTPS, HTTPS w/ SSL and TCP.
    1. HTTP – This will route from HTTP usually to the same, HTTP. If used with HTTPS on the right side, it may cause errors to occur.
    2. HTTPS – This will route from HTTPS to HTTPS. If HTTP is on the right side, errors may occur with the site as well.
    3. HTTPS w/ SSL – This can be used to route from HTTPS to HTTP, as with this, an SSL Certificate is specified and used to encrypt and decrypt to the Load Balancer itself.
    4. TCP – This is if you are not planning to use HTTP or HTTPS with the Load Balancer but plain TCP.
  4. Backend Servers can be added to the Load Balancer as well. This is where the Load Balancer will attempt to send the traffic that comes through.
  5. By default, the Health Monitor option will be disabled. However, if enabled, this can be used to make sure the Load Balancer is only sending connections that come through to an Active or Healthy Backend Server.
  6. There are several different types of Monitoring that can be done with the Health Monitor. This can be set as HTTP, HTTPS, TCP, PING and TLS-HELLO. If using HTTP or HTTPS, this can be used to check the HTTP Response code that comes back from the server. (Test if the site is showing a 200 OK response for example). The Health Monitor will attempt this check on each Backend Server to ensure they are up before it attempts to send connections there. (From here you can also change the delay in between the checks, the Timeout as well as how many tries it should do)
  7. This is what determines how the Load Balancer will distribute the traffic that comes through. By default, there are options to set as Round Robin, Least Connections and Source IP.
    1. Round Robin – The Load Balancer will alternate between the Available Backend Servers (if using a Health Monitor it will make sure the Server is Healthy)
    2. Least Connections – The Load Balancer keeps track of how many connections it sends to each Backend Server. If this is used, it will attempt to send to the Server with the least amount of Connections.
    3. Source IP – With this algorithm, it will generate a Hash from the IP address accessing the Load Balancer and distribute to a server based on that.
      1. You also have the option to set the type of Persistence that is used with the connections through the Load Balancer. This is if you want connections made in the Load Balancer to be routed to the same Backend Server each time (if possible). The options for this are Application Cookie, HTTP Cookie, and Use Source IP. There is also the option for None, which will let the Load Balancer decide based on the Algorithm each time.
        1. Application / HTTP Cookie – This will use a Cookie to ensure that the connection is always routed to the same Server. With Application Cookie, you can set the Cookie Name.
        2. Use Source IP – This will use a Hash of the Source and Destination IP address to ensure it is sent to the same server each time.
  8. Once you have Filled out all the information as you would like with the Load Balancer (for the most part, a lot of this can be changed later on as needed), click on Add Load Balancer.

Step Five: After going through the above process in Adding the Load Balancer, it should take just a few moments while it is being creating. Once completed the status of the load balancer will change to Active, Online. To update the status, a refresh of the load balancer page will be required

Related Articles

If you should have any questions or would like assistance, do feel free to contact us through Live Chat or by submitting a ticket with our Technical Support team.