To view the most current Windows Server 2000 and Windows Server 2003 Cluster Solutions list, visit the following Microsoft Web site:
Note When you click any of the arrows next to the search boxes in the left navigation pane, the search boxes will simultaneously filter the results by the text that you typed in all the search boxes.
Windows Server 2008 Cluster solutions will not be listed in the Windows Server Catalog. For more information, visit the following Failover Clustering Configuration Program Web site:For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Note For more information about the WSC and the HCL for other Microsoft operating systems, visit the following Microsoft Web site:
- Two or more servers that are referred to as the cluster nodes.
- A mass-storage controller and drives in each node from which the operating system boots.
- A separate mass-storage controller (SCSI or Fibre) that is independent of the controller that is used to boot the operating system.
- The shared disk. This is typically an external cabinet to which the mass-storage controller is attached that is connected to all nodes in the cluster.
- Two network adapters in each cluster node.
However, there may still be configuration issues with an HCL-compliant or a WSC-compliant cluster. Therefore, we recommend that you run the Microsoft Cluster Configuration Validation Wizard to determine any potential configuration problems before you configure a Windows 2000 server cluster or a Microsoft Windows Server 2003 server cluster. To download the Microsoft Cluster Configuration Validation Wizard, visit the following Microsoft Web site:
Press I Agree to accept these conditions.
Microsoft does not support hardware configurations other than those listed in the Cluster category of the Hardware Compatibility List (HCL) located at
To indicate that you understand that Microsoft does not support hardware configurations that are not listed in the Cluster category of the HCL, click I Understand.
SAN, Geographically dispersed clusters, and Windows 2000 Datacenter ServerIf multiple clusters are attached to the same storage area network (SAN) device, extra steps are required. The nodes in the cluster must be certified with the particular SAN device. The SAN device itself must be certified as Multi-Cluster capable and listed in the Cluster/Multi-Cluster Device category.
If the cluster solution includes geographically dispersed cluster nodes, additional items such as network latency and shared disk support must be verified. The entire cluster solution must be listed in the Cluster/Geographic category. See the following Microsoft Knowledge Base article for details:
Clusters that are not listed on the HCL in the cluster categoryIf your cluster solution is not listed on the HCL or WSC in the Cluster category, the cluster solution is considered unsupported. However, PSS will offer troubleshooting tips if the customer requests them. PSS does not guarantee that a resolution will be found for non-HCL or non-WSC Clusters.
Steps for support
- Before any troubleshooting begins, the customer must contact the OEM to discuss whether the particular cluster implementation is supportable. The OEM can best answer configuration and supportability questions for the cluster hardware.
- Upon agreement that no solution is guaranteed, and that no incident refund will be given, PSS troubleshoots the issue. Microsoft does not guarantee a solution with non-HCL or non-WSC clusters. If no resolution is found, the incident is not refunded.
If it is not agreed that a solution is not guaranteed, PSS will not troubleshoot the issue and will refund the incident.
- Standard troubleshooting processes will be used to isolate the server cluster issue. Some typical troubleshooting methods that will be used by PSS include:
- The Microsoft Knowledge Base is available to customers through Microsoft TechNet and the following Microsoft Web site:
- Determine whether the problem can be replicated on supported clusters (where possible).
- If there is no solution to the problem, PSS may recommend some constructive alternatives, including:
- Having the customer reproduce the problem on a cluster that is on the Cluster HCL or WSC.
- Using a cluster solution that is on the Cluster HCL or WSC.
- Having the customer work with the OEM to get the cluster on the Cluster HCL or WSC.
- Working with the OEM for a solution.
Some examples of hardware incompatibilities that can cause cluster problems include:
- The cluster solution does not properly isolate the shared disk and HBAs from other devices on the shared bus.
- The SCSI controller does not support operating in a multiple-initiator environment.
- The HBA does not properly handle reservations or release or renew a device on the shared bus.
- The caching mechanism on the controller is incompatible with the cluster configuration.
- The network adapters for intra-cluster communication have too high a latency.
- The RAID controller does not properly replicate configuration information between controllers.
- The PCI bus is incorrectly configured and has incorrect adapters in the wrong bus (primary, secondary, tertiary, and so on).
- The controllers are incompatible the "Physical Disk Resource" type.
- The SCSI controller does not deploy proper termination.
If a complete cluster configuration is listed for an earlier operating system but is not listed for the newer operating system that you are using, support as documented in this section will be followed.
Article ID: 309395 - Last Review: Jan 17, 2014 - Revision: 1