# How to create a network load balancer? **To create a Network Load Balancer, follow the steps below:** **Step 1:** [Login](https://customer.acecloudhosting.com/index.php?m=ace_product_register_addon\&action=login) to your account. **Step 2:** Navigate to **Networks** and then click on **Load Balancer**.
**Step 3:** Click **Create Load Balancer**.
**Step 4:** Select **Network Load Balancer** and click **Next**.
**Step 5:** Enter the **Basic Details** and click **Next**.
| **Field** | **Description** | | ----------------- | ---------------------------------------------- | | Name\* | Name of the Load Balancer | | Description | Description of the Load Balancer | | IP Address type\* | Select IP address type from IPv4 and Dualstack | | Subnet\* | Select a subnet from the available networks. | **Step 6:** Enter the **Listener Details** and click **Next.** **Note:** If you do not want to create a listener, disable the toggle and click **Next**.
| **Field** | **Description** | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | | Listener Name\* | Enter the name of the Listener. | | Listener Description | Enter the description of the Listener. | | Listener Protocol\* |

Select a protocol for the listener from the below options:

  1. TCP
  2. UDP
  3. SCTP
| | Listener Port\* | The protocol port number for the resource. The default is 1. | | Client Data Timeout (in ms) | Enter client inactivity timeout in milliseconds. The default is 50000. | | TCP Inspect Timeout (in ms) | Enter time, in milliseconds, to wait for additional TCP packets for content inspection. The default is 0. | | Member Connect Timeout (in ms) | Enter member connection timeout in milliseconds. The default is 5000. | | Member Data Timeout (in ms) | Enter member inactivity timeout in milliseconds. The default is 50000. | | Allowed CIDRs | Enter a list of IPv4, IPv6 or mix of both CIDRs. | | Connection Limit\* | The maximum number of connections permitted for this listener. Default value is -1 which represents infinite connections. | **Step 7:** Enter **Pool Details**, **Server Monitor Health** details, and click **Next.** **Note:** 1. If you have not created a **Listener**, you will not be able to create a **Pool** and **Monitor**. 2. If you have not created a **Pool**, you will not be able to create a **Monitor**. 3. If you do not want to create a **Pool** and **Monitor,** disable the toggle and click **Next**.
| **Field** | **Description** | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Pool Name\* | Enter the name of the Pool. | | Pool Description | Enter the description of the pool. | | Pool Algorithm\* |

Select the load balancing algorithm for the pool from the below options:

  1. Least connections
  2. Round robin
  3. Source IP
| | Pool Protocol\* |

Select a protocol for the pool from the below options:

  1. HTTP
  2. HTTPS
  3. PROXY
  4. PROXYV2
  5. TCP
| | TLS Enabled | | | TLS Cipher String | Enter List of ciphers in OpenSSL format and it should be colon-separated. | | Session Persistence |

Select a JSON object specifying the session persistence for the pool from the below options:

  1. HTTP Cookie
  2. APP Cookie
  3. Source IP
| | Cookie Name\* | Enter the name of the cookie to use for session persistence. | | Monitor Name\* | Enter the name of the Health Monitor. | | Monitor Protocol\* |

Select a protocol for the health monitor from the below options:

  1. HTTP
  2. HTTPS
  3. PING
  4. TCP
  5. TLS-HELLO
  6. UDP-CONNECT
  7. SCTP
| | Max Retries Down\* | Enter the number of allowed check failures before changing the operating status of the member to ERROR. A valid value is from 1 to 10. The default is 3. | | Delay (in sec.)\* | Enter the interval, in seconds, between health checks. The default is 10. | | Max Retries\* | Enter the number of successful checks before changing the operating status of the member to ONLINE. The default is 1. | | Timeout (in sec.)\* | The time, in seconds, after which a health check times out. The default is 5. | | HTTP Method |

Select the HTTP method that the health monitor uses for requests from the below options:

  1. GET
  2. HEAD
  3. POST
  4. PUT
  5. DELETE
  6. TRACE
  7. OPTIONS
  8. PATCH
  9. CONNECT
| | Expected Codes\* | Enter the HTTP status codes expected in response from the member to declare it healthy. The default is 200. | | URL Path\* | Enter the HTTP URL path of the request sent by the monitor to test the health of a member. Must be a string that begins with a forward slash. The default URL path is /. | **Step 8**: Enter **the Backend Server** details and click **Next**. **Note:** 1. If you have not created a **Pool**, you will not be able to create **Backend Servers**. 2. If you do not want to create a **Backend Server,** disable the toggle and click **Next**.
| **Field** | **Description** | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Add Servers\* | Select the servers from the dropdown. | | Specific IP | Enter the specific IP you want to Add and click on **Add** button. | | Name | Name of the server. | | IP Address | IP address of the server. | | Associated Subnet | Name of the subnet, associated with the server. | | Specific Port\* | Enter the specific port you want to add. | | Monitor Address | Enter an alternate IP address used for health monitoring a member. | | Monitor Port | Enter an alternate protocol port used for health monitoring a member. | | Weight | Enter the weight of a member determines the portion of requests or connections it services compared to the other members of the pool. | **Step 9:** Review your load balancer details and click on the **Create** button.
--- # Agent Instructions: 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: ``` GET https://docs.acecloud.ai/knowledge-base/network/how-to-create-a-network-load-balancer.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.