Windows Cluster cannot failover to other node if public network is unplugged
Dear all,
In Windows 2003 Cluster, when I unplug network cable (public connection), it can switch over to other node. However, It seems that it is not working under windows 2008 (google search and someone said it is normal in 2008....).
I found none of offical documentation on the guideline about Cluster failover test in Windows 2008. Can anyone give me some suggestion on it? Thanks.
Thomas
September 25th, 2010 1:31am
Do you have "Allow cluster network communication on this network" selected in the networks section of failover cluster manager for the public interface? If not, this could be the problem...
blog TinyInt.Com | work
Logicworks.Net
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2010 2:02am
ThomasTse,
If the public cable is pulled, the IP's associated with clusterresources becomes unavaible, this triggers the name to be unavailble and hence the whole thingy should failover. I believe this is still the case with Windows 2008.
However in 2008 there is a setting somewhere who controls how many failovers you can do in a give time. It's dangerous during testing as at certain point it won't failover due to the limit being reached.
The setting is reachable, i think on the properties of the cluster or resources, as a "hyperlink" instead of a buttong one of the tabs. Somewhere close to where you set all the other parameters regarding number of failovers/prefered owners/..http://setspn.blogspot.com
September 26th, 2010 5:11am
yes, I do so. both Private and Public checked on it.
Free Windows Admin Tool Kit Click here and download it now
September 26th, 2010 11:21pm
Would it be possible for you to post your cluster log? However it would be best to only include the portion from a few seconds prior to cable unplugged to a few seconds after the cable is unplugged since it is so verbose...
You will have to follow the instructions here to export the log:
http://blogs.technet.com/b/pfe-ireland/archive/2008/07/04/windows-2008-clustering-the-cluster-log.aspx
More info about exporting the log is here:
http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspxblog TinyInt.Com | work
Logicworks.Net
September 27th, 2010 12:27am
If all tests are passed during cluster installation, should it work fine?
And, really no articles about failover test? Thanks.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2010 9:56pm
Hi,
Please check the following link.
Step-by-Step Guide for Testing Hyper-V and Failover Clustering
http://www.microsoft.com/downloads/details.aspx?FamilyId=CD828712-8D1E-45D1-A290-7EDADF1E4E9C&displaylang=en
Best Regards,
Vincent Hu
September 28th, 2010 10:27pm
For public, "Allow the cluster to use this network" & Allow Clients to connect through this network" have been checked.
For private, only " "Allow the cluster to use this network" is checked.
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2010 11:58pm
If you power both nodes than, then cold start them up again.
Does it then work once as expected?http://setspn.blogspot.com
September 29th, 2010 2:46am
If I power off / reboot one of them, it can failover to another node.
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 9:59pm
Plz try my original suggestion:
However in 2008 there is a setting somewhere who controls how many failovers you can do in a give time. It's dangerous during testing as at certain point it won't failover due to the limit being reached.
The setting is reachable, i think on the properties of the cluster or resources, as a "hyperlink" instead of a button on one of the tabs. Somewhere close to where you set all the other parameters regarding number of failovers/prefered owners/..http://setspn.blogspot.com
October 7th, 2010 3:03am
any suggested settings? I will try on it.
Free Windows Admin Tool Kit Click here and download it now
October 10th, 2010 10:28pm
I tried fail-over test. Server 1 can failover to Server 2 when network unplugged at server 1. However, it can't failover when server 2 's network disconnected. anyone can help what is the problem?
October 18th, 2010 2:33am
To be more precise, the settings I was referring too:
Open Failover Cluster Manager
Right click your cluster (the thing ABOVE "services and applications")
Choose properties
In the general tab, in the right under corner this is a hyperlink "manage core cluster resources group". click it
There is a tab with some failover settings: play with the "maximum failures" in the "specified period". Defaults is 2 times in 2 hours. You could set it too 4,5 or more times in 2 hours just for testing.
If this doesnt solve your issue. Id go trippelchecking/comparing both nodes to found out whether they are configured identically.
Or dig in the log
Windows 2008 Clustering & the Cluster Loghttp://setspn.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
October 18th, 2010 3:25pm
Thanks and after that setting apply, failover from 1 to 2 and 2 to 1 is successful. One more question here, if it is in fail status, any sideback effect will be produced? Thanks.
October 26th, 2010 5:17pm