This topic describes how to add a TCP listener to a Classic Load Balancer (CLB) instance. TCP allows you to transmit data in a reliable and accurate manner but at relatively low speeds. Therefore, you can use TCP to transfer files, send or receive emails, and perform remote logons. You can add a TCP listener to forward TCP requests.
A CLB instance is created. For more information, see Create and manage a CLB instance.
Step 1: Configure a TCP listener
- Log on to the CLB console.
- In the top navigation bar, select the region where the CLB instance is deployed.
- Use one of the following methods to open the listener configuration wizard:
- On the Instances page, find the CLB instance and click Configure Listener in the Actions column.
- On the Instances page, find the CLB instance that you want to manage and click the ID of the instance. On the Listener tab, click Add Listener.
- Set the following parameters and click Next.
Parameter Description Select Listener Protocol Select TCP. Listening Port Set the listening port that is used to receive requests and forward them to backend servers. Valid values: 1 to 65535. Listener Name Specify a name for the listener. Advanced Click Modify to configure advanced settings. Scheduling Algorithm Select a scheduling algorithm.
- Weighted Round-Robin (WRR): Backend servers that have higher weights receive more requests than backend servers that have lower weights.
- Round-Robin (RR): Requests are distributed to backend servers in sequence.
- Consistent Hash (CH):
Note Only high-performance CLB instances support the CH algorithm.
- Tuple: specifies consistent hashing that is based on four factors: source IP address, destination IP address, source port, and destination port. Requests that contain the same information based on the four factors are distributed to the same backend server.
- Source IP: specifies consistent hashing that is based on source IP addresses. Requests from the same source IP address are distributed to the same backend server.
Enable Session Persistence Specify whether to enable session persistence.
After session persistence is enabled, CLB forwards all requests from a client to the same backend server.
For TCP listeners, session persistence is implemented based on IP addresses. Requests from the same IP address are forwarded to the same backend server.
Enable Access Control Specify whether to enable access control.
Select an access control method after you enable access control. Then, select an access control list (ACL) that is used as the whitelist or blacklist of the listener.Note IPv6 instances can be associated only with IPv6 ACLs, while IPv4 instances can be associated only with IPv4 ACLs. For more information, see Create an access control list.
Enable Peak Bandwidth Limit
Specify whether to set the bandwidth limit of the listener.
If a CLB instance is billed based on bandwidth usage, you can set different maximum bandwidth values for different listeners. This limits the amount of traffic that flows through each listener. The sum of the maximum bandwidth values of all listeners that are added to a CLB instance cannot exceed the maximum bandwidth value of the CLB instance. By default, this feature is disabled and all listeners share the bandwidth of the CLB instance.Note If a CLB instance is billed based on data transfer, the bandwidth of its listeners is not limited by default.
Idle Timeout Specify the timeout period of idle TCP connections. Unit: seconds. Valid values: 10 to 900. Proxy Protocol Use the proxy protocol to pass client IP addresses to backend servers.Note You cannot enable this feature in scenarios where PrivateLink is used. Obtain Client Source IP Address Specify whether to retrieve the real IP addresses of clients. Only Layer 4 listeners support this feature. By default, this feature is enabled. Automatically Enable Listener After Creation Specify whether to immediately enable the listener after it is created. By default, listeners are enabled after they are created.
Step 2: Add backend servers
After you configure the listener, you must add backend servers to process client requests. You can use the default server group that is configured for the CLB instance. You can also configure a vServer group or a primary/secondary server group, or enable the primary/secondary mode for the listener. For more information, see Backend server overview.
- On the Backend Servers wizard page, select the type of the server group to which requests are forwarded.
The default server group is used in this example.
Select Default Server Group and click Add More.
- In the My Servers panel, select the ECS instances that you want to add as backend servers and click Next.
- On the Configure Ports and Weights wizard page, specify the weights of the backend servers that you added. A backend
server with a higher weight receives more requests. Note If the weight of a backend server is set to 0, no request is distributed to the backend server.
- Click Add. On the Default Server Group tab, specify the ports that you want to open on the
backend servers to receive requests. The backend servers are the ECS instances that
you selected. Valid values: 1 to 65535.
You can specify the same port on different backend servers that are added to a CLB instance.
- Click Next.
Step 3: Configure health checks
CLB performs health checks to check the availability of the ECS instances that serve as backend servers. The health check feature improves overall service availability and reduces the impact of backend server failures.
On the Health Check wizard page, click Modify to modify the health check configurations. For more information, see Configure health check.
Step 4: Submit the configurations
- On the Confirm wizard page, check the configurations. You can click Modify to modify the configurations.
- After you confirm the configurations, click Submit.
- When Configuration Successful appears, click OK.
After you configure the listener, you can view the listener on the Listener tab.