Windows 2008 Failover Cluster Heartbeat

i have windows 2008 failover cluster setup disk majority both nodes @ same site.

 

i have production lan team 2 nics.  questions below:

1. teaming, means have redudant network in such no heartbeat network required?

2. have created private cross cabled heartbeat network, , realize if remove production network on active node, after default threshold of 5 sec, resource group still failover.  if so, purpose of heartbeat in case.  keep quorum alive , leave quorum @ fail node fail on resource groups working node?

 

would need advise have done setup , have tested heartbeat.

this confusing found.

from kb: http://support.microsoft.com/kb/258750

"also base on kb snip: windows server 2008 , windows server 2008 r2 failover clusters not have have private heartbeat network."

hi,

here comments side:

"...with teaming, means have redudant network in such no heartbeat network required?...."

generally should avoid within failover cluster single points of failure within networking infrastructure. therefore personal recommendation - team cards single virtual adapter - should have have redundant networks cluster communications. kb articles not (fully) apply windows 2008 clusters, there no more dedicated hb adapter required have "redundant" networks available and have "cluster internal" communication enabled. detailed requirements networking can find here ->

appendix a: failover cluster requirements
http://technet.microsoft.com/en-us/library/dd197454(ws.10).aspx

understanding requirements failover clusters
http://technet.microsoft.com/en-us/library/cc771404.aspx

"...if so, purpose of heartbeat in case.  keep quorum alive , leave quorum @ fail node fail on resource groups working node?...."

from technet:

"...by default, regardless of subnet configuration, heartbeat frequency (also known subnet delay) once every second (1000 milliseconds). range heartbeat frequency once every 250-2000 milliseconds on common subnet, , 250-4000 milliseconds across subnets. default, when node misses series of 5 heartbeats, node initiate failover, , range value (also known subnet threshold) 3 through 10."

configure heartbeat , dns settings in multi-site failover cluster
http://technet.microsoft.com/en-us/library/dd197562(ws.10).aspx

note: only applies multi-site, in single site configuration don't need configured heartbeat latency!

there more communication done between "cluster internal" networks depending on implementation. if interested more details, going on cluster internal networks can check cluster logs ;-)

regards

ramazan

---

ramazan can [mvp cluster] http://ramazancan.wordpress.com/

Windows Server  >  High Availability (Clustering)