Cluster network name resource cannot be brought online due to a timeout

Microsoft.Windows.2008.R2.Cluster.Management.Monitoring.Cluster.network.name.resource.cannot.be.brought.online.due.to.a.timeout (Rule)

Knowledge Base article:

Sammanfattning

In a cluster, a Network Name resource can be important because other resources depend on it. A Network Name resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Event Details

Händelse-ID:

1566

Källa:

Microsoft-Windows-FailoverClustering

Symbolic Name:

RES_NETNAME_TIMEDOUT

Message: Cluster network name resource '%1' cannot be brought online. The network name resource was terminated by the resource host subsystem because it did not complete an operation in an acceptable time. The operation timed out while performing:%n '%2'

Lösningar

Check Active Directory configuration

If you do not currently have Event Viewer open, see "Opening Event Viewer and view events related to failover clustering." After reviewing event messages, check the following:

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.

Opening Event Viewer and view events related to failover clustering

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

Verify

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.

Verifying that a Network Name resource can come online

To verify that a Network Name resource can come online:

To perform a quick check on the status of a resource, you can run the following command.

Using a command to check the status of a resource in a failover cluster

To use a command to check the status of a resource in a failover cluster:

CLUSTER RESOURCE ResourceName /STATUS

If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.

Element properties:

TargetMicrosoft.Windows.2008.R2.Cluster.Monitoring.Service
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
Cluster network name resource cannot be brought online due to a timeout
{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.Management.Monitoring.Cluster.network.name.resource.cannot.be.brought.online.due.to.a.timeout" Enabled="onEssentialMonitoring" 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>1566</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.2008.R2.Cluster.Management.Monitoring.Cluster.network.name.resource.cannot.be.brought.online.due.to.a.timeout.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>