IBM BladeCenter Deployment Guide
13.Power on the server and enter the QLogic BIOS by pressing CTRL+Q.
14.From the Configurable Boot Settings, set the BOOT Device to the alternate controller's World Wide Name (that you gathered) and the BOOT LUN to 0.
15.From the Basic Settings panel, verify that the BIOS on this adapter is Enabled.
16.Verify that your storage partitioning and host group configuration looks similar. This configuration should account for both HBA worldwide port names, and the boot partition being configured to LUN 0.
17.Reboot the server.
4.2 Kickstart Information
The SYSLINUX.CFG should have the following line at the top of the file. Of note: the ks.cfg file is built into initrd.img. “text” is specified to avoid problems displaying the graphical installation dialogs via the Management Module that result in blank screens. “nofb” is another way to avoid a black screen during install.
default ksinstall prompt 1 timeout 600
…
label ksinstall kernel vmlinuz
append ks=file://ks.cfg text initrd=initrd.img lang= devfs=nomount ramdisk_size=7168
The kickstart config file will have some blade specific entries:
mouse generic3usb
Sample partition statements. clearpart
part /boot
part swap
4.3 Multipath Red Hat Installation
While it is possible to install RHAS2.1 with both paths enabled using the standard partitioning statements in the kickstart configuration file, this approach does not work with Version 3.0. The installation will complete and Linux will begin to boot, but you will eventually witness the following error:
Version 3.0, 3/10/2006 | 27 |
The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for
guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.