Microsoft Azure Public Cloud Enterprise Exchange 2016 Deployment 6-Create a dual-Nic VM

In this section we will create the first mail server, as shown in:

650) this.width=650; "height=" 702 "title=" clip_image002 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M02/83/A0/wKioL1d43YuSTJHmAAEcIPJSFDo567.jpg "border=" 0 "/>

In order to separate the DAG replication data from the mailbox MAPI data, we configure the dual NIC here. Although in the Exchange2016, 2013 version, the dual NIC is not recommended by Microsoft to be equipped.

But replicating data and MAPI data apart has the following benefits:

A. This provides redundancy for network and network paths, allowing the system to differentiate between server failures and network failures. Using a single network adapter can prevent the system from distinguishing between these two types of failures.

B. If the failure affects the MAPI network, a server failover occurs (assuming that a healthy mailbox database copy can be activated).

C. When a failure affects a replication network, if the MAPI network is not affected by a failure, the log shipping and seeding operations revert to using the MAPI network, and the MAPI network sets its Replicationenabled property to False. When a failed replication network resumes normal and is ready to resume log shipping and seeding operations, you must manually switch to the replication network.

Microsoft Azure supports the creation of multi-NIC virtual machines to meet the traffic isolation between front-and back-end NICs, or to separate data-tier communications from management-level communication. The following is a sample diagram of the Microsoft Azure multi-NIC app:

650) this.width=650; "height=" title= "clip_image004" style= "Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/M00/83/A0/wKioL1d43YywxuM0AAI7_HShSEE583.png "border=" 0 "/>

When creating a virtual machine with multiple NICs, there are a few limitations to note:

A. The VM must reside in an Azure virtual network.

B. Only the following types of VMS support multiple NICs, the type and number of support are as follows:

Large (A3) and A6:2

Ultra-Large (A4) and A7:4

A9:2 A

D3:2 A

D4:4 A

D13:4 A

C. Single and multi-NIC hybrid deployments are not supported in the same Azure cloud service, that is, you cannot enable multi-Nic VMs in a cloud service that already has a single network card, or you cannot enable a single-Nic VM in a cloud service that already has multiple network cards.

D. Adding or removing network cards after VM creation is not supported.

E. The secondary network card cannot forward traffic, nor can it be used as a 3rd IP gateway.

F. The Internet-facing VIP is only supported on the default network card, and only one VIP is mapped to the IP of the default network card, and the secondary network card cannot be used in a load-balanced set.

G. The order of the network cards is random, but the IP address and the corresponding Mac will remain intact.

F. Applying a network security group or forced tunneling to a non-default network card is not supported.

Next, we'll create a VM with a dual NIC as a mail server.

1. Create a new cloud service

Because the single and dual NICs cannot be mixed in the same cloud, we create a new cloud service, which is the same as the DC Service area and the eastern part of Japan.

650) this.width=650; "height=" 218 "title=" clip_image006 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/M01/83/A0/wKioL1d43f7ChLmXAABSSJKF0qc128.jpg "border=" 0 "/>

650) this.width=650; "height=" 147 "title=" clip_image007 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/M02/83/A0/wKioL1d43f-yzSH0AAAda7V6OXk574.png "border=" 0 "/>

2. Add Subnets

This separates the network segments of the default network card and the secondary network card, creating a new subnet for internal data replication

650) this.width=650; "height=" 208 "title=" clip_image008 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/M02/83/A1/wKiom1d43f-hu34zAAAmhI2hP2U146.png "border=" 0 "/>

3. Create a multi-nic VM

To create a multi-nic VM requires Azure Poweshell, you can use the following command:

New-azurevmconfig-name "hhcloud-ex01"-instancesize "Large"-availabilitysetname "HHCLOUD-EXJP"-ImageName " A699494373c04fc0bc8f2bb1389d6106__windows-server-2012-datacenter-20160430-en.us-127gb.vhd "| Add-azureprovisioningconfig-windows-adminusername hhcloud-password "xxxx" | Set-azuresubnet-subnetnames "Subnet-3" | Set-azurestaticvnetip-ipaddress 192.168.2.21 | Add-azurenetworkinterfaceconfig-name "dag"-subnetname "Subnet-4"-staticvnetipaddress 192.168.4.21 | New-azurevm-servicename "HHCLOUD-EXJP" –vnetname "Hhcloud"

The command function is to create a VM named EX01 win2012 system A3 type, set the default NIC IP to 192.168.2.21, the secondary NIC IP is 192.168.4.2, enable the VM and join the availability set EXJP.

650) this.width=650; "height=" 157 "title=" clip_image010 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/M00/83/A1/wKiom1d43gCjaXQtAAC13e8UC9M830.jpg "border=" 0 "/>

Once created, we can confirm the parameters in the setup

650) this.width=650; "height=", "title=" clip_image011 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image011 "src=" http://s3.51cto.com/wyfs02/M01/83/A1/wKiom1d43gDQhOLLAAAfZRo7M4E282.png "border=" 0 "/>

650) this.width=650; "height=" 339 "title=" clip_image012 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M02/83/A1/wKiom1d43gDzmCgEAAAgl-By5Vs697.png "border=" 0 "/>

After logging in to the VM, you can see that there are two network cards enabled, of course, the secondary network card is not a gateway

650) this.width=650; "height=" 435 "title=" clip_image014 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image014 "src=" http://s3.51cto.com/wyfs02/M00/83/A0/wKioL1d43gGBZW9kAAGD96G_OpQ272.jpg "border=" 0 "/>

4. Adding a data disk

Because the initial VM has only 127G of system space and a disk for temporary data storage. We need to add an extra disk to the mail server to hold the data.

We are in the virtual machine item, select additional empty disk

650) this.width=650; "height=" "title=" clip_image015 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image015 "src=" http://s3.51cto.com/wyfs02/M01/83/A0/wKioL1d43gHgPwDXAAARPf4H_G8158.png "border=" 0 "/>

The maximum additional disk is 1023G. Because Azure disk charges are calculated based on the actual use of space, in order to reduce the future in the face of insufficient disk space, here directly attached to a 1023G disk.

650) this.width=650; "height=" 495 "title=" clip_image016 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image016 "src=" http://s3.51cto.com/wyfs02/M00/83/A1/wKiom1d43gKRy_CaAABFg3TzBYQ196.png "border=" 0 "/>

After attaching, to disk Management in the VM, you can see that a new disk needs to be initialized.

650) this.width=650; "height=" 311 "title=" clip_image017 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image017 "src=" http://s3.51cto.com/wyfs02/M02/83/A0/wKioL1d43gLBQGDZAAAqvpKlb5I658.png "border=" 0 "/>

Select New Simple Volume

650) this.width=650, "height=", "title=" clip_image018 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "Alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/M01/83/A1/wKiom1d43gOQ_KqcAAAlX4iu6Ik470.png "border=" 0 "/>

After specifying the drive letter and formatting, we can see that there are now several disks

650) this.width=650; "height=" 142 "title=" clip_image019 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image019 " Src= "Http://s3.51cto.com/wyfs02/M02/83/A0/wKioL1d43gOBPd81AAAxrFr0uTg974.png" border= "0"/>

In this way, the virtual machine environment of our first mail server is created, and the next section we install to configure the Exchange2016 mail server.

This article from the "Invincible Speaker of the Iron Fist" blog, reproduced please contact the author!

Microsoft Azure Public Cloud Enterprise Exchange 2016 Deployment 6-Create a dual-Nic VM