I wasn't sure which forum to put this in to be honest, as it could be a general server issue, Hyper-V or clustering.
I'm having a really frustrating issue with Hyper-V Server 2012 R2. I'm currently in the process of upgrading our old 2008 R2 Hyper-V cluster based on HP DL380 G7 servers using iSCSI through a HP P2000 SAN. To do this, I've removed a single node from the old cluster and have rebuilt it using 2012 R2 and created a new fresh cluster with new LUNs on the SAN.
The server has 4 onboard Broadcom NIC ports, and 8 PCI-E card Intel NIC ports. I'm using the latest HP ProLiant Support Pack, which has updated the BIOS and firmware to the latest version, as well as the drivers. I've also manually inserted the latest INF for the Intel NIC.
At first the build goes smoothly, up until the point I create the failover cluster. I start to lose network connectivity to the server, and even processes run locally on the server fail and time out. The symptoms I've come across are:
-Cannot log in through RDP (errors in logs about winlogon terminating unexpectedly)
-Constant error logs about iSCSI disconnecting and reconnecting
-Disk management from client works for a bit and then starts to time out and not connect
-Any changes in Hyper-V Manager from a client times out
-Broadcom Management Suite (BACS 4) times out connecting to localhost when run locally from console
-Powershell runs really slowly when run locally from console
I've disabling offloading, RSS, VMQ and IPv6, and I've tried building the server without using the Proliant Support Pack and using the default Microsoft drivers, but it did exactly the same thing.
I've built the server using a full copy of Server 2012 R2 instead of Hyper-V Server using the exact same build process and it worked fine.
Any one got any ideas?