Patch-ID# 105310-14 Keywords: I/O disks offlines remove_device luxadm multiple paths panic A5x00 Synopsis: SunOS 5.5.1: Patch for socal, sf driver, and luxadm Date: Oct/17/2000 Solaris Release: 2.5.1 SunOS Release: 5.5.1 Unbundled Product: Unbundled Release: Xref: Topic: socal and sf driver patches, luxadm utility patches Relevant Architectures: sparc BugId's fixed with this patch: 4025409 4030734 4036472 4036749 4047301 4050519 4051284 4054687 4054760 4055040 4055228 4056709 4057005 4058810 4060193 4060307 4060560 4062000 4063084 4063493 4063496 4063497 4063499 4063742 4064114 4064166 4064279 4064482 4064549 4065043 4065321 4065385 4065417 4065420 4065940 4066322 4066415 4066713 4067130 4067384 4067387 4068175 4068954 4069476 4069883 4070007 4070019 4070592 4071327 4071488 4071594 4073562 4073760 4073974 4075971 4076393 4076803 4078020 4078980 4080541 4080808 4080854 4081122 4081476 4083412 4083546 4083799 4085407 4085409 4085991 4086742 4087136 4087441 4088087 4088433 4090727 4095654 4097503 4099594 4100443 4100605 4101561 4103081 4103990 4104809 4104842 4106624 4106779 4108240 4109787 4110058 4110306 4115628 4116879 4119615 4121257 4121285 4121455 4121615 4122222 4125140 4126345 4126347 4127594 4127968 4135264 4138400 4138453 4139161 4139458 4144915 4145080 4147776 4149538 4153316 4156789 4157938 4163232 4163363 4164752 4166008 4166309 4167039 4168974 4170833 4171180 4173215 4173432 4175643 4178514 4178550 4179070 4179119 4179506 4180833 4181098 4183049 4188044 4190846 4199373 4202214 4208177 4208731 4209393 4234606 4249003 4257384 4259911 4301468 4303182 4307129 4346651 Changes incorporated in this version: 4147776 4301468 4303182 4307129 4259911 4346651 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: NOTE: The following patch IDs and version are recommended for running concurrent with this patch: 103346 104708 104850 104915 105298 105324 106129 Obsoleted by: Files included with this patch: /kernel/drv/socal /platform/sun4d/kernel/drv/sf /platform/sun4d/kernel/drv/sf.conf /platform/sun4u/kernel/drv/sf /platform/sun4u/kernel/drv/sf.conf /platform/sun4u1/kernel/drv/sf /platform/sun4u1/kernel/drv/sf.conf /usr/lib/firmware/fc_s/fcal_s_fcode /usr/lib/locale/C/LC_MESSAGES/ibfirmware /usr/sbin/luxadm Problem Description: 4147776 high io load and lbf utility causes socal_intr to loop hanging machine 4301468 socal/photon sequential throughput regression 4303182 does not connect A5200 with on-board SOC+ after Power ON/OFF 4307129 Incorrect Payload length on FCP status 4259911 SOC+ HA may generate a bad map sometimes 4346651 sf driver causes kmem_cache corruption of 16-byte buffers (from 105310-13) 4257384 luxadm probe: display rewinds tape media, silent loss of backed up data possible. (from 105310-12) 4249003 luxadm: interface change required in libg_fc and luxadm to offline/online ports. (from 105310-11) 4180833 LW GBIC Boot problem 4202214 LW GBIC OFFLINE messages and Target 0x0 Reset Failed. 4209393 LW GBIC download problem 4234606 Bad token panic occurred on Solaris 7 4208177 "Offline Timeout" -> requeue cmd fail with release 6, 2.5.1 OS (from 105310-10) 4199373 hardware failures do not allow loop to hard hang and use dmp (from 105310-09) 4208731 A5x00 22 disks + metaset -t + luxadm display = Panic ! 4121285 luxadm queries return very slowly (from 105310-08) 4106779 E3500 should have utility to get status on internal FCAL drives 4138453 luxadm: Printing of enclosure abnormal condition will not work 4167039 luxadm power_off enclosure does not work with no logical path device 4085991 Incorrect error msg when doing inquiry to a powered off drive 4168974 power_off cmd will take place on busy devices under volume manager. 4095654 luxadm display wrong enclosure when WWN=0 4171180 luxadm reports status of backplane element incorrectly when bypassed. 4175643 Implement bypass, enable & sysdump subcommands in luxadm 4179070 Device Type:Disk device displayed for device in enclosure. 4178514 luxadm -e bypass doesn''t give a usage error message 4179506 luxadm -e bypass backplane not showing correct status 4181098 Segmentation Fault (core dumped) when try to remove drive with WWN0s 4121257 luxadm: power_off subcommand with -F option is giving Usage errors. 4116879 luxadm doesn''t check return from devctl_acquire correctly 4135264 luxadm disp on /dev/es/ses# sees disks it shouldn''t!!! 4139161 luxadm remove -F does not work on reserved and unreserved paths 4115628 luxadm fcal does not see the FC100/S cards. 4138400 luxadm: drive with reservation is shown with "SCSI Error" 4190846 IB goes into failed state while running load-stress tests on 22-drive 4173432 sf: sfioctl does not free devctl_iocdata on success 4178550 "fc packet status = 34" messages at every lip 4157938 panic on 251 OS with intermixing 14/22 drive photons, no-27, dual host 4170833 Since upgrading I/B firm to 1.07, installing patch 105375-09 and disk firm 4163232 lip on one loop causes SCSI transport failed/rejected on other loop 4173215 misreported Lost Frame messages 4188044 io hang with lips on the heavy io loop 4166309 SF - removing one drive from an E3500 hangs system 4183049 Unused FCAL port is reported as OFFLINE timeout 4179119 STORtools: System panic while running Installation Verification 4156789 sf mutex panic when running IO tests, DR 4139458 Photon/DR : BAD TRAP when connecting board, during resume 4127594 sf_reset calls kmem_alloc possibly from interrupt context 4153316 Panic while installing on a 22 drive Photon disk from a sun4d (1000e) 4149538 sf_scsi_impl_pktfree: freeing free packet on 7,2.6,2.5.1 4164752 Starfire Panic, BAD TRAP occurred in module "socal" due to an illegal us 4163363 00 nodes and loops went OFFLINE when lip on one of busy i/o loops [S2.5.1] 4166008 panic[cpu1]/thread=0x30033ec0: SBus0 : Ultra2, 2.5.1 (from 105310-07) 4083412 socal, sf: needs to support DETACH/SUSPEND/RESUME 4108240 ifp not getting response from PHOTON (from ABTS after LIP) 4110058 data corruption with data stored on photons 4121455 i/o hung on 2 photon disks 4121615 Panic while dual host testing with ultraII 4119615 sf: assertion failed: prev_state != SF_STATE_IDLE 4125140 ssd: DDI_SUSPEND code to handle outstanding IO will not work for sf 4126347 sf: can cause retry and ultimate failure of recovered commands 4144915 I/O ''s can hang for a Dual Ported FC drive in error recovery cases 4122222 dd command was aborted with another system booted. 4126345 sf: issues unnecessary logouts when host adapter al_pa changes 4127968 SF: sf state marked incorrectly, sf_reset&sf_abort pass incorrect timeouts. 4145080 IB f/w does not work with 11 slot backplanes. 4106624 luxadm prints "Error: SCSI Error - Sense Byte: busy" when devices report (from 105310-06) 4080541 luxadm: l_forcelip_all does not understand multiple 4109787 luxadm: luxadm does not remove links when removing 4103990 luxadm: remove_device should provide an option to open a device in non EXCL mode. (from 105310-05) 4066415 remove_device offlines the A5000 disks while doing I/O to the disks. 4064279 disks: luxadm display subcmd. doesn''t print the multiple paths to ... 4057005 display -r output format should be aligned properly 4063499 luxadm display commands does not show box ID 4063742 remove_device displays incorrect warning message(could not blink ...) 4051284 luxadm: User can''t use WWN as path to device if multiple boxes have... 4025409 luxadm, ssaadm: Problem parsing path when in /devices/... directory 4030734 luxadm is not evaluating the command line argument properly for ... 4036472 luxadm restricts possible box names. 4064166 luxadm, ssaadm: fcal_s_download/fc_s_download dumps core on sun4d 4065385 luxadm fcal_s_download breaks with SSA HA in system. 4067130 luxadm fc_s_download -f fcal_s_fcode can blitz SSA HA''s 4068954 luxadm: fc_s_download subcommand fails when -F option is used 4063493 ibfirmware: no way to determine rev level for ibfirmware image 4065043 multiple paths to an enclosure prints different temperature info 4060193 FPM doesn''t print the Loop Type properly in split loop configuration 4036749 Data Access Error during boot due to device not coming online 4050519 FPM:setup: naming the A5000 does not go into a confirm screen... 4054687 FPM : warning sign(!) is not displayed when Interconnect assembly... 4055040 no-26, FPM: do not display Temperature status on the Back plane screen 4058810 firmware: Reset to the A5000 causes the firmware to halt. 4054760 FPM: can not clear using back-space key on Name screen 4056709 fcode: Can''t boot from a A5000 disk in a dual host scenario 4055228 loop hangs while doing heavy IOs to all four A5000s in a single loop. 4063084 socal: system will hang if polled commands timeout 4063496 socal: not using WWN from fcode dev tree property 4063497 A5000 error recovery takes too long due to OFFLINE/ONLINE sequence 4064549 kernel panics while booting from a A5000 disk 4060307 In split loop config. ses driver is not creating the /dev/es/ ... 4060560 sf driver hba event notification handling incorrect - needs to use scsa 4069476 panic: freeing a free packet on E6000 and 6 rack configuration 4062000 sf: driver send ABTS too soon for target reset; seen in luxadm... 4070019 System panics during DR_attach of sysbd with A5000s attached 4071594 A5000: error recovery problems triggered by SCSI 4073760 panic in sf caused by Data Fault 4078980 Patch 2 binaries and veritas (I/O hang) 4083546 Symon 1.5 panics on E4K with onboard soc+ and A5000. 4075971 Bad Trap PANIC when utilizing A5000 under heavy I/O 4076393 sf: panic when swapping out A5000 on idle system 4083799 heavy I/O and running lbf test caused panic on 4065417 enatest FATAL: "Could not communicate with the 4065420 socaltest FATAL: "Failed ioctl FCIO_DIAG_XRAM" 4076803 A5000 drivers should report target numbers 4080854 socal: facility to verify token returned (debug mode) 4047301 luxadm: Remove need for led_on subcommand for A5000 by 4069883 luxadm: luxadm reports open failed when IB is on 4071327 luxadm: remove_device fails to offline all the disks 4066322 if remove_dev subcmd. fails then it should restore the 4068175 can''t power on the disks from one host if they are 4064482 ibfirmware: The Rqst Insert bit in the device element 4067384 assertion failure due to soc+ microcode returning 4080808 firmware: PLOGI payload isn''t being sent fully. 4081122 sf: els packets can be freed twice 4066713 Drive hang doing dual port write [Seagate (0410.lod)] 4071488 remove_device: cannot remove the enclosure in dual-host configuration 4073562 ibfirmware: Reset to IB fails. [IB 1.03] 4100443 2nd instance of RUN dd test gets timeouts on 4064114 In multipath configuration, seagate disk reservation is not consistent. 4065940 luxadm -e dump_map does not accept the socal node as a parameter. 4070592 luxadm should report an error when host tries to release rsrvd. disks. 4065321 power_off subcommand offlines reserved disk or busy disks 4110306 luxadm: Typo and error displaying reserved status found in code 4097503 initialization of loop fails to create links with 2 racks using 2 HA''s 4103081 Only 2 initiators are allowed per photon array, one 4081476 PRLI ACC payload returned by Photon is incorrect 4086742 kernel panic due to bad token from soc+ microcode 4087441 drives could hang under DMP configuration 4090727 Socal port stuck when download IB firmware on system 4070007 one or more photon racks fails to come online in 4073974 Photon Dual Loop Config Limited to ~70 Mbyte 4104809 BAD TRAP occurred in module "ses" due to an illegal 4087136 Host drivers can''t complete login to any devices on 4101561 luxadm insert_device fails to insert a new disk during 4078020 sf: WWN for the Host Adapter in the loop map is zero. 4100605 sf driver could return with out releasing target 4104842 shouldn''t display to console ONLINE/OFFLINE mesg when 4067387 fcode doesn''t recover from the lip while booting from 4088433 Fibre Channel online/offline during booting 4088087 parallel downloads not supported on photons in a 4085407 FPM: Wrong ICON used in one of the FPM backplane 4085409 FPM: It takes 2 times to online both backplanes in FPM 4099594 Replacing interface board causes restarting ******************************************************************* ******************************************************************* IMPORTANT NOTICE: !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! Failure to read and follow the "Special Install Instructions" BEFORE attempting to install this patch could result in disabled A5x00 Interface Boards. In some cases, boards disabled by not following the "Special Install Instructions" may have to be replaced. Make sure you read the "Special Install Instructions" section in this README file BEFORE installing this patch. If a firmware upgrade failure has already occurred, see the section at the end of the Special Install Instructions titled "What to do in case of IB firmware upgrade failure". !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! The A5x00 IB firmware may have to be downloaded to the IBs after installing this patch. The FC100/S Host Adapter fcode may have to be downloaded into the FC100/S Host Adapter after installing this patch. ******************************************************************* ******************************************************************* Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic ''installpatch'' and ''backoutpatch'' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- Note - Upgrading IBs with firmware revision level 1.01 requires extra steps to complete the upgrade safely. There are two ways that the upgrade may be performed: A. Interface Boards (IB) with firmware revision 1.01 must be upgraded to revision 1.03 BEFORE being upgraded to revision 1.08. IB firmware revision level 1.03 is included in older patch 105310-04, which may be available from your service representative. B. IBs on A5x00s with firmware revision 1.01 must be upgraded one at a time, which involves temporarily removing one IB while the other is upgraded. Later on in the patch install instructions you will be asked to choose one of these methods. Note that method A is preferred and requires that older patch 105310-04 be available if it is not already installed on the system. The following patches need to be installed along with this patch: 103346-xx - Check for latest release... Only required for Sun Enterprise I/O boards with onboard FCAL. 104708-16 104850-02 104915-10 - Only required on sun4u1 platforms. 105029-10 - Only required on sun4u1 platforms configured with AP 2.0. 105310-xx - This patch... 105324-03 106129-07 108102-02 108104-01 See FINI0382-x Before installing this patch on the system, you must check the Interface Board (IB) firmware level for all A5X00s on the system: 1. Enter the following command to see what the firmware revision is for each A5X00 on your system: # /usr/sbin/luxadm display where enclosure is the name of the A5X00. For more information, see the luxadm.1m man page. Look at the output for a line similar to the following to find the firmware level: Revision:1.09 Box ID:0 Node WWN:5080020000000398 Enclosure Name:macs0 The firmware level is referred to as the Revision number. For the example above, the firmware level is 1.09. 2. Based on the firmware levels for all A5X00s on the system, decide what to do next: - If all A5X00s on the system have firmware revision 1.03 or higher, go to step 13. 3. Due to IB firmware revision level incompatibilities between revisions 1.01 and 1.09, upgrading between these revisions requires additional steps. There are two methods to accomplish this upgrade: Method A -------- If you have not already done so, you can install patch older 105310-04, which contains IB firmware revision 1.03, upgrade all A5X00s to IB firmware revision level 1.03, and then continue with the installation of this patch and subsequent upgrade to IB firmware revision 1.09. -or- Method B -------- You can temporarily remove IB A on all A5X00s during the firmware upgrade. Note - If you have already installed this latest patch, on the system, you MUST follow method B above, or you may remove this latest patch and select method A. Older patch 105310-04 may be available from your local Service representative. 4. Select method A or B above. Method A is the preferred approach. Method B should only be used if it is not possible to get older patch 105310-04. If you select method A, make sure you have older patch 105310-04 on hand before continuing and go to step 5. If you select method B, go to step 6. 5. Install older patch 105310-04 on the system. Follow the "Special Install Instructions" in the patch README file to upgrade all A5X00s on the system to IB firmware revision 1.03. Ignore the instructions to upgrade fcode. Go to step 13. 6. This step applies only to A5X00s that have IB firmware revision 1.01 or lower. It is not necessary to perform this step on A5X00s that have IB firmware revision 1.03 or higher. Temporarily remove IB A on all A5X00s with IB firmware revision 1.01 or lower. If there is only one cable connected to the A5X00, through IB A, connect the cable to IB B. 7. Install this latest patch on the system. 8. Download the firmware to all A5X00(s) on the system. Note - If the boot device is a part of a A5X00, the host MUST be rebooted from another boot device other than a A5X00 as firmware cannot be downloaded while booted from a A5X00. Note that you will need access to the luxadm utility and the A5X00 firmware file to do the download. a) Stop all I/O activity on the A5X00. b) Unmount any filesystems residing on the A5X00 disks. c) Stop all Sun Enterprise Volume Manager (SEVM) volumes (if any) running on the A5X00. d) Put the system in single user mode using the init command: # /etc/init s NOTE - The following step must be completed for each A5X00 to download the firmware safely: e) Use the luxadm download command to download the new firmware to each A5X00 on the system. Download the firmware to only one A5X00 at a time: # /usr/sbin/luxadm download -s -f where enclosure is the name of the A5X00(s) and firmware_file is the firmware image for the A5X00, which is usually located in /usr/lib/locale/C/LC_MESSAGES/ibfirmware. For more information, see the luxadm.1m man page. CAUTION: This operation may take a few minutes to complete. Do NOT interrupt the operation before it is finished or the system may not be able to communicate with the A5X00. Note that the luxadm command may complete BEFORE the firmware update completes on the A5X00. Verify that the A5X00 has completed by checking the firmware level for all Interface Boards on your A5X00(s) through the Front Panel Module (FPM). 9. After you verify that all A5X00s have IB firmware revision 1.09, power off all A5X00s on which you removed IB A, from step 6 above. 10. Re-install IB A on these A5X00(s) and temporarily remove IB B on these A5X00s. Re-cable the A5X00 if necessary. 11. Turn on power to these A5X00s and wait until the FPM says the A5X00 is OK. 12. Re-install IB B on these A5X00s. Wait until the A5X00 re-initializes. Verify the IB firmware level for all Interface Boards on your A5X00(s) through the FPM. Go to step 18. 13. Install this latest patch on the system. After installing the patch, check to see if you have to upgrade the firmware for the A5X00 and/or the fcode for the FC100/S Host Adapter. 14. Enter the following command to see what the firmware level is for each A5X00 on your system: # /usr/sbin/luxadm display where enclosure is the name of the A5X00. For more information, see the luxadm.1m man page. Look at the output for a line similar to the following to find the firmware level: Revision:1.09 Box ID:0 Node WWN:5080020000000398 Enclosure Name:macs0 The firmware level is referred to as the Revision number. For the example above, the firmware level is 1.09. 15. Determine if you need to upgrade the firmware. If the firmware level reported by the luxadm command (Step 1) is 1.09 or higher for ALL A5X00s on the system then you do not have to upgrade your firmware as it is already at the proper level. Go to step 18. 16. Download the firmware to your A5X00, if necessary. If the boot device is a part of a A5X00, the host MUST be rebooted from another boot device other than a A5X00 as firmware cannot be downloaded while booted from a A5X00. Note that you will need access to the luxadm utility and the A5X00 firmware file to do the download. a) Stop all I/O activity on the A5X00. b) Unmount any filesystems residing on the A5X00 disks. c) Stop all Sun Enterprise Volume Manager (SEVM) volumes (if any) running on the A5X00. d) Put the system in single user mode using the init command: # /etc/init s NOTE - The following step must be completed for each A5X00 to download the firmware safely: e) Use the luxadm download command to download the new firmware to each A5X00 on the system. Download the firmware to only one A5X00 at a time: # /usr/sbin/luxadm download -s -f where enclosure is the name of the A5X00(s) and firmware_file is the firmware image for the A5X00, which is usually located in /usr/lib/locale/C/LC_MESSAGES/ibfirmware. For more information, see the luxadm.1m man page. CAUTION: This operation may take a few minutes to complete. Do NOT interrupt the operation before it is finished or the system may not be able to communicate with the A5X00. Note that the luxadm command may complete BEFORE the firmware update completes on the A5X00. Verify that the A5X00 has completed by checking the firmware level for all Interface Boards on your A5X00(s) through the FPM. 17. The firmware download is now complete. 18. Use the luxadm fcal_s_download command to check the fcode level of all of the FC100/S Host Adapters on the system: # /usr/sbin/luxadm fcal_s_download Found Path to 2 FC100/S Cards Device: /devices/sbus@f,0/SUNW,socal@0,0 Detected FC100/S Version: @(#) FCode 1.11 97/12/07 Device: /devices/sbus@2,0/SUNW,socal@2,0 Detected FC100/S Version: @(#) FCode 1.11 97/12/07 Complete The fcode level is reported for each FC100/S. For the example above, the firmware level is 1.11 for both FC100/S Host Adapters found. NOTE: The fcal_s_download command DOES NOT check the SOC+ on Sun Enterprise I/O Boards. Patch 103346-11 (or newer) should be applied on systems with onboard SOC+ ports. 19. Determine if you need to upgrade the fcode. If the fcode level for ALL of the FC100/S Host Adapters is 1.11 or higher then you do not have to upgrade your fcode as it is already at the proper level. Go to step 22. 20. If you are in the single user mode (from step 8 or 16 above), go to step 21, otherwise: a) Stop all I/O activity on the A5X00. b) Unmount any filesystems residing on the A5X00 disks. c) Stop all Sun Enterprise Volume Manager (SEVM) volumes (if any) running on the A5X00. d) Put the system in single user mode using the init command: # /etc/init s 21. Use the luxadm fcal_s_download command to download the new fcode to all FC100/S Host Adapters on the system: # /usr/sbin/luxadm fcal_s_download -f where fcode-file is the path to the FC100/S Host Adapter fcode image file. This is usually /usr/lib/firmware/fc_s/fcal_s_fcode. This command is interactive and expects user confirmation before downloading the fcode to each Host Adapter. For more information, see the luxadm.1m man page. 22. Reboot the system. 23. You have now completed the upgrade process. What to do in case of IB firmware upgrade failure ------------------------------------------------- An upgrade failure could happen under the following circumstances: - Attempting to upgrade from IB firmware revision 1.01 to 1.09 without following the steps outlined above. - Interrupting the luxadm download command before it has time to complete. - Interrupting the re-initialization of the A5X00 after the completion of the "luxadm download" command, say because of power failure to the A5X00. - On very rare occasions, upgrading from IB firmware revision 1.03 to revision 1.09. Such a failure may manifest itself in one of several ways: - The A5X00 is non-responsive to probing as with the "luxadm probe" command. - The disks in the A5X00 become unavailable to the system. - The A5X00 goes offline and does not come back online after more than 5 minutes during the upgrade process. - The FPM on the A5X00 exhibits a flashing warning sign - a triangle with an exclamation point inside - and the failure is traced down to one or both of the IBs. - The FPM is blank, scrambled or otherwise unreadable and is not responsive to queries. If such a failure is encountered, it may be possible to recover by following this procedure: R1. If it is possible to use the FPM, determine if either of the IBs has a valid copy of IB firmware. See the A5X00 service manual for instructions on how to determine IB firmware revision level from the FPM. If both IBs on the A5X00 have valid, matching revisions of firmware, then the problem may be in the cable, Host Adapter, or GBICs. R2. If only one of the IBs has a valid firmware revision, power off the A5X00 and remove the IB that is invalid. If neither of the IBs have a valid revision of firmware or the A5X00 is unresponsive, go to step R6. R3. Put the IB with a valid revision in slot B and power on the A5X00. Wait until the A5X00 initializes and verify that the IB in slot B has a valid firmware revision. Note - It may be possible that the revision will be different after this operation is complete. R4. Power off the A5X00 and remove the IB in slot B. Insert the other IB into slot A. Power on the A5X00. Wait until the A5X00 initializes and verify that the IB in slot A now has the same firmware revision as the other IB. If the A5X00 does not initialize, go to step R6. R5. Insert the other IB in slot B. - If both IBs now have IB firmware revision 1.09, then IB firmware upgrade for this A5X00 is complete. Continue with the upgrade process above. - If both IBs now have firmware revision 1.03 or 1.01, follow the instructions above to upgrade the IBs to revision 1.09. R6. If it is not possible to use the FPM, power-cycle the A5X00, and wait until it initializes. If initialization does not complete and the A5X00 does not complete POST, remove one of the IBs and power cycle again. If initialization still does not complete, swap the IBs and power cycle again. If initialization still does not complete it is necessary to replace the IB board(s). Contact your local service representative to replace the IB boards. README -- Last modified date: Friday, October 5, 2001