Hi,
I have <g class="gr_ gr_73 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling ins-del" data-gr-id="73" id="73">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_78 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling ins-del multiReplace" data-gr-id="78" id="78">anti virus</g> software installed. I confirmed network connectivity. But while performing some tests <g class="gr_ gr_80 gr-alert gr_tiny gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling multiReplace" data-gr-id="80" id="80">i</g> 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 Snapin
Failover 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 attempted
NODE2
For more information see the Failover Cluster Manager Diagnostic channel.
And this error
ErrorDistributedCOM10028None
DCOM was unable to communicate with the computer SVR3-NYC1 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 <g class="gr_ gr_68 gr-alert gr_tiny gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling multiReplace" data-gr-id="68" id="68">i</g> CAN connect to the cluster remotely without a problem