IBM Power Systems p (AIX/Linux)

Microcode Update for BP15KHDD

300/600GB 4K
SAS Hard Disk Drive
Microcode Level 7F1C

DATE: June 11, 2021

Table of Contents

1. General Information

1.1 Disk Drives Affected

1.2 Microcode Change History

2. AIX and VIOS(PowerVM Virtual I/O Server) Operating System

2.1 Installation Time

2.2 Determine Drive Model, FRU&PN and Current Microcode Level

2.3.1 Internet AIX self extracting file (.bin)
2.3.2 Internet RPM package
2.3.3 CD-ROM

2.4 Microcode Download Procedure

3. Linux Operating System

3.1 ReadHat (RHEL) and SLES

3.2 Ubuntu

=============================================================
==

1. General Information
The Microcode files provided in this package are for SAS disk drives used in IBM system P Servers
with AIX or Linux operating systems

1.1 Disk Drives Affected

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

Disk Drive P/N Microcode File

Size FRU# Checksum
Model (VPD) Name
 00E9974 00LY179
600GB ST600MP0065 ST600MP.A1700D4A.37463143
00E8689 00LY173
12796
00E9972 00LY178
300GB ST300MP0065 ST300MP.A1700D4A.37463143
00E8687 00LY172

1.2 Microcode Change History

Release Code Impact/

Change Description
date level Severity
Function/ - Drive asserts while processing write
ATT same commands
- Drive becomes unresponsive
June 11, following Hard Reset during Write
7F1C
2021 command workload
- One of two SAS port became
unresponsive during error injection
test
Function/ Many Skip Mask Write commands in
June 2020 7F1B ATT a short amount of time causes Assert
and drive becomes unresponsive
Function/ -Fixed drive hang during SAS
Feb 2018 7F1A ATT adapter FW update
-False overlap command 0B/4E00/02
-This firmware addresses another
possible undetected data corruption
during a specific drive error recovery
June 1,
7F16 sequence. IBM recommends that all
2016
customers with the affected drives
apply this latest level of code.
-Other fixes and enhancements
This firmware addresses a possible
undetected data corruption during a
specific drive error recovery
June 2015 7F13
sequence. IBM recommends that all
customers with the affected drives
apply this latest level of code.
Feb. 2015 7F10 General enhancements and fixes
Dec 2014 7F0F Initial Release

==============================================================
=

2. AIX and VIOS(PowerVM Virtual I/O Server) Operating System

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.
2.1 Installation Time
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

Vital Product Data (VPD)

hdisk0 U5887.001.Z02K007-P1-D11 SAS 4K Disk Drive (300000 MB)

Manufacturer................IBM
Machine Type and Model......ST300MP0065
FRU Number.......................00E9972
ROS Level and ID................ 37463143
Serial Number.....................S2J0141H
EC Level.............................L38401
Part Number........................ 00LY178
Device Specific.(Z0).............000006329F001002
Device Specific.(Z1).............05087F1C
Device Specific.(Z2).............0021
Device Specific.(Z3).............13222
Device Specific.(Z4)........
Device Specific.(Z5).............22
Device Specific.(Z6).............L38401
Hardware Location Code.......U5887.001.Z02K007-P1-D11

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 "37463142", 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,
37 Hex= ASCII character "7"; 46 Hex= ASCII character "F"; 31 Hex=ASCII character "1"; 43 Hex=ASCII
character "C", microcode level is "7F1C". Also note that the microcode level "7F1C " is displayed in “Z1”
field.

==============================================================
=
2.3 Transferring and Unpacking the Microcode Update Package

2.3.1 Internet AIX self extracting file (.bin)

a) Make a directory on an 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 EP15KHDD.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x BP4K15KHDD.bin
./BP4K15KHDD.bin
[Don't overlook the periods (.) in the above command.]
The directory EP15KHDD 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/BP4K15KHDD/ST* /etc/microcode

e- If transferring files to a different system using floppy diskettes, use the following procedure to copy files to
diskette
Note: Don't overlook the complete path of microcode files, AIX Diag microcode download
will not work if files are not copied with complete path onto the diskette.
Enter the following command to copy microcode file(s) onto a floppy diskette
ls /etc/microcode/ microcodefilename | backup -ivf /dev/rfd0
where microcodefilename is microcode file that is needed, for example:
ls /etc/microcode/ ST* | backup -ivf /dev/rfd0

2.3.2 Internet RPM package

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 BP4K15KHDD–7F1C-AIX.rpm
c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos --force BP4K15KHDD–7F1C-AIX.rpm ;(please note, there are two dashes)
The file size and checksum will be verified.
The microcode files will be added to /etc/microcode/

2.3.3 CD-ROM
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.
========================================================

2.4 Microcode Download Procedure

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.2.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
diskette

- Use /etc/microcode if "restore" command is used to copy files from diskette onto the disk
- Use diskette if using diskette as the source for download

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 ST9xx...", 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.1.2.2 Standalone (Service Mode) Download

This procedure is used for all drives including rootvg or paging space drives
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.

======================================================
3. Linux Operating System
3.1 ReadHat (RHEL) and SLES
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. If using SLES 9 base, install the package by typing:

rpm -ivh --ignoreos BP4K15KHDD–7F1C-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

--------------------------------------------------------------------------
3.2 Ubuntu

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. tar -C-xzvf BP4K15KHDD–7F1C-LINUX.tgz

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