Compartir a través de

Event ID 1360 — Cluster Network Connectivity

  • Artículo

Applies To: Windows Server 2008

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

Product: Windows Operating System
ID: 1360
Source: Microsoft-Windows-FailoverClustering
Version: 6.0
Symbolic Name: RES_IPADDR_INVALID_NETWORK
Message: Cluster IP address resource '%1' failed to come online. Ensure the network property '%2' matches a cluster network name or the address property '%3' matches one of the subnets on a cluster network. If this is an IPv6 Address type, please verify that the cluster network matching this resource has at least one IPv6 prefix that is not link-local or tunnel.

Resolve

Check IP resource configuration

Compare the properties of the IP Address resource with the properties of the corresponding network to ensure that the network and subnet information matches. If this is an IPv6 resource, make sure that the cluster network for this resource has at least one IPv6 prefix that is not link-local or tunnel.

If you do not currently have Event Viewer open, see the procedure that follows to open it.

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

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:

  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.
  4. Expand the console tree under Nodes.
  5. Right-click the node that you want to start and then click More Actions. If Stop Cluster Service is available, click it. Otherwise, skip to the next step.
  6. Right-click the node that you want to start, click More Actions, and then click Start Cluster Service.
  7. Repeat the previous two steps for any other nodes you want to start.
  8. Click Nodes and then view the status of the nodes in the center pane. If a node is Up, the Cluster service is started on that node.
  9. In the console tree, click Networks and then view the status of the networks.

Cluster Network Connectivity

Failover Clustering