Windows Azure Affinity Groups (3) modifies the configuration of the Virtual network affinity Group (Affinity Group)

Windows Azure Platform Family of articles Catalog

This article describes the domestic use of the century connected operation of the Azure China

In the author's previous article, we know that Microsoft is not currently recommending the use of affinity group affinity groups.

If the user is based on an affinity group, the virtual Machine network is created. Then all virtual machines that join this virtual network do not support reserved virtual IP Address (fixed public IP).

At this moment, Microsoft Azure doesn ' t support deploying a Cloud Service or Vsan associated with a Reserved IP Into an ' Affinity Group based Virtual Network '. The following snippet shows a sample error message that you'll get when to try-to-deploy a Virtual machine deployment WI Th Reserved IP into an ' Affinity Group based VNET '.

　　 New-Azurevm : badrequest  : the  deployment containsvirtualnetwork DemoVNET< Span class= "PLN" > that belongs to An affinity  group and Reservedip that belongs to a region.  this combination isnot allowed

http://azure.microsoft.com/blog/2014/05/14/reserved-ip-addresses/

　　This creates a problem, and if we have already used the Azure affinity group, How should we modify the configuration?

Here we simulate a scene:

1. Assume that the author has an Azure subscription named "Internal Billing"

2. In this subscription, the author has used the affinity group Chinaeastaffinitygroup in the data center in East Shanghai

　　

3. Then we created the virtual machine network based on this affinity group, named Myvnet

4. Then in this virtual machine network, create a new virtual machine MYVM

　　

We follow the steps below to make changes:

1. First find this virtual machine network myvnet, click Export

　　

2. We will save this exported file in the root directory of the C drive. Then open it with Notepad.

To find the Myvnet node, the value of the observed location is:

　　

　　

We revise to East China:

　　

3. After the modification, we use the Azure management interface to import the updated virtual network configuration file Networkconfig.xml

　　

4. In the popup screen, import the configuration file we saved in the C packing directory Networkconfig.xml

　　

5. This modification was successful.

　　

　　

Windows Azure Affinity Groups (3) modifies the configuration of the Virtual network affinity Group (Affinity Group)