Changes made to networking when adding to cluster

Question

I'm wondering what exactly is going on behind the scenes when you add a node to a cluster using Failover Cluster Manager?

We had a host that was experiencing issues so was removed from the cluster and rebuilt. When I add this node to the cluster I start to get around 10% packet loss on one of the virtual adapters configured. I say one of them as it's not always the same adapter and I've not figured out a pattern as to which it's affected.

Before adding to the cluster I can setup constant pings and I see zero percent drop, it's only AFTER it's added to the cluster that the problems arise so I assume something is being changed during this process that I was not previously aware of.

Answer 1

Hi,

Generally, adding the node into the cluster won't affect the node's network.

After adding the node into the cluster, does the node running lot of clustered roles? Does the node have a heavy network load? If there's a heavy network load on the node, it might have a network delay.

Thanks for your time!
Best Regards,
Anne

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

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.

Answer 2

It happens with zero load, I initially discovered the problem after a handful of VMs were migrated to it and they were sporadically dropping off the network but the issue occurs even with the node paused.

Remove the host from the cluster and the issue goes away, re-add and it immediately comes back regardless of any roles migrating to it.

I do see the following event pop up each time but I've not found any errors anywhere else to help narrow down the problem;

Cluster network interface 'HOSTNAME - vEthernet (CSV)' for cluster node 'HOSTNAME' on network 'CSV' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.