IBM QS21 User Guide - Page 65

Updating, system, firmware, images, optional, expansion, Integrating, Gigabit, Ethernet, controller

Get IBM QS21 - BladeCenter - 0792 PDF manuals and user guides
UPC - 883436016940
View all IBM QS21 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

For example, to copy the image file cp QB-1.9.1-2-boot_rom.bin to /proc/ppc64/rtas/firmware_update enter: cp QB-1.9.1-2-boot_rom.bin /proc/ppc64/rtas/firmware_update shutdown -r now 8. Once the system reboots, update the system firmware images. See "Updating the system firmware images" for instructions. Updating the system firmware images Once the system firmware is updated, the BladeCenter QS21 boots from the new firmware. However, there are always two copies of the system firmware image on the blade server: TEMP This is the firmware image normally used in the boot process. When the firmware is updated, it is the TEMP image that is replaced. PERM This is a backup copy of the system firmware boot image. The blade server only boots from this image if the TEMP image is corrupt. See "Recovering the system firmware code" on page 63 for further information about how to recover from a corrupt TEMP image. Once you have updated the system firmware and booted the blade server, you should copy the TEMP image to the PERM image. This ensures that the PERM and TEMP images are at the same revision level. The TEMP and PERM images should always be at the same revision level. There are two commands you can use to update an old image on PERM. v From the Linux prompt issue the following command: update_flash -c Note: The script checks whether the board has booted from the TEMP image. If not, the script does not complete. v From the Linux prompt issue the following command: echo 0 > /proc/rtas/manage_flash For more information on booting from the TEMP or PERM images, see "Recovering the system firmware code" on page 63. Updating the optional expansion card firmware If you have installed the SAS optional expansion card or the high-speed InfiniBand expansion card you may have to update the firmware. See the documentation that comes with the components for instructions about how to update the firmware. IBM periodically makes updates available for both SAS and InfiniBand expansion cards. These may be downloaded from http://www.ibm.com/support/us/en/. Integrating the Gigabit Ethernet controller into the BladeCenter One dual-port Gigabit Ethernet controller is integrated on the blade server system board. Each controller port provides a 1000-Mbps full-duplex interface connecting to one of the Ethernet Switch Modules in BladeCenter unit I/O bays 1 and 2 of the BladeCenter H unit or the BladeCenter HT unit. These enable simultaneous transmission and reception of data on the Ethernet local area network (LAN). Chapter 5. Configuring the blade server 49

  • 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
For
example,
to
copy
the
image
file
cp
QB-1.9.1-2-boot_rom.bin
to
/proc/ppc64/rtas/firmware_update
enter:
cp
QB-1.9.1-2-boot_rom.bin
/proc/ppc64/rtas/firmware_update
shutdown
—r
now
8.
Once
the
system
reboots,
update
the
system
firmware
images.
See
“Updating
the
system
firmware
images”
for
instructions.
Updating
the
system
firmware
images
Once
the
system
firmware
is
updated,
the
BladeCenter
QS21
boots
from
the
new
firmware.
However,
there
are
always
two
copies
of
the
system
firmware
image
on
the
blade
server:
TEMP
This
is
the
firmware
image
normally
used
in
the
boot
process.
When
the
firmware
is
updated,
it
is
the
TEMP
image
that
is
replaced.
PERM
This
is
a
backup
copy
of
the
system
firmware
boot
image.
The
blade
server
only
boots
from
this
image
if
the
TEMP
image
is
corrupt.
See
“Recovering
the
system
firmware
code”
on
page
63
for
further
information
about
how
to
recover
from
a
corrupt
TEMP
image.
Once
you
have
updated
the
system
firmware
and
booted
the
blade
server,
you
should
copy
the
TEMP
image
to
the
PERM
image.
This
ensures
that
the
PERM
and
TEMP
images
are
at
the
same
revision
level.
The
TEMP
and
PERM
images
should
always
be
at
the
same
revision
level.
There
are
two
commands
you
can
use
to
update
an
old
image
on
PERM.
v
From
the
Linux
prompt
issue
the
following
command:
update_flash
-c
Note:
The
script
checks
whether
the
board
has
booted
from
the
TEMP
image.
If
not,
the
script
does
not
complete.
v
From
the
Linux
prompt
issue
the
following
command:
echo
0
>
/proc/rtas/manage_flash
For
more
information
on
booting
from
the
TEMP
or
PERM
images,
see
“Recovering
the
system
firmware
code”
on
page
63.
Updating
the
optional
expansion
card
firmware
If
you
have
installed
the
SAS
optional
expansion
card
or
the
high-speed
InfiniBand
expansion
card
you
may
have
to
update
the
firmware.
See
the
documentation
that
comes
with
the
components
for
instructions
about
how
to
update
the
firmware.
IBM
periodically
makes
updates
available
for
both
SAS
and
InfiniBand
expansion
cards.
These
may
be
downloaded
from
Integrating
the
Gigabit
Ethernet
controller
into
the
BladeCenter
One
dual-port
Gigabit
Ethernet
controller
is
integrated
on
the
blade
server
system
board.
Each
controller
port
provides
a
1000-Mbps
full-duplex
interface
connecting
to
one
of
the
Ethernet
Switch
Modules
in
BladeCenter
unit
I/O
bays
1
and
2
of
the
BladeCenter
H
unit
or
the
BladeCenter
HT
unit.
These
enable
simultaneous
transmission
and
reception
of
data
on
the
Ethernet
local
area
network
(LAN).
Chapter
5.
Configuring
the
blade
server
49