Hi All,
Situation:
Old Vnet with affinity group, with all the VM's under it
With this setup i can't set a PIP address to the VM01 (this works not)
I have created a new VNET and here i can set a PIP on a teset VM (so this works)
Problem is that:
The "Old" VNET has an affinity group associate with it.
I have reading this article http://clemmblog.azurewebsites.net/assign-public-ip-addresses-azure-vms/ to export and import the "NetworkConfig.xml" file
The thing is that in the NetworkConfig.xml the setting are already correct, see under:
<NetworkConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/ServiceHosting/2011/07/NetworkConfiguration">
<VirtualNetworkConfiguration>
<Dns />
<VirtualNetworkSites>
<VirtualNetworkSite name="Working" Location="West Europe">
<AddressSpace>
<AddressPrefix>10.0.0.0/8</AddressPrefix>
</AddressSpace>
<Subnets>
<Subnet name="Subnet-1">
<AddressPrefix>10.0.0.0/11</AddressPrefix>
</Subnet>
</Subnets>
</VirtualNetworkSite>
<VirtualNetworkSite name="Not Working" Location="West Europe">
<AddressSpace>
<AddressPrefix>10.0.0.0/8</AddressPrefix>
</AddressSpace>
<Subnets>
<Subnet name="Subnet-1">
<AddressPrefix>10.0.0.0/8</AddressPrefix>
</Subnet>
</Subnets>
</VirtualNetworkSite>
</VirtualNetworkSites>
</VirtualNetworkConfiguration>
</NetworkConfiguration>
If i'm running the powershell command to set a PIP in the "Old" Vnet i get the error showing below:
Update-azurevm : InternalError : The server encountered an internal error. Please retry the request.
At line:1 char:99
+ ... me VM01 | Update-azurevm
+ CategoryInfo : CloseError: (:) [Update-AzureVM], CloudException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.UpdateAzureVMCommand
i know i can move all the VM's to the newly created Vnet only that will be to much effort.
Can someone please help me to achieve this in the "Old" Vnet
Kind Regards,
Daniel