IBM
pSeries Servers
Microcode Update for
Model: VPCAXXX900EST1
3.5”
Microcode Level A3C4
For
Blade Products
DATE: March 13, 2013
Table of Contents
2.2 Determine Drive Model,
FRU&PN and Current Microcode Level
SCSI
Drives attached to PCI SCSI RAID Controllers
2.3 Transferring and Unpacking
the Microcode Update Package
2.3.1 Internet AIX self
extracting file (.bin)
2.4 Microcode Download
Procedure
2.4.1 SCSI Drives Attached to
SCSI Adapter
2.4.2 SCSI Drives Attached to
PCI RAID Adapter
3.1 Linux 2.6 kernel(such as SuSE SLES 9 or RHEL
4)
===============================================================
The Microcode files provided in this package are for SAS disk
drives used in IBM System P with AIX, VIOS or Linux operating systems
Below is the list of microcode files in this
package:
NOTE: To insure the integrity of microcode
files, please make sure the checksum value is correct after extraction
Size Disk Drive Model
FRU# P/N (VPD) Microcode File Name Checksum
---------- ----------------------------- ----------- ------------
------------------------------------------- -----------
300GB VPCA300900EST1 44W2235 44W2238 VPCA300.42524346.41334334 12934
450GB VPCA450900EST1 44W2240 44W2243 VPCA450.42524346.41334334 12934
600GB VPCA600900EST1 44W2245 44W2248 VPCA600.42524346.41334334 12934
1.2 Microcode Change History
Release date |
Code level |
Change Description |
March 13, 2013 |
A3C4 |
Drive FW enhancements to
prevent a possible undetected data loss or data error during a proximal
write. (The “proximal
write” feature improves performance of the drive by combining
operations that are to locations that are close to one another.) This issue occurs when the starting logical
Block Address (“LBA”) is a reassigned LBA. |
March 30, 2011 |
A3C0 |
Original Release |
===============================================================
Note: For VIOS systems, microcode of shared
physical I/O resources can only be updated from VIOS partition.
To update disk drive microcode, from VIOS
partition, enter the following command:
oem_setup_env
Then follow the instruction in section 2.3
to transfer/extract the microcode file, and section 2.4.1 to update the disk
drive code.
Approximately
20 minutes if using Diagnostics CD; Approximately 5 minutes/drive using AIX
concurrent diagnostics.
2.2 Determine Drive Model, FRU&PN and Current
Microcode Level
To see the drive type and current microcode level, Execute the following
command:
lscfg -vl hdisk* |pg ; For
drives NOT configured for RAID
lscfg
–vl pdisk* |pg ; For drives configured for RAID
Example:
DEVICE LOCATION DESCRIPTION
hdisk1 U4545.001.07CM0CP-P2-D2 SAS Disk Drive (450000 MB)
Manufacturer................IBM-ESXS
Machine Type and
Model......VPCA450900EST1 N
FRU Number..................44W2240
ROS Level and ID............41334334
Serial Number...............JVV1DJAE
EC Level....................L81062
Part Number.................44W2243
Device
Specific.(Z0)........000006329F001002
Device Specific.(Z1)........VCXSA3C4
Device Specific.(Z2)........0068
Device Specific.(Z3)........09150
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........L81062
Hardware Location
Code......U4545.001.07CM0CP-P2-D2
If the data returned in the “Part Number”, “FRU Number”, and
“Machine Type and Model” fields match the one listed in
section 1.1 AND the "ROS Level and ID...." field of that data is
below "41334334", this
microcode applies.
Note: Drive microcode level in “ROS Level and ID …” field
is displayed in Hex value of ASCII characters in VPD data. Each alpha-numeric
ASCII character converts to a 2-digit hex number. For example in VPD displayed
above, 41Hex= ASCII character "A"; 33
Hex= ASCII character "3";
43 Hex=ASCII character "C";
34 Hex=ASCII character "4", microcode
level is "A3C4". Also note
that the microcode level "A3C4"
is displayed in “Z1” field.
===============================================================
2.3 Transferring and Unpacking the Microcode Update Package
a) Make a directory on AIX
system to receive the AIX format file.
Enter: mkdir
/tmp/fwupdate
b) Transfer the AIX format file to /tmp/fwupdate
directory (using "Save as ...").
You'll see the filename is 15K600-XP-A3C4.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x 15K600-XP-A3C4.bin
./15K600-XP-A3C4.bin
[Don't overlook the periods (.) in above command.]
The
directory A3C4 with microcode files
listed in section 1.1 will be added to /tmp/fwupdate.
d-Enter
the following command to copy the microcode files to "/etc/microcode"
directory:
cp /tmp/fwupdate/A3C4/VPC*
/etc/microcode
Note: The
instructions that follow are specific AIX commands. AIX commands are CASE
(lower and upper) SENSITIVE,
and must be entered exactly as shown, including
filenames.
a)
Make a directory on an AIX system to receive the RPM format file.
Enter: mkdir
/tmp/microcode
b)
Transfer the RPM format file to the /tmp/microcode
directory.
You'll see the filename is 15K600-XP-A3C4-AIX.rpm
c)
Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv
--ignoreos
--force 15K600-XP-A3C4-AIX.rpm
The
file size and checksum will be verified.
The
microcode files will be added to /etc/microcode/
Copy
microcode updates from the CD-ROM to standard locations on your local disk:
1.
RPM packaged microcode files will be copied to "/tmp/microcode/RPM"
2. Microcode files will be copied to /usr/lib/microcode
Notes:
- "/etc/microcode" is a
symbolic link to "/usr/lib/microcode".
- If permission does not allow the copy to the above stated directory
or file then the user will be prompted for a new location.
========================================================
Warning: Do not power off the system or the drive during microcode download as
this may permanently damage the disk drive
NOTE: Please save current and older versions of the microcode update files
in case you need to restore your system.
Caution: The microcode download process is nondestructive to the hard disks;
however, as a precaution, ensure that a backup operation has been performed on
the affected systems PRIOR to the microcode installation.
Can microcode be installed Concurrently? YES
Is system reboot needed to activate the microcode: Yes if stand alone
diagnostics CD is used, NO if concurrent diagnostics is used.
Installation Time: Approximately 20 minutes/drive if stand alone
diagnostics is used(using Diagnostics CD); Approximately 5 minutes/drive if
concurrent diagnostics is used.
2.4.1 Concurrent Download
1.
Type diag at the prompt.
2. Select the "Task Selection" from diagnostics menu.
3. Select "Microcode Download" from "Task Selection" menu.
4. Select resource that microcode will be applied to(hdisk? For physical disk, pdisk
for RAID configured disks) and press ENTER, then press "F7" to
commit..
5- A small screen displays the message " *** NOTICE*** The microcode
installation occurs while the attached drives are available for use..... "
Press enter to continue
6. Select the source for microcode, use arrow key to go up/down, Enter to
continue.
/etc/microcode
optical media (ISO 9660 file system
format)
cd0
- Use /etc/microcode
if microcode files were added to /etc/microcode directory
- Use “optical media” if code are in CD/DVD
NOTE: A prompt will ask you to insert the
microcode diskette in diskette drive(if Diskette is selected above).
Insert the diskette and press ENTER
7- Display shows a list of microcodes available for the selected drive, highlight
option "M ST3xx...", the latest microcode for the drive and
press ENTER. A message may warn you that current level of microcode is not
available on the media, press ENTER to continue.
8. You will receive a msg. "Current
Microcode is...." and "Download has completed successfully"
(this may take a few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard
disk that requires this microcode.
10. Exit diagnostic(and reboot if needed).
2.4.2 Standalone (Service Mode) Download
1. Properly shutdown the system.
2. Boot up the system in standalone diagnostics mode with the CDROM
diagnostics(Use diagnostics level 4.21 or above; It is recommended to use
the same level
of Diagnostic CD as the AIX ).
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to(hdisk?) and PRESS ENTER.
6. Press "F7" to commit.
(The current microcode
level of the resource you selected earlier will be displayed at the top of the
screen)
7. Make the following selections on the next screen:
Select Input Device
--------------------------------------- [ diskette]
Microcode level to download
-----------------------------[ latest]
Download latest level even if
-----------------------------[ yes]
current is missing
NOTE: A prompt will ask you to insert the
microcode diskette into the floppy drive. Insert the diskette which
accompanies these instructions. If this level is already installed in the drive
you've selected a message will let you know. A message also may come up to let
you know that the Diskette(or Disk) does not have the previous level microcode
file. This is true and is not required to complete the download.
PRESS "F7" to commit
8. You will receive a msg. "Current Microcode
is...." and "Download has completed successfully"
(this may take a
few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard
disk that requires this microcode.
10. Exit diagnostic and reboot system in normal mode.
======================================================
Microcode can
be updated using the iprconfig utility. The iprconfig utility
allows for
multiple levels of adapter and device microcode to exist on the
system at the
same time. After the device to update microcode is
selected, all
available microcode levels are presented to choose to download.
1.
a) If using SLES 9 base, install the package by
typing:
rpm -ivh --ignoreos
15K600-XP-A3C4-LINUX.rpm
b) If using SLES 9 SP1 or better or RHEL 4 or better, install the
package by typing:
rpm -ivh 15K600-XP-A3C4-LINUX.rpm
2. Update the
microcode by typing:
iprconfig
Press Enter.
3. Select
Download microcode and press Enter.
4. Select the
device you wish to update by typing a 1 then pressing Enter. Multiple devices
may be selected.
5. Select the
microcode image to be downloaded to the device by typing a 1 then pressing
Enter.
6. Press Enter again
to confirm the download (display shows “Microcode Download in
Progress” with elapsed time)
7. If multiple
devices were selected, repeat from Step 5 for the next device.
To check the
microcode level:
1. Start iprconfig utility,
2. Select
"Display hardware status" option.
3. Select disk
to query by typing a 1 next to it and pressing "Enter"
4. Look at the
"Firmware Version" field
--------------------------------------------------------------------------
Microcode can
be updated using the iprupdate utility. If iprupdate finds newer
microcode on
the system it will be downloaded to the disk.
1. Install the
package by typing:
rpm -ivh --ignoreos
15K600-XP-A3C4-LINUX.rpm
Press Enter.
2. Update the
microcode by typing:
iprupdate
Press Enter.
To check the
microcode level:
1. Start iprconfig utility,
2. Select
"Display disk hardware status" option.
3. Find the
disk you wish to query and note its serial number.
4. Type
"d" to get to the "Display disk unit details" screen.
5. Select disk
to query by typing a 5 next to it and pressing "Enter"
6. Look at the
"Firmware Version" field
-------------------------------------------------------------------------
Microcode can
be updated using the sisupdate utility. If sisupdate finds newer
microcode on
the system it will be downloaded to the disk.
1. Install the
package by typing:
rpm -ivh --ignoreos
15K600-XP-A3C4-LINUX.rpm
Press Enter.
2. Update the
microcode by typing:
sisupdate
Press Enter.
To check the
microcode level:
1. Start sisconfig utility,
2. Select
"Display disk hardware status" option.
3. Find the
disk you wish to query and note its serial number.
4. Type
"d" to get to the "Display disk unit details" screen.
5. Select disk
to query by typing a 5 next to it and pressing "Enter"
6. Look at the "Firmware
Version" field