Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, October 16, 2010 5:46 AM
Hello All,
After a power outage our Hyper-v failover cluster stopped funtioning properly.
Configuration is a 2 Node Hyper-v failover cluster (HVS-01 and HVS-02). HVS-01 and HVS-02 can both own the VMs however when HVS-02 restarts instead of failing over cluster the VMs to HVS-01 cluster completely shuts down. When I check the log I see that HVS-01 complains about connectivity to the Quorum is gone and stops the cluster services on HVS-01 as well.
When I look at the network everything is just the way they were before when I was working just fine.
When I run the Cluster Validation I get below error msg:
"DHCP status for network interface HVS-02.soandso.local - Local Area Connection Mgnt differs from network Cluster Network 1."
This is the management network and it does have a static IP so I'm not sure what this means???
ps: After the power outage cluster came online but the IPv6 was enabled for some network cards. I manually disabled them again if it makes any difference.
any ideas?
Thank you,
All replies (5)
Saturday, March 5, 2011 4:58 PM
I am setting up a new cluster and have the same message when I run the validation. Have you found the answer yet? Thanks.
Sunday, April 3, 2011 12:19 AM
Add me to the list. Same error message about DHCP status not matching. The interface mentioned has a static address assigned but there is also another interface (in my case called Local Area Connection* 88). I can't change any properties (DHCP enabled for example) and it has no address.
Sunday, April 3, 2011 10:47 PM
Just as a side note, you should not disable IPv6 when clustering on windows 2008 or later.
I dont have the article at hand but there is stuff going on with IPv6 within the cluster, and disabling it can lead to odd errors or cluster behavior.
Maybe someone else can fill me in here?
Tuesday, July 24, 2012 11:31 AM
Same issue here. However I did have IPv6 disabled but not on the node raising the problem. Reenabling IPv6 dit not resolve the issue. In my case that particular NIC is used for the virtual network adapter in Hyper-V and is also used for all network traffic excep iSCSI with the server node itself. Can that be a problem?
Regards,
Jonas
Friday, May 23, 2014 5:43 PM
Running Window Svr 2012 R2 Hyper-V cluster, I had this error as well via cluster validation report; I fixed mine by first looking at http://technet.microsoft.com/en-us/library/aa998136(v=exchg.80).aspx. It turns out that mine was simple as I 1) left out a DNS server from one nic not in another, and 2) One was still a static IP. Doing this I got 'Validate Cluster Network Configuration' Success.
Lee Everest http://www.texastoo.com