Partager via

Event ID 1583 — Network Connectivity and Configuration

  • Article

Applies To: Windows Server 2008 R2

Each node in a failover cluster requires network connectivity with the other 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: 1583
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: CLUSSVC_NETFT_DISABLE_CONNECTIONSECURITY_FAILED
Message: Cluster service failed to disable Internet Protocol security (IPsec) on the Failover cluster virtual adapter '%1'. This could have a negative impact on cluster communication performance. If this problem persists, please verify your local and domain connection security policies applying to IPSec and the Windows Firewall. Additionally, please check for events related to the Base Filtering Engine service.

Resolve

Local and domain security policies can prevent the Cluster service from disabling IPSec on a network adapter used by a failover cluster. If IPSec cannot be disabled, the performance of the cluster can be negatively impacted. Review the policies, or work with a network administrator to review the policies related to IPSec and Windows Firewall with Advanced Security. Also confirm that the Base Filtering Engine service (which manages firewall and IPSec policies) is started on the node. For more information, see "Opening Services and viewing or restarting the Base Filtering Engine service."

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering or the firewall."

Opening Services and viewing or restarting the Base Filtering Engine service

To open Services and view or restart the Base Filtering Engine service:

  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 Yes.
  2. In the console tree, expand Configuration, and then click Services.
  3. In the center pane, right-click the Base Filtering Engine service, and then click Properties.
  4. View the status of the service. If needed, start or restart the service by clicking Start or by clicking Stop and then Start.

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

  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 Yes.
  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.
  5. To clear the filter so that you can view other events, in the Actions pane, click Clear filter.
  6. In the console tree, under Event Viewer, expand Applications and Services Logs, expand Microsoft, and then expand Windows.
  7. Scroll down in the list, expand Windows Firewall with Advanced Security, and then click on a log.

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.

Network Connectivity and Configuration

Failover Clustering