- CLB Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring a TCP Listener
- Configuring a UDP Listener
- Configuring a TCP SSL Listener
- Configuring an HTTP Listener
- Configuring an HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Configuring Layer-7 Redirection
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practise
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Queries CLB instances with high traffic under the current account
- DescribeTaskStatus
- Gets the CLB exclusive logset
- CreateClsLogSet
- CreateTopic
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- SetLoadBalancerSecurityGroups
- SetSecurityGroupForLoadbalancers
- ReplaceCertForLoadBalancers
- DescribeLoadBalancerListByCertId
- SetLoadBalancerClsLog
- DescribeQuota
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Announcements
- Service Level Agreement
- Glossary
- SDK Documents
- CLB Release Notes
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring a TCP Listener
- Configuring a UDP Listener
- Configuring a TCP SSL Listener
- Configuring an HTTP Listener
- Configuring an HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Configuring Layer-7 Redirection
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practise
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Queries CLB instances with high traffic under the current account
- DescribeTaskStatus
- Gets the CLB exclusive logset
- CreateClsLogSet
- CreateTopic
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- SetLoadBalancerSecurityGroups
- SetSecurityGroupForLoadbalancers
- ReplaceCertForLoadBalancers
- DescribeLoadBalancerListByCertId
- SetLoadBalancerClsLog
- DescribeQuota
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Announcements
- Service Level Agreement
- Glossary
- SDK Documents
After creating a classic CLB instance, you need to configure a listener for it. The listener listens to requests on the instance and distributes traffic to real servers based on the load balancing policy.
Prerequisites
You need to create a CLB instance first and select "Classic CLB" for Instance type.
Note：
Currently, there are two types of Tencent Cloud accounts: bill-by-EIP/CLB and bill-by-CVM. All Tencent Cloud accounts registered after June 17, 2020 00:00:00 are bill-by-EIP/CLB accounts. For Tencent Cloud accounts registered before June 17, 2020, check your account types in the console. Bill-by-EIP/CLB accounts no longer support classic CLB. You can now only purchase a CLB instance.
Configuring the Listener
Step 1. Open the Listener Management page
- Log in to the CLB Console.
- Select CLB Instance List on the left sidebar.
- On the Instance Management page, click the ID/Name of the instance to be configured to enter the instance details page.
- Select the Listener Management tab, or click Configure listener under the Operation column on the Instance Management page.
- The Listener Management page is as shown below.
Step 2. Configure a listener
Click Create under Listener Management and configure a TCP listener in the pop-up window.
1. Basic configuration
| Configuration Item | Description | Example |
|---|---|---|
| Name | Listener name. | test-tcp-80 |
| Listener Protocol and Ports | Listener protocol and listening port |
TCP:80 |
| Backend Port | The port through which the CVM instance provides services, receives and processes traffic from a CLB instance. | 80 |
To create a TCP listener, complete the basic configuration as shown below:
2. Advanced configuration
| Configuration Item | Description | Example |
|---|---|---|
| Balance Method | For TCP listeners, CLB supports two scheduling algorithms: weighted round robin (WRR) and weighted least-connection (WLC). |
WRR |
| Session Persistence | Whether to enable or disable session persistence. |
Enabled |
| Hold Time | Session persistence time. |
30s |
Complete the configuration as shown below:
3. Health check
| Configuration Item | Description | Example |
|---|---|---|
| Health Check | Whether to enable or disable health check. In TCP listeners, CLB instances send SYN packets to specified server ports to perform health checks. | Enabled |
| Check Protocol | To be added. | To be added |
| Check Port | To be added. | To be added |
| Response Timeout | 2s | |
| Check Interval | 5s | |
| Unhealthy Threshold | failure for n consecutive times (n is user-defined), the real server is unhealthy and the unhealthy status is displayed in the console. |
3 times |
| Healthy Threshold | success for n consecutive times (n is user-defined), the real server is healthy and the healthy status is displayed in the console. |
3 times |
Complete the health check configuration as shown below:
Step 3. Bind a real server
Click Bind on the Listener Management page and select the real server to be bound in the pop-up window, as shown below:
The configuration is as shown below:
Note：
If you configure multiple listeners to a classic CLB instance and bind multiple real servers, each listener will forward requests to all real servers based on its configuration.
Step 4. Security group (optional)
You can configure a CLB security group to isolate public network traffic. For more information, see Configuring a CLB Security Group.
Step 5. Modify or delete a listener (optional)
If you need to modify or delete an existing listener, select the listener on the Listener Management page and click Modify or Delete.
Was this page helpful?