Readme.txt file for QLogic QLA22002FS fcode Contents -------- 1. OS Support 2. Supported features 3. Selecting a boot device 4. Setting and viewing Fibre Channel connection mode 5. Setting and viewing adapter loopId 6. Flashing adapter with fcode 7. Building a bootable disk 8. File contents 9. Contacting QLogic ====================================================================== 1. OS and Openboot Support -------------------------- This driver has been tested with Solaris 6,7 and 8. ====================================================================== 2. Supported Features --------------------- * 256 ID Support * 256 LUN Support * Fabric boot support * Local loop boot support ====================================================================== 3. Selecting a boot device -------------------------- A. To scan for attached Fibre Channel devices: ok probe-scsi-all or At the ok prompt locate the QLogic device in device tree and select it. Example: ok show-devs . . . /sbus@1f,0/QLGC,qla@1,30000 /sbus@1f,0/QLGC,qla@1,30400 . . ok " /sbus@1f,0/QLGC,qla@1,30000" select-dev ok show-children Select a boot device and write down the WWPN, LoopId and Lun of the boot device. B. Save the boot device information to adapter NVRAM. ** Note: If you are working with 32bit machines, i.e. SparcServer 1000, please refer to section B.1 If you have not already done so, you must select the device. example: ok " /sbus@1f,0/QLGC,qla@1,30000" select-dev Enter the WWPN, LoopId and Lun and type "set-boot-id". example: ok 2200002037009eeb 82 0 set-boot-id Calculating NVRAM checksum, please wait.... done Boot device login successful Boot WWN - 20000020 37009eeb WWPN - 22000020 37009eeb Id - 82 Lun - 0 ok If the following message is printed, the boot device can't be logged in: "Boot device login failed, check boot device settings Boot WWN - 20000020 37009eeb Id - 82 Lun - 0" Please recheck the boot device settings and reenter them using the "set-boot-id" command. B.1 Setting boot id for 32bit machine (i.e. SparServer 1000). If you have not already done so, you must select the device. example: ok " /io-unit@f/e0200000/sbi@0,0/QLGC,qla@2,30000" select-dev Enter the WWPN.hi, WWPN.lo, LoopId and Lun and type "set-boot-id". example: ok 22000020 37009eeb 82 0 set-boot-id This machine takes two 32-bit parameters to represent WWPN. Syntax: WWPN.hi WWPN.lo Id Lun set-boot-id Calculating NVRAM checksum, please wait.... done Boot device login successful Boot WWN - 20000020 37009eeb WWPN - 22000020 37009eeb Id - 82 Lun - 0 ok If the following message is printed, the boot device can't be logged in: "Boot device login failed, check boot device settings Boot WWN - 20000020 37009eeb Id - 82 Lun - 0" Please recheck the boot device settings and reenter them using the "set-boot-id" command. You may see the following message if you enter the wrong number of parameters: "Stack Underflow" Please re-issue "select-dev" and reenter the "set-boot-id" command with the correct parameters. C. To verify boot device you can type "show-boot-id" example: ok show-boot-id Boot WWN - 20000020 37009eeb WWPN - 22000020 37009eeb Id - 82 Lun - 0 ok D. To boot device, type the complete boot path including Id and Lun. The Id and Lun must match those entered in step B. example: ok boot /sbus@1f,0/QLGC,qla@1,30000/sd@82,0 NOTE: It is recommended that the "reset" command be entered before attempting to boot if the boot was interrupted or any of the QLogic fcode commands were executed. E. To clear the boot device information from the NVRAM, type "clear-boot-id". example: ok clear-boot-id 4. Setting and viewing Fibre Channel connection mode ---------------------------------------------------- A. To view the current host adapter Fibre Channel connection mode type "show-connection-mode" example: ok show-connection-mode Current HBA connection mode: 3 - Point-to-point preferred, otherwise loop Possible connection mode choices: 0 - Loop Only 1 - Point-to-point only 2 - Loop preferred, otherwise point-to-point 3 - Point-to-point preferred, otherwise loop B. To change the current host adapter Fibre Channel connection mode type "set-connection-mode" example: ok 0 set-connection-mode Calculating NVRAM checksum, please wait... Current HBA connection mode: 0 - Loop Only Possible connection mode choices: 0 - Loop Only 1 - Point-to-point only 2 - Loop preferred, otherwise point-to-point 3 - Point-to-point preferred, otherwise loop 5. Setting and viewing adapter loopId ------------------------------------- A. To view the current host adapter loopId type "show-adapter-loopid" example: ok show-adapter-loopid Adapter loopId - 7c B. To change the current host adapter loopid type "set-adapter-loopid" example: ok 0 set-adapter-loopid Adapter loopid - 0 6. Flashing adapter with fcode ------------------------------ First locate the device in the device tree example: ok show-devs . . . . . /sbus@1f,0/QLGC,qla@1,30000 . . . If you wish to update the fcode this can be done using the QLogic qla2x00fcode utility. A QLogic Solaris HBA driver revision xxxx or later must be installed before this flash utility can be run. To run the utility perform the following steps: 1. Copy the qla2x00fcode file and 22002sf.prom file to desired directory. 2. Enter the command line with the appropriate path as in the example below. qla2x00fcode -l /devices/sbus@1f,0/QLGC,qla@1,30000:devctl 2202sf.prom WARNING EXTREME CARE MUST TO BE TAKEN WHEN CHANGING FLASH CONTENTS, INCORRECT DATA MAY RENDER THE ADAPTER UNUSABLE TO THE POINT THAT THE OPERATING SYSTEM MAY NO LONGER FUNCTION. 7. Building a bootable disk --------------------------- This procedure assumes the system is already booted from an existing system disk, and that you have already performed a full system backup. The device name shown in this example is for a device on the first sbus slot, target Id 130, Lun 0, slice 0. The device path will be different on each system depending on which sbus slot, target Id, Lun etc. You must have already completed the steps listed above before attempting to create a bootable disk. This procedure involves using the Solaris command, ufsdump to create temporary saveset files for each partition on your current boot disk. In order for this method to be successful, you must have enough extra disk space to create the saveset files or your Solaris machine must have a high capacity tape drive attached. 1. Determine the amount of disk space used/available on your current boot disk. Use the '/usr/bin/df -k -l' command for a listing. Example: /usr/bin/df -k -l Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 2577118 1650245 875331 66% / /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab swap 1310480 0 1310480 0% /var/run swap 1311344 864 1310480 1% /tmp /dev/dsk/c0t0d0s7 5135326 114 5083859 1% /home This df example shows that the current boot disk is /dev/dsk/c0t0d0s(x). There are two partitions of interest, slice 0 or "/" and slice 7 or "/home". Slice 0 is using 1.6GB and has 875MB free. Slice 7 uses 114KB and has 5GB free. Therefore, we can use Slice 7 or "/home" to store our temporary saveset files. If we did not have at least 1.7GB free on this disk, we would have to create a partition on the new bootable disk large enough to hold the largest temporary saveset plus the largest used space on a partition. In this example, that would be a partition at least 3.2GB(1.6GB+1.6GB). 2. Use the 'format' command to create, label and format partitions on the new bootable disk. These partitions must be able to contain the contents of your temporary savesets. If you are not familiar with the 'format' command, please carefully read the Solaris documentation and manual pages for the command. Misuse of 'format' could destroy the data on your current disk drives. Example: format partition print Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 8738 4.00GB (8739/0/0) 8389440 1 swap wu 8739 - 9188 210.94MB (450/0/0) 432000 2 backup wu 0 - 9201 4.21GB (9202/0/0) 8833920 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 label quit quit 3. Use the 'newfs' command to create the file system. Example: newfs -v /dev/rdsk/c1t130d0s0 NOTE: The target device Id (t130) is in decimal! The hexadecimal value for the target Id is used in the boot command line shown in step 11. 4. Mount the boot partition to the /mnt mount point. Example: mount /dev/dsk/c1t130d0s0 /mnt 5. Cd to the root partition mount point. example: cd /mnt 6. Use the 'ufsdump' utility to copy the root partition to the new boot disk. Example: ufsdump 0f - / | ufsrestore rf - 7. rm restoresymtable 8. Install the boot block on the new boot disk. Example: installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t130d0s0 9. Edit the new vfstab file to properly mount the new partition(s) during boot. In this case each reference to c0t0d0s0 would be changed to c1t130d0s0. Example vi /mnt/etc/vfstab 10. Shutdown the system. Example: /sbin/init 0 11. Boot from the newly created boot disk. Example: boot /sbus@1f,0/QLGC,qla@1,30000/sd@82,0 NOTE: The target device Id (sd@82) is in hexadecimal! The decimal value is used in step 2. 12. View the current dump device setting. Example: # dumpadm Dump content: kernel pages Dump device: /dev/dsk/c0t0d0s1 (swap) Savecore directory: /var/crash/saturn Savecore enabled: yes 13. Change the dump device to the swap area of the new boot drive. Example: # dumpadm -d /dev/dsk/c1t0d0s1 NOTE: The following two steps set the newly created boot disk to be the default boot disk. These steps are performed at the system OBP (ok) prompt. 14. Create an alias entry for the new boot device (optional) Example: ok nvalias fibredisk /sbus@1f,0/QLGC,qla@1,30000/sd@82,0 15. Set default boot device to be the new boot device (optional) Example: ok setenv boot-device fibredisk 8. File contents ---------------- The following files are included with the fcode binary file: 1. 2202fs.prom - Fcode binary file 2. readme.txt - Fcode readme file 3. qla2x00fcode - Solaris flash utility 4. Readme - Readme for qla2x00fcode 9. Contacting QLogic -------------------- Please visit QLogic's website (http://www.qlogic.com). On this site you will find product information, our latest drivers and links for technical assistance if needed. ====================================================================== Copyright (c) 2000 - 2001 QLogic Corporation. All rights reserved.