Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Cluster service initiates a failover after a delay of about 80 seconds when you shutdown the active node in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You configure a failover cluster on some computers that are running Windows Server 2008 R2.
  • You add a crossover cable between two nodes of the cluster.
  • You shutdown the active node of the cluster.
In this scenario, the Cluster service initiates a failover after a delay of about 80 seconds.

Note The Cluster service usually initiates the failover within 5 seconds.

↑ Back to the top


Cause

This issue occurs because the Cluster service incorrectly waits for Global Update Manager (GUM) updates.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    0.
    21xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.1.7600.210104,604,41616-Jul-201105:17x64
Clussvc.exe6.1.7601.217724,604,92816-Jul-201105:24x64
Cluswmi.dll6.1.7600.21010540,16016-Jul-201105:19x64
Cluswmi.mofNot applicable76,75215-Jul-201122:56Not applicable
Cluswmiuninstall.mofNot applicable17615-Jul-201122:56Not applicable
Cluswmi.dll6.1.7601.21772541,69616-Jul-201105:25x64
For all supported IA-64–based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Clussvc.exe6.1.7600.210107,744,00016-Jul-201104:00IA-64
Clussvc.exe6.1.7601.217727,745,53616-Jul-201104:10IA-64
Cluswmi.dll6.1.7600.21010884,22416-Jul-201104:01IA-64
Cluswmi.mofNot applicable76,75215-Jul-201122:43Not applicable
Cluswmiuninstall.mofNot applicable17615-Jul-201122:43Not applicable
Cluswmi.dll6.1.7601.21772886,27216-Jul-201104:12IA-64

↑ Back to the top


Workaround

To work around this issue, add the DisableDHCPMediaSense registry entry on the two cluster nodes. To do this, follow these steps:
  1. Click Startstart button , type regedit in the Start Search box, and then press ENTER.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters
  3. Click Edit, point to New, and then click DWORD Value.
  4. Type DisableDHCPMediaSense, and then press ENTER.
  5. Right-click DisableDHCPMediaSense, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
Note After you change the registry on the two cluster nodes, restart the two clusters nodes to apply the setting.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7600.21010_none_1686c761d42656cc.manifest
File versionNot applicable
File size7,438
Date (UTC)16-Jul-2011
Time (UTC)05:59
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7601.21772_none_182e6d51d17b69ca.manifest
File versionNot applicable
File size7,438
Date (UTC)16-Jul-2011
Time (UTC)06:23
File nameAmd64_microsoft-windows-f..overcluster-cluswmi_31bf3856ad364e35_6.1.7600.21010_none_1934c0a5d26bf0a9.manifest
File versionNot applicable
File size6,668
Date (UTC)16-Jul-2011
Time (UTC)05:57
File nameAmd64_microsoft-windows-f..overcluster-cluswmi_31bf3856ad364e35_6.1.7601.21772_none_1adc6695cfc103a7.manifest
File versionNot applicable
File size6,668
Date (UTC)16-Jul-2011
Time (UTC)06:19
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7600.21010_none_20db71b4088718c7.manifest
File versionNot applicable
File size4,604
Date (UTC)16-Jul-2011
Time (UTC)04:44
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7601.21772_none_228317a405dc2bc5.manifest
File versionNot applicable
File size4,604
Date (UTC)16-Jul-2011
Time (UTC)05:14
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7600.21010_none_1686c761d42656cc.manifest
File versionNot applicable
File size7,438
Date (UTC)16-Jul-2011
Time (UTC)05:59
File nameAmd64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7601.21772_none_182e6d51d17b69ca.manifest
File versionNot applicable
File size7,438
Date (UTC)16-Jul-2011
Time (UTC)06:23
File nameAmd64_microsoft-windows-f..overcluster-cluswmi_31bf3856ad364e35_6.1.7600.21010_none_1934c0a5d26bf0a9.manifest
File versionNot applicable
File size6,668
Date (UTC)16-Jul-2011
Time (UTC)05:57
File nameAmd64_microsoft-windows-f..overcluster-cluswmi_31bf3856ad364e35_6.1.7601.21772_none_1adc6695cfc103a7.manifest
File versionNot applicable
File size6,668
Date (UTC)16-Jul-2011
Time (UTC)06:19
File nameAmd64_microsoft-windows-f..r-cluswmi.resources_31bf3856ad364e35_6.1.7600.21010_en-us_a779814bcdf21446.manifest
File versionNot applicable
File size3,079
Date (UTC)16-Jul-2011
Time (UTC)05:40
File nameAmd64_microsoft-windows-f..r-cluswmi.resources_31bf3856ad364e35_6.1.7601.21772_en-us_a921273bcb472744.manifest
File versionNot applicable
File size3,079
Date (UTC)16-Jul-2011
Time (UTC)05:48
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7600.21010_none_20db71b4088718c7.manifest
File versionNot applicable
File size4,604
Date (UTC)16-Jul-2011
Time (UTC)04:44
File nameWow64_microsoft-windows-f..overcluster-clussvc_31bf3856ad364e35_6.1.7601.21772_none_228317a405dc2bc5.manifest
File versionNot applicable
File size4,604
Date (UTC)16-Jul-2011
Time (UTC)05:14

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2575625
Revision : 1
Created on : 1/7/2017
Published on : 11/7/2012
Exists online : False
Views : 257