w w w . d e l l . c o m s u p p o r t . d e l l . c o m
20On node 2, open Disk Management.
21Ensure that the drive letters for node 2 are correct.
To modify the drive letters on node 2, repeat step 7 through step 9.
Installing and Configuring MSCS
MSCS is a software component in Windows 2000 and an integrated service in Windows Server 2003. MSCS performs the basic cluster functionality, which includes membership, communication, and failover management. When MSCS is installed properly, the service starts on each node and responds automatically if one of the nodes fails or goes offline. To provide application failover for the cluster, the MSCS software must be installed on both cluster nodes. See "Using MSCS" for more information.
NOTE: For systems with split backplane modules installed, the cluster installation tries to use the logical drives on the secondary backplane as cluster disks. Because these drives are not accessible to all nodes in the cluster, ensure that they are removed from the cluster after the installation is complete.
NOTE: In Windows Server 2003, mapping a network drive to the same drive letter as a cluster disk resource renders the cluster disk inaccessible from Windows Explorer on the host. Ensure that mapped network drives and cluster disks are never assigned the same drive letter.
Verifying Cluster Readiness
To ensure that your server and storage systems are ready for MSCS installation, ensure that these systems are functioning correctly and verify the following:
•All cluster servers are able to log on to the same domain.
•The shared disks are partitioned and formatted, and the same drive letters that reference logical drives on the shared storage system are used on each node.
•For each attached PowerVault 22xS storage system, the
•Cluster mode is enabled on all PERC RAID adapters connected to shared storage.
•The controller’s SCSI IDs (6 or 7) on each node are different.
•All peer PERC RAID adapters are connected to the same PowerVault system through the same channel number.
•All IP addresses and network names for each system node are communicating with each other and the rest of the network. The private IP addresses should not be accessible from the LAN.
48