Setup should be the same.
See the link for lots of good info:
http://www.microsoft.com/d
Main Topics
Browse All TopicsDoes Windows Server 2008 Failover Clustering use a heartbeat network in the same manner that Server 2003 did? Anyone have any documentation on this, I can't seem to find anything.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Setup should be the same.
See the link for lots of good info:
http://www.microsoft.com/d
Hi,
As far as I remember, on windows 2008, during cluster creation you have to designate the network cards that will permit heartbeat.
If I'm wrong anyway, you can adjust the configuration later.
One thing I just forgot about NIC configurations: on the NIC that you'll dedicate for heartbeat, in IP configuration, advanced settings, modify the "metrics" of the interface to raise it up. By default all interfaces have same metric at 10, modify the metrics for the hearbeat interface to 100.
Doing like this, your ensure that when you ping node.domain.com from the node1 server it will ping itself on the client interface, not on the heratbeat dedicate network. That seems almost nothing but it can provocate total cluster failure in certains cluster configurations.
Have a good day.
Business Accounts
Answer for Membership
by: PaciBPosted on 2009-08-12 at 08:07:57ID: 25079502
Hi,
Yes it does... exactly like on server 2003.
You are not forced to dedicate a network for heartbeat, you can mix client traffic and hearbeat on the same network.
But to have Microsoft supported configuration you must have at least 2 NICs per node.
Usually, production infrastructures use 3 physical netcards:
- 2 of them are joined in a network team, and will supply network access for clients. It can be a good idea to allow heartbeat on this network also to avoid cluster resources move if someone unplug the heartbeat dedicated card.
- the third one is dedicated for hearbeat (it's a recommanded configuration to have one NIC dedicated to heartbeat).
You define a private IP range for heartbeat dedicated network. You will assign one IP address in this range for each node for heartbeat dedicated card. You're not supposed to have anything else on this hearbeat dedicated network.
On hearbeat dedicated netcard configuration you'll disable of course DNS dynamic registration, NetBIOS over IP. You should not need a gateway on this network.
You will name explicitly network connections in Windows to avoid ambiguous names like "Network connection #1"... "LAN" and "Heartbeat" are good names to avoid mistake in cluster configuration.
Have a good day.