Node Membership in Cluster
Applies To: Windows Server 2008 R2
Failover cluster nodes must have the ability to start the Cluster service, form a cluster (when a given node starts but no other nodes are up) and join a cluster (when a given node starts and discovers that one or more nodes are already up). This requires that certain conditions be met, for example, failover cluster nodes must run compatible versions of the operating system.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-FailoverClustering |
Cluster node %1 has been evicted from the failover cluster. | |
Microsoft-Windows-FailoverClustering |
The node failed to join failover cluster '%1' due to error code '%2'. | |
Microsoft-Windows-FailoverClustering |
Failed to form cluster '%1' with error code '%2'. Failover cluster will not be available. | |
Microsoft-Windows-FailoverClustering |
The Cluster service cannot identify node '%1' as a member of failover cluster '%2'. If the computer name for this node was recently changed, consider reverting to the previous name. Alternatively, add the node to the failover cluster and if necessary, reinstall clustered applications. | |
Microsoft-Windows-FailoverClustering |
Cluster service is shutting down because the membership engine detected a membership event while trying to join the server cluster. Shutting down is the normal response to this type of event. Cluster service will restart per the Service Manager's recovery actions. | |
Microsoft-Windows-FailoverClustering |
Security Handshake between Joiner and Sponsor did not complete in '%1' Seconds, node terminating the connection | |
Microsoft-Windows-FailoverClustering |
Sponsor node failed to Authorize the client request, Check whether the cluster service account at the Sponsor and the joiner nodes are the same | |
Microsoft-Windows-FailoverClustering |
Node '%1' failed to form a failover cluster. This was due to one or more nodes executing incompatible versions of the cluster service software. If node '%1' or a different node in the cluster has been recently upgraded, please re-verify that all nodes are executing compatible versions of the cluster service software. | |
Microsoft-Windows-FailoverClustering |
Node '%1' attempted to join a failover cluster but failed due to incompatibility between versions of the cluster service software. If node '%1' or a different node in the cluster has been recently upgraded, please verify that the changed cluster deployment with different versions of the cluster service software is supported. | |
Microsoft-Windows-FailoverClustering |
Node '%1' established a communication session with node '%2' and detected that it is running a different but compatible version of the cluster service software. It is recommended that the same version of the cluster service software be installed on all nodes in the cluster. | |
Microsoft-Windows-FailoverClustering |
Node '%1' established a communication session with node '%2' without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported. | |
Microsoft-Windows-FailoverClustering |
Node '%1' formed a failover cluster without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported. | |
Microsoft-Windows-FailoverClustering |
Node '%1' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software. | |
Microsoft-Windows-FailoverClustering |
Node '%1' failed to establish a communication session while joining the cluster. This was due to an authorization failure. Please verify that the nodes are running compatible versions of the cluster service software. | |
Microsoft-Windows-FailoverClustering |
The cluster service has detected that the failover cluster virtual adapter has stopped. This is expected when hot replace CPU is performed on this node. Cluster service will stop and should automatically restart after the operation is complete. Please check for additional events associated with the service and ensure that the cluster service has been restarted on this node. |