REVISED: Jan 11, 2007
3.0 Cautions and Important Notes
4.0 Determine Current Microcode Level
5.0 Downloading and Unpacking the Firmware
Update
Package from WEB (AIX binary)
5.1 Downloading and Unpacking the Firmware Update
Package from CORE
5.2
Downloading the RPM format to the Target Server
5.3 Discovery Tool Microcode CD-ROM creation and download
instructions
6.0 Microcode Download Procedure
7.0 Restoring the Array Configuration on the New Adapter
Adapter Firmware Level |
Description of Code |
NOTE |
Note levels 4.50.01, 4.70.11 and 4.84.01 have proven to be equivalent on pSeries. Any of these levels are acceptable to be installed on the adapter. Any level 5.xx.xx or above is xSeries only microcode. FRU replacements typically come w/ a xSeries microcode level flashed on the adapter. If one of these levels is on the adapter please downlevel the microcode. |
4.84.01 |
Large Sequential Write Enhancements, Spin Down Defunct Drives |
4.70.11 |
Further Command Timeout Fixes |
4.50.01 |
Fixes Command Timeout Issue |
4.20.18 |
First Customer Ship Level |
7025 - F50, F80, H70,
6F0, 6F1
7026 - H50, H70, H80, M80, B80, 6H0, 6H1, 6M1
7028 - 6C1, 6E1, 6C4, 6E4
7029 - 6C3, 6E3
7038 - 6M2
7043 - 150, 260, 270
7044 - 170, 270
7046 - B50
7311 - D10, D20
9112 - 265, 275
Approximately 30 min
1) Remove cables from the adapter noting which cable goes to which connector so they can be reconnected in exactly the same positions
2) Remove the battery backed-up cache card from the base card by removing the 8 screws visible when looking at the battery side of the adapter
3) Carefully separate the 2 cards by rocking the cache card near the connectors joining the 2 cards. Do not disconnect the battery wires because there may be valid data in the the battery backed-up cache card
4) Install the battery backed-up cache card on the replacement base card being careful to position the battery wires so they do not interfere with the mounting screws or the PCI connector
5) Reinstall the adapter and cables in the system
Before you install the microcode, it is important to determine the Microcode level of the adapter when you install it in the target system. Use the following instructions to read the Loadable Microcode Level stored in the adapter's non-volatile memory
1) List the PCI Raid adapters installed in the system by typing:
lsdev -C | grep scraid
Note the device names of all PCI 4-Channel PCI Ultra3 SCSI Raid Adapters installed. The adapter device name will be scraidX,where X is 0,1, or some other number
Identify the name of the card you just installed
2) To check the current microcode level for the adapter enter the following command
lscfg -vl scraidX
Where X is the number of the card you just installed
The Command will produce output similar to
The adapter microcode is listed in the field Loadable Microcode Level. In the case below, the adapter microcode is 6.20.01
DEVICE LOCATION DESCRIPTION
scraid0 20-58 PCI 4-Channel Ultra3 SCSI RAID Adapter
Part Number.................09P1521
EC Level....................0H10522
Serial Number...............00000001
FRU Number..................37L6892
Manufacturer................IBM000
Displayable Message.........UL3RAID
Diagnostic Level............03
Device Driver Level.........03
Loadable Microcode Level....6.20.01
ROS Level and ID............4.00.26
Device Specific.(YL)........P2-I9
If the FRU Number is 37L6892 and Loadable Microcode Level is different than 4.50.01, 4.70.11 or 4.84.01 as it is in the above case (6.20.01) then you should update the microcode
The WEB package is found under the Adapter Microcode section. The filename is tr48401.bin. It is a self expanding executable which will create a directory containing the download code and these instructions for replacing the adapter base card FRU:
* readme (these instructions as text)
* 2e1014C.4.84.01 (update code)
In the table for Adapter Microcode, find PCI 4-Channel Ultra SCSI RAID Adapter In the Files to read/download column, you will find: Description (this instructions document), AIX Format file (for downloading to an AIX system or workstation) You will want a copy of the description (instructions document) and AIX format file. Detailed download/unpacking instructions is as follows for AIX format files:
A) Make a directory on an AIX system to receive the AIX format file. Enter:
mkdir /tmp/raidtemp
Note: if the directory /tmp/raidtemp already exists, make sure it
is empty before proceeding.
B) Transfer the AIX format file to the /tmp/raidtemp directory
(using "Save as..."). You'll see the filename is tr48401.bin
C) Unpack the file by executing the instructions below. You will
be asked for the password from the license agreement: pass = **RS/6000**
Enter the commands :
cd /tmp/raidtemp
chmod +x tr48401.bin
./tr48401.bin
(don't overlook the periods (.) In the above command) The
directory
pci4raid with these files will be added to /tmp/raidtemp: 2e1014C.4.84.01 &
rdme_4_84_01.HTM. Ignore rdme_4_84_01.HTM, use this readme.
Enter the following command to copy the microcode file to
"etc/microcode"
directory:
cp /tmp/raidtemp/pci4raid/2e1014C.4.84.01 /etc/microcode
NOTE: CORE can be only accessed by an IBM CE.
The CORE package is found under IBM RS/6000-Microcode-Adapter. The filename is 4_84_01.exe. It is a self expanding executable which will create a diskette containing the download code in backup format.
The diskettes that are produced with this procedure are in a format that the SSR can use directly with a computer that is using AIX as it's operating system. These diskettes once produced on the most platform cannot be read using normal platform tools or command line operations.
1. Place a 1.44 Mbyte diskette into your 'A' Diskette drive.
2. Press 'Launch' on the line that represents the Firmware that
you want to generate.
3. Label Diskette "IBM PCI 4-Channel Ultra3 SCSI RAID Adapter
Firmware-Version
4.84.01"
Transfer update files from this AIX backup diskette onto the workstation that you are going to use this firmware.
4. Insert the diskette in the floppy diskette reader (rfd0).
5. Login as su or "root" on the workstation.
6. Enter the AIX command:
restore
This command will extract the binary image of the microcode to the system /etc/microcode directory.
Alternatively, the AIX binary file or RPM file can be downloaded to the target server and extracted via the process in the previous and following sections.
5.2 Downloading the RPM format from the Target Server
Use this method to download to an AIX system:
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/RPM
b) Transfer the
RPM format file to the /etc/microcode directory (using "Save as ...").
You'll see the filename is adapter.scraid.4.84.01.rpm
c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos
adapter.scraid.4.84.01.rpm
The microcode files will be added to /etc/microcode/
5.3 Discovery Tool Microcode CD-ROM creation and download instructions
To obtain information how to burn a
CD-ROM and run the Discovery Tool for an AIX System please go to: CDROMhelp.html
1) After running the Discovery Tool successfully the "/tmp/microcode/RPM"
directory was created and your rpm files are copied from the CD-ROM.
2) Change to that directory, "cd /tmp/microcode/RPM".
3) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos
adapter.scraid.4.84.01.rpm
4) Microcode files will be copied to "/etc/microcode". The file
size and checksum of the microcode image will be verified in Section
6.0
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.
This section describes the method for transferring the new firmware into the target adapter. Each flash update should complete within one minute.
WARNING: Do not power off the target server at any time
before
the flash process completes. If power is removed or the system is reset
while flash_update is being run, irrecoverable failures may occur. This
could require return of the adapter for exchange.
Please verify the filesize and checksum of the raw microcode file in
the /etc/microcode/ directory.
Filesize: 536852
Checksum: 54319
FLASH the adapter EEPROM using
one
of the 2 following commands:
A) If the loadable microcode level listed
previously is below 4.84.01 then type
diag -c -d scraidX -T"download"
Where X is the numerical character denoting the logical ID of the SCSI RAID adapter you identified previously.
B) If the loadable microcode level listed previously is above 4.84.01 then type
diag -c -d scraidX -T"download -P"
This will cause 4.84.01 load even if a
higher
level from some other application is on the card.
You should
receive
a confirmation that microcode has been updated.
NOTE: If downleveling to 4.84.01 you will receive a message
stating,
"The configuration data could not be restored to the NVRAM of the
adapter.
Run the Disk Array Manager to resolve the adapter configuration error."
This message is displayed falsely. Verify the update (below) and
then type "smit pdam -> List PCI SCSI Disk Arrays" to verify the configuration
is present.
Verifying the Update
To verify that the correct level of
microcode,
4.84.01, is on the adapter type:
lscfg -vl scraidX
Where X is the numeric character denoting the logical ID of the SCSI RAID adapter you identified previously. The Loadable Microcode Level should be 4.84.01.
7.0 Restoring the Array Configuration on the New Adapter
After downloading the adapter follow the procedure in the chapter:
"Replacing the PCI 4-Channel Ultra3 SCSI RAID Adapter" in the adapter REFERENCE GUIDE, SA23-1239-00 which is summarized below:
Attention:
If the adapter being replaced experienced
an abrupt failure, there may be valid data in the adapter's non
volatile
write cache.
If an existing disk array configuration
will be imported from the attached drives, then the write cache card
from
the adapter being replaced should be used with the new adapter. This
will
ensure any data which may exist in the non-volatile write cache module
is correctly written to the attached disk drives.
A configuration conflict may result
when
a PCI 4-Channel Ultra3 SCSI RAID Adapter within a
configured
system is replaced (possibly due to a defective adapter). The
configuration
stored on the adapter may be out of sync with the configuration stored
on the drives. The configuration can be restored by synchronizing
the adapter configuration with the drive configuration. This can
be accomplished
using the ACCEPT CONFIGURATION ON DRIVES option under PDAM
RECOVERY
OPTIONS. PDAM is the PCI SCSI Disk Array Manager under SMIT.
Use the following to do this:
1. Start PDAM by entering the following command
smit pdam
2. Select the RECOVERY OPTIONS option.
3. Select RESOLVE PCI SCSI RAID ADAPTER CONFIGURATION option.
4. Select ACCEPT CONFIGURATION ON DRIVES option.
5. Select the adapter that was replaced.
NOTE: following an Accept Configuration on Drives option, the PCI 4-Channel Ultra3 SCSI RAID Adapter will automatically perform a Consistency Check with Auto-Repair on all redundant level RAID arrays. Progress of the Consistency Check can be monitored using the list PCI SCSI Disk Arays option of PDAM.
SA23-1239-00 PCI 4-Channel Ultra3 SCSI RAID Adapter - REFERENCE GUIDE
SA23-2597-00 PCI 4-Channel Ultra3 SCSI RAID Adapter - INSTALLATION & USER'S GUIDE