Azure Arm (one) Arm mode, create virtual machines and configure the load balancer

Windows Azure Platform Family of articles Catalog

　　This article is more content, please read carefully, thank you!

In the first few chapters, we did the preparatory work:

1. Create Arm resouce Group, called Leiresourcegroup

2. Create Arm Storage account, called Leistorageaccount

3. Create arm Virtual Network, called Leiarmvnet

In this chapter, I will show you how to create VM VMs in arm mode. It is mainly divided into the following steps:

1. Creating the first arm VM Leiarmweb01,azure will automatically create a network card NIC. We can make this arm VM have a fixed pip address, Remember to set availability set

2. Quickly create a 2nd arm VM LeiARMWeb02, remembering to set availability set

3. Create a load balancer. Load Balancer,load Balancer is level 4.

4. Join the 2 VMS behind this load balancer

5. Set the Load Balancer's

6. Set the Snat of the load balancer

　　Start with the first part of the content and create the first Azure RM.

1. Sign in to Azure ARM Portal: http://portal.azure.cn, select New, and then click Virtual Machines. Such as:

If you need to select additional VM template templates, select the See all

　　

　

2.DEPLOYMENBT Model, select Resource Manager

　　

　　

3. First set up the user name and password for the Azure VM. The VM disk type can choose HDD, the normal SAS disk. Select SSD If you require an all-solid-state drive.

　　

4. Then we set the virtual machine size. Choose STANDARD_A1 here. If you want to select a different VM Size, select the View all

　　

5. Then set up the storage account and virtual network where the virtual machine resides.

　　Remember to set availability set, Remember to set availability set, and remember to set availability.

　　

Note: We do not have a PIP for the virtual machine, and unlike ASM mode virtual machines, the virtual machines in arm mode can set a fixed pip address. Such as:

　　

Note that we must also set the high availability set for the virtual machine (availability set). Such as:

　　

The update domain is 5, up to 20. The maximum fault domain is 3.

　　

6. Finally confirm the creation of the virtual machine, entries.

7. Once created, we can see that the following Azure arm resources have been created.

(1) Create a new arm virtual machine LEIARMWEB01

(2) Automatic creation of new arm NIC NICs leiarmweb01953

(3) Create a new network Security GROUP:LEIARMWEB01-NSG

(4) Create a new high-availability set: Web-avbset

　　

　　

　　In the second part, we quickly create a 2nd Azure VM named LEIARMWEB02.

　　Remember to set availability set, Remember to set availability set, and remember to set availability.

　

After creating the 2nd Azure VM, create a new resource as follows:

(1) Create a new Azure virtual machine: LEIARMWEB02

(2) Create a new Azure virtual machine NIC

(3) Create a new network Security GROUP:LEIARMWEB02-NSG

　　The third part: Create a Load balancer. Load Balancer, loadBalancer is level 4.

1. We chose to create the load Balancer

　　

2. When creating Azure Load balancer, set the name of this lb and bind the fixed public IP address for this LB

　　

　　

　　

　Part IV, before we created the load Balancer for Web server 01 and Web Server 02, and the front end is irrelevant. Now we're associating these 2 VMS with load balancer balancer

We now bind 2 Azure virtual machines to this azure Load balancer.

1. Before we click Create Leiarmloadbalancer, select backend pools. Such as:

　　

, we click on "Choose an availability set" to select a high-availability set of the previous 2 Web VMS

　　

Setup is complete, such as:

　　

　　In part V, we need to set up the load balancer to the backend Web Server Listener (Probe), and the load balancer will not send traffic to this Web server when there is a problem with the backend Web server.

We clicked Settings,probes, and added the Listener (Probe). In the Red section, we add rules for 80 ports, send a listen request every 5 seconds, 3 failures in a row (total 15 seconds), set the state of this Web server to be unstable, and the load balancer will not send traffic to the Web server

　　

　

　　Part six, we're going to set the rules for the load balancer.

In the previous article, I introduced the load Balancer rules for the five-tuple or two-tuple.

　　Azure PowerShell (8) Set up Azure load balancer rules with PowerShell

　　

We'll show you how to set the rules for 80-port load balancer in arm mode. Such as:

　　

　　

, we can also load balancer rules for five-tuple or two-tuple, such as:

　　

In

(1) None, indicating that the session is not preserved

(2) Client IP, which indicates that the session is retained based on the IP address

(3) Client IP and Protocol, which indicates that the session is retained according to the IP address + protocol

Once our load balancer for 80 ports is set, the schema is as follows:

　　

　

　　Finally, we can also set up port forwarding for a single virtual machine through a load balancer.

We select the inbound NAT Rule, click Add, then select the desired virtual machine, then set the service and Port,target Port

　　

　　

That way, with the load Balancer + port number (in port:60021), we can access the RDP port of the LeiARMWeb01 behind the load balancer 3389

Azure Arm (one) Arm mode, create virtual machines and configure the load balancer