Event ID 1047 — IP Address Resource Availability

Applies To: Windows Server 2008 R2

In a cluster, an IP Address resource is important because in most cases, other resources (such as a Network Name resource) depend on it. An IP Address resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Event Details

Product: Windows Operating System
ID: 1047
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: RES_IPADDR_INVALID_ADDRESS
Message: Cluster IP address resource '%1' cannot be brought online because the address value is invalid. Please check your IP address resource properties.

Resolve

Check IP address settings

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." After reviewing event messages, check the following:

  • Check the address, subnet, and network properties of the IP Address resource. For more information, see "Viewing properties of an IP Address resource in a cluster."
  • If the resource is an IPv6 Tunnel address resource, make sure it depends on at least one IP Address (IPv4) resource. (For information about viewing dependencies between resources, see "Viewing properties of an IP Address resource in a cluster.") Also make sure the network supports Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunneling.
  • If the IP Address resource appears to be configured correctly, check the condition of network adapters and other network components used by the cluster.

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.

Viewing properties of an IP Address resource in a cluster

To view properties of an IP Address resource in a cluster:

  1. 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.
  2. 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.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
  4. In the console tree, click a clustered service or application.
  5. In the center pane, expand the Name listing for the clustered service or application.
  6. Right-click the IP Address resource you want to view, and then click Properties.
  7. View the properties of the resource. If you also want to view the dependencies for the resource, click the Dependencies tab.

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

  1. 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 Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. 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.
  4. 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:

  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:

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 an IP Address resource can come online

To verify that an IP Address resource can come online:

  1. 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.
  2. 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.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
  4. In the console tree, click a clustered service or application.
  5. In the center pane, expand the Name listing for the clustered service or application that uses the IP Address resource that you want to verify. View the status of the IP Address resource.
  6. If an IP Address resource is offline, to bring it online, 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:

  1. On a node in the cluster, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. 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.

IP Address Resource Availability

Failover Clustering