Hi,
I have <g class="gr_ gr_45 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" data-gr-id="45" id="45">setup</g> a 2 node Server 2016 hyper-v cluster and passed the validation wizard. I have a team switch created from 4 NIC's, I have my windows firewall disabled on both nodes and no <g class="gr_ gr_46 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="46" id="46">anti virus</g> software installed. I confirmed network connectivity. But while performing some tests I encountered the following issue:
When the team switch is disabled or if there is a network failure there is a loss of cluster communication and once it's enabled again or the network connection restored, we are unable to manage the cluster from the local cluster nodes. But using remote cluster management does work. The error that is occurring is:
ErrorFailoverClustering Manager4683MMC SnapinFailover Cluster Manager failed while managing one or more cluster. The error was An attempt to connect to the cluster failed due to one or more nodes not responding to WMI calls. This is usually caused by a problem with the WMI infrastructure on the nodes. The following is a list of the nodes that encountered this problem when the connection to the cluster was attemptedNODE2 For more information see the Failover Cluster Manager Diagnostic channel.
And this error:
ErrorDistributedCOM10028NoneDCOM was unable to communicate with the computer using any of the configured protocols; requested by PID 214c (C:\Windows\system32\mmc.exe).
The only way for me to resolve this issue is to reboot both nodes.
All my searches suggest that its a WMI bug, but the problem with that suggestion is that I CAN connect to the cluster remotely without a problem.
Here are some articles with similar issues but none seem to resolve my issue, the only way I am able to resolve is by performing a reboot, but I can't just reboot in a live environment:
https://social.technet.microsoft.com/Forums/en-US/99aa09c9-6d68-4e9a-bb20-9b34a468eb42/unable-to-connect-to-cluster-using-failover-cluster-manager?forum=winserverClustering
https://blog.workinghardinit.work/2017/09/08/an-error-occurred-connecting-to-the-cluster/
https://blogs.msdn.microsoft.com/clustering/2010/11/23/trouble-connecting-to-cluster-nodes-check-wmi/
https://sqlsanctum.wordpress.com/2016/09/21/failover-cluster-manager-connection-error-fix/
https://community.spiceworks.com/topic/639445-connecting-to-server-2012-hyper-v-cluster-throws-the-rpc-server-is-unavailable