Load Balance Dedicated Cluster
The load balancer dedicated cluster offers reliable load balancing services with guaranteed performance, exclusive resources, and isolated physical resources to meet ultra-high performance and exclusive requirements.
The load balance dedicated cluster uses dedicated physical servers to achieve hard isolation at the network resource level. Users can apply to create multiple exclusive dedicated clusters for different business departments, enabling each department to productively create load balancer instances on their corresponding dedicated clusters. If you need to use it, submit an application.
Create a dedicated cluster
- Log in to the Baidu AI Cloud Platform, go to Product Services > Baidu Load Balancer (BLB) > BLB Dedicated Cluster, and access the BLB Dedicated Cluster List page.
- Click the Create Dedicated Cluster button to open the interface for creating a new dedicated cluster.
- Enter the required configuration details.
| ConfigMap | Description |
|---|---|
| Bill type | Support Prepay only |
| Current region | Support Beijing, Baoding, Guangzhou, Suzhou, Wuhan, Shanghai, Hong Kong, Yangquan, Chengdu, Nanjing. Switch via the top-left Region |
| Dedicated cluster name | User-defined BLB dedicated cluster name |
| Cluster type | Select the cluster type, supporting Layer 4 or Layer 7 |
| Performance capacity | Select the count of CCUs. The performance capacity unit CCU is used to measure various metrics involved in BLB cluster traffic processing. The dedicated cluster adopts a mutual primary-backup disaster recovery architecture between computer rooms. The purchased CCU represents the sum of the performance of the mutually primary-backup computer rooms |
| Description | Edit the description information related to the BLB dedicated cluster |
| Purchase period | Select purchase period |
| Auto-renewal | Auto-renewal when enabled |
Cluster performance capacity parameters for 1 CCU:
- Layer 4 cluster: Supports up to 80 million concurrent connections, new connection rates of 12 million, inbound bandwidth of 120Gbps, and outbound bandwidth of 120Gbps.
- Layer 7 cluster: Supports up to 2 million concurrent connections, new HTTP connection speeds of 1.2 million, new HTTPS connection rates of 224,000, inbound bandwidth of 40Gbps, outbound bandwidth of 40Gbps, HTTP QPS of 1.2 million, and HTTPS QPS of 224,000.
- Verify the configuration details and follow the system prompts to complete the order confirmation and payment.
- Once you submit the request to create a dedicated load balancer cluster, Baidu AI Cloud staff will review your configuration details within 1-3 business days. Upon approval, the setup process will commence, and you will receive an SMS notification when it is completed.

Upgrade of dedicated cluster
- To upgrade a dedicated load balancer cluster, click the Cluster Upgrade button, select the desired performance capacity configuration, and click Next to confirm the order and make the payment.
- After making the payment, Baidu AI Cloud staff will review the submitted upgrade details within 1-3 business days. Upon approval, the upgrade process for the dedicated load balancer cluster will begin, and you will receive an SMS notification upon completion.

Manage BLB instances
BLB instance selection target cluster
- Log in to the Baidu AI Cloud Platform, navigate to Product Services > Baidu Load Balancer (BLB) > BLB Instances, and access the BLB Instance List page.
- Click "Create Load Balancer" to open the Create Load Balancer interface.
- Choose the target cluster and the active-standby mode.
Description:
- If both Layer-4 and Layer-7 clusters are dedicated clusters, no charges will be incurred for the BLB instance.

Changing the active-standby mode of a BLB instance
Click on the BLB instance name to enter the details page. Under the Basic Information section of the BLB details page, you can click to modify the active-standby mode, allowing a switch between the active-standby mode and the dual-active mode.
Notes Changing the active-standby mode affects both long and short links to the BLB. The duration is approximately the listener's health check interval * health threshold. Retries can restore access later. To minimize migration damage time, you can reduce the settings of the above two parameters.

BLB instance migration target cluster
Click on the BLB instance name to enter the details page. Under the Basic Information section of the BLB details page, you can click "Migrate Cluster" to enable migration from a shared cluster to a dedicated cluster, from a dedicated cluster to a shared cluster, or between dedicated clusters.
Note:
The migration process may cause brief traffic interruptions. Please proceed cautiously.

New BLB instance switch
Click the cluster name to access the details page and configure the switch for new BLB instance creation. This is enabled by default. If disabled, the dedicated load balancing cluster will no longer allow new BLB instances to be created.

View associated BLB instances
Click the cluster name to enter the details page, select "Associated BLB Instance" in the left navigation bar, and navigate to the Associated BLB Instance List page to view information on BLB instances linked to the dedicated cluster.

View monitor data
- Click the cluster name to enter the details page, select "Monitor" from the left navigation bar, and open the Monitor page to view monitoring and water level details of the dedicated cluster.
- Click Alarm Details on the Monitor page to enter the alarm policy configuration page, where you can manage the alarm strategy of the load balance dedicated cluster. For detailed operation steps, please see BCM Alarm Management.
Load balance dedicated clusters support TOPN statistic
TOPN: After specifying the time range, statistical method, and metric, enable the TOP display feature and click the Refresh button in the top-left corner. The system will automatically display the top 10 BLB instance IDs ranked by traffic proportion based on your selections.
Statistical methods include: Average, Maximum, Minimum, Sum.
- Layer 4 Load Balancer metrics: Health check (count), network traffic (bytes), network packets (count), concurrent connections (count), traffic dropped (bytes/minute), packets dropped (count/minute), connections dropped (count/minute), new connections (count/minute), network inbound bandwidth (bps), network outbound bandwidth (bps), rate-limited traffic (bytes), rate-limited packets (count)
- Layer 7 Load Balancer metrics: Health check (count), request count (count/minute), network traffic (bytes), network packets (count), concurrent connections (counts), traffic dropped (bytes/minute), packets dropped (count/minute), connections dropped (count/minute), new connections (counts/minute), response time (ms), response status codes (counts/minute), response status code ratio (percentage), real server response status codes (count/minute), real server response time (ms), network inbound bandwidth (bps), network outbound bandwidth (bps), queries per second (count), rate-limited traffic (bytes), rate-limited packets (count), QPS usage (percentage)
Log in to the Baidu AI Cloud Management Console, go to Product Services > Network > Baidu Load Balancer (BLB). From the left navigation bar, select the BLB dedicated cluster, click on the cluster name, choose "Monitor" from the left navigation bar, and review the "BLB Instance Monitor Information."
Description:
- At present, the TOPN function is in the public beta stage. If you need to use it, please submit a Ticket application.
- The BLB dedicated cluster instance status is "Available";
- Network traffic must pass through the BLB dedicated cluster;
- After clicking the Refresh button, there may be a delay before the Traffic Graph appears. Please wait approximately three minutes for it to load.
- Data should be available within the past three days, and the maximum query time span is 30 days.
- The system supports three time selection methods: 1. Query time range less than 1 hour (1–59 minutes): For example, if you initiate a query at 20:00, only data from 18:56 to 19:55 can be queried. 2. Query time range of more than 1 hour: Query time must be an integer multiple of 1 hour, ranging from 1 to 12 hours. For example, if you query at 20:00 with a range between 1 and 12 hours, only data before 19:00 will be available. 3. For ranges over 1 hour that are not whole multiples, you can query up to an hour's data combined with a range of less than 1 hour (1–59 minutes).
