Hi Guys,
- I am dealing with a quite interesting problem when migrating VMs from Hyper-V cluster 2012R2 to Hyper-V Cluster 2019.
The old infrastructure was connected 1x LM adapter directly, I forbid this connection, put the old infrastructure 10 GbE cards and connected with the new 10 GbE SW, which is connected to the new infrastructure.
In the old cluster, I set live migration to run on a 10GbE network - 192.168.140.0/24 - the same in the new cluster.
I set up a delegation in AD.
If I have 192.168.140.0/24 set in the hyper-v settings on the source cluster and want to migrate the VM to the new Hyper-V - migration fails ... if I set at using "any" then the data flows through the production network ... ie max 1 GbE ...
ping between all servers at 10 GbE - fine
If I am migrating VM in 2012R2 cluster - live migration - OK - 10 GbE
If I am migrating VM in 2019 cluster - live migration - OK - 10 GbE
if I have set in hyper-v settings to use any adapter - migrates, but only after gig ...
"Virtual machine migration operation failed at migration source" Failed to copy file.
On HyperV1 (source) i have set use theese IP "192.168.140.0/24" on destination same settings...
This is already the second customer and the same problem as if hyper-v ignored the new 10GbE retina. Is it possible to set priority / weight etc.?
Below is an orientation diagram
Get-ClusterNetwork | ft Name, Metric, AutoMetric, Role
Name Metric AutoMetric Role
---- ------ ---------- ----
HB 900 False Cluster
iDRAC USB NIC 80000 True None
iSCSI_10GbE_230 70240 True None
iSCSI_10GbE_231 70241 True None
LM 1200 False Cluster
PRODUCTION_VLAN130 70080 True ClusterAndClient
Name Metric AutoMetric Role
---- ------ ---------- ----
HB 900 False Cluster
iDRAC USB NIC 80000 True None
iSCSI_10GbE_230 70240 True None
iSCSI_10GbE_231 70241 True None
LM 1200 False Cluster
PRODUCTION_VLAN130 70080 True ClusterAndClient