IBM JS20 User Guide - Page 55

Committing, temporary, firmware, image, using, Verifying, system, levels

Page 55 highlights

diag v Otherwise, boot standalone diagnostics; then press Enter. 3. From the "Function Selection" menu, choose Task Selection. 4. From the "Tasks Selection List", choose Update and Manage System Flash. 5. From the "Update and Manage System Flash" list: v If, in step 1 on page 42, you have put the image in the /etc/microcode file system, then choose the File System selection. At the flash update image file prompt, specify the directory that contains the image (normally /etc/microcode), and then choose Commit (PF7). v If, in step 1 on page 42, you have put the image on optical media or diskette, place the media containing the image into the drive and choose Removable Media and then choose Commit (PF7). Note: If you have booted standalone diagnostics from a CD, you may remove the standalone diagnostics CD media from the drive and replace it with the optical media containing the image that you want to update. 6. Follow the instructions that are displayed on the screen; for example: Choose Yes to proceed with the flash operation. 7. After the system flash operation completes, and the system reboots, you may remove the media containing the image from the diskette or optical drive, or from the /etc/microcode directory on the file system. You may also remove the temporary file created in the "/var/update_flash_image" directory after the reboot occurs, after you log in to the operating system. Committing the temporary firmware image using AIX After the system reboots successfully and once you are satisfied with the functionality of the new image, commit the update by using the following AIX diagnostic commands: 1. Run diagnostics. v If you have booted AIX, log in as "root" or use the CE login; then, at the command line, enter: diag v Otherwise, boot standalone diagnostics; then press Enter. 2. From the "Function Selection" menu, choose Task Selection. 3. From the "Tasks Selection List" choose Update and Manage System Flash. 4. Choose Commit the Temporary Image. 5. Choose Yes to commit the image. 6. Press F10 to exit diagnostics Note: This selection commits the Temporary system firmware image to the PERM image when booted from the Temporary image. Verifying the system firmware levels using AIX To verify levels of system firmware on the PERM and TEMP sides, use the AIX diagnostics "Update and Manage System Flash" (see "Updating the system flash using AIX" on page 42). The diagnostics function displays the system firmware image level for both the PERM and TEMP sides as well as an indication as to which side was used for the current boot cycle. The following illustration is an example screen: Chapter 5. Configuration requirements for the blade server 43

  • 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

diag
v
Otherwise,
boot
standalone
diagnostics;
then
press
Enter.
3.
From
the
“Function
Selection”
menu,
choose
Task
Selection
.
4.
From
the
“Tasks
Selection
List”,
choose
Update
and
Manage
System
Flash
.
5.
From
the
“Update
and
Manage
System
Flash”
list:
v
If,
in
step
1
on
page
42,
you
have
put
the
image
in
the
/etc/microcode
file
system,
then
choose
the
File
System
selection.
At
the
flash
update
image
file
prompt,
specify
the
directory
that
contains
the
image
(normally
/etc/microcode
),
and
then
choose
Commit
(PF7).
v
If,
in
step
1
on
page
42,
you
have
put
the
image
on
optical
media
or
diskette,
place
the
media
containing
the
image
into
the
drive
and
choose
Removable
Media
and
then
choose
Commit
(PF7).
Note:
If
you
have
booted
standalone
diagnostics
from
a
CD,
you
may
remove
the
standalone
diagnostics
CD
media
from
the
drive
and
replace
it
with
the
optical
media
containing
the
image
that
you
want
to
update.
6.
Follow
the
instructions
that
are
displayed
on
the
screen;
for
example:
Choose
Yes
to
proceed
with
the
flash
operation.
7.
After
the
system
flash
operation
completes,
and
the
system
reboots,
you
may
remove
the
media
containing
the
image
from
the
diskette
or
optical
drive,
or
from
the
/etc/microcode
directory
on
the
file
system.
You
may
also
remove
the
temporary
file
created
in
the
“/var/update_flash_image”
directory
after
the
reboot
occurs,
after
you
log
in
to
the
operating
system.
Committing
the
temporary
firmware
image
using
AIX
After
the
system
reboots
successfully
and
once
you
are
satisfied
with
the
functionality
of
the
new
image,
commit
the
update
by
using
the
following
AIX
diagnostic
commands:
1.
Run
diagnostics.
v
If
you
have
booted
AIX,
log
in
as
“root”
or
use
the
CE
login;
then,
at
the
command
line,
enter:
diag
v
Otherwise,
boot
standalone
diagnostics;
then
press
Enter.
2.
From
the
“Function
Selection”
menu,
choose
Task
Selection
.
3.
From
the
“Tasks
Selection
List”
choose
Update
and
Manage
System
Flash
.
4.
Choose
Commit
the
Temporary
Image
.
5.
Choose
Yes
to
commit
the
image.
6.
Press
F10
to
exit
diagnostics
Note:
This
selection
commits
the
Temporary
system
firmware
image
to
the
PERM
image
when
booted
from
the
Temporary
image.
Verifying
the
system
firmware
levels
using
AIX
To
verify
levels
of
system
firmware
on
the
PERM
and
TEMP
sides,
use
the
AIX
diagnostics
“Update
and
Manage
System
Flash”
(see
“Updating
the
system
flash
using
AIX”
on
page
42).
The
diagnostics
function
displays
the
system
firmware
image
level
for
both
the
PERM
and
TEMP
sides
as
well
as
an
indication
as
to
which
side
was
used
for
the
current
boot
cycle.
The
following
illustration
is
an
example
screen:
Chapter
5.
Configuration
requirements
for
the
blade
server
43