Server Load Balancer:Create and manage a server group

Prerequisites

• Before you add Elastic Compute Service (ECS) instances, elastic network interfaces (ENIs), or elastic container instances to a server group, make sure that the resources are created and applications are deployed on them to receive requests forwarded by NLB.

• To forward requests to the backend servers in a server group, specify the server group when you create a listener or a forwarding rule. For more information, see NLB listeners.

Create a server group

1. Log on to the NLB console.

2. In the top navigation bar, select the region in which the NLB instance is deployed.

3. In the left-side navigation pane, choose NLB > Server Groups.

4. On the Server Groups page, click Create Server Group.

5. In the Create Server Group dialog box, configure the parameters and click Create. The following table describes the parameters.

   Parameter	Description
   Server Group Type	Select a server group type. Valid values: Server Type: allows you to add backend servers by specifying ECS instances, ENIs, or elastic container instances. IP: allows you to add backend servers by specifying IP addresses. Note You can specify only private IP addresses. You cannot specify public IP addresses.
   VPC	Select a virtual private cloud (VPC) from the drop-down list.
   Backend Server Protocol	Select a backend protocol. Valid values: TCP: If you select this option, you can associate the server group with a TCP listener or a TCP/SSL listener. UDP: If you select this option, you can associate the server group with a UDP listener.
   Scheduling Algorithm	Select a scheduling algorithm. Valid values: Round-Robin: Requests are forwarded to backend servers in sequence. Weighted Round-Robin (default): Backend servers that have higher weights receive more requests than backend servers that have lower weights. Source IP Hashing: specifies consistent hashing that is based on source IP addresses. Requests from the same source IP address are distributed to the same backend server. Four-Element Hashing: specifies consistent hashing that is based on the following factors: source IP address, destination IP address, source port, and destination port. Requests that contain the same information based on the preceding factors are forwarded to the same backend server. QUIC ID Hashing: specifies consistent hashing based on QUIC IDs. Requests with the same QUIC ID are forwarded to the same backend server. Important QUIC is implemented based on draft-ietf-quic-transport-10 and iterates rapidly. Therefore, compatibility is not guaranteed for all QUIC versions. We recommend that you perform tests before you apply the protocol to a production environment. Weighted Least Connections: Requests are forwarded based on the weights and the number of connections to backend servers. If two backend servers have the same weight, the backend server that has fewer connections receives more requests. Note You can select the QUIC ID hashing algorithm only when the backend protocol is UDP.
   Resource Group	Select the resource group to which the server group belongs.
   Tag	Configure the Tag Key and Tag Value parameters.
   IPv6	Specify whether to enable IPv6. If you enable IPv6, you can add IPv4 and IPv6 backend servers to the server group. If you do not enable IPv6, you can add only IPv4 backend servers to the server group. Note If IPv6 is disabled for the VPC that you select for the server group, IPv6 is disabled for the server group by default.
   Connection Draining	Specify whether to enable connection draining. By default, connection draining is disabled. To enable connection draining, set the Connection Draining Timeout Period parameter. Valid values: 0 to 900. Unit: seconds. A value of 0 specifies immediate disconnection. When you remove a backend server or a backend server is declared unhealthy, connection draining is disabled by default. Existing connections remain open until the clients proactively close the connections or the session persistence duration ends. After you enable connection draining, existing connections remain open for data transmission until the connection draining timeout period ends. Connection draining ensures a smooth undeployment of services.
   Client IP Preservation	Specify whether to preserve client IP addresses. If client IP preservation is enabled, backend servers can retrieve client IP addresses. If client IP preservation is disabled, a backend server can work as a client to access your NLB instance. In this case, if you still want to retrieve client IP addresses, enable Proxy Protocol for the associated listener. Note You cannot enable client IP preservation for a server group of the IP type. If you want the server group to retrieve client IP addresses, enable Proxy Protocol for the associated listener.
   Enable All-port Forwarding	Specify whether to enable multi-port forwarding. After you enable multi-port forwarding, you do not need to specify a port when you add a backend server. The NLB instance forwards requests to a backend server based on the frontend port. Note If you enable all-port forwarding for your listener, you must enable this feature for the backend server group.
   Enable Health Check	Specify whether to enable health checks.
   Health Check Settings	After health checks are enabled, you can click Modify to modify health check settings.
   Health Check Protocol	Select a health check protocol. Valid values: TCP (default): To perform TCP health checks, NLB sends SYN packets to a backend server to check whether the port of the backend server can receive requests. HTTP: To perform HTTP health checks, NLB sends HEAD or GET requests to a backend server to check whether the backend server is healthy. UDP: To perform UDP health checks, NLB sends ICMP echo requests and UDP probe packets to check whether the backend server is healthy. Note You can set Health Check Protocol to UDP only if you set the backend server protocol to UDP.
   Health Check Method	Select an HTTP method that is used for health checks. Valid values: GET: If the size of a response exceeds 8 KB, the response is truncated. However, the results of the health check are not affected. HEAD: HTTP health checks use the HEAD method by default. Make sure that your backend servers support HEAD requests. If your backend server does not support the HEAD method or the HEAD method is disabled, the health check may fail. In this case, you can use the GET method. Note This parameter takes effect only if HTTP is specified as the health check protocol.
   Health Check Protocol Version	This parameter is available when Health Check Protocol is set to HTTP. Select HTTP1.0 (default) or HTTP1.1 based on the following guilelines: If applications deployed on backend servers support only HTTP/1.0, select HTTP1.0. If applications support only HTTP/1.1, select HTTP1.1. If applications support both HTTP/1.0 and HTTP/1.1, you can select either HTTP1.0 or HTTP1.1. If applications support only HTTP/1.0 and you set this parameter to HTTP1.1, or vice versa, health checks will fail.
   Health Check Port	Specify the ports that are probed by health checks. Backend Server Port: Health checks probe the ports of backend servers. This is the default setting. Custom Port: Health checks probe a specified port. Note If all-port forwarding is enabled, you must specify a specific health check port.
   Health Check Path	Enter the URL of the health check page. Note This parameter takes effect only if HTTP is specified as the health check protocol.
   Health Check Domain Name	Enter the domain name that is used for health checks. Backend Server Internal IP: NLB uses the private IP addresses of backend servers for health checks. This is the default value. Custom Domain Name: Enter a domain name. Note This parameter takes effect only if HTTP is specified as the health check protocol.
   Health Check Status Codes	Select one or more HTTP status codes that indicate that the health check is passed. Valid values: http_2xx (default), http_3xx, http_4xx, and http_5xx. Note This parameter takes effect only if HTTP is specified as the health check protocol.
   Custom Request/Response	You can turn on Custom Request/Response for UDP listener health checks. In the Custom Request field, enter custom request content, such as youraccountID. In the Custom Response field, enter custom response content, such as slb123. Meanwhile, you can add health check response logic to the business logic of the backend server. For example, you can configure the backend server to return slb123 when the backend server receives youraccountID. In this case, if the NLB instance receives the expected response, the backend server is declared healthy. Otherwise, the backend server is declared unhealthy. You can use this method to improve the accuracy of UDP health checks. Note This parameter takes effect only when you set the health check protocol to UDP.
   Response Timeout Period	Specify a timeout period for a health check response. If a backend server does not respond within the specified timeout period, the backend server is declared unhealthy.
   Health Check Interval	Specify the interval between two consecutive health checks. Note If you set Health Check Protocol to UDP, you must set the Health Check Interval parameter to a value that is equal to or larger than the response timeout period to ensure that UDP response timeouts are not determined as no responses.
   Healthy Threshold	Specify the number of times that an unhealthy backend server must consecutively pass the health check before it is declared healthy.
   Unhealthy Threshold	Specify the number of times that a healthy backend server must consecutively fail the health check before it is declared unhealthy.

