*IBM eServer SAS Enclosure Services for 8202-E4B/E4C/E4D & 8205-E6B/E6C/E6D* *FC 5630, EJ01 CCIN 2BD6* *0009** Microcode Update* DATE: Dec 20, 2013 *Table of Contents* *1.0 Microcode Change History <#1.0>* *2.0 General Information <#2.0>* *2.1 Installation Time <#2.1> 2.2 Machine's Affected <#2.2> 2.3 AIX Requirements <#2.3> 2.4 Linux Requirements <#2.4>* *2.5 IBM i Requirements <#2.5>* *3.0 Determine the Current Microcode Level for AIX <#3.0> **3.1 Determine the Current Microcode Level for Linux <#3.1>* *4.0 Downloading and Unpacking the Firmware Update Package from CORE <#4.0>* *4.1 Downloading the RPM Format File to the Target Server <#4.1>* *4.2 Microcode Update via CD <#4.2>* *5.0 Verifying microcode before download and notes <#5.0>* *5.1 Microcode Download Procedure-SAS Enclosure Services for FC 5652 for AIX <#5.1> **5.2 Microcode Download Procedure-SAS Enclosure Services for FC 5652 for Linux <#5.2>* *6.0 Microcode Readme Change History <#6.0>* *=====================================================================================* *1.0 Microcode Change History:* 0009 -Corrected EPOW function to send Notify Primitive Previously, the SAS Expanders on this DASD backplane would not send the Notify (of unexpected power off) primitive on an EPOW (unexpected power off event). Notify gives the disk drive a slight advance warning that power is about to drop. When Notify is received, the drive stops accepting new write commands and finishes all writes in process prior to power off. Without the notify being received, there is a slight chance that a write command could be in process. If that occurred then there would be a write splice on the disk drive. On the next drive power on, this would be detected as a bad sector. 0008 -GA Level * 2.0 General information* *NOTE:* Microcode update cannot be performed to both SAS expanders (SES) at the same time. * 2.1 Installation Time:* Approximately 30 minutes *2.2 Machine's Affected:* 8202-E4B/E4C/E4D & 8205-E6B/E6C/E6D * 2.3 AIX Requirements:* AIX 5.3TL10 SP5 AIX 5.3TL11 SP5 AIX 5.3TL12 SP2 AIX, 6.1TL06 AIX 7.1 or above * 2.4 Linux Requirements:* SUSE Linux Enterprise Server 10-SP3, 11-SP1 for POWER or above Red Hat Enterprise Linux for POWER Version 5 Update 5 or above * 2.5 IBM i Requirements:* IBM I 7.1 or later * 3.0 Determine the Current Microcode Level for AIX:* Before you install the microcode, it is important to determine the microcode level of the Adapter installed in the target system. Use the following instructions to read the ROM level stored in the Adapter's VPD. 1) List the SES installed in the system by typing: lsdev -C | grep ses Note: All of the SAS RAID initiators addresses that are installed will be displayed. The names will be sesX, where X is 0, 1, etc. 2) To check the current microcode level for the adapter or controller enter the following command lscfg -vl sesX Where X is the number/s of the previous command. The Command will produce output similar to * DEVICE LOCATION DESCRIPTION* ses0 U78AA.001.WIH002J-P2-Y2 SAS Enclosure Services Device *ROM Level.(alterable).......0008* Hardware Location Code......U78AA.001.WIH002J-P2-Y2 If the *ROS Level and ID* is less than *0009* then you should update the microcode. * 3.1 Determine the Current Microcode Level for Linux:* 1) Type "iprconfig" 2) Select "Display hardware status" 3) Select SES by typing a "1" in front of it and pressing Enter. 4) The Command will produce output similar to "*Firmware Version . . . . . . . . . . . . : 0008*" If the *Firmware Version* is less than *0009* then you should update the microcode. *4.0 Downloading and Unpacking the Firmware Update Package from CORE* NOTE: The CORE image will now be the RPM Format File. 1) After downloading the files from CORE on to your personal system find the following files in the CORE destination directory (c:\ibmdocs\DISKIMG): A) "*ses.5630.8pack-0009-1.aix5.1.noarch.rpm*" B) "*ses.5630.8pack-0009-1.Linux.noarch.rpm*" 2) Log in to the Target Server 3) Create a directory, if not already existent (mkdir /tmp/microcode; mkdir /tmp/microcode/RPM) 4) Transfer the file to the Target Server "/tmp/microcode/RPM directory" using ftp or another method. Change to that directory, "cd /tmp/microcode/RPM". 5a) For AIX: Unpack the RPM file by using the following command: "rpm -ihv --ignoreos --force ses.5630.8pack-0009-1.aix5.1.noarch.rpm" 5b) For Linux: Unpack the RPM file by using the following command: "rpm -ihv --ignoreos --force ses.5630.8pack-0009-1.Linux.noarch.rpm" 6a) For AIX: The microcode files will be added to /usr/lib/microcode/. 6b) For Linux: The microcode files will be added to /lib/firmware/. *4.1 Downloading the RPM Format File to the Target Server* Use this method to download to an AIX or Linux system: *Note:* The instructions that follow are specific AIX/Linux commands. AIX/Linux commands are CASE (lower and upper) SENSITIVE, and */must/* be entered exactly as shown, including filenames. 1) Make a directory on an AIX/Linux system to receive the RPM format file. Enter: "mkdir /tmp/microcode" Enter: "mkdir /tmp/microcode/RPM" 2) Transfer the RPM format file to the /tmp/microcode/RPM directory (using "Save as ..."). Change to that directory, "cd /tmp/microcode/RPM". You'll see the filenames for the RPM files. A) For AIX: The filename is *ses.5630.8pack-0009-1.aix5.1.noarch.rpm * B) For Linux: The filename is * ses.5630.8pack-0009-1.Linux.noarch.rpm *3) Unpack the file by executing the instructions below: A) For AIX: Type "*rpm -ihv --ignoreos --force ses.5630.8pack-0009-1.aix5.1.noarch.rpm" * B) For Linux: Type "*rpm -ihv --ignoreos --force ses.5630.8pack-0009-1.Linux.noarch.rpm"* 4a) For AIX: The microcode files will be added to /usr/lib/microcode/. 4b) For Linux: The microcode files will be added to /lib/firmware/. * 4.2 Microcode Update via CD* Below are references and the general flow on how to update microcode update via CD 1) Boot the system via a Standalone Diagnostic's CD b) To create a bootable Diagnostic's CD go to the following URL. Burn cdlatest.iso on to a CD-R (or CD-RW). Currently, DVD media cannot be utilized. http://www14.software.ibm.com/webapp/set2/sas/f/diags/home.html c) After booting to Standalone Diagnostics, the Diagnostic's CD can be removed. 2) The Diagnostic's CD should be replaced by a CD containing the unpacked microcode image(s). The CD containing the microcode images should be prepared prior. This can be done by taking the rpm file(s) from the microcode download site and unpacking them on a usable server. The unpacked files can then be burned on to the CD media. b) Another method is to use a Microcode Update CD See the below website for more details http://www14.software.ibm.com/webapp/set2/firmware/lgjsn?mode=10&page=cdrom.html#downloadcdrom The Microcode Update CD and Discovery Tool can also be ordered through the following link http://www14.software.ibm.com/webapp/set2/firmware/lgjsn?mode=10&page=compare.html&title=Microcode%20Survey%20and%20update%20tool * 5.0 Verifying microcode before download and notes* *NOTE:* Microcode download must be performed separately for each "ses" under distinct Logical Partitions (LPAR's). Please save current and older versions of the microcode update files in case you need to restore your system. *NOTE:* Microcode update cannot be performed to both SAS expanders (SES) at the same time. /Installation Time: /Approximately 30 min System Time. Please verify the file size and checksum of the raw microcode files matches the below.* **Filesize: 379296* *Checksum: 31421* For AIX: "ls -l /usr/lib/microcode/A1700DE6.0009" to verify Filesize. "sum /usr/lib/microcode/A1700DE6.0009" to verify Checksum. For Linux: "ls -l /lib/firmware/IBM-A1700DE6.0009" to verify Filesize. "sum /lib/firmware/IBM-A1700DE6.0009" to verify Checksum. For systems that have LPAR installed, the microcode file must be placed on all partitions that have a SES device in order to update the code. Follow this procedure for each partition: For AIX: A) Log into the target partition. B) Type: "cd /usr/lib/microcode" C) FTP (for AIX) or SFTP (for Linux) to the partition that has the media bay assigned. (ie. ftp/sftp partition1.ibm.com) D) Type: "cd /usr/lib/microcode" E) If using FTP then Type: "bin" F) Type: "get A1700DE6.0009" G) Type: "quit" For Linux: A) Log into the target partition. B) Type: "cd /lib/firmware" C) SFTP to the partition that has the media bay assigned. (ie. "sftp partition1.ibm.com") D) Type: "cd /lib/firmware" E) Type: "get IBM-A1700DE6.0009" F) Type: "quit" *5.1 Microcode Download Procedure-**SAS Enclosure Services for FC 5652 for AIX* */Procedure:/* 1) It is advised, but not necessary to stop all applications. 2) Enter diag 3) Select the "Task Selection" from diagnostics menu. 4) Select "Download Microcode" or "Microcode Tasks -> Download Microcode" from "Task Selection" menu. 5) Select all of the SAS Enclosure Services (FC 5652) that need to be updated from the list of devices by pressing "Enter". The devices will be displayed as ses#, where # is the number of the device. Press "F7". 6) A dialogue box will be displayed on screen. Press "Enter" to continue. 7) Select "/usr/lib/microcode". 8) A dialogue box will may be displayed on screen. It will state that the current microcode level on the adapter is not in the /usr/lib/microcode directory. This is acceptable as you will be flashing new microcode onto the adapter. Also, incorrect code will automatically be rejected. Press "Enter" to continue. 9) An "M" will be displayed next to the latest level of microcode in the /usr/lib/microcode directory. Select that level and press "Enter". 10) The following message will appear on the screen when download is completed: "Microcode download complete successfully. The current microcode level for the device ses# is ..... Please run diagnostics on the adapter to ensure that it is functioning properly." DO NOT run diagnostics on the device at this time. 11) Exit diagnostics. 12) Verify the code level is 0009 by typing "lscfg -vl ses#" for each SES device updated. *5.2 Microcode Download Procedure-SAS Enclosure Services for FC 5652 for Linux* */Procedure:/* 1) Stop all applications. 2) Type "iprconfig" and press "Enter". 3) Select "Download Microcode" and press "Enter". 4) Select all of the SAS Enclosure Services (FC 5652) that need to be updated from the list of devices by pressing "1". Then press "Enter". 5) Select the appropriate microcode image to flash by pressing "1". (The image will end in 0009). Press Enter. Press Enter again to confirm. 6) If multiple devices were selected in step 4, then repeat step 5 until finished. *6.0 Microcode Readme Change History* 2013-12-20 -Added 8202-E4D, 8205-E6D 2012-01-20 -Added FC EJ01 and MTMs 8202-E4C, 8205-E6C 2011-07-19 -Enhanced description of the microcode fix in level 0009 2011-06-28 -First Readme for release of Microcode level 0009