Installing a High-Availability Cluster Solution Using Windows NT
Chapter 4. Installing a High-Availability Cluster Solution Using Windows NT
To install a high-availability cluster solution using Windows NT, complete the following procedure.
-Important- Before beginning this procedure, make sure you have:
- Install Microsoft Windows NT Server Enterprise Edition with the update to Service Pack 3 or later, on both servers, but do not
install the Microsoft Cluster Server (MSCS) software.
- When the system prompts you, deselect the option to install MSCS. It will be installed later in this procedure.
For information on installing Windows NT Server Enterprise Edition, refer to the documentation that comes with it.
When you are finished, return here and continue with this procedure.
- Format all shared logical drives and assign drive letters to them by doing the following:
-Important- Before using the IPSHAHTO.EXE program:
- Use the Administration and Monitoring Utility to scan for new devices.
- Check to see if all synchronization of RAID level-5 logical drives is completed.
To check if any synchronization is running, use the ServeRAID Administration and Monitoring Utility.
If arrays are currently being synchronized, a popup window appears showing the progress of the synchronization.
- On server A, run the utility IPSHAHTO.EXE from the ServeRAID NT Cluster Solutions Diskette by typing the
following command from a Windows NT command line or from the Add/Remove Programs control panel:
a:\support\ipshahto
This utility will make all the shared logical drives available for access by server A.
Note: It is helpful if part of the volume label that you assign contains the drive letter that is assigned to a drive,
such as drive_E.
- Using the Windows NT Disk Administrator, format all shared logical drives as NTFS (NT File System), assign volume
labels, and specify drive letters to each.
- On server B, run the same utility, IPSHAHTO.EXE, to make all shared logical drives available for access by server B.
Note: The volume label is used as a guide to make sure the same letters are assigned on server B as were
assigned on server A.
- Using the Windows NT Disk Administrator, assign the same drive letters that you assigned to each drive on server A.
- Run IPSHAHTO from server A again to regain control of all shared logical drives to that server.
- Install the Microsoft Cluster Server (MSCS) software.
Note: The directory name and path where the MSCS software is installed must be the same on both servers.
To start the installation, do the following:
-Important- You must use the localquorum option when installing the
Microsoft Cluster Server (MSCS) software with ServeRAID.
- Insert the Windows NT Server Enterprise Edition Component CD ROM into the CD-ROM drive on Server A and issue the
following command, either from a command line or from Add/Remove Programs in the Control panel:
Note: The "localquorum" parameter must be typed in lowercase
\MSCS\CLUSTER\I386\SETUP /localquorum
Note: A local quorum drive will be installed on the server's local/boot drive.
Later in this procedure, the local quorum drive must be moved to a ServeRAID logical array resource.
Instructions are given when this needs to be done.
- Install the Microsoft Cluster Server software following the instructions in the documentation that comes with the MSCS software.
Server A will restart when the installation is completed.
- To make server B join the cluster, do the following:
Note: The directory name and path where the MSCS software is installed must be the same on both servers.
- Insert the Windows NT Server Enterprise Edition Component CD ROM into the CD-ROM drive on Server B and issue the
following command, either from a command line or from Add/Remove Programs in the Control panel:
\MSCS\CLUSTER\I386\SETUP
- Install the Microsoft Cluster Server software following the instructions in the documentation that comes with the MSCS
software to have Server B join the newly created high-availability cluster solution.
Server B will restart when the installation is completed.
- Make server A the preferred owner of the cluster group by doing the following:
- Run the Cluster Administrator program that comes with the MSCS software.
Refer to the documentation that comes with the MSCS software for instructions.
- Select the Cluster Group.
- Display its properties window by selecting File; then, selecting Properties.
- Click on Modify next to the Preferred Owner text box.
- Select Server A and move it to the right side, into the Preferred Owners panel.
- Click on OK.
Server A appears in the Preferred Owners text box.
- Make sure that the Cluster Group has failover enabled.
For instructions on how to do this, refer to the documentation that comes with the Microsoft Cluster Services package.
- Close the connection to the cluster and open it again to ensure that the connection is through server A.
- Install the IBM ServeRAID NT Cluster Solution utility by doing the following:
- From server A, run the SETUP.EXE program from the ServeRAID NT Cluster Solution Diskette and follow the
instructions that appear on the screen.
- When complete, repeat the procedure from server B.
Upon completion of the installation of the utility on both servers, all shared ServeRAID groups
and disk resources will be automatically created by the IBM Cluster Solution setup program and
then brought online.
Server A will be the current owner of these groups.
- Move the quorum resource from Local Quorum to a ServeRAID disk resource by doing the following:
- From the Cluster Administrator, select the cluster you are using by clicking the left mouse button on the cluster name.
- Click the right mouse button to open the cluster.
- Select Properties; then, select the Quorum tab.
- In the Quorum Resource field, select a ServeRAID shared disk and click on OK.
Refer to the Microsoft Cluster Solution Administrator's Guide for more information.
You will need to ensure that the same server (for example, server A) owns the ServeRAID disk resources
and the local quorum resource and that the quorum resource is moved to a RAID level-1 logical drive.
Shared disk resources can now be moved manually using the Microsoft Cluster Administrator utility or automatically during
failover.
Back to
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.