Add backend servers by specifying ECS instances, ENIs, or elastic container instances

If you set the server group type to Server Type, you must add backend servers by specifying ECS instances, ENIs, or elastic container instances. You cannot add the same ECS instance, ENI, or elastic container instance to a server group for which all-port forwarding is enabled.

1. On the Server Groups page, find the server group that you want to manage, and use one of the following methods to go to the Backend Servers tab:

   • Click Modify Backend Server in the Actions column.

   • Click the ID of the server group. On the details page of the server group, click the Backend Servers tab.

2. On the Backend Servers tab, click Add Backend Server.

3. In the Add Backend Server panel, select a type of cloud service and click Next.

   • Select ECS/ENI for Server Type and select the ECS instances or ENIs that you want to add, or click Purchase ECS Instance in the upper-right corner of the instance list.

   • Note

     To use an ENI of an ECS instance, ensure that the ENI has been associated with the ECS instance. For more information, see Bind a secondary ENI. Turn on Advanced Mode, click the icon next to the ECS instance ID, and select the ENI.

   • Select ECI for Server Type and select the elastic container instances that you want to add, or click Purchase Elastic Container Instance in the upper-right corner of the instance list.

4. Specify the ports and weights of the backend servers and click OK.

   Note

   If multi-port forwarding is enabled for a server group, you do not need to specify a port when you add a backend server. NLB forwards requests to the backend server based on the frontend port.

   The default weight is 100. A server that has a higher weight receives more requests.

   You can move the pointer over the icon to change the weights and ports of multiple servers.

   • If you click Replicate to Below, the weights and ports of all servers below the current server are set to the weight and port of the current server.

   • If you click Replicate to Above, the weights and ports of all servers above the current server are set to the weight and port of the current server.

   • If you click Replicate to All, the weights and ports of all servers in the server group are set to the weight and port of the current server.

   • Reset:

     • If you click Reset next to Weight, the weights of all servers in the server group are reset to the default value.

     • If you click Reset next to Port, the ports of all servers in the server group are cleared.

   Warning

   If you set the weight of a server to 0, the server does not receive requests.

