
The following information was adapted from material found on the IBM web site[1].
Like our other examples, one server is named paul, and the other silas.
Read the good background information on the CD contents from the IBM web site[2]
Boot Server paul from the IBM ServeRAID Management CD[2] in the CD-ROM Drive. Make sure Server silas is powered off.
Upgrade the firmware on paul's ServeRAID controller. The ServeRAID Support CD will automatically check the controller firmware and prompt the user to upgrade if it is found to be downlevel. For this reason, you should always grab the latest version of the ServeRAID Support CD from the IBM web site before you begin.
If the ServeRAID controller is not already configured, the user will be prompt with Express Configuration. Click Cancel.
Confirm Window will appear. Click Yes to confirm. When complete, a message will appear at the bottom of the screen.
Select either Express Configuration or Custom Configuration for controller.
Select Next.
If Express Configuration was selected, the software will automatically create the arrays or hot spares.
If Custom Configuration was selected, the user has the option to create the arrays.
To create Raid level 1, two or more drives are needed. ServeRAID firmware does not reliably support any RAID5-based configuration in cluster mode.
Click Next to continue.
Configuration Summary screen will appear. Click Apply to confirm.
Select Configure for Clustering.
Enter the name of first controller under Controller Host ID. It is best to name it the same as the local Linux host name (paul).
Enter the name of second controller under Cluster Partner Host ID. It is best to name it after the partner's Linux host name (silas).
Click on shared checkbox for the logical drives that will be shared between the two ServeRAID controllers. Assign a merge group ID[3] to the shared drives. Each shared logical drive must have a unique merge ID. Make note of the merge group ID for use in configuring the ServeRAID heartbeat resource agent[4].
Exit and Shut down Server paul.
Boot Server B from the IBM ServeRAID Management CD[2] in the CD-ROM Drive. Make sure Server paul is powered off.
Upgrade the firmware on silas's ServeRAID controller. The ServeRAID Support CD will automatically check the controller firmware and prompt the user to upgrade if it is found to be downlevel. For this reason, you should always grab the latest version of the ServeRAID Support CD from the IBM web site before you begin.
If the ServeRAID controller is not already configured, the user will be prompted with Express Configuration. Click Cancel.
Select Restore to Factory Defaults.
Click Yes to confirm.
Select Configure for Clustering.
Enter the name of second controller (silas) under Controller Host ID.
Enter the name of the first controller (paul) under partner Controller Host ID.
Exit and Reboot Server silas and bring up paul.
| [1] | http://www-306.ibm.com/pc/support/site.wss/MIGR-4FJPZ7.html |
| [2] | http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-495PES |
| [3] | http://www.linux-ha.org/ServeRAIDMergeGroup |
| [4] | http://www.linux-ha.org/HeartbeatResourceAgent/ServeRAID |
This information provided courtesy of the Linux-HA project at http://linux-ha.org/