best practice on Cluster network

John JY 221 Reputation points
2021-09-08T15:10:11.043+00:00

Hi all,

We built windows 2016/2019 cluster with only one NIC
on two virtual VMs. Is this best practice?
should we have two NICs (one for data, one for private
heartbeat)?

Thank you!

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
969 questions
0 comments No comments
{count} votes

Accepted answer
  1. Leon Laude 85,701 Reputation points
    2021-09-08T16:22:17.227+00:00

    Hi @John JY ,

    I'm not sure if there are best practices for this, however there certainly are good practices.
    From experience in the field it would be better with at least two (2) NICs, but this may depend entirely on the cluster, the purpose of the cluster and cost.

    I would really recommend for you to go through John's very detailed post about Failover Clustering and networking basics/fundamentals in the post below:
    https://techcommunity.microsoft.com/t5/failover-clustering/failover-clustering-networking-basics-and-fundamentals/ba-p/1706005

    The above post should give you the essential information and some good practices.

    ----------

    If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

    Best regards,
    Leon


3 additional answers

Sort by: Most helpful
  1. Limitless Technology 39,461 Reputation points
    2021-09-09T07:29:31.187+00:00

    Hello John,

    As reference you can read this article: https://techcommunity.microsoft.com/t5/failover-clustering/no-such-thing-as-a-heartbeat-network/ba-p/388121

    But all in all with one NIC you are ready to go with a Cluster service. Basically you can run the Cluster with 1 network, in the case that the NIC in one node fails, heartbeat will fail, this node will be removed from the membership and all roles moved to other available node. However, in case the virtual switch fails, it will fail for all members and the cluster will be down. The main recommendation is to create a separate network for heartbeat, as it is lightweight but important and you would like to avoid at all cost any heartbeat package lost that may bring down the cluster. However, if your network bandwidth is solid and the network usage is low for the cluster, one network is still an option.

    Everything depends on the usage or purpose of the cluster itself.

    Hope this helps with your query,
    Best regards,


  2. John JY 221 Reputation points
    2021-09-13T15:16:47.693+00:00

    @Limitless Technology

    From the link https://techcommunity.microsoft.com/t5/failover-clustering/no-such-thing-as-a-heartbeat-network/ba-p/388121 and see the picture on stretch site, I did not see a dedicated heartbeat network created?

    131579-strech-site.png

    131664-strech-site.png

    can you explain on this? Thank you!

    0 comments No comments

  3. John JY 221 Reputation points
    2021-09-13T15:41:08.637+00:00

    Hi all,

    after reading https://techcommunity.microsoft.com/t5/failover-clustering/no-such-thing-as-a-heartbeat-network/ba-p/388121, it seems that there is no need to set up a dedicated network for heartbeats.

    Can anyone help out whether my view of this article is right or not?

    Thank you!