The IPv6 CLB is in beta test. To try it out, submit a ticket.
Currently, IPv6 CLBs are available in the following regions: Guangzhou, Shenzhen Finance, Shanghai, Shanghai Finance, Nanjing, Beijing, Beijing Finance, Chengdu, Chongqing, Hong Kong (China), Singapore, Virginia, and São Paulo. Due to compliance requirements, you need to submit a ticket to open Shenzhen Finance and Shanghai Finance regions. IPv6 CLB does not support classic CLB.
IPv6 load balancing does not support conventional load balancing.
IPv6 load balancing facilitates the acquisition of the client's IPv6 source address. Both four-layer and seven-layer protocols inherently transmit the client's source address from the IPv6 load balancer. Additionally, the seven-layer IPv6 load balancer supports the retrieval of the client's IPv6 source address via the HTTP's X-Forwarded-For header field.
Currently, IPv6 CLB balances the load completely over a public network. Clients in the same VPC cannot access IPv6 CLB over a private network.
IPv6 implementations are still at the preliminary stage across the internet. In case of access failure, submit a ticket. SLA is not guaranteed during the beta test period.
Overview
IPv6 load balancing is implemented based on the IPv6 single stack technology. It can collaborate with IPv4 CLB to implement IPv6/IPv4 dual-stack communication. An IPv6 CLB instance is bound to an IPv6 address of a CVM instance and provides an IPv6 VIP address.
IPv6 CLB Advantages
Tencent Cloud IPv6 CLB has the following advantages when helping your business quickly connect to IPv6:
Quick connection: CLB enables connection to IPv6 within seconds and is available upon purchase.
Ease of use: IPv6 CLB is compatible with IPv4 CLB flowchart and easy to use with no additional learning costs incurred.
End-to-end IPv6 communication: IPv6 CLB instances communicate with CVM instances over IPv6, which helps applications deployed on the CVM instances quickly upgrade to IPv6 and implement end-to-end IPv6 communication.
IPv6 CLB Architecture
CLB supports creating IPv6 CLB instances. Tencent Cloud will assign an IPv6 public IP address, i.e., VIP of the IPv6 edition, to an IPv6 CLB instance, and the VIP will forward requests from IPv6 clients to the real IPv6 CVM instance.
An IPv6 CLB instance can support quick access of users from IPv6 public network and communicate with real servers over IPv6, which helps in-cloud applications quickly upgrade to IPv6 and implement end-to-end IPv6 communication.
The IPv6 CLB architecture is as shown below:
Step 1. Create an IPv6 CLB instance
1. Log in to the Tencent Cloud console and go to the CLB purchase page.
2. Select the following CLB configuration items as needed:
Bill-by-IP account
Parameter
Description
Billing mode
Supports pay-as-you-go billing. IPv6 CLB is supported only in pay-as-you-go mode. For other restrictions, see IP Versions.
Region
Select a region. For more information on the regions supported by CLB, see Region List.
Instance type
Supports the CLB instance type only. Starting from October 20, 2021, classic CLB instances can no longer be purchased. For more information, see Classic CLB End-of-Sale Notice.
Network type
Supports two network types: public network and private network. For more information, see Network Types. Select the public network type for IPv6 CLB.
EIP
Don't select an EIP.
IP version
Select the IPv6 version.
Network
Select an existing VPC or subnet. If the existing networks are inapplicable, you can create a VPC or create a subnet as required.
ISP
Select Multi-line BGP.
Instance specification
Supports shared and LCU-supported instances.
Shared instances guarantee performance according to their specifications. A single instance can sustain up to 50,000 concurrent connections, 5,000 new connections per second, and 5,000 queries per second.
An LCU-supported instances provide guaranteed performance according to specifications. A single instance can sustain up to Ten million concurrent connections, 1 million new connections per second, and 300,000 queries per second.
Dual-stack binding
After this feature is enabled, the layer-7 listener can be bound with both IPv4 and IPv6 backend servers. But layer-4 listeners only support binding of IPv6 backend server.
Network billing mode
Supports bill by traffic and bill by bandwidth package.
Bandwidth cap
The public network bandwidth cap of a shared CLB is 2 Gbps. For the private network bandwidth cap, it's suggested to set a value within 5 Gbps.
The bandwidth cap of an LCU-supported CLB instance depends on the selected specification. For details, see Instance Specifications Comparison.
The name can contain up to 60 characters, including letters, numbers, hyphens, underscores, and dots. If it is not specified, a name will be automatically generated by default.
Select a region. For more information on the regions supported by CLB, see Region List.
Instance type
Supports the CLB instance type only. Starting from October 20, 2021, classic CLB instances can no longer be purchased. For more information, see Classic CLB End-of-Sale Notice.
Network type
Supports two network types: public network and private network. For more information, see Network Types.
Public network: CLB is used to distribute requests from a public network.
Private network: CLB is used to distribute requests from the Tencent Cloud private network. A private network instance does not support the following configuration items, and therefore they are not displayed by default: IP version, ISP, and instance specification.
IP version
Select IPv6. For more information on the use limits, see IP Versions.
Network
CLB supports classic network and VPC.
The classic network is a public network resource pool for all Tencent Cloud users. The private IPs of all CVMs are assigned by Tencent Cloud. You cannot customize IP ranges or IP addresses.
A VPC is a logically isolated network space in Tencent Cloud. In a VPC, you can customize IP ranges, IP addresses, and routing policies.
A VPC is more suitable for use cases requiring custom configurations. Besides, the overall classic network products were officially discontinued on December 31, 2022. For details, see Ending Support for Classic Network. We recommend you choose a VPC.
ISP
Select Multi-line BGP.
Instance specification
Supports shared and LCU-supported instances.
Shared instances guarantee performance according to their specifications. A single instance can sustain up to 50,000 concurrent connections, 5,000 new connections per second, and 5,000 queries per second.
An LCU-supported instances provide guaranteed performance according to specifications. A single instance can sustain up to Ten million concurrent connections, 1 million new connections per second, and 300,000 queries per second.
The name can contain up to 60 characters, including letters, numbers, hyphens, underscores, and dots. If it is not specified, a name will be automatically generated by default.
3. After configuring the above items, click Buy now. In the "CLB order confirmation" pop-up window, click Confirm order. Then, return to the Instance Management page where you can view the IPv6 CLB instance you just purchased.
Step 2. Create an IPv6 CLB listener
1. Log in to the CLB console and click the IPv6 CLB instance ID to go to the details page.
2. Select the Listener management tab and click Create. For example, create a TCP listener.
Note:
CLB supports creating layer-4 (TCP/UDP/TCP SSL) and layer-7 (HTTP/HTTPS) IPv6 CLB listeners. For more information, see CLB Listener Overview.
3. In Basic configuration, configure the name, listening protocol and port, and balancing method, and click Next.
4. Configure health check and click Next.
5. Configure session persistence and click Submit.
6. After the listener is created, select it and click Bind on the right.
Note:
Before binding the listener to a CVM instance, make sure that the CVM instance has obtained an IPv6 address.
7. In the pop-up window, select the target IPv6 CVM instance, configure the server ports and their weights, and click OK.
More Operations
Binding IPv6 CLB with both IPv6 and IPv4 real servers
After enabling the dual-stack binding, the IPv6 CLB layer-7 listener can be bound with both IPv4 and IPv6 backend servers, and can obtain the source IP via XFF. But layer-4 listeners only support binding of IPv6 backend server.
1. Enable dual-stack binding.
Enable dual-stack binding when purchasing IPv6 CLB on the purchase page.
Enable dual-stack binding on the IPv6 CLB instance details page.
2. Create a layer-7 HTTP or HTTPS listener.
3. Bind the listener with a IPv6 or IPv4 real server.
Yes
No
Was this page helpful?