Interface. The Lan Interface (NIC) on our active node went down so our
clients could not access the server. Since the services and the Heartbeatr
interface did not go down the passive node did not failover and take control
of the Cluster automatically. We had to force the passive cluster to
failover. Is there anyway we can prevent this from happening in the future ?
Hi
Have you had a look at
http://support.microsoft.com/default...;en-us;242600?
If you have Media Sense Disabled, the cluster will not fail over.
Regards
Mike
"ejcs@.noemail.nospam.com" wrote:
> We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
> Interface. The Lan Interface (NIC) on our active node went down so our
> clients could not access the server. Since the services and the Heartbeatr
> interface did not go down the passive node did not failover and take control
> of the Cluster automatically. We had to force the passive cluster to
> failover. Is there anyway we can prevent this from happening in the future ?
|||Hi,
I wanted to post a quick note to see if you would like additional
assistance or information regarding Mike's suggestions on this particular
issue. Have you tried the method described in KB:Q242600, does this resolve
your problem?
Please feel free to let me know if there is anything more I could do to
help on this issue and we appreciate your patience and look forward to
hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I thought I would post this here in case somebody else has this problem. Incidentally, the link above to the KB article doesn't work: here it is again:
http://support.microsoft.com/default...b;en-us;242600
A common expectation of a virtual SQL running on a MS cluster is that link failure on the active node NIC will result in a failover.
Examples: loose cable, kicked cable, failed switch or switch module.
However, this will not cause a failover to the passive node
"Simply removing the network cable from the client network adapter does not constitute an adapter failure."
http://support.microsoft.com/kb/176320
I'm currently exploring a different issue for a client which if I find a solution for I will post here.
Scenario: 2 cluster active/passive MS cluster running SQL 2000 Enterprise. Public NICS are mixed mode, Private NIC is internal heartbeat only.
Symptons:
- unplugging public NIC cable from passive node will cause interface to dissapear from Cluster Admin
- unplugging public NIC cable from active node will cause both public NICs to become unavailable in Cluster Admin
- unplugging BOTH public NICs will cause public NIC of active to RE-APPEAR and be normal!
Anyway, I'll post more if I find a solution...|||Erratim: sorry the link from the second poster does work... didn't realise it was truncating the display.
Also, when both cables are pulled from the public NICs the status is unreachable, not unavailable
|||As a conclusion to this post, my issue related to the DisableDHCPMediaSense in the Windows Registry.The active node had this set. Nobody set this value, so it seems to have been set by the system at some point.
Check MS KB on this issue if you have a cluster that won't failover when the network cable or switch goes down.
