IBM QS21 Service Guide - Page 78

Booting, system

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144

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