Add backend servers by specifying IP addresses

If you set the server group type to IP, you must add IP addresses to receive requests. You cannot add duplicate IP addresses to a server group which has all-port forwarding enabled.

1. On the Server Groups page, find the server group that you want to manage, and use one of the following methods to add IP addresses:

   • Click Modify Backend Server in the Actions column.

   • Click the ID of the server group.

2. On the details page of the server group, click the Backend Servers tab and click Add IP Address.

3. On the Select Servers tab of the Add Backend Server panel, enter an IP address and click Next.

   You can specify multiple ports for an IP address and specify a weight for each port.

4. On the Ports/Weights tab, specify the ports and weights of IP addresses, and then click OK.

   Note

   If multi-port forwarding is enabled for a server group, you do not need to specify a port when you add a backend server. NLB forwards requests to the backend server based on the frontend port.

   The default weight is 100. A server that has a higher weight receives more requests.

   You can move the pointer over the icon to change the weights and ports of multiple servers.

   • If you click Replicate to Below, the weights and ports of all servers below the current server are set to the weight and port of the current server.

   • If you click Replicate to Above, the weights and ports of all servers above the current server are set to the weight and port of the current server.

   • If you click Replicate to All, the weights and ports of all servers in the server group are set to the weight and port of the current server.

   • Reset:

     • If you click Reset next to Weight, the weights of all servers in the server group are reset to the default value.

     • If you click Reset next to Port, the ports of all servers in the server group are cleared.

   Warning

   If you set the weight of a server to 0, the server does not receive requests.

What to do next

References

• CreateServerGroup: creates a server group for an NLB instance.

• DeleteServerGroup: deletes a server group from an NLB instance.

• AddServersToServerGroup: adds backend servers to a server group of an NLB instance.

• RemoveServersFromServerGroup: removes backend servers from a server group of an NLB instance.

• UpdateServerGroupAttribute: updates the configurations of an NLB server group.