IBM JS20 Hardware Maintenance Manual - Page 75

Update, manage, system, flash

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

For many adapters and devices, microcode installation occurs and becomes effective while the adapters and devices are in use. It is recommended that a current backup be available and the installation be scheduled during a non-peak production period. Notes: 1. If the source is /etc/microcode, the image must be stored in the /etc/microcode directory on the system. If the system is booted from a NIM server, the image must be stored in the usr/lib/microcode directory of the SPOT the client is booted from. 2. If the source is CD (cdX), the CD must be in ISO 9660 format. There are no restrictions as to what directory in which to store the image. 3. If the source is diskette (fdX), the diskette must be in backup format and the image stored in the /etc/microcode directory. The following is the common syntax command: diag [-c ]-d -T "download [-s {/etc/microcode|}][-1 {latest|previous}[-f ]" Flag descriptions are as follows: Flag -c -d

  • 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
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
For
many
adapters
and
devices,
microcode
installation
occurs
and
becomes
effective
while
the
adapters
and
devices
are
in
use.
It
is
recommended
that
a
current
backup
be
available
and
the
installation
be
scheduled
during
a
non-peak
production
period.
Notes:
1.
If
the
source
is
/etc/microcode,
the
image
must
be
stored
in
the
/etc/microcode
directory
on
the
system.
If
the
system
is
booted
from
a
NIM
server,
the
image
must
be
stored
in
the
usr/lib/microcode
directory
of
the
SPOT
the
client
is
booted
from.
2.
If
the
source
is
CD
(cdX),
the
CD
must
be
in
ISO
9660
format.
There
are
no
restrictions
as
to
what
directory
in
which
to
store
the
image.
3.
If
the
source
is
diskette
(fdX),
the
diskette
must
be
in
backup
format
and
the
image
stored
in
the
/etc/microcode
directory.
The
following
is
the
common
syntax
command:
diag
[-c
]-d
<device>-T
"download
[-s
{/etc/microcode|<source>}][-1
{latest|previous}[-f
]"
Flag
descriptions
are
as
follows:
Flag
Description
-c
No
console
mode.
Run
without
user
interaction.
-d
<device
Run
the
task
on
the
device
or
adapter
specified.
-T
download
Install
microcode.
-s
/etc/microcode
Microcode
image
is
in
/etc/microcode.
-s
<source>
Microcode
image
is
on
specified
source.
For
example,
fd0,
cd0.
-l
latest
Install
latest
level
of
microcode.
This
is
the
default.
-l
previous
Install
previous
level
of
microcode.
-f
Install
microcode
even
if
the
current
level
is
not
on
the
source.
Update
and
manage
system
flash
Note:
The
firmware
update
can
be
done
using
the
service
aid
or
the
AIX
command
line.
This
selection
validates
a
new
system
firmware
flash
image
and
uses
it
to
update
the
system
temporary
flash
image.
This
selection
can
also
be
used
to
validate
a
new
system
firmware
flash
image
without
performing
an
update,
commit
the
temporary
flash
image,
and
reject
the
temporary
flash
image.
Look
for
additional
update
and
recovery
instructions
with
the
update
kit.
You
need
to
know
the
fully-qualified
path
and
file
name
of
the
flash
update
image
file
provided
in
the
kit.
If
the
update
image
file
is
on
a
diskette
or
optical
media,
the
service
aid
can
list
the
files
on
the
diskette
or
optical
media
for
selection.
The
diskette
must
be
a
valid
backup-format
diskette.
Refer
to
the
update
instructions
with
the
kit
to
determine
the
current
level
of
the
system
unit
or
service
processor
flash
memory.
When
this
service
aid
is
run
from
online
diagnostics,
the
flash
update
image
file
is
copied
to
the
/var
file
system.
It
is
recommended
that
the
source
of
the
microcode
Chapter
8.
General
AIX
and
xSeries
standalone
diagnostic
information
65