============================================================================= Multiboot Update for Qlogic System-X 8Gb FibreChannel HBAs ============================================================================= Multiboot Version 2.32-4 NOTEs: A vendor-supplied readme file from Qlogic is attached to the end of this file. It is a general release document included for informational purposes only and may contain references to update procedures not directly supported by this package. It is recommended that adapters are updated one at a time, or adapters of the same type (SSDID) are updated together. Do not have different adapter models in the system during the update/flash process. It is recommended that QLogic's BIOS to be disabled before performing the update in DOS (Update.bat). (C) Copyright International Business Machines Corporation 1999, 2008. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Before using this information and the product it supports, please read the general information in "Notices and Trademarks" in this document. CONTENTS ________ 1.0 Overview 2.0 Installation and setup instructions 3.0 Configuration information 4.0 Unattended mode 5.0 Web information and support phone Number 6.0 Notices and Trademarks 7.0 Disclaimer 1.0 Overview _____________ 1.1 This update applies to Qlogic System-X FibreChannel HBAs. 1.2 Limitations - None 1.3 Problems fixed: - See change history for more details. 1.4 Level of Recommendations and Prerequisites for the update: - None 1.5 Dependencies - None 1.6 Update Contents o qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.bin - The executable update package o qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.chg - Change history o qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.txt - Readme 2.0 Installation and setup instructions ________________________________________ This package can be used with several of IBM's update management tools, including IBM UpdateXpress Manager, IBM UpdateXpress System Packs, and IBM Director. It can also be used as a standalone executable package. To use the package with one of IBM's update management tools, follwing the instructions that came with your specific management tool. 2.1 Standalone usage instructions --------------------------------- As a standalone package, this executable can be used in the following ways: - to update the Qlogic FW/BIOS on the local system. - to copy all files necessary for the update to the local hard drive or other media. Updating the local system: 1) Type "./qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.bin -s" at a command prompt. Extracting files 1) Type "./qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.bin -x ", where is the fully qualified path where you want to extract the files, at a command prompt. 2.2 Troubleshooting tips ------------------------ - The automated installation tools supress the responses generated by running the Update.sh script. If installation is not successful, try running the installation manually, per the instructions elsewhere in this readme. 3.0 Configuration information ______________________________ - None 4.0 Unattended Mode ____________________ To run this package in unattended mode, use the following command: qlgc_fw_fc_8g-mb2.32-4_linux-sysx_32-64.bin -s 5.0 Web Sites and Support Phone Number ______________________________________ o You can download new and updated files for IBM products from the IBM Support Web site: http://www.ibm.com/support/ o For the latest list of supported operating systems, see the IBM Server Proven Web site: http://www.ibm.com/servers/eserver/serverproven/compat/us/indexsp.html o With the original purchase of an IBM hardware product, you have access to extensive support coverage. During the IBM hardware product warranty period, you may call the IBM HelpCenter (1-800-IBM-SERV in the U.S.) for hardware product assistance covered under the terms of the IBM hardware warranty. 6.0 Trademarks and Notices __________________________ IBM is a registered trademark of International Business Machines Corporation in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. 7.0 Disclaimer ______________ THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. (Qlogic-supplied Readme begins here...) ******************************************************************************** Multi-boot Image for 8Gb FC adapters BIOS Readme File This software license applies only to QLogic customers. QLogic Corporation. All rights reserved. Table of Contents 1. Package Contents 2. 8Gb BIOS 2.1 BIOS Package Contents 2.2 Supported Features 2.3 Adapter Configuration (Fast!UTIL) 2.4 Updating the BIOS (Flasutil) 2.5 Additional Notes 3. Contacting Support ====================================================================== 1. Package Contents The multi-boot package for 8Gb adapters is a compressed file that contains the QLx256x BIOS, FCode, and firmware. This package also includes the Flasutil and the VPD applications. * The multi-boot BIOS contained in this package supports 8Gb adapters on Intel x86, Intel EM64T, and AMD64 platforms. * The EFI Fibre Channel driver contained in this package supports 8Gb adapters on Intel IA64 platforms. * The FCode contained in this package supports 8Gb adapters on Solaris SPARC platforms. * readme.txt - Readme file for the multi-boot package. This readme file contains details for the multi-boot image, including the BIOS, EFI code, and FCode contained in this package. * release.txt - Release notes for the multi-boot package. This file contains revision notes for the multi-boot image, including the BIOS, EFI code, and FCode contained in the package. ====================================================================== 2. 8Gb BIOS This section provides user notes regarding the BIOS contained in the 8Gb multi-boot package. 2.1 BIOS Package Contents ------------------------- The following list describes the BIOS files included for updating the adapter BIOS. * update.bat - DOS batch file that calls the executable files to update the adapter BIOS. * FlasUtil.exe - Utility to update multi-boot code and firmware. * VPD.exe - Utility to update the adapter's Vital Product Data. * q25xxyyy.bin - Combined binary file, which includes the binaries for the firmware, FCode, EFI, and BIOS. 2.2 Supported Features ---------------------- * Up to 2031 target IDs. * Up to 256 LUNs. * Point-to-point and loop configuration. * Boot capability in FC-AL and fabric topologies. * Compatible with DOS, Windows 2000, Windows Server 2003, Windows XP Professional, Windows Vista, Windows Server 2008, Novell NetWare, Solaris x86, and Linux on IA32, AMD64, and Intel 64-based systems. 2.3 Adapter Configuration (Fast!UTIL) ------------------------------------- NOTE: The Fast!UTIL BIOS utility does not run on SUN SPARC systems. This section provides detailed configuration information for advanced users who want to customize the configuration of the 8Gb adapter and the connected devices. You can configure the adapter using Fast!UTIL. To access Fast!UTIL, press + or + during the adapter BIOS initialization (it may take a few seconds for the Fast!UTIL menu to appear). If you have more than one adapter, Fast!UTIL asks you to select the adapter you want to configure. After changing the settings, Fast!UTIL reboots your system to load the new parameters. CAUTION! If the configuration settings are incorrect, your adapter may not function properly. The Fast!UTIL Options menu provides the following options: * Configuration Settings (section 2.3.1) * Scan Fibre Channel Devices (section 2.3.2) * Fibre Disk Utility (section 2.3.3) * Loopback Data Test (section 2.3.4) * Select Adapter (section 2.3.5) * Exit Fast!UTIL (section 2.3.6) 2.3.1. Configuration Settings ----------------------------- The following topics show and describe the configuration settings for the 8Gb adapter. * Adapter Settings (section 2.3.1.1) * Selectable Boot Settings (section 2.3.1.2) * Restore Default Settings (section 2.3.1.3) * Raw NVRAM Data (section 2.3.1.4) * Advanced Adapter Settings (section 2.3.1.5) 2.3.1.1. Adapter Settings ------------------------- * Host Adapter BIOS (Enabled/Disabled: Default - Disabled) Disabling this setting disables the ROM BIOS on the adapter, which frees space in upper memory. If you are booting from an FC disk drive attached to the adapter, you must enable this setting. For details, see section 2.3.1.2. * Frame Size (512/1024/2048: Default - 2048) This setting specifies the maximum frame length supported by the adapter. * Loop Reset Delay (0 - 60 seconds: Default - 5 seconds) After resetting the loop, the firmware refrains from initiating any loop activity for the number of seconds specified in this setting. * Adapter Hard Loop ID (Enabled/Disabled: Default - Disabled) This setting forces the adapter to attempt to use the ID specified in the Hard Loop ID setting. * Hard Loop ID (0 - 125: Default - 0) If the Adapter Hard Loop ID setting is enabled, the adapter attempts to use the ID specified in this setting. * Spin Up Delay (Enabled/Disabled: Default - Disabled) When this bit is set, the BIOS waits up to two minutes to find the first drive. * Connection Options (0/1/2: Default - 2) This setting defines the type of connection: 0 – Loop only 1 - point-to-point only 2 - loop preferred otherwise point-to-point * Fibre Channel Tape Support (Enabled/Disabled: Default - Enabled) This setting enables FCP-2 recovery. * Data Rate (0/1/2/3: Default - 2) This setting determines the data rate: 1 - Adapter runs at 2 Gb/s. 2 - Adapter auto-negotiates and determines the data rate. 3 - Adapter runs at 4 Gb/s. 4 - Adapter runs at 8 Gb/s. 2.3.1.2. Selectable Boot Settings --------------------------------- The Configuration Settings menus provide access to the Selectable Boot Settings option. If you enable the Host Adapter BIOS in the adapter Settings, this option allows you to select the boot device as follows: Selectable Boot Port Name Boot /LUN Device Boot ---------- -------------- ----------- Disabled X BIOS configures the first disk drive it finds as boot device. Enabled none specified BIOS configures the first disk drive it finds that is also a LUN 0 as boot device. Enabled specified BIOS scans through the specified WWPN/LUN list until it Boot drive. This finds a disk configured as the boot device. This option allows you to specify up to four WWPN/LUN as boot devices. To enable the Selectable Boot option and insert devices into the boot device locations, follow these steps: 1. From the Configuration Settings menu, select Host Adapter Settings. 2. Enable the adapter BIOS, then press ESC to return to the Configuration Settings menu. 3. From the Configuration Settings menu, select Selectable Boot Settings. 4. Press ENTER to enable or disable (toggle) the Selectable Boot option. Use the down arrow key to move to the Primary location of the Selectable Boot List menu. 5. Press ENTER to see a list of accessible devices (in the Select Fibre Channel Device menu). 6. Select a drive using the arrow keys to scroll down to the device you want to put into your Selectable Boot menu list, then press ENTER to select the requested device and load it into the Selectable Boot menu list. 7. Repeat this step to specify a secondary boot device on the QLE256x adapter or up to seven alternate boot devices. NOTES: System BIOS Compatibility In a computer system with a multi-boot system BIOS (CMOS), in order to boot from a QLogic host adapter, the adapter must be included in the list of bootable devices in the system's Boot menu. Solaris X86 Boot from a SAN To boot from an FC drive connected to a QLogic host adapter, reboot the system and enter fast!Util. Enter into the Selectable boot menu,enable selectable boot and insert the BOOT drive in the Primary location of the Selectable Boot menu prior to performing the OS (Solaris X86) installation. For these BOOT from SAN configurations, the Solaris x86 QLA driver supports booting from the Primary location only. The driver will not attempt to boot from the Alternate 1, Alternate 2, and Alternate 3 entries. 2.3.1.3 Restore Default Settings -------------------------------- The Restore Defaults option from the Configuration Settings menu restores the BIOS settings back to default. 2.3.1.4 Raw NVRAM Data ---------------------- This option displays the adapter’s NVRAM contents in hexadecimal format. This is a QLogic troubleshooting tool; You cannot modify the RAW NVRAM data. 2.3.1.5 Advanced Adapter Settings From the Configuration Settings menu in Fast!UTIL, select Advanced Adapter Settings. The following paragraphs describe the default settings for the 8Gb adapter. * Execution Throttle ( 1-65535: Default - 65535) This setting specifies the maximum number of commands executing on any one target port. After reaching a target port’s execution throttle, it stops issuing new commands until one of the current commands finishes executing. * LUNs per Target (0/8/16/32/64/128/256: Default - 128) This setting specifies the number of LUNs supported per target if the target does not support the "Report LUNs" command. Multiple LUN support typically applies to a redundant array of independent disks (RAID) boxes that use LUNs to map drives. * Enable LIP Reset (Yes/No: Default - No) This setting determines the type of loop initialization process (LIP) reset used when the operating system initiates a bus reset routine: Yes - The driver initiates a global LIP reset to reset the target devices. No - The driver initiates a global LIP reset with full login. * Enable LIP Full Login (Yes/No: Default - Yes) This setting instructs the ISP chip to re-login to all ports after any LIP. * Enable Target Reset (Yes/No: Default - Yes) This setting enables the drivers to issue a Target Reset command to all devices on the loop when a SCSI Bus Reset command is issued. * Login Retry Count (0 - 255: Default - 8) This setting specifies the number of times the software tries to log in to a device. * Port Down Retry Count (0 - 255 seconds: Default - 30 seconds) This setting specifies the number of seconds the software waits to retry a command to a port returning port down status. * Link Down Timeout (0 - 255 seconds: Default - 30 seconds) This setting specifies the number of seconds the software waits for a link down to come up. * Operation Mode (0/5/6: Default - 0) This setting specifies the reduced interrupt operation (RIO) modes, if supported by the software driver. The RIO modes allow posting multiple command completions in a single interrupt. This option supports the following modes: 0 - Interrupt for every I/O completion 5 - Interrupt when Interrupt Delay Timer expires 6 - Interrupt when Interrupt Delay Timer expires or no active I/Os * Interrupt Delay Timer (0 - 255 seconds: Default - 0) This setting contains the value (in 200-microsecond increments) that a timer uses to set the wait time between generating an interrupt. * Enable Interrupt ( Yes/No: Default - No) Enable or disable the interrupt: Yes - Enables the BIOS to use the IRQ assigned to the ISP25xx. No - The BIOS polls for ISP mailbox command completion status. * EV Controller Order (Enabled/Disabled: Default - Disabled) This setting enables BIOS compatibility with older HP (G3) systems such as the ML370G3, DL360G3, and DL380G3. When disabled system boots to QLogic Controller first. When enabled, system only boots when QLogic is set as the first controller in the system BIOS\Boot Controller Order. 2.3.2. Scan Fibre Devices ------------------------- This option scans the FC loop and lists all the connected devices by loop ID. It lists information about each device (for example, vendor name, product name, and revision). This information helps when configuring your adapter and attached devices. 2.3.3. Fibre Disk Utility ------------------------- This option scans the Fibre Channel loop and lists all the connected devices by loop ID. You can select a Fibre Channel hard disk and do one of the following tests: * Perform a low-level format * Verify the disk media * Verify the disk data (Some targets do not support this feature.) * Select a disk device CAUTION! Performing a low-level format destroys all data on the disk. 2.3.4. Loopback Data Test ------------------------- This option allows you to perform Loopback tests. You can select one of the following Loopback tests: * External Loopback Data Test * Internal 1 bit Interface Loopback Data Test * Internal 10 bit Interface Loopback Data Test NOTE: When running an external Loopback data test, make sure that the FC loop is up or a Loopback plug is attached to the adapter before starting the test. If your adapter is attached to a fabric switch port, you must set the adapter and Switch ports to run in Arbitrated Loop mode. 2.3.5. Select Adapter --------------------- If you have a multi-port or multiple 8Gb adapters in your system, use this option to select and then configure or view the settings of a specific adapter port or adapter. 2.3.6. Exit Fast!UTIL -------------------- This option allows you to exit the utility and reboot the system or to return to Fast!UTIL. After making changes to the QLogic adapter in Fast!UTIL, make sure you save the changes before you reboot the system. 2.4 Updating the BIOS (FlasUtil) The QLogic flash programming utility is a DOS utility. To run this utility, boot to a DOS hard drive or USB removable drive. NOTE: Do not run this utility from drive connected to the 8Gb adapters. Make sure Flasutil.exe and the q25xxyyy.bin source files are in the same directory. 2.4.1. Flashing the BIOS ----------------------- To flash the BIOS: 1. Insert the 8Gb adapter in the system. 2. Boot to DOS. 3. Run the update script at the command prompt: C:\>update.bat This script program updates the BIOS image on the adapter. 4. Reboot the system. NOTE: You can also use SANsurfer GUI/CLI to flash the Multi-boot image. 2.4.2. FlasUtil Command Line Options ------------------------------------ The executable file Flasutil.exe is used by the UPDATE.BAT file to update your adapter BIOS. The application FlasUtil.exe, may be used to read, write or verify the multi-boot image, or the NVRAM on the adapter. The following paragraphs describe the command line options available with this utility. Use of Flasutil will modify the way your adapter operates, and it must be used with extreme caution. Certain features (i.e. The NVRAM options) may require additional data files and passwords not provided in this file. Default Options --------------- Enter Flasutil will list QLogic adapters at different I/O addresses. Enter adapter I/O address for menu options. Flasutil /? for command line details. Boot Code only -------------- /FB xxxx = Writes 1MB complete boot image to the FC adapter at address = xxxx. Using this option without an address writes the complete boot image to all adapters. /CB xxxx = Verifies the 1MB complete boot image of FC adapter at address xxxx. Using this option without an address verifies the complete boot image of all adapters. /WB xxxx = Copies the 1MB complete boot image from the FC adapter at address xxxx to a file (for example, QL25ROM.SAV). /F xxxx = Writes BIOS code to the FC adapter at I/O address = xxxx. Using this option without an address writes BIOS code to all adapters. If the FC adapter already contains a valid BIOS, this option preserves the existing NVRAM contents. /C xxxx = Verifies the image of the BIOS on the FC adapter at address xxxx. Using this option without an address verifies the BIOS images of all adapters. /W xxxx = Copies the image of the BIOS from the FC adapter at address xxxx into a file (for example, QL25ROM.SAV). /O = Use instead of q2xyyzzz.bin. /V xxxx = Displays current version of the BIOS on adapters at address xxxx. Using this option without an address displays the BIOS version of all adapters. NVRAM only ---------- /l xxxx = Write NVRAM to adapter at I/O address xxxx. /D xxxx = Copy NVRAM to file: QLxxNVR.SAV, adapter address = xxxx. /N = Use instead of NVRAMxx.DAT. /X xxxx = Verify NVRAM of adapter at address xxxx. FCode only ---------- /FF xxxx = Writes FCode to the adapter at address = xxxx. Using this option without an I/O address writes the FCode to all HBAs. /CF xxxx = Verifies the FCode on the adapter at address xxxx. Using this option without an address verifies the FCode of all HBAs. Firmware only ------------- /FR xxxx = Writes firmware to the FC adapter at address = xxxx. Using this option without an address writes firmware to all adapters. /CR xxxx = Verifies the firmware on the FC adapter at address xxxx. Using this option without an address verifies firmware of all adapters. /WR xxxx = Copies the image of the firmware from the FC adapter at address xxxx to a file. /VR xxxx = Displays current version of the firmware on adapters at address xxxx. Using this option without an address displays the firmware version of all adapters. Other options: -------------- /S xxxx = Displays the serial number of the FC adapter at address xxxx. Entering this option without an address displays the serial number of all adapters. /Y xxxx = Displays the port name of the FC adapter at address xxxx. Entering this option without an address displays the port name of all adapters. /I = Ignore subsystem ID. /Q = Quiet mode, which does not display any messages. For example, for adapters with previously valid flash and NVRAM contents, use the following command line options: * To update the flash on a QLogic adapter: c:\>flasutil /fb /o q2xyyzzz.bin * To update the firmware code (only) on a QLogic adapter: c:\>flasutil /fr /o 2x00.bin (Firmware File) c:\>flasutil /fr /o q25xx.bin (Firmware File) 2.5 Additional Notes -------------------- * If you used an FC RAID target in a Cluster Environment, you should enable the Enable Target Reset = Enabled (Advanced Adapter Settings). * Use /I option if the update utility, FlasUtil, does not detect your Fibre Channel adapter. * From the Flasutil application menu, the only option for dumping/copying is W and this will 1) Save/dump a 256 KB imge of the file 2) Save/dump the Flash in a file called QL24ROM.SAV * The /D option dumping/copying the NVRAM is will save the NVRAM in a file called QL25NVR.SAV * Some FlasUtil options may require the use of an external filename instead of the default file. EXAMPLES: C:\Flasutil /C /O QL25xxyy.BIN C:\Flasutil /D /N QLE2542.DAT ====================================================================== 3. Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: http://support.qlogic.com Email: support@qlogic.com (c)Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. ************************************************************************************ 8Gb Fibre Channel Driver and Utilities for UEFI Readme File Table of Contents 1. Introduction 2. UEFI Package Contents 3. Supported HBAs 4. Supported Features 5. Supported Computer Systems 6. Supported Operating Systems 7. HBA Configuration 8. Updating the UEFI Driver 9. Additional Notes 10. Contacting Support 1. Introduction This document provides user notes regarding the Fibre Channel Driver and Utilities for UEFI 2. UEFI Package Contents The following list describes the files included in the EFI driver package: * q2xyzzzz.bin - Combined binary file, which includes the binaries for FCode, EFI driver, and BIOS. * 2500.bin or 2400.bin - RISC firmware file. If this file is not provided, the firmware is included in the q2xyzzzz.bin file. * EfiUtilx64.EFI - UEFI Utility to update the UEFI driver, firmware, and NVRAM. * QL25XX.DRV - Auxiliary driver file used for updating the HBA. * UPDATE.NSH - UEFI script file used to update the HBA on an UEFI system. * EFI\EFICFG.PDF - HBA Configuration and Diagnostic PDF. * EFI\EFIUTIL.PDF - HBA EfiUtilx64 Utility PDF. NOTES: * All bin, uefi, and nsh files are required to update the HBA on an UEFI system. 3. Supported HBAs * QLx24xx * QLE25xx * QMI25xx * QMI35xx 4. Supported Features The UEFI driver supports the following features: * UEFI Specification 1.10, 2.1 * UEFI protocols: SCSI Pass Thru, Block IO, Driver Diagnostics, Driver Configuration, Component Name * 382 targets * 2047 LUNs per target * Fabric and arbitrated loop topologies * Boot from SAN 5. Supported Computer Systems The UEFI driver supports the following systems: * x64 based systems 6. Supported Operating Systems The UEFI driver has been tested with the following operating systems: * Linux x64 * Windows 2008 x64 7. HBA Configuration Refer to the EFICFG.PDF file to configure the HBA parameters. 8. Updating the UEFI Driver For systems that do not include a built-in UEFI Shell, please obtain the UEFI Shell program from the open source site https://www.tianocore.org/ . To update the UEFI Driver and RISC Firmware on all HBAs: 1. Unzip and copy the update kit files to the root level of a USB storage device. NOTE: Please do not change or rearrange the kit directories and/or files that were unzipped and copied to the USB storage device. 2. Connect the USB device to the UEFI based system with the HBAs. 3. As the system is starting to boot-up, Press F1 to enter setup. 4. Go to Boot Manager 5. Go to Boot From File 6. Select the USB device from the list where your files reside. 7. Navigate to the FullShell.efi file that you previously downloaded and hit enter. 8. The system will now be at the UEFI shell prompt "SHELL>", run the "map -b" command to display the file system mapping. 9. Locate the USB device and change to that device. For example, if the USB device is mapped to fs1 after the map -b, run: fs1: The UEFI shell prompt should change as follows: fs1:\> 10. Run the update.nsh script to update the UEFI driver and RISC Firmware. For example: fs1:\> update.nsh Update.nsh will call EfiUtilx64.efi to update all of the HBAs. 11. Reboot the system to make the Driver/Firmware changes take effect. For additional EfiUtilx64.efi functions, refer to efiutil.pdf. 9. Additional Notes If the storage is modified, added or deleted at the UEFI level and is not detected by the QLogic HBA, reboot the system and re-enter UEFI setup. 10. Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: http://support.qlogic.com North America Contact Information Email: support@qlogic.com Phone: (952) 932-4040 Support contact information for other regions of the world is available at the QLogic website: http://support.qlogic.com © Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. ************************************************************************************ FCode for SUN_SPARC FC Adapters Readme File This software license applies only to QLogic customers. QLogic Corporation. All rights reserved. Contents ------------ 1. OS Support 2. Supported features & Notes 3. Selecting the Fibre Channel HBA device 4. Setting and viewing NVRAM Parameters A. Setting and viewing Fibre Channel connection mode (4Gb & 8Gb HBAs only) B. Setting and viewing Fibre Channel data rate (4Gb & 8Gb HBAs only) c. Setting and viewing FCode operation mode D. Setting and viewing login-retry-count E. Setting and viewing link-down-timeout F. Setting and viewing port-down-retry-count G. Setting and viewing max-frame-size H. Setting and viewing boot-wait-time I. Restoring NVRAM Parameter Defaults J. Displaying & entering boot device information 5. Diagnostic Commands A. Version command B. Beacon support C. Selftest D. ext-loopback-test command E. Show-children command F. disk-test command 6. Updating FCode on adapter 7. Building a bootable disk 8. Contacting QLogic ============================================================================== 1. OS Support -------------- This FCode supports SUN Solaris SPARC 8,9,10. ============================================================================== 2. Supported Features & Notes ----------------------------- * 2048 Target ID Support * 256 LUN/Target Support for qla mode * 16384 LUN/Target Support for qlc mode * Boot from Fabric and Local Loop. (4Gb & 8Gb HBAs) * Boot from Fabric Topology only. (all CNAs) * 1,2 or 4 Gb/sec data rate support (4Gb HBAs) * 2,4 or 8 Gb/sec data rate support (8Gb HBAs) * 10 Gb/sec data rate (all CNAs) * Auto NVRAM/VPD backup/recovery (8Gb HBAs and all CNAs) Notes: 1. Some FCode settings at OBP will not be reflected in the SCLI or the SANSurfer. 2. Issue reset-all when change is made to the FCode or Fiber link/target. 3. External Optical Loop back is required when issue test /pci@xxx... 4. All Converged Network Adapters (CNAs) do not allow changing the connection mode or the data-rate. They are fixed at 'Fabric' and '10Gb'. 5. HBA FCode does not support "Loop Only" connection mode when attached directly to an EMC Symmetrix Storage. =============================================================================== 3. Selecting QLogic/SUN HBA port from OBP ----------------------------------------- Prior to setting Fibre Channel HBA NVRAM parameters or executing Diag commands, the device must be selected at the OBP ok prompt. Before you can select the HBA device, you must first 'halt' Solaris and then enter the following commands at the ok prompt: setenv auto-boot? false reset-all This will initialize the OBP environment properly. You can skip the 'setenv' command if the auto-boot? environment flag is already set to 'false'. You may view the current flag settings using the 'printenv' command. To select the device, you may use either select-dev or select methods, as Shown in the examples below. NOTE: When finished setting parameters or running diagnostics and prior to booting the system, you should always unselect the device by typing: unselect-dev. Example: {0} ok " /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1" select-dev ^-- must have leading space. or {0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1 If you are in a windows environment, you can cut and paste the HBA's device path into the select or select-dev command. To view a list of all devices in the system, enter: show-devs. Another way to show a list of HBA devices attached to the system is to use the "show-disks" command, as shown in the example below. Example: {0} ok show-disks a) /pci@7c0/pci@0/pci@9/QLGC,qla@0,1/sd (QLogic HBA Port 1) b) /pci@7c0/pci@0/pci@9/QLGC,qla@0/sd (QLogic HBA Port 0) c) /pci@7c0/pci@0/pci@8/QLGC,qla@0/sd d) /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk e) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1,1/fp@0,0/disk (SUN HBA Port 1) f) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk (SUN HBA Port 0) g) /pci@7c0/pci@0/pci@9/SUNW,qlc@0,3/fp@0,0/disk (SUN 8100 CNA Port 1) h) /pci@7c0/pci@0/pci@9/SUNW,qlc@0,2/fp@0,0/disk (SUN 8100 CNA Port 0) i) /pci@7c0/pci@0/pci@8/QLGC,qlc@0,7/fp@0,0/disk (Qlogic 82xx CNA port 1) j) /pci@7c0/pci@0/pci@8/QLGC,qlc@0,6/fp@0,0/disk (Qlogic 82xx CNA port 0) k) /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom l) /pci@7c0/pci@0/pci@1/pci@0/ide@8/disk q) NO SELECTION Enter Selection, q to quit: f /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk has been selected. Type ^Y ( Control-Y ) to insert it in the command line. e.g. {0} ok nvalias mydev ^Y for creating devalias mydev for /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk {0} ok " /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1" select-dev ^-- enter ^Y here ^-- use backspace to remove fp... or if you had selected the a) device, then ^Y would produce: {0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/QLGC,qla@0,1 ^-- enter ^Y here ^-- use backspace here When the HBA device is selected the first time, similar banner should appear: QLogic MMMMMMM Host Adapter FCode(SPARC): XX.XX YYYYYYY Firmware version Z.ZZ.ZZ NOTE: Where MMMMMMM = HBA/CNA Model Number, (e.g. QLE2562) XX.XX = FCode Version, YYYYYYY = Date/Time code of FCode release version Z.ZZ.ZZ = Firmware Version ============================================================================== 4. Setting and viewing NVRAM Parameters ----------------------------------------- To list all NVRAM and Diagnostic Commands: type "show-commands" at ok prompt. {0} ok show-commands NVRAM Parameter commands show-settings set-connection-mode (4Gb & 8Gb HBAs only) set-data-rate (4Gb & 8Gb HBAs only) set-fc-mode set-login-count set-link-timeout set-port-down-count set-max-frame-size set-boot-wait-time restore-default-settings set-boot-wwn (qla mode only) set-boot-id (qla mode only) Diag Commands version beacon selftest ext-loopback-test show-children disk-test sel-dev sel-lun See Readme file for details To show the current value of all of the NVRAM parameters, as well as the version, serial number, and HBA WWN, type "show-settings". Example: {0} ok show-settings QLogic MMMMMMM Host Adapter FCode(SPARC): XX.XX YYYYYY Firmware version Z.ZZ.ZZ Serial# AFC0731P01932 node-wwn 2000001b 3216ecea port-wwn 2100001b 3216ecea Current HBA Connection Mode: point-to-point (4Gb & 8Gb HBAs only) Current HBA Data Rate: Auto-negotiated (4Gb & 8Gb HBAs only) Current Fcode Mode: qla Current FW login-retry-count: 8(8) Current link-down-timeout: 3c(60) seconds Current port-down-retry-count: 8(8) Current max-frame-size: 800(2048) Current boot-wait-time: DISABLED Current Boot-WWPN: 210000203711bfb9, Boot-LUN: 1b(27), Boot-Target-ID:aa(170) NOTES: Where MMMMMMM = HBA/CNA Model Number, (e.g. QLE2562) XX.XX = FCode Version, YYYYYYY = Date/Time code of FCode release version Z.ZZ.ZZ = Firmware Version Current Boot-WWPN, Boot-LUN, Boot-Target-ID are only displayed in qla-mode. 4A. Setting and viewing Fibre Channel connection mode (4Gb & 8Gb HBAs only) ---------------------------------------------------------------------------- To change or view the current host adapter Fibre Channel connection mode, type "set-connection-mode". Example: {0} ok set-connection-mode Current HBA connection mode: 2 - Loop preferred, otherwise point-to-point Do you want to change it? (y/n) y Choose HBA Connection Mode: 0 - Loop Only 1 - Point-to-point only 2 - Loop preferred, otherwise point-to-point Enter: 2 Current HBA connection mode: 2 - Loop preferred, otherwise point-to-point NOTE: FL-port (Loop) topology is not supported with the QLE220 model HBA. If your Device ID is 54xx (e.g. QLE220) then you cannot change the connection-mode. By default = Loop preferred, otherwise point-to-point 4B. Setting and viewing Fibre Channel data rate (4Gb & 8Gb HBAs only) --------------------------------------------------------------------- To change or view the current host adapter Fibre Channel data rate, type: "set-data-rate". Example: {0} ok set-data-rate Current HBA Data Rate: Auto-Negotiated Do you want to change it? (y/n) y Choose Data Rate: 0 - 1 Gb/sec (4Gb HBAs only) 1 - 2 Gb/sec 2 - Auto-negotiated 3 - 4 Gb/sec 4 - 8 Gb/sec (8Gb HBAs only) Enter: 2 Current HBA Data Rate: Auto-Negotiated NOTE: If your Device ID is 54xx (e.g. QLE220) then you cannot change the data-rate. By default = Auto-Negotiated. 4C. Setting and viewing FCode operation mode --------------------------------------------- FCode supports two FCode operation modes - qla and qlc, default = qlc. qla mode requires a driver named qla2300 qlc mode requires a driver named qlc qla mode is not supported on Sun (SUNW) branded HBAs. WARNING: Use extreme caution when changing the FCode Mode as changing it may cause Solaris to create new device paths for this adapter, which may affect driver instance numbers and mount points in Solaris Example: {0} ok set-fc-mode Current Fcode Mode: qlc Do you want to change it? (y/n) y Choose Fcode Mode: 0 - qlc 1 - qla enter: 0 Current Fcode Mode: qlc 4D. Setting and viewing login-retry-count ----------------------------------------- The login-retry-count NVRAM parameter is used by the Fcode to set the Login Retry Count field in the Firmware Initialization Control Block. This specifies the number of login retries attempted by the FW. The default value is 8. Use the set-login-count command to change this parameter. Example: {0} ok set-login-count Current FW login-retry-count: 8(8) Do you want to change it? (y/n) y FW login-retry-count: Enter 1-ff hex: 7 Current FW login-retry-count: 7(7) 4E. Setting and viewing link-down-timeout ----------------------------------------- The link-down-timeout NVRAM parameter is used by the FCode to determine the number of seconds to wait for the link to come up. The default value is 30. Use the set-link-timeout command to change this parameter. Example: {0} ok set-link-timeout Current link-down-timeout: 1e(30) seconds Do you want to change it? (y/n) y link-down-timeout: in Secs. Enter 2-ff hex: 14 Current link-down-timeout: 14(20) seconds 4F. Setting and viewing port-down-retry-count --------------------------------------------- The port-down-retry-count NVRAM parameter is used by the FCode to determine the number of retries for the start, read and write SCSI commands. The default value is 30. Use the set-port-down-count command to change this parameter. Example: {0} ok set-port-down-count Current port-down-retry-count: 1e(30) Do you want to change it? (y/n) y port-down-retry-count: Enter 1-ff hex: 10 Current port-down-retry-count: 10(16) 4G. Setting and viewing max-frame-size -------------------------------------- The max-frame-size NVRAM parameter is used by the FCode to set the maximum frame length field in the Firmware Initialization Control Block. The default value is 2048. Use the set-max-frame-size command to change this parameter. Example: {0} ok set-max-frame-size Current max-frame-size: 800(2048) Do you want to change it? (y/n) y Choose max-frame-size: 1 - 512 2 - 1024 3 - 2048 enter: 2 Current max-frame-size: 400(1024) 4H. Setting and viewing boot-wait-time -------------------------------------- The boot-wait-time NVRAM parameter is used by the FCode to adjust the time to wait in seconds for the boot device to become online. The default value is 'DISABLED', which sets it to 8 seconds. The maximum value is 65,535 seconds (18 hours, 6 minutes). The minimum value is 8 seconds, same as when disabled. Because this wait-time can be very long, the boot process may be aborted at any time by typing the 'escape' key. Use the set-boot-wait-time command to change this parameter. Example 1: {0} ok set-boot-wait-time Current boot-wait-time: DISABLED Do you want to change it? (y/n) y boot-wait-time: Enter 8-65535 (decimal): 360 Current boot-wait-time: 360 seconds (this example sets it to 6 minutes) Example 2: {0} ok set-boot-wait-time Current boot-wait-time: 360 seconds Do you want to change it? (y/n) y Do you want to Disable it? (y/n) y Current boot-wait-time: DISABLED (this example disables the parameter) 4I. Restoring NVRAM Parameter Defaults -------------------------------------- Use the restore-default-settings command to restore the default values of all NVRAM parameters used by the FCode. Example: {0} ok restore-default-settings Reset all NVRAM values back to defaults. Are you sure? (y/n) y NVRAM defaults restored Current HBA Connection Mode: Loop preferred, otherwise point-to-point Current HBA Data Rate: Auto-negotiated Current Fcode Mode: qlc Current FW login-retry-count: 8(8) Current link-down-timeout: 1e(30) seconds Current port-down-retry-count: 1e(30) Current max-frame-size: 800(2048) Current boot-wait-time: DISABLED Current Boot-WWPN: 0000000000000000, Boot-LUN: 0(0), Boot-Target-ID: 0(0) {0} ok 4J. Displaying & entering boot device information (required for qla mode only) ------------------------------------------------------------------------------ If the FCode operation is in qla mode the boot device information must be saved to the HBA as in the example below. Example showing selection of boot device from list --------------------------------------------------- {0} ok set-boot-wwn Current Boot-WWPN: 0000000000000000, Boot-LUN: 0(0), Boot-Target-ID: 0(0) Do you want to change it? (y/n) Select one of these devices: 0 - Dev# 0(0) PortID 10b9b Port WWN 216000c0fff02f95 1 - Dev# 1(1) PortID 10b9d Port WWN 216000c0ffe02f95 2 - Dev# 2(2) PortID 10b9e Port WWN 216000c0ffd02f95 3 - Enter Manually Select #: 1 Boot-Target-ID: Enter 0-7ff hex: 82 Current available LUNs: LUN 0(0) SUN StorEdge 3510 421D Boot-LUN: Enter 0-ff hex: 0 Current Boot-WWPN: 216000c0ffe02f95, Boot-LUN: 0(0), Boot-Target-ID: 82(130) * {0} ok * Target-ID = Format Target number i.e. c1t130d0s0. Example of manual entry of boot device information -------------------------------------------------- (This step is not required if set-boot-wwn is entered correctly) {0} ok set-boot-wwn Current Boot-WWPN: 216000c0ffe02f95, Boot-LUN: 0(0), Boot-Target-ID: 82(130) Do you want to change it? (y/n) Select one of these devices: 0 - Dev# 0(0) PortID 10b9b Port WWN 216000c0fff02f95 1 - Dev# 1(1) PortID 10b9d Port WWN 216000c0ffe02f95 2 - Dev# 2(2) PortID 10b9e Port WWN 216000c0ffd02f95 3 - Enter Manually Select #: 1 Boot-WWPN: Enter HI 32-bit hex: 216000c0 Boot-WWPN: Enter LOW 32-bit hex: ffe02f95 Boot-Target-ID: Enter 0-7ff hex: 82 Boot-LUN: Enter 0-ff hex: 0 Current Boot-WWPN: 216000c0ffe02f95, Boot-LUN: 0(0), Boot-Target-ID: 82(130) {0} ok Example of setting and viewing the boot Target ID only ------------------------------------------------------ (This step is not required if set-boot-wwn is entered correctly) {0} ok set-boot-id Boot-Target-ID: 9a(154) Do you want to change it? (y/n) y Boot-Target-ID: Enter 0-7ff hex: 1a Boot-Target-ID: 82(130) {0} ok set-boot-wwn Current Boot-WWPN: 216000c0fff02f95, Boot-LUN: 0(0), Boot-Target-ID: 82(130) Do you want to change it? (y/n) No change {0} ok ============================================================================== 5. Diagnostic Commands ---------------------- Version: List FCode version. beacon : Flashing Adapter's LED. selftest : Test Adapter memory and loopback. ext-loopback-test : Test external Loopback. show-children : List all attached targets. disk-test: Test a selected target. sel-dev: Select a device for disk-test. sel-lun: Selet LUN # for disk-test. 5A. Version command ------------------- To display the current FCode and Firmware version, simply type "version". Example: {0} ok version QLogic QLE2562 Host Adapter FCode(SPARC): X Y Firmware version Z {0} ok NOTE: Where X = FCode Version,Y = Date of FCode version release and Z = Firmware version 5B. Beacon support ------------------- Beacon is a feature to allow a specific host adapter to be visually located easily. When the feature is activated, the yellow and amber LEDs on the back of the adapter will flash at approximately one second intervals. To enable the feature do the following: 1. Select the host adapter device you wish to locate as described in section 3, above. 2. Enter: "beacon" The following message is displayed: Flashing adapter LEDs, type any character to quit - The yellow and amber LEDs on the selected host adapter will flash until any character is entered on the keyboard. NOTE: For multi-channel host adapters, only one channel's LED will flash. 5C. Selftest ------------- Selftest is the name of the method that is executed when the "test " command is entered at the ok prompt. Example: {0} ok test /pci@1c,600000/SUNW,qlc@1 or {0} ok test /pci@1d,700000/pci@2/QLGC,qla@0,1 NOTE: It is recommended using a Loopback plug. This will insure that the external loopback test will be executed. An alternative way to test the HBA device is to first, select the device you wish to test as described in section 3, above. Then enter "selftest". Example: {0} ok selftest nvram ok FCode Checksum OK Testing memory, pattern 0 - PASS Testing memory, pattern ffffffff - Passed Testing memory, pattern 55aa5555 - Passed Testing memory, pattern aaaa55aa - Passed Testing memory, pattern a55aa55a - Passed Testing memory, pattern 5b5a5a6a - Passed Testing memory, pattern ff00f0f0 - Passed Testing memory, pattern 1ff00f0e - Passed 10-bit Internal Loopback Test - Passed 1-bit Internal Loopback Test - Passed External Internal Loopback Test - Passed {0} ok 5D. ext-loopback-test command ------------------------------- The ext-loopback-test method allows the user to manually execute the external looback test. Selftest will skip this test if the HBA device is attached to a Switch. The Diag Echo command is used instead of the loopback command if the topology is either F-port or FL-port (i.e. a Switch). The Diag Echo command is not supported by all FC Switches. Therefore, it is skipped during Selftest. Example: ext-looback-test Switch Diag Echo Loopback Test - Passed {0} ok 5E. show-children command --------------------------- show-children is the name of the method that is called when "probe-scsi-all" is executed. The probe-scsi-all command will show all of the SCSI Target/Luns attached to the system by executing the show-children method of all devices with the device-type property set to "scsi" or "scsi-fcp". To show the Targets and Luns of a single HBA, select the HBA device as described in section 3, above. Then enter "set-mode". Example: {0} ok show-children Adapter portID - 10800 ************** Fabric Attached Devices ************** Dev# 0(0) PortID 10b9b Port WWN 216000c0fff02f95 LUN 0(0) SUN StorEdge 3510 421D Dev# 1(1) PortID 10ba9 Port WWN 216000c0ff702f95 LUN 0(0) DISK SUN StorEdge 3510 421D LUN 1(1) DISK SUN StorEdge 3510 421D LUN 2(2) DISK SUN StorEdge 3510 421D {0} ok 5F. disk-test command ----------------------- The disk-test was added as a diagnostic tool to allow the user to perform as simple, non-destructive, read/write data test to a selected target. To execute disk-test, follow these steps, below. 1. Select the HBA device as described in section 3, above. 2. Execute show-children Pick a target (Dev#) and LUN from the listed devices. 3. Login to the target by typing: " sel-dev" Example: 7 sel-dev (will login to Dev# 7) 4. Select a LUN. by typing: " sel-lun" Example: 4d sel-lun (will select LUN 4d, hex) NOTE: You may skip this step if the LUN # =0, which is the default. 5. Execute disk-test by typing "disk-test". disk-test will perform a read-write-read-compare test to the selected target, 64 blocks (32k bytes) at a time. While it is running it will display the current disk block address. The test can be terminated by pressing any key. The disk-test command can also be used to locate a particular target, if there is an activity LED on the target. ============================================================================== 6. Updating FCode on adapter ---------------------------- You can update the FCode using SANsurfer FC HBA Manager or the SCLI application. Before flashing the FCode, the latest QLogic/Sun Solaris HBA driver must be installed. Copy the multi-boot binary file Q25xxyyy.BIN on Sun Sparc System under root(/) directory. For procedures on updating FCode using the SANsurfer applications, see the FC HBA Manager Online Help and the SCLI User's Guide. ============================================================================== 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 third PCI bus slot, target Id 130, Lun 0, and slice 0. The device path is different on each system depending on which PCI bus 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 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, Slice 7 or "/home" can be used to store the temporary saveset files. If at least 1.7GB free was not available on this disk, a partition would have to be created 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 the temporary savesets. If you are not familiar with the "format" command, carefully read the Solaris documentation and manual pages for the command. Misuse of "format" could destroy the data on the current disk drives. Example: # format partition print Current partition table (original): Total disk cylinders available: 3880 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 2650 2.73GB (2651/0/0) 5726160 1 swap wu 2651 - 2930 295.31MB (280/0/0) 604800 2 backup wm 0 - 3879 4.00GB (3880/0/0) 8380800 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 home wm 2931 - 3879 1000.90MB (949/0/0) 2049840 label quit quit 3. Use the "newfs" command to create the file system. Example: In case of qla FCode(fc) mode # newfs -v /dev/rdsk/c3t130d0s0 (/) # newfs -v /dev/rdsk/c3t130d0s7 (home) Example: In case of qlc FCode(fc) mode # newfs -v /dev/rdsk/c5t216000c0ffe02f95d0s0 (/) # newfs -v /dev/rdsk/c5t216000c0ffe02f95d0s7 (home) 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 12. 4. Mount the boot partition to the /mnt mount point. Example: For qla FCode(fc) mode # mount /dev/dsk/c3t130d0s0 /mnt Example: In case of qlc FCode(fc) mode # mount /dev/dsk/c5t216000c0ffe02f95d0s0 /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: (Same in both qla and qlc operation mode) # ufsdump 0f - / | ufsrestore rf - 7. # rm restoresymtable 8. Install the boot block on the new boot disk. Example: In case of qla FCode(fc) mode # installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c3t130d0s0 Example: In case of qlc FCode(fc) mode # installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c5t216000c0ffe02f95d0s0 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 c3t130d0s0(qla mode) or c5t216000c0ffe02f95d0s0(qlc mode). Example: # vi /mnt/etc/vfstab NOTE: Replace every instance of c0t0d0 with c3t130d0 (in case of qla operation mode) or c5t216000c0ffe02f95d0 (in case of qlc operation mode) in the /mnt/etc/vfstab file. 10.Edit the /mnt/kernel/drv/sd.conf to add the boot target id and LUN # Example: name="sd" class="scsi" target=16 lun=6; 11. Shutdown the system. Example: # /sbin/init 0 12. Boot from the newly created boot disk. for qla FCode(fc) mode Example: {0} ok boot /pci@if,2000/QLGC,qla@1/sd@82,0 (Boot to port 0 target 130 LUN 0) or {0} ok boot /pci@if,2000/QLGC,qla@1,1/sd@82,ff (boot to port 1 target 130, LUN 255) For qlc FCode(fc) mode Example: {0} ok boot /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ffe02f95 (In case of JBOD) {0} ok boot /pci@1f,700000/SUNW,qlc@3,1/fp@0,0/disk@w216000c0ff898d16,a (Port 1, Lun No. 10) (In case of RAID) 13. View the current dump device setting. # dumpadm Dump content: kernel pages Dump device: /dev/dsk/c0t0d0s1 (swap) Savecore directory: /var/crash/saturn Savecore enabled: yes 14. Change the dump device to the swap area of the new boot drive. Example: In case of qla FCode(fc) mode # dumpadm -d /dev/dsk/c3t130d0s1 Example: In case of qlc FCode(fc) mode # dumpadm -d /dev/dsk/c5t216000c0ffe02f95d0s1 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. 15. Create an alias entry for the new boot device (optional). Example: (in OBP at the ok prompt) {0} ok nvalias fibredisk /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ffe02f95 16. Set default boot device to be the new boot device (optional). Example: {0} ok setenv boot-device fibredisk * NOTE: Another way to build SANboot disk from CD/DVD or Boot Server as below: # ok boot cdrom or # ok boot net ...Select FC Target for OS install. qlc driver will be installed. Refer to the Solaris Insllation manual for detail procedures. 8. Contacting Support --------------------- Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: http://support.qlogic.com Email: support@qlogic.com (c)Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.