> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-products/networking/loadbalancer/configure-load-balancing.md).

# Configure Load Balancing

## Create a Load Balancer

{% embed url="<https://youtu.be/JaSdSVNW9bk?si=pCafm9ww-O9Low6b>" %}

{% hint style="info" %}

* Make sure before creating the load balancer in your cloud to add proper rules, ports, and network.
* When setting up a load balancer, verify that the connected server is active and operational.
  {% endhint %}

Navigate to the networking section and select the Load Balancer.

<figure><img src="/files/43Ah61G4h3HZERpyL3nL" alt=""><figcaption></figcaption></figure>

## Select Network

In the network section, select the public network.

<figure><img src="/files/bkqJflFAZWD6R8lrWK7Z" alt=""><figcaption></figcaption></figure>

## Select Pool Members

Pool members are also known as backend servers or nodes. are the individual servers or resources that handle incoming traffic and requests behind a load balancer.

<figure><img src="/files/LVW02x8c2YGhDiD4LJV8" alt=""><figcaption></figcaption></figure>

## Set the Listener

A **listener** in load balancing is a process that checks for incoming client connections on a specific port and protocol on the load balancer. It listens for requests and routes the traffic to the appropriate pool members (backend servers) based on predefined rules and algorithms. The listener plays a crucial role in managing and directing the flow of traffic, ensuring efficient distribution and optimal resource utilization.

* **Port**: The port number on which the load balancer listens for incoming traffic.
* **Protocol**: The protocol used for communication, such as HTTP, HTTPS, TCP, or UDP.

<figure><img src="/files/2trtHITEti0YkbkuNFdn" alt=""><figcaption></figcaption></figure>

## Select the Algorithm

Algorithm-> **Round Robin** -  Round Robin is a load-balancing technique that distributes incoming network traffic across a group of servers in a sequential manner. It is a simple and widely used algorithm that forwards client requests to each server in turn and then repeats the process from the beginning.  &#x20;

**Least Connections** - Least connections load balancing is a dynamic load balancing algorithm that distributes client requests to the server with the fewest active connections minimizing the chances of server overload.

**Source IP: The source** IP algorithm refers to the methods and processes used to determine the source IP address in network communications. This selection is crucial for ensuring that responses to packets reach the correct originating devices.

Select Algorithm:- Round Robin

<figure><img src="/files/yzyFkTLtgZgbfzWGIZVj" alt=""><figcaption></figcaption></figure>

Set the name of the load balancer and click on Create a load balancer

<figure><img src="/files/wXv4Y24RiGdJoItH356w" alt=""><figcaption></figcaption></figure>

## Check the status of the Load Balancer

After creating the load balancer navigate to the load balancer and click on the overview

<figure><img src="/files/YdHqXRNe485BcDY0bCEi" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.neevcloud.com/neevcloud-products/networking/loadbalancer/configure-load-balancing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.