Azure multi-nic virtual machine

Virtual machines in Azure now support multiple network card (NIC) configurations, but there are a few things to note when you want to use multi-NIC virtual machines-First, a multi-NIC virtual machine that cannot be used as a three-tier (IP) gateway because traffic cannot be forwarded. The second is that a virtual machine that is not full size (size) can support multiple network adapters, except for basic specifications, with only the following support:

Large (A3) and the A6 : 2 a

Ultra-Large (A4) and the A7 : 4 a

A9 : 2 each

D3 : 2 each

D4 : 4 each

D13 : 4 each

Also note that the multi-card virtual machine must be in the virtual network, and the VIP address will only be mapped to the default network card, other details can be seen in the Microsoft Azure official website, below to see how to use multi-NIC Azure virtual machine.

##################################################################################

First you want to have a virtual network, as well as the necessary subnets, the specific configuration of the subnet to see the requirements, generally speaking, multi-network card virtual machine needs to divert traffic, such as using a separate NIC to communicate with the backend data, the default NIC to receive external access, this is a more typical scenario, In my Azure subscription I created a virtual network called "Sstpvnet", then there were two subnets "outbound" and "inbound", and they each had a 172.16.10.0/28 subnet address, such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6B/E2/wKiom1U4xnjBBZ1JAAKreXkBmMI875.jpg "style=" float: none; "title=" 2015-04-21_14-02-03.png "alt=" Wkiom1u4xnjbbz1jaakrexkbmmi875.jpg "/>

Next is to create a multi-nic virtual machine, to use PowerShell to operate, because the multi-network card settings can not be implemented through the graphical interface, and the virtual machine can not add the NIC, can only be set at the time of creation, as shown in the first I used to define a $ Image variable to get a desired operating system image as the virtual machine template, here I use the image of "Windows Server R2 Datacenter" with the latest release date.

Then the key is the 2nd step, and the difference between the creation of a normal virtual machine is to pay attention to instancesize, can not be less than "Large", otherwise there will be a hint that the current specification does not support multiple network cards, the second is to pay attention to the virtual machine placed in the virtual network, and then add additional new network card " Add-azurenetworkinterfaceconfig "and specify the name"-name ", here I call it" back_end ", this is the NIC interface name used when passing parameters, is fixed, but not the name of the NIC displayed in the Guestos, It must be clear that this back_end will not appear in the system, and finally to the additional NIC to attach a subnet within the IP, such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6B/DE/wKioL1U4x9fzjOzqAARWmOhonQI874.jpg "style=" float: none; "title=" 2015-04-21_14-41-40.png "alt=" Wkiol1u4x9fzjozqaarwmohonqi874.jpg "/>

The creation starts successfully and you can see in the cloud service that the current VM role is being deployed, such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6B/E2/wKiom1U4xnqjvGBdAAJIfYsgBh8799.jpg "style=" float: none; "title=" 2015-04-21_14-41-59.png "alt=" Wkiom1u4xnqjvgbdaajifysgbh8799.jpg "/>

After successful deployment, you can see the dual NIC configuration after entering Guestos, such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6B/DE/wKioL1U4x9qDP1u9AAUT7pEAyEA511.jpg "style=" float: none; "title=" 2015-04-21_16-09-14.png "alt=" Wkiol1u4x9qdp1u9aaut7peayea511.jpg "/>

You can see that the IP addresses used by the two NICs are those in the previously specified virtual subnets, that is, the IP in outbound and inbound, such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/6B/E2/wKiom1U4xnyi8xl_AAb_EfbIHOM943.jpg "style=" float: none; "title=" 2015-04-21_16-09-40.png "alt=" Wkiom1u4xnyi8xl_aab_efbihom943.jpg "/>

Multi-NIC capabilities enrich the role of azure virtual machines while satisfying some user scenarios and at no additional cost:), but when I deploy a multi-nic virtual machine, I find that the virtual machine is always in the provisioning state ... Know the last time out, but the actual I have been able to enter the Guestos operation, do not know is not accidental phenomenon.

This article is from the "Technology Not Home" blog, please be sure to keep this source http://maomaostyle.blog.51cto.com/2220531/1637705

Azure multi-nic virtual machine