Event ID 1173 — 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.
|Product:||Windows Operating System|
|Message:||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.|
Allow time for multiple cluster nodes to join or leave cluster
Sometimes when multiple nodes are joining or leaving a cluster at the same time, a node will temporarily stop because multiple changes are happening simultaneously. However, the nodes will recover from this automatically. No action is necessary.
To perform this procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Verifying that the Cluster service is started on all the nodes in a failover cluster
To verify that the Cluster service is started on all the nodes in a failover cluster:
- To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
- If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Nodes.
- View the status for each node. If a node is Up, the Cluster service is started on that node.
Another way to check whether the Cluster service is started is to run a command on a node in the cluster.
Using a command to check whether the Cluster service is started on a node
To use a command to check whether the Cluster service is started on a node:
On the node that you are checking, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
CLUSTER NODE /STATUS
If the node status is Up, the Cluster service is started on that node.