Recovering From A Failover In A Microsoft Cluster Service Server; Recovering From A Failed Server In A Serveraid Cluster - IBM Netfinity ServeRAID-4H Ultra160 User Reference

12. In the Main Tree, click the new controller.
13. Click Actions → Change stripe-unit size.
14. Click the new stripe-unit size for your installation.
15. Shut down and turn off the server.
16. Reconnect the SCSI channel cables to the controller.
17. If the ServeRAID controller being replaced attaches to any of the following:
18. In the Main Tree, click the new controller.
19. Click Actions → Copy configuration from drives.
20. Click the merge group number for the non-shared logical drives (that is, 206 or
21. Remove the IBM ServeRAID Support CD from the CD-ROM drive.
22. Restart your server.

Recovering from a failover in a Microsoft Cluster Service server

After a failover occurs in a Microsoft Cluster Services server, the red drive lights in
the IBM Netfinity EXP10 or IBM Netfinity EXP15 enclosures might turn on for
physical drives that are online. There is no hardware problem; the lights turn off
within an hour.

Recovering from a failed server in a ServeRAID cluster

Contact IBM technical support for assistance.
Note: Be sure to connect the cables to the correct SCSI channels as noted in
step 2 on page 142.
v The server startup disk array
v Other non-shared disk arrays
v Shared arrays which have not failed-over to the other server,
start the system with the IBM ServeRAID Support CD (version 4.0, or later) in
the CD-ROM drive. The ServeRAID Manager program starts.
If the ServeRAID controller being replaced does not attach to any of these
items, go to step 21
207).
Note: The last number in the merge group number is the shared SCSI initiator
ID. That is, if the merge group number is 206, the SCSI initiator ID is 6.
Note: If the controller you replaced is the startup controller, the system will
now start the operating system properly.
Chapter 12. Solving ServeRAID problems
143