README: 36GB 4mm Tape Drive Microcode ------------------------------------------------------------------------ Table of Contents *README: 36GB 4mm Tape Drive Microcode <#Header_1>* # Date: March 16, 2010 <#Header_2> # Versions: V315, B016 and BS11 <#Header_3> # General Information <#Header_4> # Microcode Download Information <#Header_6> # Operating System levels supported: <#Header_7> # Can microcode be installed Concurrently? <#Header_8> # Is system reboot needed to activate the microcode. <#Header_9> # Additional Cautions: <#Header_10> # Machines Affected: <#Header_11> # Microcode Levels <#Header_12> # V315 Drive Microcode History, Feature Code 1991 & 6258 <#Header_13> # B016 Drive Microcode History, Feature Code 1991 & 6258 <#Header_14> # B016 Drive Microcode History, Feature Code 1955 <#Header_15> # BS11 Drive Microcode History, Feature Code 5907 <#Header_16> # Display Microcode Level <#Header_17> # Feature Code 1991(5.25" Drive) <#Header_18> # Feature Code 6258(5.25" Drive) <#Header_19> # Feature Code 1955(3.5" Drive) <#Header_20> # Feature Code 5907(SAS 5.25" Drive) <#Header_21> # Putting the microcode on the system <#Header_22> # From the IBM WEB site via the user downloading the files. <#Header_23> # From a CD-ROM. <#Header_24> # Packaged Microcode Files <#Header_25> # AIX bin file <#Header_26> # RPM file <#Header_27> # Verifying the Microcode <#Header_28> # Which Microcode file to Use? <#Header_29> # You downloaded "RPM" files <#Header_30> # You downloaded the AIX zip file <#Header_31> # Copy files for AIX diagnostics <#Header_32> # Copy files for Genucode <#Header_34> # How to Use AIX 5.1 Diagnostics Microcode Download <#Header_36> ------------------------------------------------------------------------ README: 36GB 4mm Tape Drive Microcode <#ToC_1> Date: March 16, 2010 <#ToC_2> Versions: V315, B016 and BS11 <#ToC_3> ------------------------------------------------------------------------ General Information <#ToC_4> ******* PLEASE READ THIS ENTIRE NOTICE ********* This package is being provided to allow the update of older IBM 36GB 4mm Tape Drives to the current level of microcode that is currently shipping from IBM. * * *Customers are responsible to install the latest microcode level themselves. The microcode and instructions are available at the IBM external web site: http://www-933.ibm.com/support/fixcentral/ * ------------------------------------------------------------------------ Microcode Download Information <#ToC_6> In order to complete the microcode download to a 36GB 4mm tape drive you will need use AIX 5.1 diagnostics, or higher, or the Genucode program. The Genucode package is available from the IBM WEB site: * http://www14.software.ibm.com/webapp/set2/firmware/gjsn * For both the AIX diagnostic package and for the genucode package from the WEB you will need the * microcode * and * dsdata * files in this package. *This package, the 36GB 4mm package, will get you to step where you will need to use AIX diagnostics or Genucode to download the microcode into the tape drive. * * * **Note: *The BS11 level of microcode supports the new Serial Attached SCSI(SAS) DAT72 tape drive. The BS11 level of microcode is included as a reference only as this General Availability level of this drives microcode and there is no need to update a DAT72 SAS drive with this microcode as this level is already in the drive. * ------------------------------------------------------------------------ Operating System levels supported: <#ToC_7> All levels of AIX that this product was announced on. ------------------------------------------------------------------------ Can microcode be installed Concurrently? <#ToC_8> Yes, but the tape drive must be available with no tape in the drive, and no other processing running to the tape drive. ------------------------------------------------------------------------ Is system reboot needed to activate the microcode. <#ToC_9> A reboot is not needed as the microcode is active in the drive when the drive completes microcode download. If the microcode install is done with Genucode the tape drive Vital Product Data(VPD) will not show the new microcode level until you use the AIX * rmdev * and * mkdev * commands to remove and add back the tape drive. Diagnostics does the * rmdev * and * mkdev * for you so you do not need to do the commands. The typical time to install this microcode is .4 hrs. The microcode becomes active when installed and does not require a system reboot to become active. ------------------------------------------------------------------------ Additional Cautions: <#ToC_10> *Note: * Do not power off the tape drive during microcode download as this may damage the tape drive microcode requiring the tape drive to be replaced. Remove any tape cartridge from the drive prior to attempting the microcode download. ------------------------------------------------------------------------ Machines Affected: <#ToC_11> All eServer pSeries and RS/6000 machines this product was announce on. In general if the tape drive configures and is available with the VPD showing the Machine Type and microcode level as described in this README the machine is one affected. ------------------------------------------------------------------------ Microcode Levels <#ToC_12> There are now three different microcode files for the DAT72 tape drive: * Two different, but equivalent levels of the DAT72 Low Voltage Differential(LVD) SCSI tape drive. There is the level that uses * V315 * level of microcode. This is the original drive. The new RoHS compliant level that uses the * B016 * level of the microcode. The drives look similar but internally they are different, that is why there are two different microcode files for the of the DAT72 LVD drive. There are different P/Ns for the different LVD drives. levels of the drive. * The new DAT72 Serial Attached SCSI(SAS) tape drive introduced in late 2007. This drive uses the * BS11 * level of microcode. This is feature code * 5907. * V315 Drive Microcode History, Feature Code 1991 & 6258 <#ToC_13> The microcode update will bring the IBM 36GB 4mm tape drive up to the current level of microcode which is: * V315 * *Table 1. Microcode History* Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID Release Date What does this microcode change 18P8777 18P8779 V311 A170029F Nov 2003 * First Microcode level shipped. 18P8777 18P8779 V314 A170029F July 2004 * Implementation of additional statically data saved within the drive. * Added check of internal drive information during diagnostics. * Updated checks for 50 tape motion hours since the drive was last cleaned. 18P8777 24R1986 18P8779 24R1987 V315 A170029F A1700D59 Feb 2005 * Release of new drive P/N 24R1986 and FRU P/N 24R1987. *Note: *The tape drive microcode is for the tape drive Part Number and Device Specific(LI) combination. Use the specific microcode file that corresponds to the tape drive Part Number and Device Specific(LI) combination. B016 Drive Microcode History, Feature Code 1991 & 6258 <#ToC_14> The microcode update will bring the 5.25" IBM 36GB 4mm tape drive up to the current level of microcode which is: * B016 * *Table 2. Microcode History* Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID Release Date What does this microcode change 95P1986 95P1987 95P1988 95P1989 B007 A1700D61 A1700D62 Feb 2006 * First Microcode level shipped. 95P1986 95P1987 95P1988 95P1989 B010 A1700D61 A1700D62 Nov 2006 * Correct rewind/load handling when the tape drive reports cleaning required on a rewind command. 95P1986 95P1987 95P1988 95P1989 B011 A1700D61 A1700D62 Feb 2007 * Modify the tape drive diagnostics to improve the drives diagnostic for Error Rate Check process. 95P1986 95P1987 95P1988 95P1989 B012 A1700D61 A1700D62 June 2007 * Additional modifications to the tape drive diagnostics to improve the drives diagnostic for Error Rate Check process. * Modifications to support drive internal HW changes for component changes. * Remove "H0" from the Vital Product Data(VPD). 95P1986 95P1987 95P1988 95P1989 B013 A1700D61 A1700D62 Nov 2007 * Fix to report any errors on rewind that were previously not reported. * Change time for holding the eject button for emergency/forced eject from 5 seconds to 20 seconds. * Fix occasional formatting issue with 2 partition tape. 95P1986 95P1987 95P1988 95P1989 B014 A1700D61 A1700D62 May 27, 2008 * Request cleaning when a bad tape fails to load. * Improve Reset and Abort handling. * Fix causes of read and read filemark errors. * Change to not eject tapes in a drive when microcode download is done. (This will take effect after the microcode is downloaded) 95P1986 95P1987 95P1988 95P1989 B015 A1700D61 A1700D62 April 6, 2009 * * Internal Drive Self Test Implemented * * Request Sense flags to indicate state of drive/media * Added additional information to the tape drive internal log. 95P1986 95P1987 95P1988 95P1989 B016 A1700D61 A1700D62 March 9, 2010 * Indicate the drive Internal Self Test(IST) IST has been initiated by flashing the Ready LED. * Modify IST to check the dead bit after the tape is loaded. If the dead bit is set, fail without performing the diagnostic. B016 Drive Microcode History, Feature Code 1955 <#ToC_15> The microcode update will bring the 3.5" IBM 36GB 4mm tape drive up to the current level of microcode which is: * B016 * *Table 3. Microcode History* Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID Release Date What does this microcode change 23R2618 23R2619 B008 A1700D62 Feb 2006 * First Microcode level shipped. 23R2618 23R2619 B010 A1700D62 Nov 2006 * Correct rewind/load handling when the tape drive reports cleaning required on a rewind command. 23R2618 23R2619 B011 A1700D62 Feb 2007 * Modify the tape drive diagnostics to improve the drives diagnostic for Error Rate Check process. 23R2618 23R2619 B012 A1700D62 June 2007 * Additional modifications to the tape drive diagnostics to improve the drives diagnostic for Error Rate Check process. * Modifications to support drive internal HW changes for component changes. 23R2618 23R2619 B013 A1700D62 Nov 2007 * Fix to report any errors on rewind that were previously not reported. * Change time for holding the eject button for emergency/forced eject from 5 seconds to 20 seconds. * Fix occasional formatting issue with 2 partition tape. 23R2618 23R2619 B014 A1700D62 May 27, 2008 * Request cleaning when a bad tape fails to load. * Improve Reset and Abort handling. * Fix causes of read and read filemark errors. * Change to not eject tapes in a drive when microcode download is done. (This will take effect after the microcode is downloaded) 23R2618 23R2619 B015 A1700D62 April 6, 2009 * * Internal Drive Self Test Implemented * * Request Sense flags to indicate state of drive/media * Added additional information to the tape drive internal log. 23R2618 23R2619 B016 A1700D62 March 9, 2010 * Indicate the drive Internal Self Test(IST) IST has been initiated by flashing the Ready LED. * Modify IST to check the dead bit after the tape is loaded. If the dead bit is set, fail without performing the diagnostic. BS11 Drive Microcode History, Feature Code 5907 <#ToC_16> The microcode update will bring the IBM 36GB 4mm SAS tape drive up to the current level of microcode which is: * BS11 * *Table 4. Microcode History* Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID Release Date What does this microcode change 23R2528 23R2530 BS08 A1700D65 Nov 2007 * First Microcode level shipped. 23R2528 23R2530 BS09 A1700D65 May 27, 2008 * Request cleaning when a bad tape fails to load. * Improve Reset and Abort handling. * Fix causes of read and read filemark errors. * Change to not eject tapes in a drive when microcode download is done. (This will take effect after the microcode is downloaded) 23R2528 23R2530 BS10 A1700D65 May 27, 2008 * * Internal Drive Self Test Implemented * * Request Sense flags to indicate state of drive/media * Added additional information to the tape drive internal log. 23R2528 23R2530 BS11 A1700D65 March 9, 2010 * Indicate Internal Self Test(IST) has been initiated by flashing the Ready LED. * Modify IST to check the dead bit after the tape is loaded. If the dead bit is set, fail without performing the diagnostic. ------------------------------------------------------------------------ Display Microcode Level <#ToC_17> *Note: *In some cases you may already have the most current level of microcode already installed. The following instructions show you how to check the tape drive microcode level. To display the level of microcode in the tape drive do the following AIX command: lscfg -vl rmt0 <--- change the drive number to reflect the actual rmt address of the 36GB 4mm tape drive. The output of the lscfg command will look like the following with the * "Device Specific.(Z1)" * showing the microcode level: Feature Code 1991(5.25" Drive) <#ToC_18> * * * rmt0 P1/Z1-A3 SCSI 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 H0 Device Specific.(Z1)........V315 Serial Number...............25001R23 Device Specific.(LI)........A1700D59 Part Number.................24R1986 FRU Number..................24R1987 EC Level....................H81257 Device Specific.(Z0)........0180020283000130 Device Specific.(Z3)........L1 * * OR * * * * rmt0 P1/Z1-A3 SCSI 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 H0 Device Specific.(Z1)........B007 Serial Number...............2559X025 Device Specific.(LI)........A1700D62 Part Number.................95P1987 FRU Number..................95P1989 EC Level....................H81467 Device Specific.(Z0)........0180020283000130 Device Specific.(Z3)........L1 * The B016 level of microcode removes the H0 from the drive vital product data. * Manufacturer................IBM Machine Type and Model......DDS Gen5 H0 Device Specific.(Z1)........B007 With B016 or higher the Vital Product Data is now Manufacturer................IBM Machine Type and Model......DDS Gen5 Device Specific.(Z1)........B016 * Feature Code 6258(5.25" Drive) <#ToC_19> * * * rmt0 P1/Z1-A3 SCSI 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 Device Specific.(Z1)........V315 Serial Number...............50011445 Device Specific.(LI)........A170029F Part Number.................18P8777 FRU Number..................18P8779 EC Level....................H80564 Device Specific.(Z0)........0180020283000130 Device Specific.(Z3)........L1 * * OR * * * * rmt0 P1/Z1-A3 SCSI 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 Device Specific.(Z1)........B016 Serial Number...............20589015 Device Specific.(LI)........A1700D61 Part Number.................95P1986 FRU Number..................95P1988 EC Level....................H81467 Device Specific.(Z0)........0180020283000130 Device Specific.(Z3)........L1 * Feature Code 1955(3.5" Drive) <#ToC_20> * * * rmt0 P1/Z1-A3 SCSI 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 Device Specific.(Z1)........B016 Serial Number...............2659X042 Device Specific.(LI)........A1700D62 Part Number.................23R2618 FRU Number..................23R2619 EC Level....................H81486 Device Specific.(Z0)........0180020283000130 Device Specific.(Z3)........L1 * Feature Code 5907(SAS 5.25" Drive) <#ToC_21> * * * rmt0 U787A.001.DPM0LVZ-P1-C1-T1-L0-L0 SAS 4mm Tape Drive (36000 MB) Manufacturer................IBM Machine Type and Model......DDS Gen5 Device Specific.(Z1)........BS11 Serial Number...............20670009 Load ID.....................A1700D65 Part Number.................23R2528 FRU Number..................23R2530 EC Level....................H82070 Device Specific.(Z0)........0180030283001000 Device Specific.(Z3)........L1 * ------------------------------------------------------------------------ Putting the microcode on the system <#ToC_22> There are 2 ways a user can get the microcode files. Each of these will put the microcode on the user's system but the user may have to move the files to appropriate directory for system use. From the IBM WEB site via the user downloading the files. <#ToC_23> When the user downloads the microcode files from the IBM web site the user will put the packaged microcode files in to the * /tmp * directory. * If the user downloads the * 36GB4mm.bin * file the user will put the downloaded file into the * /tmp * directory and then use the instructions in the section of this README titled * "AIX bin file". * * If the user downloads the * Tape4mm36GB-V315B016BS11-01.rpm * file the user will put the downloaded file into the * /tmp * directory and then use the instructions in the section of this README titled * "RPM file". * From a CD-ROM. <#ToC_24> * If the CD-ROM process is used to put the * 36GB4mm.bin * file on the user system the microcode files will expanded into the * /tmp/36GB4mm_web * directory. The next step is to follow the instructions in this README titled * "AIX bin file" * and copy the files to the appropriate directory. The building and putting of the files into the * /tmp/36GB4mm_web * directory was done by the user when they used the CD-ROM build instructions. * Tape4mm36GB-V315B016BS11-01.rpm * file. * If the CD-ROM RPM process is used to put the * Tape4mm36GB-V315B016BS11-01.rpm * file on the user system the microcode files will be in the * tmp/microcode/RPM * directory. To put the microcode in the appropriate directory for the system the user executes the following AIX commands: * cd /tmp/microcode/RPM rpm -ihv --ignoreos Tape4mm36GB-V315B016BS11-01.rpm * This puts the following files in the * /etc/microcode * directory for system use: * o DDS_Gen5.A170029F.V315 o DDS_Gen5.A170029F.dsdata o DDS_Gen5.A1700D59.V315 o DDS_Gen5.A1700D59.dsdata o DDS_Gen5.A1700D61.B016 o DDS_Gen5.A1700D61.dsdata o DDS_Gen5.A1700D62.B016 o DDS_Gen5.A1700D62.dsdata o DDS_Gen5.A1700D65.BS11 o DDS_Gen5.A1700D65.dsdata * The next step is to follow the instructions in this README titled * "Verifying the Microcode". * *Note: * * AIX commands and file names are case sensitive. If the users AIX permission does not allow the copy to the above stated directory or file then the user will be prompted for a new location. * ------------------------------------------------------------------------ Packaged Microcode Files <#ToC_25> AIX bin file <#ToC_26> * Download the * 36GB4mm.bin * file to the eServer pSeries or RS/6000 to the * /tmp * directory. * Do the following AIX commands to make the file executable: * cd /tmp chmod +x 36GB4mm.bin * * To expand the * 36GB4mm.bin * file use the following command: * ./36GB4mm.bin * *Note: *The * ./ * before the command insures AIX paths thru the current directory to find the command. This with put the following files in the * /tmp/36GB4mm_web * directory: * o DDS_Gen5.A170029F.V315 o DDS_Gen5.A170029F.dsdata o DDS_Gen5.A1700D59.V315 o DDS_Gen5.A1700D59.dsdata o DDS_Gen5.A1700D61.B016 o DDS_Gen5.A1700D61.dsdata o DDS_Gen5.A1700D62.B016 o DDS_Gen5.A1700D62.dsdata o DDS_Gen5.A1700D65.BS11 o DDS_Gen5.A1700D65.dsdata * RPM file <#ToC_27> * Download the * Tape4mm36GB-V315B016BS11-01.rpm * file to the eServer pSeries or RS/6000 to the * /tmp * directory. * To expand the * Tape4mm36GB-V315B016BS11-01.rpm * file use the following commands: * cd /tmp rpm -ihv --ignoreos Tape4mm36GB-V315B016BS11-01.rpm * * You will have the following files in the * /etc/microcode * directory: * o DDS_Gen5.A170029F.V315 o DDS_Gen5.A170029F.dsdata o DDS_Gen5.A1700D59.V315 o DDS_Gen5.A1700D59.dsdata o DDS_Gen5.A1700D61.B016 o DDS_Gen5.A1700D61.dsdata o DDS_Gen5.A1700D62.B016 o DDS_Gen5.A1700D62.dsdata o DDS_Gen5.A1700D65.BS11 o DDS_Gen5.A1700D65.dsdata * ------------------------------------------------------------------------ Verifying the Microcode <#ToC_28> Change to the directory where the microcode was just placed. * cd /tmp/36GB4mm_web or cd /etc/microcode * To insure the file was downloaded without error use the AIX command sum to get the checksum of the microcode file: * sum DDS* * Compare the sum you got with the sum of the file here, if they do not match recheck your steps in creating the file on the system: * 09240 331 DDS_Gen5.A170029F.V315 51855 2 DDS_Gen5.A170029F.dsdata 09240 331 DDS_Gen5.A1700D59.V315 23767 2 DDS_Gen5.A1700D59.dsdata 45686 298 DDS_Gen5.A1700D61.B016 10286 2 DDS_Gen5.A1700D61.dsdata 45686 298 DDS_Gen5.A1700D62.B016 53937 2 DDS_Gen5.A1700D62.dsdata 31138 314 DDS_Gen5.A1700D65.BS11 31004 2 DDS_Gen5.A1700D65.dsdata * ------------------------------------------------------------------------ Which Microcode file to Use? <#ToC_29> You downloaded "RPM" files <#ToC_30> If you downloaded the RPM file to the system and expanded it AIX diagnostics will use the appropriate file for updating the drive. Go to the step in this documentation * "How to Use AIX 5.1 Diagnostics Microcode Download". * You downloaded the AIX zip file <#ToC_31> If you downloaded the zip file you will need to determine which microcode file to use and copy the file with the appropriate name to the appropriate directory. You need to determine how you are going to download the microcode: * AIX 5.1 diagnostics(or higher). * or * * Genucode. AIX diagnostics and Genucode use different naming conventions for the microcode and dsdata file. * AIX diagnostics requires the microcode file and the dsdata file to be in the * /etc/microcode * directory. * Genucode requires the microcode file and the dsdata file to be in the * /tmp * directory. Once you have determined which program you are going to use, AIX diagnostics or Genucode, you will need to copy the appropriate files from the /tmp directory to the appropriate directory: Copy files for AIX diagnostics <#ToC_32> * * *cd /tmp/36GB4mm_web cp DDS_Gen5.A170029F.V315 /etc/microcode/DDS_Gen5.A170029F.V315 cp DDS_Gen5.A170029F.dsdata /etc/microcode/DDS_Gen5.A170029F.dsdata cp DDS_Gen5.A1700D59.V315 /etc/microcode/DDS_Gen5.A1700D59.V315 cp DDS_Gen5.A1700D59.dsdata /etc/microcode/DDS_Gen5.A1700D59.dsdata or cp DDS_Gen5.A1700D61.B016 /etc/microcode/DDS_Gen5.A1700D61.B016 cp DDS_Gen5.A1700D61.dsdata /etc/microcode/DDS_Gen5.A1700D61.dsdata cp DDS_Gen5.A1700D62.B016 /etc/microcode/DDS_Gen5.A1700D62.B016 cp DDS_Gen5.A1700D62.dsdata /etc/microcode/DDS_Gen5.A1700D62.dsdata or cp DDS_Gen5.A1700D65.BS11 /etc/microcode/DDS_Gen5.A1700D65.BS11 cp DDS_Gen5.A1700D65.dsdata /etc/microcode/DDS_Gen5.A1700D65.dsdata * Run AIX Diagnostics For instructions on using the AIX Diagnostics microcode download capability refer to the section of this document titled "How to Use AIX 5.1 Diagnostics Microcode Download". Copy files for Genucode <#ToC_34> Genucode uses a file */tmp/dsdata * to control microcode update in the tape drives. The */tmp/dsdata * file is unique based on the * Load ID * of the tape drive. Depending on the * Load ID * you will need to copy different files. To determine the * Load ID * of the tape drive refer to the * Display Microcode Level * section of this document. The * Load ID * of the drive is the * Device Specific.(LI)........A1700D62 *. In this example its the * A1700D62 * Depending on the * Load ID * of your drive you will need to copy the files with the corresponding * Load ID * to the * /tmp * directory. * cd /tmp/36GB4mm_web cp DDS_Gen5.A170029F.V315 /tmp/DDS_Gen5.V315.A170029F cp DDS_Gen5.A170029F.dsdata /tmp/dsdata or cp DDS_Gen5.A1700D59.V315 /tmp/DDS_Gen5.V315.A1700D59 cp DDS_Gen5.A1700D59.dsdata /tmp/dsdata or cp DDS_Gen5.A1700D61.B016 /tmp/DDS_Gen5.B016.A1700D61 cp DDS_Gen5.A1700D61.dsdata /tmp/dsdata or cp DDS_Gen5.A1700D62.B016 /tmp/DDS_Gen5.B016.A1700D62 cp DDS_Gen5.A1700D62.dsdata /tmp/dsdata * Run Genucode You now need to use the instructions in the Genucode package to complete the install of the microcode. Once you have completed the instructions in the genucode package the drive will be at the current microcode level and the microcode update is complete. ------------------------------------------------------------------------ How to Use AIX 5.1 Diagnostics Microcode Download <#ToC_36> There are 2 ways to do the microcode download using the AIX diagnostics. * Using the AIX Diagnostics menu * Using the AIX Diagnostics via command line input. Using the AIX Diagnostics menu To use the AIX 5.1 diagnostics menu for microcode download do the following: * diag (enter) Task Selection (enter) Download Microcode (enter) * Select the drive you wish to download microcode to and follow the system instructions. *Note: * When the system asks where the microcode file is to be found select * /etc/microcode, not diskette. * Using the AIX Diagnostics via command line input. The command line to download microcode will use the highest level of microcode in the /etc/microcode directory for the device selected. To use the AIX 5.1 diagnostics command line input for microcode download do the following: *Note: *If the previous level of microcode is not in the /etc/microcode directory you will need to use the -f option(force) as the diagnostics expect the previous level to be present in the /etc/microcode directory. * diag -c -d rmt0 -T "download" (enter) * *or* *diag -c -d rmt0 -T "download -f" (enter) *