Communication was lost and reestablished between cluster nodes

Microsoft.Windows.2008.R2.Cluster.Communication.was.lost.and.reestablished.between.cluster.nodes (Rule)

Knowledge Base article:

Podsumowanie

A failover cluster requires network connectivity among nodes and between clients and nodes. Problems with a network adapter or other network device (either physical problems or configuration problems) can interfere with connectivity.

Event Details

Identyfikator zdarzenia:

1592

Źródło:

Microsoft-Windows-FailoverClustering

Symbolic Name:

CLUSSVC_TCP_RECONNECT_CONNECTION_REESTABLISHED

Message: Cluster node '%1' lost communication with cluster node '%2'. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Rozwiązania

Check network adapter and other network hardware

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." After reviewing event messages, choose actions that apply to your situation:

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.

Using the Validate a Configuration Wizard to review the network configuration

To use the Validate a Configuration Wizard to review the network configuration:

Opening Event Viewer and viewing events related to failover clustering

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

Verify

Restart the Cluster service, confirm that the nodes come up successfully and that the clustered networks are functioning.

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

To restart the Cluster service on a node and confirm the status of the nodes and networks:

Element properties:

TargetMicrosoft.Windows.2008.R2.Cluster.Monitoring.Service
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Communication was lost and reestablished between cluster nodes
{0}

Member Modules:

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

Source Code:

<Rule ID="Microsoft.Windows.2008.R2.Cluster.Communication.was.lost.and.reestablished.between.cluster.nodes" Enabled="true" Target="Clus2008Library!Microsoft.Windows.2008.R2.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.2008.Cluster.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>1592</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>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.2008.R2.Cluster.Communication.was.lost.and.reestablished.between.cluster.nodes.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>