Cluster service cannot identify a node as a member of failover cluster

Microsoft.Windows.6.2.Cluster.Management.Monitoring.Cluster.service.cannot.identify.a.node.as.a.member.of.failover.cluster (Rule)

Knowledge Base article:

Summary

Cluster service cannot identify a node as a member of failover cluster

Resolutions

If a change to the computer name of a node appears to have caused a problem, the simplest way to correct it is to revert to the previous computer name.

Note We recommend you change the computer name of a node only when it is necessary.

If reverting to the previous computer name is not workable, you must carry out the following sequence of actions.

If you do not currently have Event Viewer open, also see 'Opening Event Viewer and viewing events related to failover clustering.'

To perform the following procedures, 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.

To evict a node name that is no longer in use:

To run a cleanup command on a renamed node to prepare it to be re-added to the cluster:

For the following procedure, it is assumed that you have already connected the networks and storage to the server that you want to add, and that you have validated the current set of nodes and other hardware that you are using.

To add a node to a failover cluster:

After adding the node, confirm that all necessary applications are installed on the node.

To open Event Viewer and view events related to failover clustering:

Element properties:

TargetMicrosoft.Windows.6.2.Cluster.Monitoring.Service
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
Cluster service cannot identify a node as a member of failover cluster
{0}

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.6.2.Cluster.EventProvider Default
WA WriteAction Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription Default

Source Code:

<Rule ID="Microsoft.Windows.6.2.Cluster.Management.Monitoring.Cluster.service.cannot.identify.a.node.as.a.member.of.failover.cluster" Enabled="true" Target="Clus8Library!Microsoft.Windows.6.2.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.6.2.Cluster.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>1093</Value>
</ValueExpression>
</SimpleExpression>
</Criteria>
<LogName>System</LogName>
<PublisherName>Microsoft-Windows-FailoverClustering</PublisherName>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="ClusLibrary!Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.6.2.Cluster.Management.Monitoring.Cluster.service.cannot.identify.a.node.as.a.member.of.failover.cluster.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>