The VCS (Cluster Server) node shows a node as disconnected in the System Connectivity tab, in the Java Console.
Event ID 11306 "Did not Receive Cluster Membership manual intervention may be needed for seeding.
This behavior has been observed when the "Microsoft Network Monitor 3" driver is bound to the network interfaces that are used for cluster heartbeats.
Follow these steps, on all nodes of the cluster, to unbind the Microsoft Network Monitor 3 Driver from the heartbeat network interfaces.
1. Stop HAD, GAB and LLT by using the procedure in the following technote:
How to stop and restart the VCS Cluster Engine (HAD), GAB & LLT without taking production cluster groups, or resources, offline in Veritas Storage Foundation HA for Windows
2. From Window Network Properties (ncpa.cpl) select the heartbeat network interface and click "Properties."
3. Uncheck "Network Monitor 3 Driver" and click "OK" (Figure 1). Repeat Steps 2 and 3 for any other heartbeat network interfaces.
Note: Do not perform this step if LLT is not stopped. This may cause the dialog box to become unresponsive. If you are unable to stop GAB, or LLT, a server reboot is required.
4. Restart HAD, GAB and LLT, using the procedure described in TECH53516.
We also recommend performing a test reboot of the node, when possible, to confirm that the server is still able to shutdown and restart gracefully.