Hybrid access to the same Web service using azure lb and ILB (2)

now, let's start by configuring the Internal for the next two Web servers. Load balancer:

1. Open Powershell , check the endpoint configuration for the current two virtual machines:

Get-azurevm-servicename Webstevennodes-name webstevennode2| Get-azureendpoint

2. Create an ILBthat specifies its service address as the intranet address 10.0.0.88:

Add-azureinternalloadbalancer-internalloadbalancername myilb-servicename Webstevennodes-subnetname Subnet-1- Staticvnetipaddress 10.0.0.88

3. Add endpoint information to both test VMS webstevennode1 and webstevennode2, noting that both the local port and the external port are 80:

PS c:\> get-azurevm-servicename webstevennodes-name webstevennode1 | Add-azureendpoint-name httpinternal-protocol tcp-localport 80-publicport 80-defaultprobe-internalloadbalancername m Yilb-lbsetname myilbset| Update-azurevm

PS c:\> get-azurevm-servicename webstevennodes-name webstevennode2| Add-azureendpoint-name httpinternal-protocol tcp-localport 80-publicport 80-defaultprobe-internalloadbalancername m Yilb-lbsetname myilbset| Update-azurevm

4. Once the add is complete, verify the endpoint configuration information:

PS c:\> get-azurevm-servicename webstevennodes-name webstevennode2| Get-azureendpoint

Get-azurevm-servicename Webstevennodes-name webstevennode2| Get-azureendpoint

You can see that the ILB configuration for the computer's two VMs is complete, and the service IP address is 10.0.0.88.

5. To test the actual effect, you need to login to the test Windows 2012 virtual machine, open IE browser, enter the ILB service address 10.0.0.88, test:

After a few more refreshes, you can see that the request can be distributed to VM1 and VM2:

6. We check the endpoint configuration on the portal of Azure, and we can see that because we are configuring the ILB port, we are not currently seeing it on the Portal:

Hybrid access to the same Web service using azure lb and ILB (2)