{"id":892,"date":"2015-05-08T00:20:06","date_gmt":"2015-05-07T22:20:06","guid":{"rendered":"https:\/\/www.vioreliftode.com\/?p=892"},"modified":"2016-04-14T13:31:11","modified_gmt":"2016-04-14T11:31:11","slug":"virtual-machine-with-multiple-nics-in-azure-stuck-in-running-provisioning-or-running-provisioning-timed-out","status":"publish","type":"post","link":"https:\/\/www.vioreliftode.com\/index.php\/virtual-machine-with-multiple-nics-in-azure-stuck-in-running-provisioning-or-running-provisioning-timed-out\/","title":{"rendered":"Virtual machine with multiple NICs in Azure stuck in Running (Provisioning) or Running (Provisioning timed out)"},"content":{"rendered":"

The Azure VM Multi-NIC feature is available for a while (Q3 2014). I personally haven\u2019t got till now the need to host virtual machines with multiple NICs in Azure.<\/p>\n

 <\/p>\n

In the last days I decided to build a part of my test environment in Azure. Since my on-premises setup rely on 10 subnets and multiple NICs, I decided to leverage the Multi-NIC feature also in cloud, but I encounter issues with the VM provisioning. I think this is temporary until Microsoft is fixing it. However, I lost couple of good hours with it till I found the workaround, so it deserve a post.<\/p>\n

 <\/p>\n

How to:<\/strong><\/span>
\n1. In Azure I defined my own Virtual Network with 3 (three) subnets.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_01\"<\/a>
\nINTERNAL#48 – intended to be used for heartbeat
\nINTERNAL#49 – intended to be used for dedicated MS SQL traffic
\nINTERNAL#50 – all other network traffic<\/p>\n

 <\/p>\n

2. I also created a storage account where to host my Azure VM disks.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_02\"<\/a><\/p>\n

 <\/p>\n

3. Create a multi-NIC VM (possible only through PowerShell)<\/p>\n

\r\nAdd-AzureAccount\r\n\r\n$subscriptionName = 'Visual Studio Premium with MSDN'\r\n$storageAccountName = 'itechwe'\r\n$location = 'West Europe'\r\n$vmSize = 'ExtraLarge'\r\n$serviceAndVmName = "ITECH-DB01"\r\n$vnet = "ITECH_CLOUD_WE"\r\n\r\nSet-AzureSubscription -SubscriptionName $subscriptionName -CurrentStorageAccount $storageAccountName\r\nSelect-AzureSubscription -SubscriptionName $subscriptionName -Current\r\n\r\n$imageFamily = "Windows Server 2012 R2 Datacenter"\r\n$imageName = Get-AzureVMImage | where { $_.ImageFamily -eq $imageFamily } | sort PublishedDate -Descending | select -ExpandProperty ImageName -First 1\r\n\r\n$imageName\r\n\r\n$cred = Get-Credential -Message "Enter admin credentials for the VM(s)"\r\n$adminUser = $cred.UserName\r\n$pwd = $cred.GetNetworkCredential().Password\r\n\r\n$vm1 = New-AzureVMConfig -ImageName $imageName -Name $serviceAndVmName -InstanceSize $vmSize | Add-AzureProvisioningConfig -Windows -AdminUsername $adminUser -Password $pwd | Set-AzureSubnet -SubnetNames "INTERNAL#50" | Set-AzureStaticVNetIP -IPAddress "192.168.50.4" | Add-AzureNetworkInterfaceConfig -Name "NIC#48" -SubnetName "INTERNAL#48" -StaticVNetIPAddress "192.168.48.4" | Add-AzureNetworkInterfaceConfig -Name "NIC#49" -SubnetName "INTERNAL#49" -StaticVNetIPAddress "192.168.49.4"\r\n\r\nNew-AzureService -ServiceName $serviceAndVmName -Location $location\r\n\r\nNew-AzureVM -ServiceName $serviceAndVmName -Location $location -VNetName $vnet -VMs $vm1\r\n<\/pre>\n
\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_03\"<\/a><\/p>\n
 <\/p>\n
The problem:<\/strong><\/span>
\nThe VM is started, gets into the Running (Provisioning) status and remains in this state for almost 1 hour.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_04\"<\/a>
\nAfter the long provisioning attempt the VM status is changed to Running (Provisioning timed out). Connection via RDP is not working, restarting the VM will not help – pretty much nothing to be done anymore.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_05\"<\/a><\/p>\n
 <\/p>\n
Solution (workaround):<\/strong><\/span>
\nI think the new 2015 virtual machine images have some issues during provisioning if the VM is configured with multiple NICs. The workaround I found out is to first successfully provision the VM with only one NIC and later use that OS disk and attach it to a new multi-NIC VM.
\nBecause I want to use the same VM and service names, before running the next steps I deleted the previous created VM (including the disk and cloud service).<\/em><\/p>\n
 <\/p>\n
1. First let’s create the VM using one NIC.<\/p>\n
\r\nAdd-AzureAccount\r\n\r\n$subscriptionName = 'Visual Studio Premium with MSDN'\r\n$storageAccountName = 'itechwe'\r\n$location = 'West Europe'\r\n$vmSize = 'ExtraLarge'\r\n$serviceAndVmName = "ITECH-DB01"\r\n$vnet = "ITECH_CLOUD_WE"\r\n\r\nSet-AzureSubscription -SubscriptionName $subscriptionName -CurrentStorageAccount $storageAccountName\r\nSelect-AzureSubscription -SubscriptionName $subscriptionName -Current\r\n\r\n$imageFamily = "Windows Server 2012 R2 Datacenter"\r\n$imageName = Get-AzureVMImage | where { $_.ImageFamily -eq $imageFamily } | sort PublishedDate -Descending | select -ExpandProperty ImageName -First 1\r\n\r\n$imageName\r\n\r\n$cred = Get-Credential -Message "Enter admin credentials for the VM(s)"\r\n$adminUser = $cred.UserName\r\n$pwd = $cred.GetNetworkCredential().Password\r\n\r\n$vm1 = New-AzureVMConfig -ImageName $imageName -Name $serviceAndVmName -InstanceSize $vmSize | Add-AzureProvisioningConfig -Windows -AdminUsername $adminUser -Password $pwd | Set-AzureSubnet -SubnetNames "INTERNAL#50" | Set-AzureStaticVNetIP -IPAddress "192.168.50.4"\r\n\r\nNew-AzureService -ServiceName $serviceAndVmName -Location $location\r\n\r\nNew-AzureVM -ServiceName $serviceAndVmName -Location $location -VNetName $vnet -VMs $vm1\r\n<\/pre>\n
\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_06\"<\/a><\/p>\n
 <\/p>\n
This time the machine will be properly provisioned. The easiest way to verify this is to remotely connect to it using RDP.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_07\"<\/a><\/p>\n
 <\/p>\n
But this is not the VM with 3 (three) NICs. In the next step I will delete this VM without deleting the disks<\/span>. Basically I used this machine to make sure the provisioning is successfully completing. Once I delete the VM, I will recreate the 3 (three) NICs VM via PowerShell by attaching the existing OS disk.<\/p>\n
 <\/p>\n
2. Identify the OS disk name used by the provisioned VM.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_08\"<\/a><\/p>\n
 <\/p>\n
3. Delete the existing VM with preserving<\/span> the OS disk image.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_09\"<\/a><\/p>\n
 <\/p>\n
In the virtual machines disks section make sure the disk is not attached to the VM anymore (in Azure the detach disk operation is a bit delayed from the VM deletion).
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_10\"<\/a><\/p>\n
 <\/p>\n
4. Recreate the 3 (three) NICs virtual machine by attaching the exiting OS disk.<\/p>\n
\r\n$location = 'West Europe'\r\n$vmSize = 'ExtraLarge'\r\n$serviceAndVmName = "ITECH-DB01"\r\n$vnet = "ITECH_CLOUD_WE"\r\n$diskName='ITECH-DB01-ITECH-DB01-0-201505070854370389'\r\n\r\n$vm1 = New-AzureVMConfig -Name $serviceAndVmName -DiskName $diskName -InstanceSize $vmSize | Add-AzureEndpoint -Name 'Remote Desktop' -LocalPort 3389 -Protocol tcp | Set-AzureSubnet -SubnetNames "INTERNAL#50" | Set-AzureStaticVNetIP -IPAddress "192.168.50.4" | Add-AzureNetworkInterfaceConfig -Name "NIC#48" -SubnetName "INTERNAL#48" -StaticVNetIPAddress "192.168.48.4" | Add-AzureNetworkInterfaceConfig -Name "NIC#49" -SubnetName "INTERNAL#49" -StaticVNetIPAddress "192.168.49.4"\r\n\r\nNew-AzureVM -ServiceName $serviceAndVmName -Location $location -VNetName $vnet -VMs $vm1\r\n<\/pre>\n
\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_11\"<\/a><\/p>\n
 <\/p>\n
5. The virtual machine gets into the Running status and if we RDP to it we will see the VM is linked to the 3 (three) subnets.
\n\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_07\"<\/a><\/p>\n
\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_12\"<\/a><\/p>\n
\"VM_With_Multiple_NICs_In_Azure_Stuck_In_Provisioning_13\"<\/a><\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
The Azure VM Multi-NIC feature is available for a while (Q3 2014). I personally haven\u2019t got till now the need to host virtual machines with multiple NICs in Azure.   In the last days I decided to build a part of my test environment in Azure. Since my on-premises setup rely on 10 subnets and … Continue reading Virtual machine with multiple NICs in Azure stuck in Running (Provisioning) or Running (Provisioning timed out)<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"#VirtualMachine with multiple NICs in #Azure stuck in Running (Provisioning) or Running (Provisioning timed out) https:\/\/wp.me\/p4NfDd-eo","jetpack_is_tweetstorm":false},"categories":[75],"tags":[82,78,81],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4NfDd-eo","_links":{"self":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts\/892"}],"collection":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/comments?post=892"}],"version-history":[{"count":0,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts\/892\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/media?parent=892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/categories?post=892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/tags?post=892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}