IBM QS21 Service Guide - Page 78
Booting, system
UPC - 883436016940
View all IBM QS21 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 78 highlights
Once the operating system is installed, the BladeCenter QS21 can also boot either from attached SAS storage if you have the installed the optional SAS Expansion Card or from the network. If you wish to perform a standard Bootp/TFTP network boot, please note the following restrictions: v Only the built-in Gigabit Ethernet Controller of I/O Bridge is supported v Only boot through the Ethernet switch on the top side of BladeCenter v No fall back or configurable change to the bottom switch is possible v In the Advanced Management Module you need to set boot list to Network v There is no support for a router between the blade and TFTP server. Only local TFTP is supported. Use Advanced Management Module to configure the required boot mode. See IBM BladeCenter Management Module Installation Guide for more information. Booting the system This section provides an overview on how to interpret the console output of the host firmware. The output is grouped into several parts, which are detailed below. 1. The first part of the boot process shows the system name and build date. You see an error at this point if the firmware image is corrupted. QS21 Firmware Starting Check ROM = OK Build Date = Apr 24 2007 13:43:46 FW Version = QB-1.6.0-0 Press "F1" to enter Boot Configuration (SMS) 2. Memory initialization follows next. Note: It can take several seconds to initialize the RAMBUS memory. 3. The memory is initialized. The screen displays details of the vendor and the speed of memory modules. Initializing memory configuration... MEMORY Modules = Elpida 512MB, 3200 Mhz XDRlibrary = v0.32, Bin A/C, RevB, DualDD Calibrate = Done Test = Done The next screens show the open firmware section of the boot process and provide checkpoints and an overview which adapters are available in the system. The details in the adapter list are not meaningful. Note: The warning(!) Permanent Boot ROM is displayed if there is a problem with the TEMP image and system firmware is running on from the PERM image. You should correct this problem as soon as possible. See "Recovering the TEMP image from the PERM image" on page 59 for further information. 60 BladeCenter QS21 Type 0792: Problem Determination and Service Guide