IBM
pSeries Servers
Microcode Update for Hitachi Ultrastar C10K900 73/146/300/600/900 GB
Model:
HUC1090xxCSS600
2.5”
SAS SFF Hard Disk Drive
Microcode Level J2EH
For
Blade and ITE Products
DATE: October 9, 2014
Table of Contents
2.2 Determine Drive Model,
FRU&PN and Current Microcode Level
2.2.2 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)
4.0 Drive Fails Code Update in Power Blade
JS21
===============================================================
The Microcode files provided in
this package are for SAS disk
drives used in IBM Blade systems 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
--------
-------------------------
-----------
------------
-------------------------------------
-----------
73GB
HUC109007CSS600
26K5779 26K5267 HUC1090.42524348.4A324548 04397
146GB HUC109014CSS600 42D0422
42C0251
“
“
300GB HUC109030CSS600 42D0628
42D0631
“
“
450GB HUC109045CSS600
81Y9595
81Y9594
“
“
600GB HUC109060CSS600
49Y2023
49Y2026
“
“
900GB HUC109090CSS600
00J0017
81Y3804
“
“
1.2 Microcode Change History
Release date |
Code level |
Change Description |
October, 2014 |
J2EH |
Fix
for a bug which sent 3 IDENTIFY frames to host adapter during speed
negotiation phase. This bug causes the drive to go offline
after a system reboot or power cycle. This bug only affects IBM Power
Blade JS21 (Type/Model: 8844-31U), no other Blade/ITE products are
affected by this issue. |
January, 2014 |
J2EG |
Drive FW enhancement to improve
Sequential read and write performance issue. Other fixes and
enhancements. |
June, 2013 |
J2EC |
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
DEVICE
LOCATION
DESCRIPTION
Vital Product Data
(VPD)
hdisk1
U78AE.001.TA4S004-P1-D1 SAS Disk
Drive (600000 MB)
Manufacturer................IBM-ESXS
Machine Type and
Model......HUC109090CSS60
FRU Number..................49Y2023
ROS Level and ID............4A324548
Serial Number...............KNG21PWF
EC Level....................N24774
Part Number.................49Y2026
Device Specific.(Z0)........000006329F011002
Device Specific.(Z1)........J2EHJ2EHJ2EH
Device Specific.(Z2)........00SS
Device Specific.(Z3)........12045
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........N24774
Hardware Location
Code......U78AE.001.TA4S004-P1-D1
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 "4A324548", 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, 4A Hex=
ASCII character "J"; 32
Hex= ASCII character "2"; 45
Hex=ASCII character "E";
48 Hex=ASCII character "H", microcode
level is "J2EH".
===============================================================
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 C10K900-XP-J2EH.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x C10K900-XP-J2EH.bin
../C10K900-XP-J2EH.bin
[Don't overlook the periods (.) in above command.]
The
directory C10K900-XP-J2EH 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/C10K900-XP-J2EH/* /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 C10K900-XP-J2EH-AIX.rpm
c)
Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv
--ignoreos --force C10K900-XP-J2EH-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
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.
======================================================
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 C10K900-XP-J2EH-AIX.rpm
b) If using SLES 9 SP1 or better or RHEL 4 or better, install
the
package by typing:
rpm -ivh --ignoreos C10K900-XP-J2EH-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 RHEL 6:
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
C10K900-XP-J2EH-AIX.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
C10K900-XP-J2EH-AIX.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
4.0 Drive Fails
Code Update in Power Blade JS21
NOTE:
The following problem only
applies to AIX microcode download in JS21 blade; it does not affect
other
blades and/or operating systems
Problem
Description:
With
disk drive version at or below C274, microcode
update in a Power Blade JS21 using AIX diagnostic utility or Standalone
AIX
diagnostic CD will fail with the following message:
A
software error occurred. Contact the service
support structure for further
assistance.
Workaround:
Before
updating the drive microcode, use the “chdev”
command to change the ‘max_transfer’
size to allow the download utility to transfer larger amount of data.
chdev -l hdisk0 -a max_transfer=0x100000
For data drive
chdev -l hdisk0 -a max_transfer=0x100000
–P
For OS drive
Note: Reboot
is required after the command for OS drive.
After
updating the drive microcode, make sure to set
‘max_transfer’ rate back to 0x40000.
chdev -l hdisk0 -a max_transfer=0x40000
For data drive
chdev -l hdisk0 -a max_transfer=0x40000
–P
For OS drive
Note: Reboot is
required after the command for OS drive.
Note: a. There is no
workaround to update the microcode from Standalone Diagnostic CD. This workaround Requires AIX operating system command
line.