Patch-ID# 122165-01 NOTE: *********************************************************************** READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE. *********************************************************************** Keywords: sun fire t2000 1064_fcode 370-7696-04 lsi3041xl Synopsis: Hardware/1064_FCode Sun Fire T2000 1064 FCode update Date: Feb/06/2006 Install Requirements: Additional instructions may be listed below Solaris Release: 10 SunOS Release: 5.10 Unbundled Product: Hardware/Fcode LSI1064 PCI-X Unbundled Release: N/A Xref: Topic: Relevant Architectures: sparc, sun fire t2000 NOTE: Replacing plug-in card when RAID volumes exist will cause the volumes to move to an inactive state. A new command activate_volume is needed to move the volume back to a usable state. Fixed in 1.00.39: add "Inactive" to show-volumes display if appropriate add "activate-volume" word BugId's fixed with this patch: 6378605 Changes incorporated in this version: 6378605 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: 370-7696-04_FCode_1_00_37.ROM-old, 370-7696-04_FCode_1_00_39.ROM-latest, copyright README.122165-01 Problem Description: 6378605 activate_volume FCode command is needed for PCI-X 1064 plugin card Patch Installation Instructions: ============================== ABOUT THIS PATCH ------------------------- This patch updates the PCI-X 1064 FCode: From version 1.00.37 To version 1.00.39 It is important to ensure that you have the required PCI-X Fcode version before you configure RAID on your server. TO CHECK THE VERSION OF THE FCODE -------------------------------------------------- There are two ways to check the PCI-X FCODE version: o From the Solaris Operating System (OS) o From the OpenBoot PROM (OBP) From the Solaris OS: 1. As root, run the prtconf command. Example: # prtconf -vp | egrep '(model|version)' | \ egrep -vi '(obp|firmwareversion| mpt-version)' model: 'LSI,1064' version: '1.00.37' # In this example, the PCI-X FCODE is version 1.00.37. From the OBP: 1. Identify the node for the PCI-X 1064 card: Example: {0} ok show-disks a) /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk b) /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom c) /pci@7c0/pci@0/pci@1/pci@0/ide@8/disk q) NO SELECTION Enter Selection, q to quit: q {0} ok In this example on the Sun-Fire-T2000, "a" represents the plugin card. The plugin card has LSILogic in the name because it is treated as a third party add in card. Once you identify the node in this list, type q to return to the ok prompt. 2. Select the node. Example: {0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2 {0} ok In this example, only the full path to the node is specified (the path does not include the "disk"). 3. Display the node properties. Example: {0} ok .properties firmware-version 1.06.00.00 mpt-version 1.05 assigned-addresses 81061010 00000000 00001000 00000000 00000100 82061014 00000000 03000000 00000000 00010000 8206101c 00000000 03010000 00000000 00010000 82061030 00000000 03200000 00000000 00200000 compatible pci13e9,50 pci1000,50 AAPL,MPT model LSI,1064 reg 00061000 00000000 00000000 00000000 00000000 01061010 00000000 00000000 00000000 00000100 03061014 00000000 00000000 00000000 00010000 0306101c 00000000 00000000 00000000 00010000 02061030 00000000 00000000 00000000 00200000 ---> version 1.00.37 wide 00000010 device_type scsi-2 name LSILogic,sas fcode-rom-offset 00009a00 66mhz-capable devsel-speed 00000001 latency-timer 00000040 cache-line-size 00000010 max-latency 0000000a min-grant 00000040 interrupts 00000001 class-code 00010000 subsystem-id 000030f0 subsystem-vendor-id 00001000 revision-id 00000002 device-id 00000050 vendor-id 00001000 In this example, the PCI-X FCODE is version 1.00.37, and needs to be updated. 4. UN-select the node before booting the server. Example: {0}ok unselect-dev {0}ok TO UPDATE THE FCODE ------------------------------ 1. Boot the Solaris OS. 2. Login as root. 3. Copy the new FCODE image onto the system. The new FCode image is included in this patch. Copy the image into a dir on the system which you are going to update or to a network accessible dir. Use this full path along with the image name in step 5) below. 4. Identify the controller. In the following example, the controller is identified with the "LSI" string: # ls -al /dev/cfg total 22 drwxr-xr-x 4 root root 512 Jan 19 17:28 . drwxr-xr-x 16 root sys 4608 Jan 20 10:47 .. lrwxrwxrwx 1 root root 50 Jan 19 17:28 c0 -> ../../ devices/pci@7c0/pci@0/pci@1/pci@0/ide@8:scsi ---> lrwxrwxrwx 1 root root 61 Jan 19 17:28 c1 -> ../../ devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi lrwxrwxrwx 1 root root 45 Jan 19 17:28 c2 -> ../../ devices/pci@780/pci@0/pci@9/scsi@0:scsi 5. Update the FCODE using the raidctl command. Syntax: # raidctl -F [full_path_of_image] [controller] Example: # raidctl -F 370-7696-04_FCode_1_00_39.ROM-latest 1 Image file contains: 1.00.39 Update flash image on controller 1 (yes/no)? y Flash updated successfully. # 6. Reboot the server to load the new FCode. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Special Install Instructions: ----------------------------- ************************************************************************** **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** * PLEASE READ THE INSTRUCTIONS CAREFULLY AND ENTIRELY. PLEASE FOLLOW THE INSTRUCTIONS EXACTLY AS THEY ARE STATED. * FAILURE TO FOLLOW INSTRUCTIONS COULD EITHER RESULT IN A DEFECTIVE BOARD OR UNSUCCESSFUL 1064 FCode UPDATE. * THIS IS NOT A STANDARD PATCH IN THAT IT DOES NOT USE THE INSTALLPATCH AND BACKOUTPATCH SCRIPTS. * PLEASE REVIEW NOT ONLY THIS README BUT ALSO ADDITIONAL DOCUMENTATION GIVEN. **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** ************************************************************************** ************************************************************************** README -- Last modified date: Monday, February 6, 2006