Design hyper-v cluster

Question

Hello,

I need to install my first hyper-v cluster for a customer.
I will have 2 nodes with 8 nics.
2 are reserved for datacore.
I have 6 ports for cluster (management, live migration, csv, vm).

I have 2 main questions :

What do you think about this design :
2x VM
2x live migration
1x management
1x csv
or I do
2x VM
2x management
2 x csv + live migration

Then, my second question is about how do you choose network ?
I need to have 1 vlan for management + 1 vlan for csv + 1 vlan for live migration + 1 vlan for vm ?
I know management and VM are "mandatory" but what about live migration and csv ? I would like to find step by step done by microsoft but I don't...
And lot of link I find on internet doesn't show network configuration.

Thanks for your help

Answer 1

Its good idea if you segrate network for csv, live migration and user VM , But its all depends on your requirements and availabity of ports

Here are some good articles to design cluster network

https://www.altaro.com/hyper-v/virtual-networking-configuration-best-practices/

https://ramprasadtech.com/network-recommendations-for-a-hyper-v-cluster-in-windows-server/

https://www.vembu.com/blog/windows-server-hyper-v-cluster-networks/

https://www.vembu.com/blog/hyper-v-networking-best-practices/

Answer 2

Thank you for your answer.

It's good articles about design yes.

When you have 4 network, you need to use 4 VLAN ? or it's not mandatory to setup VLAN for live migration / csv ?

With these 2 node (with datacore on VM) and 1 nas my idea is to use disk witness from NAS. For this, I need to use it as iSCSI.
If I use windows teaming to connect to it, I don't need multipath right ?
Then, do I need to dedicate a card only for this ? If yes, I think it's better to use file share witness on the setup because there will not have interface with iscsi

Answer 3

Hey,

As for VLANs, it depends on how hosts are connected between each other. In case they are direct attached, you can simply configure NICs to be on their own subnet. Speaking about iSCSI, it is recommended not to use teaming. Multipath is a preferable way to configure NICs with iSCSI. Might help:
https://learn.microsoft.com/en-us/windows-server/failover-clustering/clustering-requirements

In addition, you can use StarWind VSAN as a cluster storage backend for both iSCSI LUNs to use as CSV and for Disk Witness. The following guide covers the configuration process:
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

Cheers,
Alex Bykovskyi
StarWind Software
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose

Answer 4

Thanks for your answer.
What is sure about the design :
2 hyperv node with datacore for storage (same feature as s2d)
1 external nas

This is my environment to work.

I need to create ad forest only for the hyper-v cluster (for live migration benefit) because customer doesn t want to add it on his own domain.

I will have 2x10g + 6x1g for all networks.
2x10 will be for datacore storage.
With 6x1g i need to do all cluster traffic
If I do
2x1g management
2x1g vm
2x1g csv + live migration

How could i do for the disk quorum on my nas ? I really need to use 2 network card only for it ?
I think it s better to use file share witness and create local account maybe ? ( nas is not domain join )

What do you think about my idea ?

Answer 5

Hello @matteu31

I think the discussion on this thread from different users in the community can provide you the information you need:

https://learn.microsoft.com/en-us/answers/questions/104521/what39s-the-network-recommendations-for-hyper-v-cl.html

Hope this helps with your query,

------------------

--If the reply is helpful, please Upvote and Accept as answer--