Guest Cluster Windows Server 2019 Core. NIC configure.

Alex Vasilev 1 Reputation point
2020-12-20T17:53:30.643+00:00

Hello!

I'm going to build a new hyper-v cluster based on Windows Server 2019 Core on 4 nodes. I'm planning to create the following 5 NIC

Management
Live Migration
Cluster
Sevicese
Storage Network

Should I create separate 5 NIC for first level cluster and guest cluster?
Are there any articles with powershell commands for their creation and configure? GUI of failover cluster doesn't let to work with 5 traffic ways.

Grateful for the help!

Windows for business | Windows Server | Storage high availability | Clustering and high availability
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Mico Mi 1,936 Reputation points
    2020-12-21T08:44:47.483+00:00

    Hi,
    In a cluster, each server must have a management NIC, storage server and each node need a storage NIC for storage services. According to your description, each node also needs three NICs, of which a Cluster NIC, a Migration NIC and also a Sevicese NIC you mentioned.
    Here is the article about configuring cluster network using PowerShell (but not have many NIC types) and I hope it can be helpful for you:
    https://www.bursky.net/index.php/2014/07/windows-server-2012-failover-cluster-network-config-powershell-script/

    Thanks for your time!
    Best Regards,
    Mico Mi

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

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments

  2. Alex Vasilev 1 Reputation point
    2020-12-27T00:40:27.553+00:00

    Thanks a lot!
    But there are only information about interfaces creation and IP settings.

    How can I manage traffic between the NICs? I see only three ways in Failover Custer Manager.

    Did anyone test confuguration with more then three NICs per node? When does it add redandency, fault tolerance, flexibility and etc? May be it is bad system design? Or can be used in spesific situation?


  3. Alex Vasilev 1 Reputation point
    2020-12-29T18:11:59.363+00:00

    4 Physical Servers in one cluster
    4 VM Servers on this custer in one Guest Cluster
    On the Guest Clustet I'll setup VMs with soft for company. This soft can't stop working more then few seconds.

    0 comments No comments

  4. Mico Mi 1,936 Reputation points
    2020-12-30T06:27:27.873+00:00

    Hi,
    When you want the traffic to communicate with the external, you can create an external switch and connect to you NIC.
    The external switch is bound to a physical NIC of the Hyper-V host. It gives virtual machines access to a physical network to communicate with servers and clients on an external network. Allows virtual machines on the same Hyper-V server to communicate with each other.
    And the internal switch allows communication between virtual machines on the same Hyper-V server, and between the virtual machines and the management host OS.
    The private switch only allows communication between virtual machines on the same Hyper-V server. This type of network is useful when you must create an isolated networking environment, like an isolated test domain.
    If you select External, you can see the following choice.
    52137-image.png
    When you select “Allow management operating system to share this network adapter”, the host can use any of the settings that you configure for the virtual switch like Quality of Service (QoS) settings, security settings, or other features of the Hyper-V virtual switch.

    According to three types of traffic, there are three settings:

    • Allow cluster communication (intra-node heartbeat, configuration updates, and Cluster Shared Volume traffic)
    • Allow client connectivity to cluster resources (includes cluster communication) and cluster communications (you cannot choose client connectivity without cluster connectivity)
    • Prevent participation in cluster communications (often used for iSCSI and sometimes connections to external SMB storage)

    In cluster management>network>properties, we can see the following choices:

    • Allow cluster network communication on this network AND Allow clients to connect through this network: use these two options together for the management network. Important: The adapters in these networks SHOULD register in DNS.
    • Allow cluster network communication on this network ONLY (do not check Allow clients to connect through this network): use for any network that you wish to carry cluster communications (remember that includes CSV traffic). Do not use for iSCSI networks. Important: The adapters in these networks SHOULD NOT register in DNS.
    • Do not allow cluster network communication on this network: Use for storage networks, especially iSCSI.

    Also here are some docs that may be helpful for you:

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

    https://www.altaro.com/hyper-v/architect-networks-hyper-v-cluster/

    Thanks for your time!
    Best Regards,
    Mico Mi

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

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.