Mixed use of Azure LB and ILB to access the same web service (3)

Next, let's configure Azure Load balancer, which is a public network-oriented load balancer:

1. In this test, in order to maintain the same experience of private network access and public network access, the local port and public port are the same as ILB, which is 80:

PS C:\ > Get-AzureVM-ServiceName webstevennodes-Name webstevennode1 | Add-AzureEndpoint-Name httppub-Protocol tcp-LocalPort 80-PublicPort 80-DefaultProbe-LBSetName myPubLBSet | Update-AzureVM

two。 After the configuration is completed, we will also check the current endpoint configuration information. We can see that the configuration of ILB and PubLB is successful:

3. On the Azure management interface, we check the endpoint configuration of the next two test VM, and we can see that the endpoint configuration of the public network just configured is displayed on the portal:

4. So let's test whether AzureLB is working through the public network. Open the browser and enter the DNS address to enter. You can see that the request has been distributed to VM2. In a few minutes, change the browser and test it. You can see that the request has been distributed to VM1:

6. In retrospect, let's test whether Internal Load balancer is still working, and we can see that ILB is working:

7. Finally, we are testing the last scenario. We know that Azure's load balancer has probe, which automatically detects whether the distributed virtual machine is healthy, and then distributes the request to the healthy virtual machine. In the following test, we turn off VM1 to see if the load balancer can correctly distribute the request to the healthy virtual machine:

Use LB and ILB to access the service, respectively, and all requests are distributed to the running virtual machine VM2, which works: