Hyper-V Failover Cluster doesn't failover when nic unplugged
Posted on 2014-02-25
I have a hyper-v failover cluster running with the following config:
NAS - Windows Server 2012 with a bunch of drives acting as a NAS
VMHOST1 - Windows Server 2012 with a few VM's
VMHOST2 - Windows Server 2012 with a few VM's
10.0.0.X Corp network
192.168.1.X storage network
192.168.150.X hearbeat network
Using iSCSI targets to the NAS for VM storage. Failover validation passes. VM's all up and running fine, if I simulate failover by doing alive migration it works perfectly. If I simulate a failover by stopping the cluster service on one of the VMHOST's it works perfectly. I had an issue today that another tech was in the server room and dislodged the corp network cable to VMHOST2. I would have expected the failover to kick in and the VM's to move to VMHOST1. This did not happen. Instead my phone blew up that all the VM's on VMHOST2 were down.
I attempted to access VMHOST2 through the corp network and saw it was down. was able to RDP in through storage network. See that corp nic shows unplugged. Had tech reseat the cable and all connectivity restored.
My question is why didn't it failover thinking the nic failed if the cable was unplugged? How can I test this further and what am I missing in my setup that it passes validation and simulated tests but not a real world failure?
Thanks in advance.