Distribute Layer 4 or Layer 7 traffic to ECS through CLB

Prepare resources and environment

three

Resource requirements

Deploying the CLB load balancing service requires one CLB instance and two ECS instances, and the CLB instance and ECS instance belong to the same region.

Get free benefits

Enter the following resource collection portal and click Login/Registration Button, and complete account login (existing AliCloud account), account registration (no AliCloud account), or real name authentication (personal real name authentication or enterprise real name authentication according to the requirements of the trial product) according to the page prompts.

If you Existing corresponding resources , you may not receive free benefits, please go directly to the next step Check Resources 。

Deploy application

three

1. Sign in ECS Console 。

2. In the upper left corner of the top menu bar, select the same region as ECS 01 and ECS 02 instances.

3. Set ECS 01 and ECS 02 instance login passwords. Click in the Action column >Instance Properties>Reset Instance Password , set the login password of the ECS instance according to the interface prompts. After saving the password, on the pop-up page, click Restart Now Make the password effective.

   Resetting the instance password is supported about 3-5 minutes after the instance creation is completed. If it cannot be reset, please wait patiently and try again.

4. Connect ECS 01 and ECS 02 instances remotely.

   1. return example Page, click Remote connection 。

   2. In the pop-up connection and command dialog box, click Connect remotely through Workbench Corresponding Sign in now 。

   3. In the pop-up login instance dialog box, enter the login information.

5. Execute the following commands to deploy the Nginx static page for the ECS 01 instance. The following command takes CentOS 7.9 64 bit operating system as an example.

   yum install -y nginx

   systemctl start nginx.service

   cd /usr/share/nginx/html/

   echo "Hello World ! This is ECS01." > index.html

6. Execute the following commands to deploy the Nginx static page for the ECS 02 instance. The following command takes CentOS 7.9 64 bit operating system as an example.

   yum install -y nginx

   systemctl start nginx.service

   cd /usr/share/nginx/html/

   echo "Hello World ! This is ECS02." > index.html

Configure CLB listening

seven

Configure Layer 4 Monitoring

1. Sign in Traditional load balancing CLB console 。

2. In the top menu bar, select the region where the CLB instance belongs. Selection of this article East China 1 (Hangzhou) 。

3. stay Instance management Page, click the created CLB instance ID.

   After receiving the free trial benefits of CLB, the system will automatically create a CLB instance for you. It usually takes 1~3 minutes to create a CLB instance. Please wait patiently. When the instance status changes to In operation The CLB instance creation is completed.

4. single click monitor Tab, in monitor Tab Click Add listening 。

5. stay Protocol&Listening The configuration wizard completes the configuration of the following main parameters. The remaining parameters remain in the default configuration, and then click next step 。

   Listening configuration	explain	Sample value
   Select a load balancing protocol	Select the protocol type to listen to.	TCP
   Listening port	Set the front-end protocol port, that is, the listening port used to receive requests and forward requests to the back-end server. Listening port range: 1~65535.	eighty
   Listening name	The name of the custom listener.	TCP_80

6. stay Back-end server Configuration wizard, selecting Default Server Group , and then click Continue adding 。

   1. stay Select Server In the configuration wizard, select the created ECS01 and ECS02 instances, and then click next step 。

   2. stay Configure Ports and Weights Configuration wizard, keep the default configuration, click add to 。

   3. Enter the ports of ECS01 and ECS02. In this tutorial, set them to 80, and then click next step 。

7. stay Health Check Configuration Wizard, keep the default configuration, click next step , and then click Submit 。 After the configuration is successful, click got it 。

Configure Layer 7 monitoring

1. stay monitor Tab Click Add listening 。

