Network Saturation on a host when vMotioning a VM. Microsoft Failover cluster can't find disks when vmotioning a random VM on host.

[SanderHogewerf]

Hi Folks,

At the moment i have an issue when i am vmotioning some VM's on particular hosts.

When i vMotion a VM on a host with Microsoft Cluster the microsoft Cluster loses the connection to the disks. Resulting in downtime for the application.

The hosts got 2 uplinks in an LACP configuration. It is not possible to create a dedicated vMotion network (Yes also i don't like this).

The Host is connected to a DVS. Where vMnic LAG 1-0 is connected for Management and Lag 1-1 is connected for vMotion traffic.

I think when i vmotion a vm on the host to another host the NIC is blown full and the normal VM-traffic can't reach the VM.

Is there a way to solve this issue?

I like to hear of you and thankyou for your thoughts.

Kind regards,

Sander

[jburen]

If you can't configure a seperate vMotion network then you're out of luck. Please have a look at these best practises: Networking Best Practices for vSphere vMotion