I was using a "Syba Dual Port Gigabit Ethernet PCI Express 2.1 PCI-E x1 Network Adapter Card RTL8111" in both nodes. I removed them to try an Intel PRO/1000 PT adapter. BOOM. Works now! Seems like you can't put just any NIC into a node?
Heartbeat 2019 S2D keeps showing Partitioned
I've got one NIC connected to the domain. The other NIC is connected to the other node using a simple switch (no crossover cable). Each node can ping the other using the Cluster IP (only IP and subnet mask are entered). But I'm getting "Partitioned" as the status. My main domain IP shows "Up" as the status and "Cluster and Client" as the "Cluster Use" column. The "Cluster Network 1" shows "Cluster Only" under the column "Cluster Use".
I've got 'Client for Microsoft Networks', 'File and Printer Sharing for Microsoft Networks', IPv4, 'LLDP Protocol Driver', and the two 'Link-Layer Topology' items all checked.
I've disabled power mgt on the Cluster NICs, and disabled offload.
Nothing. Any help is appreciated!
2 additional answers
Sort by: Most helpful
-
Xiaowei He 9,871 Reputation points
2020-09-11T06:29:43.577+00:00 Hi,
The cluster network "Partitioned" status usually caused by incorrect network configurations, and the heartbeat packet UDP 3343 unable to send between the two NICs.
Please try to run ipconfig /all on the two nodes, ensure the NICs in the "Partitioned" network are configured with an IP address. Please ensure the NICs on the nodes can ping with each other.
If IP settings are well, please check if there's any firewall between the nodes, if yes, please try to turn off the firewall, try to re-enable the NIC and update the network adapter driver, check if the methods could help.
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.
-
TimCerling(ret) 1,156 Reputation points
2020-09-12T13:53:00.34+00:00 You should also run the cluster verification tool. It does a pretty good job of explaining any anomalies in the cluster configuration. With the issue you are having, I would pay particular attention to any warnings raised.