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
Identyfikator zdarzenia: | 1576 |
Źródło: | Microsoft-Windows-FailoverClustering |
Symbolic Name: | RES_NETNAME_DNS_REGISTRATION_SECURE_ZONE_REFUSED |
Message: Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'. |
Check events related to updating a DNS record
Check your DNS server event log or WINS server event log for further information. If needed, generate a network trace to see what happened during the process of accessing the DNS server or WINS server.
If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain."
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 viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Finding more information about the error codes that some event messages contain
To find more information about the error codes that some event messages contain:
View the event, and note the error code.
Look up more information about the error code in one of two ways:
Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).
Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:
NET HELPMSG errorcode
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 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 expand Services and Applications.
In the console tree, click a clustered service or application.
In the center pane, view the status of the Network Name resource you want to verify.
If a Network Name resource is offline, to bring it online, in the center pane, right-click the resource and then click Bring this resource 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:
On a node in the cluster, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type:
CLUSTER RESOURCE ResourceName /STATUS
If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.
Target | Microsoft.Windows.2008.R2.Cluster.Monitoring.Service | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.2008.Cluster.EventProvider | Default |
WA | WriteAction | Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription | Default |
<Rule ID="Microsoft.Windows.2008.R2.Cluster.Cluster.network.name.resource.failed.to.register.in.secure.DNS.zone.because.record.was.already.registered.and.owned" 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>1576</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.Cluster.network.name.resource.failed.to.register.in.secure.DNS.zone.because.record.was.already.registered.and.owned.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>