DATE:
Table of Contents
IBM
IDE DVD-RAM Drive (Slim) / RMBO0020511
3.0
Determine the Current Microcode Levels:
4.0
Downloading and Unpacking the RPM File to the Target Server
4.0.2
From the Microcode CD-ROM
5.0
Microcode Download Procedure for Optical Device
=====================================================================================
IBM RMBO0020511
|
|
|
|
|
|
For support: AIX 5.2 ML_04 and above
and AIX 5.3 ML_00 and above
Before you install the microcode, it is important to determine the microcode level of the Drive installed on the target system. Use the following instructions to read the Microcode Level.
1) List the optical
drives attached to the target systems by typing:
lsdev -Cc cdrom
2) To check the current
microcode level for the optical drive, enter the following command
lscfg -vl cdX
Where X is the number associated with
the optical drive listed as available in step 1.
Results of command
# lscfg -vl cd1
cd1
Manufacturer................IBM
Machine Type and Model......RMBO0020511
ROS Level and ID............1.13
Device Specific.(Z0)........058002028F000030
#
4.0.1 From the Web
The user should put the RPM file from the IBM website into the /tmp directory.
The RPM file for this microcode update is called ibm-ide-dvdram.rmbo0020511-1.13.rpm
Once the file is in /tmp
directory, then to unpack the file by executing following commands:
rpm -ihv
--ignoreos ibm-ide-dvdram.rmbo0020511-1.13.rpm
The microcode files will be placed in the /etc/microcode/ directory.
The RPM packaged microcode files should be located in the "/microcode/RPM"
If the user mounts the CD-ROM disc in the
/mnt
directory, then execute the following commands to unpack the microcode.
cd /mnt/microcode/RPM
rpm -ihv --ignoreos ibm-ide-dvdram.rmbo0020511-1.13.rpm
The microcode files will be copied to "/etc/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.
NOTE: Please save current and older versions of the microcode update files in case you need to restore your system.
Please verify the file size and
checksum of the raw microcode files in /etc/microcode/.
To check file size, type these next two commands
into the AIX prompt:
ls -l IBM-RMBO002051.1.13 File
size = 1343928
To determine the checksum type these commands
into the AIX prompt:
sum
IBM-RMBO002051.1.13 check sum = 38400
Procedure:
1. Stop all applications and un-mount any file system that is installed on the
drive. Media does not have to be removed
for the update process to take place.
2. Enter Diagnostics by typing the diag command into the prompt
diag
3. The first screen tells you about Diagnostics. After reading this screen press <enter> to continue
4. Arrow down to the Task Selection is highlighted and press <enter>
5. Arrow down to the Microcode Tasks and press <enter>. (Older versions of the Diagnostic utility does not list Microcode Tasks as an option. If this option is not listed, just skip this step and proceed to step 6. )
6. Arrow down to the Download Microcode is highlighted and press <enter>.
7. Select all of the
8. Select "/etc/microcode" and press <enter>.
9. A dialogue box may display on screen if the /etc/microcode doesn’t
contain the current microcode found on the device. This is just a warning
screen and if the microcode files have the same sum and file size as what is
described above, then the this process should work. Also as a last resort, the drive will reject
any corrupt microcode trying to be loaded on it. Press <enter> to continue.
10. An "M" will be displayed next to the latest level of microcode in
the /etc/microcode directory. Select that level and press <enter>.
11. The following message will appear on the screen when download is completed:
"Microcode download complete successfully. The current microcode
level for the device cd# is
..... Please run diagnostics on the drive to ensure that it is
functioning properly."
12. Verify the microcode levels by repeating process 3.0
Determining Current Microcode Levels.
13. Run diagnostics to make sure the devices are in working order.