Selecting A Domain Model; Configuring The Cluster Nodes As Domain Controllers - Dell PowerEdge Cluster SE500W Installation And Troubleshooting Manual

9 Configure the MSCS software.
The MSCS software is the clustering component of the Windows operating system that
provides the failover capabilities for the cluster.
See "Installing and Configuring MSCS" for more information.
10 Verify cluster functionality. Ensure that:
• Your cluster components are communicating properly with each other.
• MSCS is started.
See "Verifying Cluster Functionality" for more information.
11 Verify cluster resource availability.
Use Cluster Administrator to check the running state of each resource group.
See "Verifying Cluster Resource Availability" for more information.
The following sections provide detailed information for each step in the "Installation Overview"
that is specific to your Windows operating system.
NOTE:
Dell strongly recommends that you use the "PowerEdge Cluster SE500W Solution Data Form"
during the installation of your cluster to ensure that all installation steps are completed. The data form is
located in "Cluster Data Form."

Selecting a Domain Model

On a cluster running the Windows operating system, both cluster nodes must belong to a
common domain or directory model. The following membership configurations are supported:
• Both cluster nodes are member servers in an Active Directory domain.
• Both cluster nodes are domain controllers in an Active Directory domain.
• One cluster node is a domain controller in an Active Directory, and the other cluster node is a
member server.

Configuring the Cluster Nodes as Domain Controllers

If a cluster node is not configured as a domain controller and the node cannot contact a domain
controller, the cluster node will not be able to authenticate client requests.
If a cluster node is configured as a domain controller, client access to its cluster resources can
continue if the cluster node cannot contact other domain controller(s). However, domain
controller functions can cause additional overhead, such as log on, authentication, and
replication traffic on the cluster nodes.
Preparing Your Systems for Clustering
31