Each Hyper-V host is a Windows 2012 Server
Each host is Connected to a Dell Powervault MD3260 via Dual SAS Cables.
We started getting Errors similar to the Following:
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 9/22/2014 12:01:24 PM
Event ID: 5142
Task Category: Cluster Shared Volume
Level: Error
Keywords:
User: SYSTEM
Computer: SVR-HBG-VM4.HAYDON-MILL.COM
Description:
Cluster Shared Volume 'VSVR_File_Data' ('VSVR_File_Data') is no longer accessible from this cluster node because
of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.The CSV Resources that were giving the Timeout Errors were all managed on one specific host, other CSVs on the Powervault were all working fine form the Host reporting the timeout error.
Each of the Host then started to have issues with timeouts to other CSV. Dell Tech Support interrogated the Powervault and found no issued with the Connectivity and no events were present on the Powervault indicating an issue.
Each of the Host would then hand in Explorer, the Task bar would have no icons in the task bar and turn to hourglass when moving mouse to it.
Failover Cluster Manager would sometimes work, then stop working, It would not update the status of the VMs. They would jsut stay at "Loading..." Hyper-V Manager would have similar issues.
We ended up Shutting down all of the VMs and the Cluster and then bringing it back online. Though in the Process we had to tweak some things, the DNS settings on the Hosts were pointing to a VM that was Offline that was fixed. We could not reconnect to the cluster after we turned on the Hosts. We were getting RPC server unavailable.
I ended up turning off the Firewalls, resetting the NICs and things started to get better.
8 Minutes prior to the Issues did make a few GPO Changes.
Windows Firewall: Allow inbound Remote Desktop Exception Domain Profile was 10.0.0.0/8 Changed to 10.0.0.0/8,10.1.0.0/16 Windows Firewall: Allow inbound Remote Desktop Exception Standard Profile 10.1.0.0/16, localsubnet Windows Firewall: Allow inbound Remote administration Exception Domain Profile was localsubnet,10.0.0.0/8 Changed to localsubnet,10.0.0.0/8,10.1.0.0/16 Windows Firewall: Allow inbound Remote administration Exception Standard Profile 10.1.0.0/16, localsubnet Remote Registry Service Set to Manual Start
So my Question is, could these changes of Affected the Hyper-V Hosts in the Cluster?
Thanks!
Scott<-