This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You have a Windows Server 2008 R2 failover cluster in a network.
Cluster nodes connect to the network by using hubs. Different nodes may connect to the network by using different hubs, especially in a multi-subnet cluster.
One of the hubs cannot connect to the rest of the network. For example, one of the hubs cannot connect to domain controllers or to public networks.
Nodes that use this hub cannot communicate with the rest of the network.
In this scenario, cluster resources that are owned by these nodes do not fail over automatically to other nodes that have complete network connectivity.
Note You expect that resources that are hosted by the nodes automatically fail over to other nodes that have complete network connectivity.
When a network failure occurs, the Cluster service verifies network connectivity by collecting ping information from cluster nodes. However, the Cluster service does not summarize the ping information correctly. Therefore, an incorrect network topology view is established on the cluster.
This hotfix must be applied to all nodes in the failover cluster. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is 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 Web site:
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.
To apply this hotfix, you must be running Windows Server 2008 R2 on the computer. Additionally, you must have the Failover Clustering feature installed on the computer.
To use the hotfix, you do not have to change the registry.
This hotfix updates Cluster service binaries. Therefore, if this hotfix is applied to the system when the Cluster service starts, the system prompts you to restart the computer so that the hotfix takes effect after you complete the installation.
Generally, you must restart the computer after you apply this hotfix.If you do not want to restart your computer after you apply the hotfix, follow these steps.
Note You must fail over some cluster resources to install the hotfix on all CPU nodes.
Make sure that cluster resources can fail over to the other CPU nodes.
If cluster resources can fail over to other nodes, stop the Cluster service in the Failover Cluster Manager console. If you do this, the cluster resources that are owned by this node may fail over to the other CPU nodes.
Apply this hotfix.
After you install this hotfix, start the Cluster service from the cluster.
Failback cluster resources appropriately.
Repeat this step on other CPU nodes until the hotfix is installed on all CPU nodes.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 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 maintaining the state of the updated component. 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
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about server clusters, visit the following Microsoft TechNet Web site: