Hyper-V Failover Live Migration failed. Error 21502
-
What's the saturation level on 3&4? Are the linked into a single pipe?
-
@Dashrender
How do I check that? -
@LAH3385 said:
@Dashrender
How do I check that?I'd start by opening task manager and seeing how the graphs look for those interfaces - I'm not how how to setup NIC teaming - though with Server 2012 it's supposed to be pretty easy.
-
@Dashrender
I really do not know what am I looking for. The first three are physical. The last one is VM.
-
@LAH3385 said:
@Dashrender
I really do not know what am I looking for. The first three are physical. The last one is VM.You mean the first three are the NICs in the Hyper-Visor, and the last one is the VM?
Ok the second and third look linked.
-
@Dashrender
Yes. that is correct. -
Those numbers look good. Move a huge file (at least 2 GB, though it might need to be more like 4 or 6 GB so the transfer lasts long enough) from the server and take screen shots after about 30 seconds in, then move from the workstation to the server, again take screen shots about 30 seconds in.
-
@Dashrender
First screenshot 5GB. transfer rate 8MB/s - 12MB/s
Second screenshot 5GB. transfer rate steady 10.5MB/s - 12MB/s
-
@LAH3385 That's the sort of max transfer speed I'd expect out of a 100 megabit network. Something is probably not set or working right with the crossover connections.
-
@travisdh1
Beside setting static ip address I did not do anything more than that. (aside from starwind vSAN) -
Thanks - and while these graphs might be useful, I was really hoping to see the ones you posted earlier, from Task Manager, showing each of the NICs.
-
@Dashrender
it's a 10 minute transfer. The graph only shows a minute(?). Beside I think it should maxed out anyhow. Also, because I transfer the file across the network it doesn't utilize cross-over network. -
@LAH3385 said:
@Dashrender
it's a 10 minute transfer. The graph only shows a minute(?). Beside I think it should maxed out anyhow. Also, because I transfer the file across the network it doesn't utilize cross-over network.it should use the cross over cable because the data should be replicated between the StarWinds vSAN, assuming the data is being written to a partition on that volume, which was where I thought your bottleneck might be.
Also, as travishdh mentioned - is your switch a 100 Mb switch?
-
I did not replicate file between the two cross-over servers. It is from a server to workstation.
it's a gigabit switch. -
@LAH3385 said:
I did not replicate file between the two cross-over servers. It is from a server to workstation.
it's a gigabit switch.I understand - let me step back a second.
You have two servers. Those two servers have a StarWind shared volume (clustered volume), right?
That cluster is synced between the two servers using the crossover cables. What is written to one server is automatically written to the other server as well, hopefully less than a millisecond later.
So If the link that supports the syncing of the clustered volume is saturated, I would expect the whole server to slow down waiting for that link to catch up.
@LAH3385 said:
it's a gigabit switch.
So you say you have a Gb switch. Those speeds are pretty terrible for a Gb switch transfer, unless the workstation is only connecting to the switch at 100 Mb.
So now I suggest that you check that all connections are listing themselves as 1 Gb connections and correcting any that are not.
-
@Dashrender said:
@LAH3385 said:
it's a gigabit switch.
So you say you have a Gb switch. Those speeds are pretty terrible for a Gb switch transfer, unless the workstation is only connecting to the switch at 100 Mb.
So now I suggest that you check that all connections are listing themselves as 1 Gb connections and correcting any that are not.
All connections are Gb. All cables are CAT6.
