Regarding Windows Server 2012 and Hyper-V, we are very clearly in a discovery phase. When fellow Virtual Machine MVP Didier van Hoye aka @WorkingHardInIT asked me if I had already found out how to select the Live Migration networks in a Windows Server 2012 Hyper-V Cluster, I simply didn’t have a clue. I saw Aidan Finn’s blog about the new location in the Failover Cluster Manager GUI to select these networks, but he was also asking the same question.
Fortunately my rewritten PowerShell scripts to quickly configure the converged fabric switch and the different management OS virtual networks was working wonders so a new 2-node cluster could be set up in no time.
Now how do we select Live Migration Networks with PowerShell?
As you can see in the GUI, the Live Migration setting is now in the Actions Pane instead of in the properties of a high available virtual machine as with Windows Server 2008 R2. I always needed to point out to customers that this was a global setting for all VMs in the cluster. So the new location seems like a logical one.
Without touching the Live Migration Settings, all networks were enabled for Live Migration in the fresh cluster that I set up. They are in this particular order because of the cluster network metric. You can verify this by this command:
Get-ClusterNetwork | Select name, Metric, AutoMetric, State | Sort Metric | ft –Autosize
To find out about the Live Migration networks, you need this command:
By default all known networks are Enabled and have equal Priority.
If you manually move one network to the top of the list, it gets a Priority 4000. So apparently like the network metric a lower number means higher priority.
VM Migration networks are removed by
VM Migration networks are set by
Set-VMMigrationNetwork [IP Address 1, IP Address 2, IP Address n]
Priority is set by
Set-VMMigrationNework [Subnet] [IP Address] –Priority n