StarWind Software

Hello,

After reading through the resources and forum, we still have some questions:
1. What is the 'minimum' number of gigabit nics needed for a 2 node native san hyperv cluster? It looks like just two per this document:
http://www.starwindsoftware.com/custome ... yper-V.pdf
2. Beyond the minimum number of nics, if we could add just one more nic what would you assign it to and why (ie. sync channel for performance)?
3. We will be setting up a single RAID10 LUN on each node. How would you suggest partitioning this if at all?

Thanks!
Chris

Hi!

1.After reading through the resources and forum, we still have some questions: What is the 'minimum' number of gigabit nics needed for a 2 node native san hyperv cluster? It looks like just two per this document:
http://www.starwindsoftware.com/custome ... yper-V.pdf

StarWind require having at least two NICs per each server (with the same bandwidth of course) - one for SyncChannel and one is for HeartBeat plus iSCSI client traffic. Please note that you will need extra NIC for Hyper-V purposes.

2. Beyond the minimum number of nics, if we could add just one more nic what would you assign it to and why (ie. sync channel for performance)?

I would:) As I mentioned before I'd add 1 NIC for Hyper-V traffic (bandwidth is not important here from the starwind side) and one for the SyncChannel, that allows you to use RR NLB policy and fully utilize network resources (bandwidth should be identical to first two ones)

3. We will be setting up a single RAID10 LUN on each node. How would you suggest partitioning this if at all?

No matter - RAID 10 is perfect. Just don`t put host OS on it.

Good explanation, thank you. Two more questions to clarify:
1) When you say for hyper-v purposes, are you referring to a dedicated nic for hyper-v management? And all LAN traffic would still go through the heartbear nic, correct?
2) Is it not possible to include the host os on the primary partition of the raid 10? For new servers today, it is generally acceptable to make just one big RAID 10 and partition it out to include the host os.

1. I think he means for Virtual Machine traffic. I use the heartbeat nics for cluster/management traffic, but I dedicate 1 port to VM Switch and 1 to Sync Channel. So basic answer for me is 3 NIC's/
2. Not really recommended for Virtual Machine Hosts or iSCSI, in my experience there are too many random reads as it is, and you want every IOP you can get for your VMs. If you are only going to be running 1-2 boring sleepy VMs this really isn't a problem, but the second one of them get's busy...

jeddyatc, you are absolutelly correct again

rrnworks, is there anything else that we can assist you?

Thanks for the info - I think I almost have it figured out:
1) The heartbeat NIC could also be used for the VM switch if you only had two NICs?
2) If you use the hearbeat NICs for cluster/management traffic, I take it you are connecting each to a switch (and not direct NIC to NIC)?

Chris

1) The heartbeat NIC could also be used for the VM switch if you only had two NICs?

HearTbeat is low resource consuming, so it wont affect any other traffic that will run on the same NICs

2) If you use the hearbeat NICs for cluster/management traffic, I take it you are connecting each to a switch (and not direct NIC to NIC)?

Yes, exactly.

Yes my nodes are across campus so I don't have the option of direct connect. I honestly wouldn't use nativesan on a server with only 2 NICs, but I also tend to overload my VM clusters as I build them lol.

rrnworks, have you got any update for us, or some additional questions?