Chris, 

 

Only the Public NIC can be teamed, but even in some of the Windows 2003
Documentation said, if the teaming is causing problems, it might have to
be broken accordingly to troubleshoot the problem.

 

Teaming of NIC's on the Private NIC should not be done. 

 

I still go with the old school ( Public Nic (Teamed or not) (If teamed
(Fail on Fault configuration)) for the public Network and the Private
NIC (single NIC) for the Private network and  I don't set the mixed
communications on the cluster. 

 

I haven't done a Win2k8 Cluster yet, but I would stick with the tried
and true steps as they where in Win2k3 for the time being as a
troubleshooting step. 

 

Although my other question would be about the VLANing and having Nodes
across 2 different subnets. 

 

Z

 

From: Christopher Bodnar [mailto:christopher_bod...@glic.com] 
Sent: Tuesday, February 09, 2010 8:45 AM
To: NT System Admin Issues
Subject: 2008 Failover cluster

 

I'm very familiar with failover clustering in 2003, but not in 2008. A
colleague setup a 2008 cluster on our network and it's having some
issues. Unfortunately he is no longer with the company. We opened a case
with MS regarding this and the tech is asking me about the network
configuration. The server has 2 NICs and they are setup in a team. It's
configured to allow the cluster to use it (heartbeat) and clients to
connect to it. I'm reading through the documentation, specifically:

 

Step-by-Step Guide for Configuring a Two-Node File Server Failover
Cluster in Windows Server 2008

 

And the word heartbeat is not even mentioned in this document. In fact
this is a direct quote:

 

You can connect your cluster nodes with one network that is constructed
with teamed network adapters, redundant switches, redundant routers, or
similar hardware that removes single points of failure.

 

This is quite different from a 2003 cluster with distinct network
connections, one of which is for heartbeat communication. Can someone
confirm this for me? From what I've heard so far from the MS tech, he
wants to break the team and set it up with 2 distinct networks, one of
which will be for heartbeat. But from everything I'm reading, this is
NOT required in 2008 anymore. I can't even find a recommendation that
this needs to be done. 

 

Thanks,

 

 

 

 

 

Chris Bodnar, MCSE
Sr. Systems Engineer
Infrastructure Service Delivery
Distributed Systems Service Delivery - Intel Services
Guardian Life Insurance Company of America
Email: christopher_bod...@glic.com
Phone: 610-807-6459
Fax: 610-807-6003

 

 

 
________________________________


This message, and any attachments to it, may contain information that is
privileged, confidential, and exempt from disclosure under applicable
law. If the reader of this message is not the intended recipient, you
are notified that any use, dissemination, distribution, copying, or
communication of this message is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
return e-mail and delete the message and any attachments. Thank you. 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to