Microsoft KB Archive/256628

= How to Install Clustering on a SCSI IBM Server =

Article ID: 256628

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0 Enterprise Edition

-



This article was previously published under Q256628



SUMMARY
The IBM Netfinity Cluster solution using the IBM ServeRAID-3H, IBM ServeRaid 3HB, IBM ServeRaid-3L, IBM ServeRaid 4H, IBM ServeRaid 4L, IBM ServeRaid 4LX, and IBM ServeRaid 4MX SCSI Adapters use existing technology and proprietary software to implement Microsoft Cluster Server using IBM ServeRAID controllers and the IBM ServeRAID NT Cluster Solution utility. Standard installation procedures for Microsoft Cluster Server do not apply to these configurations.

You must configure the cables to the arrays and the controllers according to IBM documentation. Before you perform the steps in this article, contact IBM support and refer to the following document: ServeRAID - IBM Netfinity High Availability Cluster Solutions For IBM ServeRAID-3H and ServeRAID-3HB Installation and User's Guide.

This article describes how to install Microsoft Cluster Server on a SCSI IBM server using a ServeRAID controller. Although this article contains configuration suggestions, you may need to contact IBM support for further assistance.



MORE INFORMATION
Before you perform the installation, refer to IBM support for the location and most recent version of the ServeRAID controllers and the IBM ServeRAID NT Cluster Solution utility, and make sure that your hardware is configured correctly:
 * Check the computer's BIOS and ensure that it is the latest by booting to the latest ServeRaid support CD. The CD will always check the current level and ask to perform an upgrade if needed.
 * Verify in the ServeRAID adapters that the host IDs, partner IDs, and merge groups are all set up correctly using the ServeRaid Support CD. To do this, boot to the CD and then right click the controller. Select Clustering Actions and then configure for clustering. The controller name and partner name will then be listed.
 * Obtain the latest installation software for the IBM ServeRAID NT Cluster Solutions utility off of the ServeRaid support CD. The diskette can be made by booting into Windows NT 4.0 Enterprise Edition and running :\diskette\tools  :\diskette\clusnt.img.
 * Make sure that you are using the most recent ServeRAID device drivers, bios and firmware. They may be created using the same process as the IBM ServeRAID NT Cluster Solution diskette.

Installation Procedure
 Install Enterprise Edition, and then update both servers to Service Pack 3.

NOTE: Do not install Cluster Server at this time. Format all shared logical drives and assign drive letters to them by using the following steps:  On Node1, run the Ipshahto.exe tool to make all the shared logical drives accessible by Node1. From the IBM ServeRAID NT Cluster Solutions utility, run Ipshahto.exe by typing the following command at a command prompt:

a:\support\ipshahto

NOTE: Before you use the Ipshahto.exe tool, perform the following tasks:

 Use the Administration and Monitoring utility to scan for new devices. Check to see if the synchronization of RAID 5 logical drives is finished. You can use the ServeRAID Administration and Monitoring utility to see if any synchronization is running. The status bar will be listed on the bottom of the screen.  Use Disk Administrator (Windisk.exe) to format all shared logical drives as NTFS, assign volume labels, and specify drive letters.</li> On Node2, run Ipshahto.exe to make all shared logical drives accessible by Node2.</li> Use Disk Administrator to assign Node2 with the same drive letters that you assigned to each drive on Node1.

NOTE: The volume label is used as a guide to make sure the same letters you assigned on Node1 are assigned on Node2. It is helpful if part of the volume label that you specify contains the drive letter that is assigned to a drive (for example, drive_E).</li> Run Ipshahto.exe from Node1 again to regain control of all shared logical drives to that server.</li></ol> </li> Install Cluster Server: <ol style="list-style-type: lower-alpha;"> Insert Enterprise Edition CD-ROM 2 in Node1.</li> At a command prompt, type the following command:

\mscs\cluster\i386\setup /localquorum

NOTE: You must use the localquorum command-line option when you install clustering software with an IBM ServeRAID adapter.

A local quorum drive will be used on the server's %SystemRoot% folder. Later in this procedure, the local quorum drive must be moved to a ServeRAID logical array resource.

</li> When the installation is finished, restart Node1.</li></ol> </li> Join Node2 to the cluster: <ol style="list-style-type: lower-alpha;"> Insert Enterprise Edition CD-ROM 2 in Node2.</li> At a command prompt, type the following command:

\mscs\cluster\i386\setup

</li> When the installation is finished, restart Node2.</li></ol> </li> Install the IBM ServeRAID NT Cluster Solution utility: <ol style="list-style-type: lower-alpha;"> On Node1, from the IBM ServeRAID NT Cluster Solution utility, run the Setup.exe program and follow the instructions that appear on the screen.</li> When you are finished with step a, repeat the procedure on Node2.</li> After you install the utility on both servers, all shared ServeRAID groups and disk resources are automatically created by the IBM Cluster Solution Setup program and started.

Note: The IBM ServeRAID Cluster Solution diskette must be run first on the node that owns the drives or the resources will not be created.</li></ol> </li> <li>Move the quorum resource from local quorum to a ServeRAID disk resource: <ol style="list-style-type: lower-alpha;"> <li>From Cluster Administrator, click the cluster you are using.</li> <li>Right-click the cluster, and then click Properties.</li> <li>Click the Quorum tab.</li> <li>In the Quorum Resource area, select a ServeRAID shared disk that you want to use as the shared disk, and then click OK.

NOTE: You need to ensure that the same server (for example, Node1) owns the ServeRAID disk resources and the local quorum resource, and that the quorum resource is moved to a RAID 1 logical drive.</li></ol> </li></ol>

Shared disk resources now appear as "IBM ServeRAID Logical Disk" instead of the default Microsoft physical disk. You can now manually move these resources by using Cluster Administrator or automatically during failover.

<div class="references_section">