RS/6000
SP 9076 SMP
System and Service Processor Firmware Update (ECA N/A)
Applies to: IBM
RS/6000
SP 9076-5X0 332Mhz SMP Thin/Wide Nodes
If you experience
problems
or have questions regarding any component of this document or the
installation
of the code please call 1-800-IBM-SERV for assistance.
Please read this
document
in it's entirety and in particular
understand the
Notes and Cautions section before applying this F/W to any node.
Contents:
4.0
Cautions and Important Notes
5.0
Downloading and Unpacking the Firmware Update Package
6.0
Putting the Firmware on the System
8.0
Setting up the Distributed Shell
9.0
Determining Your Current Firmware Levels
10.0
Updating the Firmware on the Target Nodes
This update
provides new
System and Service Processor (SvP) firmware
(FW) on
RS/6000 SP 9076 332MHZ Thin/Wide Nodes. This firmware can be
applied to a
332Mhz Thin/Wide node (FC 2050/2051) operating on any model of 9076
that has an
operating system of AIX at 4.2.1 or greater.
The latest levels
are:
NOTE:
The System and
Service
Processor Firmware for the 332Mhz node
consists of two
seperate files, as indicated above.
System FW
|
Level |
Description |
|
L05292 |
|
|
L04197 |
|
|
L03323 |
|
|
L03273 |
|
|
L03115 |
|
|
WIL02113 |
|
|
WIL01337 |
|
|
WIL01269 |
|
|
WIL01159 |
|
|
WIL00278 |
|
|
WIL00125 |
|
|
WIL99308 |
|
SvP FW
|
Level |
Description |
|
wc010611 |
|
|
wc000901 |
|
|
wc991027 |
|
|
wc990831 |
|
You
may have to
refer to the following publications during this install:
4.0
Cautions and Important Notes
INSTALLATION OF THIS CODE
WILL CAUSE
AN UNCONDITIONAL REBOOT OF AIX AND IS NOT CONCURRENT WITH CUSTOMER
OPERATIONS.
Never power off the node
during the update
process
DO NOT Use The
SvP Firmware AGyymmdd
Version
Ensure that the
new Service
Processor firmware is a "WC" version such as WC980413 (98=year,
04=month, 13=day). DO NOT use the SvP
firmware AGyymmdd version because the "AG"
version is for
the 7026-H50 systems. If you update SP 9076 332MHZ nodes with "AG"
version, it will corrupt the SvP firmware.
The server
will show E212 or E213 then shut itself off. Replacing the SvP
card is the only recovery solution for the field.
How To
Determine Release Date From The File Name
Date and level identifiers for the SvP FW
uses
the 8-digit Gregorian date code method in terms of year, month, and day
(such
as 19980413 for WC980413 level). The System FW uses the 5-digit Julian
date
code method in terms of day number in a year (such as 98112 for
WIL98112 level
-- 112th day of 1998 or
The Combo FW uses
the
Gregorian date code.
The SvP
and
System Firmware need to be at companion levels
When an I/O
planar or a
Service Processor (SvP) card is replaced,
the System
firmware on the new I/O planar and the SvP
firmware
on the new SvP card must be checked to
ensure that
they are at the latest level, or that they are at companion levels. If
they are
not, it is recommended that both the System Firmware and SvP
Firmware be "re-flashed" to the latest level or at the very least to
the correct companion level. Companion levels are those files that have
the
same release date as indicated in the table below.
Installation Time
The typical time
to install
this microcode on one node is 1.0 hr. This firmware can be installed on
more
than one node at a time but the total install time will vary depending
on how
many nodes/frames are involved with the upgrade. The microcode does not
become
active when installed and requires a system reboot to become active.
This
reboot time will vary depending on the
system
and the amount of features installed.
5.0
Downloading and Unpacking the Firmware Update Package
Instructions for downloading and unpacking the firmware update package
follow.
5.1 CD-Rom Package
Follow instructions in the CD-ROM ReadMe for:
a) The AIX command to mount this CD-ROM is:
mount -v cdrfs
-r
/dev/cd0 /mnt
cd /mnt
Note: Don't forget to unmount
the /mnt directory after Section 10.0
Updating
Firmware on Target Nodes
Enter:
cd (to get out of /mnt
directory)
umount /mnt
b) Provide a directory on an AIX system to receive the AIX format
file.
Enter:
mkdir
/tmp/fwupdate
Note: If
the
directory /tmp/fwupdate already exists,
make
sure it
is empty before proceeding.
c) Manually copy WIL05292.img and
wc010611.img to
/tmp/fwupdate directory
This can be found in the
/microcode
directory under 90765X0 on the CD-ROM
Proceed to Section 7.0,Validating The
Checksum.
5.2 Internet Package
The firmware, in AIX and DOS formats, are located at the web site
download.html
Follow the instructions on this web page. You must read and agree to
the
license agreement to obtain the password (case sensitive) for unpacking
the
firmware packages.
In the table for System Microcode, scroll down to the entry for 9076
332MHZ
SMP T/W .
The download choices at that entry are:
You will want a copy of the description
(instructions
document) and one of the format choices. You may transfer files to the
target
system in one of several ways.
Detailed download/unpacking instructions follow
for each of
the downloading preferences.
5.3 Downloading the AIX Format File
Use this method to download to an AIX system.
Note:
In the instructions that follow are specific AIX commands.
AIX
commands are
CASE (lower and upper) SENSITIVE, and must be entered exactly as
shown,
including
the filenames.
a) Provide a directory on an AIX
system to
receive the AIX format file.
Enter:
mkdir
/tmp/fwupdate
Note:
If the directory /tmp/fwupdate already
exists,
make
sure it
is empty before proceeding.
b) Transfer the AIX format file
to the /tmp/fwupdate directory (using "Save
as ...").
You'll see that the filename is
90765X0F.BIN
c) Unpack the file by executing
the
instructions below.
You will be need
the password from the license agreement.
Enter the commands:
cd /tmp/fwupdate
chmod
+x 90765X0F.BIN
./90765X0F.BIN
[Don't
overlook the
periods (.) in the above command.]
These files will be added to /tmp/fwupdate:
WIL05292.IMG
wc010611.img
ReadMe.TXT
If you used the above procedure to
transfer the AIX
format file directly to the target server,
proceed
to Section 7.0,Validating the Checksum.
Otherwise, from the intermediate AIX
system, choose
one of the following methods for transferring files to
the target server.
To transfer files to the target server
via the ftp
method, continue to paragraph 5.4
To transfer files to the target server via
the
diskettes method, skip to paragraph 5.5
5.4
The FTP
Transfer Method
This method presumes you have ftp access to the target server.
On the intermediate AIX system,
Enter the commands:
ftp {name of target server}
{Login with a valid userid
and password}
bin
lcd
/tmp/fwupdate
mkdir
/tmp/fwupdate
cd
/tmp/fwupdate
put
WIL05292.IMG
quit
Proceed to Section 7.0,Validating
the Checksum.
5.5
The Diskette
Transfer Method
This method can be used for cases in
which
electronic connections between the intermediate AIX system and the
target
server are inconvenient.
Two 2MB (HD) new or freshly
formatted
diskettes are required.
With a diskette loaded in the
drive,
Enter the commands (this process
will request
additional diskettes as each is filled):
cd /tmp/fwupdate
ls *.img | backup -i -v
-f/dev/rfd0
This will produce AIX backup
diskettes. Label
these diskettes, respectively,
"Volume
1: FW
(WIL05292) for 9076-550"
"Volume 2: FW (wc010611) for 9076-550"
Proceed to Section 6.0,Updating
the Firmware.
5.6
Downloading
the DOS Format File
Use this file to download to a DOS or Windows workstation.
a) Prepare a directory for
receiving the DOS
format file.
This directory can be in any partition
with 12MB
available space.
Executing in such a partition, called
[path] in
these instructions
(ex. c:\download),
Enter:
md
[path]\fwupdate
Note: If the directory
[path]\fwupdate
already exists,
make sure it is empty before proceeding.
b) Transfer the
DOS format
file to the [path]\fwupdate directory
(using
"Save as ...").
You'll see the
filename is
90765X0F.EXE
c) Unpack the
file by
executing the instructions below.
You will need the
password
from the license agreement.
Enter
the commands:
cd
[path]\fwupdate
90765X0F
These files will be added to the fwupdate subdirectory:
L05292.EXE
wc010611.IMG
WIL5292.IMG
readme.txt
5.7
Diskettes
for Firmware Updates
One 2MB (HD) new or freshly formatted
DOS diskette
is required.
Note:
The diskettes produced below will be in a format that can be used
directly with a computer running AIX as it's
operating
system. These
diskettes, once made on a PC platform, cannot be read using normal PC
platform tools or command line operations.
a) With a diskette loaded in the
drive,
Enter the commands:
cd [path]\fwupdate
L05292.EXE
Label
this diskette,
"Volume 1:
FW
(WIL05292) for 9076-550"
6.0
Putting the Firmware on the System
On the 9076 CWS
that you
are going to use this firmware, insert the diskette in the floppy
diskette
reader (rfd0) on the CWS.
Login as
root on the Control Workstation (CWS).
Login root
Enter
the
commands:
mkdir /tmp/fwupdate
cd /tmp/fwupdate
restore
This will put the firmware files into the /tmp/fwupdate directory.
Checksums can be
used to
verify the FW files you received have not been corrupted or altered
during
transmission. To calculate the checksum, enter:
sum [FW
filename]
The
checksum is the first number of the output. Compare the number
you get
with the previous table. If the numbers match then you can be
sure the
firmware files are not corrupted. Do this for both the system and
service
processor firmware.
|
|
SYSTEM FIRMWARE |
SvP FIRMWARE |
||||
|
RELEASE DATE |
Filename |
Size |
Chksum |
Filename |
Size |
Chksum |
|
Nov 2005 |
WIL05292.img |
1048576 |
31003 |
wc010611.img |
370800 |
21507 |
|
Sept 2003 |
WIL04197.img |
1048576 |
15953 |
wc010611.img |
370800 |
21507 |
|
Dec 2003 |
WIL03323.img |
1048576 |
54524 |
wc010611.img |
370800 |
21507 |
|
Sep 2003 |
WIL03273.img |
1048576 |
41606 |
wc010611.img |
370800 |
21507 |
|
Apr 2003 |
WIL03115.img |
1048576 |
09107 |
wc010611.img |
370800 |
21507 |
|
Jul 2002 |
WIL02113.img |
1048576 |
63736 |
wc010611.img |
370800 |
21507 |
|
Jan 2002 |
WIL01337.img |
1048576 |
18006 |
wc010611.img |
370800 |
21507 |
|
Nov 2001 |
WIL01269.img |
1048576 |
41611 |
wc010611.img |
370800 |
21507 |
|
Aug 2001 |
WIL01159.img |
1048576 |
15085 |
wc010611.img |
370800 |
21507 |
|
Nov 2000 |
WIL00278.img |
1048576 |
06894 |
wc000901.img |
371056 |
24934 |
|
May 2000 |
WIL00125.img |
1048576 |
34781 |
wc991027.img |
371056 |
18658 |
|
DEC 1999 |
WIL99308.img |
1048576 |
56934 |
wc990831.img |
371048 |
11591 |
|
OCT 1999 |
WIL99287.img |
1048576 |
57737 |
wc990831.img |
371048 |
11591 |
8.0
Setting up the Distributed Shell
On an SP, you
need to
perform on each node what would normally be done on a standalone
RS/6000
server. To install the firmware you must distribute the code to
all of
the applicable nodes, then install it
there. You
must be logged on as root to properly do the install.
All the following
commands
shown will be run from a window on the CWS. It should not be necessary
to
telnet or rlogin to the individual SP nodes. You should be familiar
with the
"dsh" and "pcp"
commands. If not, refer to the (GC23-3897) IBM Parallel System
Support
Program for AIX: Administration Guide or (GC23-3900) IBM Parallel
System
Support Program for AIX: Command and Technical Reference.
splstdata
-G -n
You
should see something similar to the following:
List Node Configuration Information
node#
frame# slot# slots initial_hostname reliable_hostname
dcehostname
default_route processor_type processors_installed
description
------------------------------------------------------------------------------
1
1
1
2 vion01.pok.ibm
vion01.pok.ibm ""
9.114.201.190
MP
1 332_MHz_SMP_Wide
3
1
3
2 vion03.pok.ibm
vion03.pok.ibm ""
9.114.201.190
MP
2 332_MHz_SMP_Wide
The
output will include every node in your system. For each node that
has 332_MHz_SMP
in its description, record the first part of the initial_hostname
field. In this case since the initial_hostname
is vion01.pok.ibm, you would record vion01. This
will
become your list of nodes to be installed with the code.
cat > group1
[nodename1]
[nodename2]
[nodename3]
.
.
.
press Ctrl D
export WCOLL=/tmp/fwupdate/group1
dsh
date
You
should get back a list that looks something like:
nodename1: Wed Apr 10
nodename2: Wed Apr 10
nodename3: Wed Apr 10
nodename4: Wed Apr 10
If
this output does not contain all the nodes that you expected, examine
your node
list file /tmp/fwupdate/group1 and also ensure that the Kerberos ticket
is
current to permit "dsh" to be
performed. You may need to refresh the Kerberos. Refer to the SP
Administration
Guide (GC23-3897) for further help. The System Administrator should
also be
able to help you with Kerberos initialization. Otherwise, consult your
support
center.
9.0
Determining Your Current Firmware Levels
To check the System
Firmware level enter:
dsh "lscfg -vp | grep
-p 'System Firmware'"
This
command will produce a system configuration report containing sections
similar
to the following for each node:
System Firmware:
ROM Level
(alterable)…......Lxxxxx <==System
FW level
Version…..........................RS6K
System Info
Specific.(YL)…P2
The ROM Level
(alterable) lines list the level
numbers of your currently installed System Firmware. If the five right
most
characters of the update level are less than the
latest level
than you MUST install the update.
To check the Service
Processor Firmware level
enter:
dsh "lscfg -vp | grep
-p 'Service Processor"
This command will produce a system configuration report containing
sections
similar to the following for each node:
Service Processor:
Part
Number.........................93H4228
EC
Level..............................E76324A
FRU
Number........................93H4214
Manufacture
ID.....................3966-1944843
ROM
Level.(non-alterable).....wcxxxxxx
Serial
Number.....................00001821
ROM Level
(alterable)..........wcxxxxxx <== SvP
FW level
The ROM Level
(alterable) lines list the level
numbers of your currently installed Service Processor Firmware. If the
six
right most characters of the update level are less than the latest
level you
MUST install the update.
10.0
Updating the Firmware on the Target Nodes
This section
describes the
method for transferring the new firmware into the target nodes. Each
flash
update should complete within one minute.
WARNING:
DO NOT
POWER OFF THE TARGET SERVER
AT ANY TIME BEFORE THE FLASH PROCESS COMPLETES.
WARNING:
BE SURE
THE SYSTEM IS QUIESCED AND
NOT RUNNING ANY USER APPLICATIONS.
hostlist | pcp -w - /tmp/fwupdate/[System Firmware Filename]
/var
hostlist | pcp
-w - /tmp/fwupdate/[Service Processor
Firmware Filename] /var
NOTE:
This
Will copy the firmware images to the /var
directory.
Any other directory besides /var will not
work.
dsh "ls /var/*.img"
dsh "sync;sync;sync;sync"
dsh "/usr/sbin/shutdown
-Fu /var/[System Firmware Filename]"
dsh "/usr/sbin/shutdown
-Fu /var/[Service Processor
Firmware Filename]"
The node will power down
and reboot
to the AIX login prompt.
dsh "rm /var/*.img"
rm -r /tmp/fwupdate
Verify that
everything was
installed properly. Use section 9.0
Determining Your Current Firmware Levels to do this.