3.611 bytes

Service Hints & Tips

Document ID: MIGR-477KUL

Clustering - Error during installation of ServeRAID Cluster Solution

Applicable to: World-Wide

Source: RETAIN tip H166359

Abstract:
Error during installation of ServeRAID Cluster Solution

Symptom:
During the ServeRAID / MSCS installation process the user is instructed to move all share disk from Node "A" to Node "B". The following error CAN occur during the execution of IPSHAHTO.EXE from Node "B" "MERGE failed on merge id# X-X on ServeRAID #X <sp#X>. Error - 0x1122005".

Problem isolation aids:
The system is any IBM server certified for MSCS and ServeRAID II or III.

Note: Supported configurations are listed at the following URL:

http://www.pc.ibm.com/us/compat/clustering/matrix.shtml

examples given:
a Netfinity 5500-M10 server, Type 8661, any model.
a Netfinity 5500 server, Type 8660, any model.

The system is configured with one of the following ServeRAID options:



The system is configured with Microsoft Windows NT 4.0 Enterprise, with any level Service Pack applied.

Fix:
This problem will be fixed in a future BIOS/Firmware release.

It will be available from the following URL:

http://www.pc.ibm.com/searchfiles.html Search on ServeRAID BIOS

Note: version should be later than v3.11

Workaround:
If all resources move properly ignore error message. If all resources did not move properly, shutdown and restart Windows NT, then rerun IPSHAHTO.EXE.

Trademarks:
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries.

SAS keywords:
PSY2, NETFINITY, CLUSTER, UNCLASSIFIED, 5500-M20, D/T8662, 5500-M10, D/T8661, 5500, D/T8660, IPSHAHTO.EXE, SERVERAID, 76H3584, 01K7207, 01K7364, FIRMWARE, BIOS


Search Keywords

Document Category

Retain

Date Created

22-04-99

Last Updated

21-04-99

Revision Date

22-04-2000

Brand

IBM PC Server

Product Family

Netfinity 5500, Netfinity 5500 M10, Clustering

Machine Type

8660, 8661

Model

All

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes