IP Address Resource Availability
Applies To: Windows Server 2008
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.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-FailoverClustering |
Encountered a failure when attempting to create a new NetBIOS interface while bringing resource '%1' online (error code '%2'). The maximum number of NetBIOS names may have been exceeded. | |
Microsoft-Windows-FailoverClustering |
No matching network interface found for resource '%1' IP address '%2' (return code was '%3'). If your cluster nodes span different subnets, this may be normal. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' cannot be brought online because the subnet mask value is invalid. Please check your IP address resource properties. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' cannot be brought online because the address value is invalid. Please check your IP address resource properties. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' failed to come online. Configuration data for the network adapter corresponding to cluster network interface '%2' could not be determined (error code was '%3'). Please check that the IP address resource is configured with the correct address and network properties. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' cannot be brought online because a duplicate IP address '%2' was detected on the network. Please ensure all IP addresses are unique. | |
Microsoft-Windows-FailoverClustering |
Health check for IP interface '%1' (address '%2') failed (status is '%3'). Run the Validate a Configuration wizard to ensure that the network adapter is functioning properly. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' cannot be brought online because WINS registration failed on interface '%2' with error '%3'. Ensure that a valid, accessible WINS server has been specified. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' cannot be brought online because the cluster network '%2' is not configured to allow client access. Please use the Failover Cluster Management snap-in to check the configured properties of the cluster network. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' failed to obtain a leased IP address. | |
Microsoft-Windows-FailoverClustering |
Lease of IP address '%2' associated with cluster IP address resource '%1' has expired or is about to expire, and currently cannot be renewed. Ensure that the associated DHCP server is accessible and properly configured to renew the lease on this IP address. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' failed to release the lease for IP address '%2'. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' failed to renew the lease for IP address '%2'. Ensure that the DHCP server is accessible and properly configured to renew the lease on this IP address. | |
Microsoft-Windows-FailoverClustering |
IPv6 Tunnel address resource '%1' failed to come online because it does not depend on an IP Address (IPv4) resource. Dependency on at least one IP Address (IPv4) resource is required. | |
Microsoft-Windows-FailoverClustering |
Cluster IP address resource '%1' failed to come online because the '%2' property could not be read. Please ensure that the resource is correctly configured. | |
Microsoft-Windows-FailoverClustering |
IPv6 tunnel address resource '%1' failed to come online. Cluster network '%2' associated with dependent IP address (IPv4) resource '%3' does not support ISATAP tunneling. Please ensure that the cluster network supports ISATAP tunneling. |