2. stay Protocol&Listening The configuration wizard completes the configuration of the following main parameters. The remaining parameters remain in the default configuration, and then click next step 。

   Listening configuration	explain	Sample value
   Select a load balancing protocol	Select the protocol type to listen to.	HTTP
   Listening port	Set the front-end protocol port, that is, the listening port used to receive requests and forward requests to the back-end server. Listening port range: 1~65535.	eighty-one
   Listening name	The name of the custom listener.	HTTP_81

3. stay Back-end server Configuration wizard, selecting Default Server Group , you can see the added ECS01 and ECS02.

4. Enter the ports of ECS01 and ECS02. In this tutorial, set them to 80, and then click next step 。

5. stay Health Check Configuration Wizard, keep the default configuration, click next step , and then click Submit 。 After the configuration is successful, click got it 。

complete

five

Verifying Layer 7 Load Balancing

After creating a CLB instance and configuring Layer 7 monitoring, you can test whether the CLB instance distributes requests to the back-end ECS through the following methods, and simulate the ECS single point of failure scenario to verify the high availability of the business.

1. Sign in Traditional load balancing CLB console , at CLB Instance management Page, on Service address Column to view and copy the public network service address of the CLB instance.

2. Enter the public service address of the CLB instance in the browser http://120.XX.XX.50:81 To verify the CLB's 7-layer load balancing forwarding capability.

   Refresh the browser, and you can observe that the request is converted between two ECSs.

   The above verification process shows that CLB can distribute client traffic to different back-end servers.

   

   

Verifying Layer 4 Load Balancing

After creating a CLB instance and configuring Layer 4 monitoring, you can test whether the CLB instance distributes the request to the back-end ECS through the following methods, and simulate the ECS single point of failure scenario to verify the high availability of the business.

1. Sign in Traditional load balancing CLB console , at CLB Instance management Page, on Service address Column to view and copy the public network service address of the CLB instance.

2. Enter the public service address of the CLB instance in the browser http://120.XX.XX.50 You can observe that the request has been forwarded to a backend ECS server. The following operations take ECS01 as an example.

   1. Deactivate ECS01, refresh the public service address of the browser accessing the CLB instance, and you can observe that the request has been forwarded to ECS02.

   2. start-up ECS01 and wait for a few minutes.

   3. Deactivate ECS02, refresh the public service address of the browser accessing the CLB instance, and observe that the request has been forwarded to ECS01.

   The above verification process shows that when a single back-end server fails, CLB can still ensure service availability.

   

   

Cleaning and follow-up

two

clear

1. The free trial rights of CLB are limited in duration, and CLB instances that are not released after the expiration of the rights may incur costs. After completing the tutorial, refer to the following scenarios to process CLB instances:

   • If you do not need to use the CLB instance, you can log in Traditional load balancing CLB console ， In the left navigation bar, select Traditional load balancing CLB (original SLB) > Instance management , on Instance management Page, find the target CLB instance in the operation Column Click > Release Settings , manually release the instance according to the interface prompts.

   • If you need to continue using the CLB instance, please recharge your AliCloud account at least one hour before the trial expires to ensure that the account amount is not less than 100.00 yuan. The CLB instance that has not been renewed upon expiration will be automatically stopped due to arrears. The CLB instance will be retained within 7 days of downtime, and the CLB instance and data will be automatically released after 7 days.

2. This tutorial uses a personal ECS instance, which defaults to pay as you go instances. After completing the tutorial, please refer to the following scenarios to process ECS instances:

   • If you do not need to continue using the instance, you can Log in to the ECS console , find the target instance, and click in the operation column , search and click Release Settings , release the instance according to the interface prompt.

   • If you need to continue using the instance, please recharge your AliCloud account at least one hour before the trial expires to ensure that the account amount is not less than 100.00 yuan. Instances that have not been renewed upon expiration will be automatically shut down due to arrears. The instance will be retained within 15 days of downtime, and the instance and data will be automatically released after 15 days.

follow-up

During the probation period, you can continue to use traditional load balancing CLB products according to other business scenarios you want to test. For CLB related tutorials, see CLB Tutorial 。