Network adapter configuration for Failover Cluster with CSV, iSCSI, and Hyper-V

I have been struggling with configuring the network adapters on a 2-node Server 2008 R2 failover cluster with CSV, iSCSI, and Hyper-V. The attached screen prints will hopefully give you an idea of how I have configured my adapters. My network logic is as follows:

Host - usually called "Management", to be used by host fo all of it's normal networking needs
Hyper-V - 2 physical adapters teamed (for redundancy) and then presented to the hypervisor

Heartbeat - I am using the old term, I think the new way of naming this is something like "Cluster" or "Cluster Communications", if I can figure out how to do it I would like this to be the only adapter the cluster uses for cluster specific traffic (Heartbeat, CSV, etc), I have read some articles about being able to limit CSV to a percentage of this adapters max usage to prevent CSV from drowning out the Heartbeat and causing an unexpected failover event

Live Migration - the only reason I separated this adapter on it's own network was because of the numerous articles online which recommended it

iSCSI - 3 physical adapters using MPIO

Does this seem like a sound network configuration? Any suggestions?

If this is a good configuration how about some advice on how to configure the adapter properties for each physical adapter?
YPIT-Network-Adapter-Config.jpg
YPIT-Cluster-Networks.jpg
YPIT-Adapter-Properties.jpg
System EngineerSystems EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gtworekCommented:
Test your configuration with cluster validation wizard and read carefully all suggestions.
It's OK, but you can limit cluster network traffic on interfaces not designed you would like to use for other purposes.
0
msmamjiCommented:
That looks good provided it passes cluster validation... only validated clustered are supported by microsoft.
Regarding configuring the networks I recommend reading this.
http://technet.microsoft.com/en-us/library/dd446679(WS.10,printer).aspx

What exactly are Hyper-V NIC#1 and NIC#2 for? Whats the intented use?

Regards,
Shahid
0
System EngineerSystems EngineerAuthor Commented:
Hyper-V NIC 1&2 are the adapters exposed to Hyper-V to use as the virtual networking for all the Guest VM's.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Virtual Server

From novice to tech pro — start learning today.