You are on page 1of 49

============================================================================= Firmware and Universal Boot Update for Emulex 4Gb FC HBAs - BladeCenter - AIX ============================================================================= Firmware version 2.

82a3 Universal Boot version 6.02a7

Adapters Supported: IBM Feature Code 8251 (Option PN 43W6859) Emulex 4Gb Fibre Channel Expansion Card (CFFv) for IBM Blade Center

NOTE TO SERVICE - Reference RETAIN #N/A (C) Copyright International Business Machines Corporation 1999, 2010. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in "Notices and trademarks" in this document. CONTENTS ________ 1.0 2.0 3.0 4.0 5.0 6.0 7.0 Overview Installation and setup instructions Configuration information Unattended Mode Web site and support phone number Notices and trademarks Disclaimer

1.0 Overview _____________ 1.1 This update includes the fcode and firmware for the Emulex 4Gb Fibre Ch annel Expansion Card (CFFv) for IBM Blade Center 1.2 1.3 1.4 1.5 Limitations: - None Problems fixed: - See change history for details Dependencies: - None Update Contents o elx_fw_fc_4g-f2.82a3-b6.02a7_AIX-bc_32-64.chg - Change history o elx_fw_fc_4g-f2.82a3-b6.02a7_AIX-bc_32-64.bin

- Update binary o elx_fw_fc_4g-f2.82a3-b6.02a7_AIX-bc_32-64.txt - Readme, this file 2.0 Installation and setup instructions ________________________________________ This package can be used to update the firmware in AIX. 1) Copy the .bin file to the /etc/microcode directory and rename the fi le to: df1023fd-0002.282103 2) Use the AIX diagnostic tool "diag" to update the level of firmware.

3.0 Configuration information ______________________________ - None 4.0 Unattended Mode ____________________ This package cannot be run in unattended mode. 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 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. LSI is a registered trademark of LSI Logic, Corp 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.

(Emulex-supplied Readme begins here...) Emulex Corporation

Light Pulse Family Host Adapter Universal Boot Release Notes 6.02a7 Mar 25th, 2008

I. Introduction This Universal Boot version 6.02a7 contains: (1) x86 BootBIOS version 3.02a6 (2) OpenBoot version 3.10a0 (3) EFIBoot version 4.00a1 For detailed information about x86 BootBIOS, please refer to section II below, for OpenBoot, section III, and for EFIBoot, section IV. This Universal Boot can boot on either Intel x86 Platform, Non-Intel Fcode, or EFI environment. In othe r words, the platform is transparent and the user should not be concerned with any

differences with regard to x86 BootBIOS, OpenBoot, or EFIBoot. Universal Boot is a complete image, whenever it is enabled by any Emulex OS utility, the whole image (x86 BootBIOS, OpenBoot and EFIBoot) is enabled. This is also true for disable. Files included in this release: \602a7.txt \HU602a7.PRG \TU602a7.PRG \BU602a7.PRG \ZU602a7.PRG this file LP9802 LP10000 LP11000 LPe11000 you are reading Universal Boot Universal Boot Universal Boot Universal Boot

\elxcli400a1.efi EFI 4.00a1 Driver Universal Boot Load Procedure The Light Pulse Universal Boot is distributed as a .PRG file. This file may be downloaded to the Adapter using the firmware upgrade procedure with the followin g Utility in Various systems. 1. "Drvcfg" : EFI based Systems.

Please refer to section 4 in EFIBoot for user interface how to download Universal Boot in EFI based systems. 2. LP6DUTIL.EXE er interface how to download EFIBoot in DOS PCI systems. 3. LPUTILNT . 4. Emulex Configuration Tool : Windows Port Driver. Please refer to the elxcfg user manual for details on using the above tool. /*------------------------------------------------------------------------------*/ /* History */ /*------------------------------------------------------------------------------*/ Problems Fixed, Features added or Other Updates Since 6.00a0: ---------------------------------------------------------------------------------: Windows Miniport Driver. : DOS based utility.

Please refer to the LP6DUTIL version 9.0a13, or later, documentation for us

Please refer to the utility user manual for details on using the above tool

******************************************************************************** ***

(6) Boot fail over feature: This was implemented in BootBIOS version 1. features added or other updates since 3. History: ******************************************************************************* 3.0 and EDD 2.02a5 Problems fixed.02a5: 1.02a4 Problems fixed.1 depending on the selection made in the BIOS Utility. Start filling in the XROM Version Number field (0x12) in the PCIR data structure. (CR27758) ******************************************************************************* .II.02a6 Problems fixed. Added code to initialize a flash memory region that is now used in CLP/BOFM code (CR27757) 2. Return BOFM signature in edi for BOFM commands. x86 BootBIOS The current BootBIOS provides x86 boot capability through the use of INT13 syste m BIOS calls. (CR27906) ******************************************************************************* 3. FC-AL. The BootBIOS supports: (1) (2) (3) (4) (5) Multi-topology: Fabric Point to Point.02a1: 1. (CR27815) 2. Fixed a runtime INT-13 boot issue detecting when our host memory is moved by another device. Moved the BOFM code after XROM master checking code to ensure that BOFM commands are only performed by the master XROM. ******************************************************************************** *** 1. (CR29323) 2. Added additional CLP region check. (CR29322) ******************************************************************************* 3. The re are eight boot entries that can be configured.20. features added or other updates since 3. EDD (Enhanced Disk Drive Services): it supports both EDD 3. it is still able to boot from the second configured boot entry and so on. (CR29324) 3. Private loop and Public loop Multi-initiators: Up to 8 adapters in a system Multi-LUNs: Up to 256 LUNs Multi-boot: it complies with the BIOS Boot Specification (BBS). features added or other updates since 3. BOFM PARM command fixes. If the first boot entry fai ls for any reason.02a3: 1.

(CR26774) 6.02a1 Problems fixed. (CR27565) ******************************************************************************* 3. Fixed an issue that could cause a delay in booting from a hard disk attached to the adapter when a bootable CD-ROM is in the CD tray. Fixed an issue where not all configured boot devices would be displayed on the screen and FDISK would not be able to address all drives. Fixed BOFM PARM command target errors. (CR27094) 4. features added or other updates since 3. (CR27665) ******************************************************************************* 3. Fixed a BOFM PARM command issue where only the first two entries in the BOFM table would be searched for targets. Fixed unintentional Interrupt table writes.01a0: 1. features added or other updates since 3. Fixed a bug in the CLP memory restoring routine that could overwrite EBDA memory in certain configurations. features added or other updates since 3.02a0: 1. Fixed a BOFM issue when processing the PARM command where the the target information would get overwritten. Fixed an autoscan issue where on some systems autoscan would find the target but could not boot from it. Added BOFM support.02a0 Problems fixed. Changed the Lp950 to display as Lp952. Missing PCI boot information when booting from a configured boot device. (CR26272) . (CR27003) 8. (CR27607) 2.0 fix (non PnP). (CR26912) 7. PCI 3. Fixed an issue booting from some system when the LUN was 128 or higher.3. (CR27028) 9. (CR26473) 10. (CR27565) 2. (CR27565) 3. (CR25063) 2.02a3 Problems fixed. (CR26629) 5. Fixed an autoscan issue where on some systems autoscan would find the target but could not boot from it. (CR27003) 3.02a1: 1. to adjust the XROM's INT-13 vector to correctly point to the relocated runtime XROM location. Fixed an issue on some systems where the adapter information in the configuration utility could not be displayed and the utility could get stuck when trying to configure a boot LUN.

(CR26459) 13. Fixed a device scan and display bug causing ALPA 0 on a direct connect FC-AL not to be displayed in the configuration utility. features added or other updates since 3. (CR20313) 2.00a3 Problems fixed. (CR22081 and CR23349) 3. Fixed several issues where CLP commands would complete succsfully on a debug development system but would not work correctly on the real HW.00a3: 1. Fixed an issue where the number of sectors was not reported correctly for INT13h. Ensured that restarting adapters will restart all adapters in the system. Added alternative CLP commands to set the WWNN. Removed an I/O quiesce before resetting an adapter. (CR26560) 15. Fixed a screen display problem where the initial load of the Boot BIOS will display "Disable" instead of "Disabled" for the adapter status. (CR25628) ******************************************************************************* 3. Fixed a potential INT-15 interrupt issue that could occur on systems that do not have an Extended BIOS Data Area (EBDA). WWPN. (CR25504) 4. (CR26252) 12. (CR23166) ******************************************************************************* 3.00a2: 1. (CR26476) 14.00a4: 1. (CR23874) 16. Fixed a Fibre channel issue where a second FLOGI is issued in the adapter configuration utility without logging out from the first FLOGI. Funtion 48h that caused FDISK32 to fail in some cases. Fixed an issue where a boot BIOS message was overwritting a system BIOS message <F9> on the screen display.00a1 code base (CR25507) 2. Ported fixes over from the 2.01a0 Problems fixed.00a4 Problems fixed. features added or other updates since 3. features added or other updates since 3. (CR24867) 3. Added new feature handling of the CLP "default" command that was missing from the original implementation. Fixed an issue booting when the LUN was set to 255. and SERDES data. Enhanced the CLP default command operation to check previous values before doing a flash update.11. (CR26587) ******************************************************************************* 3. (CR21866) .

(CR19710) 5.00A0 Problems fixed.00a1: 1. (CR17414) . Added PCI firmware 3.00a1 Problems fixed. Fixed a typo associated with some CLP strings. features added or other updates since 3. (CR20398) ******************************************************************************* 3.00A0: 1. Added explicit screen display confirmation to the user when <ALT-E> or <CTRL-E> has been pressed to enter the Emulex BIOS configuration utility. Fixed an issue where the adapter card would give up on detecting drives/arrays that did not present themselves "ready" after 2 SCSI Test Unit Read commands. (CR20012) 8. (CR19873) 4.00a0: 1.00a2 Problems fixed. The boot BIOS has been updated to support the required features for host system's that have implemented the PCI firmware specification revision 3. Fixed a boot migration issue on some disk arrays. (CR17407) 2. Fixed an issue with the CLP code and the way it was restoring BIOS Data Area memory in the host system. (CR19874) 6. Changed the order of some of the internal adapter commands to ensure better functionality.0. Fixed an issue with the error path not restoring EBDA:0 and 40:0e when an error occurred in INIT code login where permanent memory had been obtained by the adapter. features added or other updates since 3. (CR20121) 2. device. (CR20121) 3. Updated the displayed copyright messages.0 support. and function) for easier identification of the selected adapter. (CR20128) 9. (CR19933) 7. Added support for allowing the key sequence <CTRL-E> to enter the Emulex BIOS configuration utility. added displaying the status of the BootBIOS (enabled/disabled)on the adapter screen.******************************************************************************* 3. Changed command timeouts to be 30 seconds from 5 seconds for HBA specific commands. features added or other updates since 2. (CR20129) ******************************************************************************* 3. Display the full PCI adapter information (bus.

(CR17750) 5. Fixed a bug where the device ID in the rediscovery code was not getting updated with the latest device id. (CR15412) 8. (CR15252) 7. Lpe1150.70A3: 1. Updated the adapter model displayed on the screen to be up to 15 characters. Moved the configuration utility LUN pop up window lower down on the screen so that it does not obscure the bottom 4 boot entry options. Fixed a bug where only the first 16 supported Emulex adapter cards in the system would be issued a reset instead of the maximum supported Emulex adapter cards. and the Lpe111 Host Bus Adapter (HBA) cards. (CR15685) 2. (CR17407. Fixed a bug where the adapter BIOS was not restoring a system BIOS variable when the user hit the <s> key to skip the Emulex adapter boot BIOS. (CR17748) 4. Fixed a potential bug when obtaining memory on a host system that does not support the Extended BIOS Data Area (EBDA). (CR15838) . but instead was using the old device id. Added an API for DMTF Command Line Protocol (CLP). Updated eVPD scanning and parsing code. (CR17751) 8. (CR15801) 4. Enhanced the method that the adapter uses to locate and access the adapter's variables located in host memory. Lpe11000. (CR17750) 6. (CR15772) 5. to support the blade mezzanine HBA. features added or other updates since 1. CR14639) 7. Enhanced the code to retry a fabric login up to 5 times if the fabric login fails during a rediscovery process. Added support for the Lpe1000.00A0 Problems fixed. (CR14243) 6. Changed the configuration utility input option for selecting the Auto Sector Format Select menu item from hex value (A) to a decimal value (10) to be consistent with the other menu item choices.3. Enhanced the mechanism in which host memory used by the adapter card is located. Fixed a bug where the adapter BIOS was inadvertently checking one too many ALPA ids. (CR15424) 3. (CR17891) 9. CR17750. Added a workaround for some Host Bus Adapters cards where the VPD data could potentially be reported incorrectly. (CR18169) ******************************************************************************* 2. Code now parses for any size eVPD.

(CR15558) 2. (CR10241) 2. The new fix will takes care this issue. Lp11000. (CR14854) . Lp1150. (CR155 60) ******************************************************************************** *** 1.******************************************************************************** *** 1. Changed the new banner display on X86 boot with the Emulex copyright. If there are two or more different HBAs with VPD support on the system. (CR15559) 4.70A2: 1. Multiple reboots causes link to not come up. Lp101. The new fix will s et the default hard ALPA of zero. Lpe1150. (CR15469) 3. The new fix take s care this issue by removed the update nvram during the init_ff. Supported E-VPD. and Lpe11000. Feature added to increase scan the eVPD data area up to 1024 bytes in VPD da ta field. if e-VPD fields are empty or blank on the HBA then the HBA will identified as it is today. Fixed the bug which fails to discover ALPA EF in private loop configuration. Features added or Other Updates Since 1. the banner display will always display the same HBA banner when press s (to skip the bi os scan). this setting can causes confusion for customers which our HB A comes from the factory with a default hard alpa of zero. Lpe111 . Features added or Other Updates Since 1. Lpe11000. Per the FC-GS4 spec. and to parse the entire VPD data to find the appropriate eVPD fields and use them. Lp111.70A2 Problems Fixed. all CT commands shall have a timeout value of 3 x R_A_T OV instead of 2 times. if VPD HBA Model number info is present. The Boot Bios Using the d command in the bios config screen leaves adapter w ith hard ALPA of 1. (CR11302) 3. The new released fixed this issue. (CR12013) 5.70A1: 1. (CR14853) 6. Lp10000. boot failure. Supported more HBA such as Lp11000. (CR11902) 4. Fail to detect the EMC cx200 when connect directly to the LP952.70A3 Problems Fixed. because it fails to discover ALPA EF in direct connect configuration. the n display the new VPD HBA Model number.

7. there is issue which mishandling the memory read-only mode during the runtime. Features added or Other Updates Since 1. In some system server. the new release clean up the display error and fixe d the issue. Move hard_alpa variable to common region area. (CR9429) 2. there should be Test-Unit-Ready commands i ssued after follow the Inquiry command during the process of scan disk target funct ion.PRG file. The new "X" build will remove some variables in runtime library. BIOS Load Procedure The Light Pulse BIOS is distributed as a . This file may be downloaded . During the BIOS login. the BIOS gave t wo times retry for the Test_Unit_Ready command. * There is display error in BIOS utility menu on 3 digit adapter card.70A1 Problems Fixed. The new release added the TUR follow the Inquiry command and makes FC boot success on secondary path. Features added or Other Updates Since 1. (CR10079) 3. which results in retries until the system times out and resets. ******************************************************************************** *** ******************************************************************************** *** 2. an d keep those variables in the init-time. (CR10080) ******************************************************************************** *** 1. And this caused the boot failure if LUN1 from the primary path was deleted an d was expecting to boot from LUN1 on the secondary path.70A0 Problems Fixed. this release will increse upto five times retry for TUR when HBA receives the Unit Attention. such as Lp982 in previous release code.70A0: 1. when HBA receives the Unit Attention. Added LP101 support. (CR12314) ******************************************************************************** *** 1.63A2: * When Start Unit Command is enable.

enable Boot BIOS. To Activate BootBios: >From the lp6dutil Main menu. If this occurs. Type Type Type Type <5> <3> <0> <7> and and and and press press press press <Enter> <Enter> <Enter> <Enter> to to to to open the Maintenance menu. NOTE: The update operation must not be interrupted or the FLASH may become corrupted. 3. (2) Boot the DOS PCI system. The operation should take less than 2 minutes to complete. NOTE: Each newly installed Host Adapter must have BIOS activated using the DOS utility (lp6dutil). return to the previous menu. This image file is downloaded into the xBxxxx's FLASH. or either Windows NT Driver Utilities: * GUI LPNTUTIL Mini-port Driver * Emulex Configuration Tool for Port Driver Please refer to the user manual for details on using these tools.0 or greater (found on the released diskette. CD-ROM.1 BIOS Upgrade Procedure with LP6DUTIL (1) Install the Adapter to be upgraded into a DOS PCI system (see Hardware Compatibility for a recommended configuration). Select Option 1 (Update Firmware) The program will prompt for the file name to download. . (3) Run LP6DUTIL revision 8. Select Option 5 (Maintenance) Ensure that the diagnostic utility identifies itself as revision 8.PRG can be found. exit the lp6dutil program. (6) The Adapter must be re-initialized to start using the upgraded BIOS. or FTP server) (4) From the Main Menu. you will not see the Boot BIOS message during boot. Specify the drive an d path where xBxxxx. 2. (5) From the Maintenance Menu.EXE. usually when no LEDs turn on. This condition can be identified by POST failure. Until Boot BIOS is enabled using the DOS utility. Once Boot BIOS is activated. the Adapter must be returned to Emulex for FLASH update. Perform a Hard Reset to the system or recycle the power. a message will appear during the boot sequence asking you press the <Alt E> key for Boot BIOS or the <s> key to skip Boot BIOS.0 or greater before continuing. BIOS was already activated if it was downloaded as performed as the above. 1. 4.to the Adapter using the firmware upgrade procedure with the DOS based utility LP6DUTIL. 2.

only the first eight adapters can be configured as the boot adapters. are determine by the list of configured boot entry in the BIOS utility. The list of entry. that are export to Multi-boot menu. Drive C: boot_entry2 * If a system supports Multi-boot (BBS). It can be any combination of LP7000. boot_entry1. * If the message "Retry this adapter!!" was display during the BIOS scanning.81 or above for LP8000.3. any adapter after the eighth adapter will not be visible during the boot process. boot_entry3.01 for LP850 and firmware 2. Adapter 2: boot_entry2. * If there are any hardware changes such as replacing drives or re-configuring a Fabric switch environment. * If a system does not have Multi-boot (BBS). this version of BIOS has to work with Firmware 2. boot_entry3. please check the hardware configuration or re-configure BIOS using the BIOS Utility. 952. The order of boot entry that are exported to the Multi-Boot (BBS) are: . Adapter 2: boot_entry2. the Boot disk (drive C:) is determined by the first configured boot entry (Primary boot entry). However. Drive C: boot_entry0 Example 2: Adapter 1: Adapter 2: boot_entry2. the Boot disk (drive C:) will be the first entry in Multi-boot on system BIOS setup Menu. If a user want to configured on the second adapter. It can be on the first adapter or the second adapter. firmware 1.22 or above for LP6000 and LP7000. do not configure any boot entry on the first adapter. 850. boot_entry1. 9002. Example 1: Adapter 1: boot_entry0. * Press <Alt E> to enter the Emulex BIOS Utility. For example: Adapter 1: boot_entry0. boot_entry3. make sure to re-configure BIOS using the BIOS Utility. * It will allow any number of LightPulse adapters in a system. and 982. BIOS Limitations and Default Configuration 3. 8000. * In order to work properly.1 Limitations and Features Below is a list of the current preliminary LightPulse BIOS limitations and features. 9802.

the maximum number of devices (ALPA) is 99 when configuring boot device in BIOS Utility. * For "Configure Boot Devices" option. * For FC-AL. PCI bus number and PCI device number will be printed on the screen. and each has a Boot drive attached. * Boot BIOS is disabled by default. * On Private Loop. * For FC-AL. * On Fabric environment.boot_entry0. All adapters or BOOT drives can be configured to different ALPAs other than their default values. user must press <Alt E> to enter the BIOS Utility to enable boot BIOS. the adapter's ALPA. BIOS will look for a Public Loop first. 100. boot_entry2 and boot_entry3. * Default PLOGI Retry Timer is 0 (no retry). * All the above default settings can be changed in the BIOS Utility. boot_entry1 and boot_entry3. the user can know exactly which adapter is in which PCI slot in the system. boot_entry1. each host adapter has a default ALPA of 00 (Hex). If a Public Loop is not detected. PCI bus number and PCI device number can be viewed on the welcome screen or in the BIOS Utility menu.0 was disabled in default. The first adapter is usually the lowest PCI slot in the system. press <d> in the Parameter menu. the eight boot entries will be zero by default (<d> key). the S_ID (source id). However. the maximum number of devices (D_ID) is 90 when configuring boot device in BIOS Utility. the first PCI-scan adapter will be the BOOT adapter. These 256 LUNs can be scanned in different stages using the BIOS Utility. 3. and 200 milli-sec. In this way.. This information can be viewed from the BIOS Utility. * For Fabric Point to Point or Public Loop. However. it will look for a Private Loop. In this case. * If more than one adapter is in the system with the same PCI bus number. Multiboot can overwrite this order by: boot_entry2. In order to use Emulex Boot BIOS. * A maximum of 256 LUNs is supported (LUN 0 through 255) per target id (D_ID or ALPA). boot_entry0. This is because current Win2K does not . only 8 entries can be seen during BIOS initialization.2 Default Configuration * To reset the selected adapter to its defaults. * In "Configure Boot Devices" option. it can be changed to 50. * EDD 3. Drive C: is boot_entry2. Loop is the default mode. * Auto Scan is disabled by default. * Spinup delay is disabled by default.

Clear selected boot entry!! This is used to clear the selected boot entry.2 Adapter Menu * The adapter is displayed by ALPA for FC-AL. it still be able to boot from the second configured boot entry and so on. 4. BIOS Utility User can press <Alt E> to enter the BIOS Utility.1 Main Menu This menu lists all the adapters in the system and the BIOS version number.1 Configure Boot Devices Fail over booting: it is always there since BIOS version 1. Currently.0 and it could hang during the Win2K installation on regular Pentium series systems. User can enter the number to select the particular adapter. this menu supports FC-AL: Private Loop and Public Loop. it can boot from either WWPN or DID. 4. on board firmware version. There are eight boot entries that can be configured. * Environmental variable is disabled in default. Public loop and Private loop. * <x> is the only way to exit the BIOS Utility and reboot the system.support EDD 3. PCI bus number and device number.2. * Start Unit command is disabled in default. On Private loop. * <d> is used to reset the selected adapter to default value while in the BIOS Utility. The first entry is the primary boot entry. it can boot from either WWPN or ALPA. * It has 8 boot entries with the first one as the primary boot entry. * The top screen also displays I/O base address. please fill in this entry before filling in the rest of the entries. On Fabric.20. port name and node name. . it will do public loop first. Each menu is described below. another menu will be displayed: 00. If this board is configured as FC-AL. If first boot entry failed for whatever hardware reason. 4. This Configure Boot Devices will take care Fabric. it will perform private loop. * If user selects any entry. 4. and Fabric Point to point. if it failed.

* Enter the two digit LUN. This option is especially useful for Tachyon-based RAID arrays. Boot this device via WWPN 2.01.2. 50. The time it takes for one PLOGI to scan the whole loop (if 126 ALPA are on the loop) is shown . it will issue a Name Server Inquiry GID_PN (Get Port Identifier).1 Enable or disable BIOS on this adapter This option is used to Enable or Disable Boot BIOS on an individual adapter basis.2 Configure This Adapter's Parameters This option is used to configure parameters for this adapter. The default is disabled. another Pop up menu will be shown. In front of each entry. then. * If user selects any two-digit number such as 01. 4. WWPN and disk information. Boot this device via DID * If a user selects 1. do the rest of the scanning.2. For example.2. This option can be used to change the ALPA of the adapter. Please enter the first two digits of the LUN to be scanned for. 1. 100 and 200 msec.2. If a user changes the Host ALPA to a different value. * A list of total 16 LUN starting with LUN that was enter above paragraph. during initial BIOS scan. However. DID or ALPA. it will not show on the NVRAM ALPA until the system has been reset. 4.2 Change default ALPA of this adapter This applies only to FC-AL. 02. The DID of the earlier selected entry will be saved in the Flash. The resolutions are 0 (no retry). B2W means Boot entry number two will boot via WWPN. Under very rare occasion. When the port comes to life. then a Pop up menu will be shown.2. 4. same as 01 with different target device. * If a user selects2. * If any two-digit number is entered. B1D means Boot entry number one will boot via DID. The default value of the ALPA for the adapter BIOS is 00 in Hex. The LUN will stop on the first LUN found in this particular target device. The WWPN of the earlier selected entry will be saved in the Flash. based on this DID.2. the PLOGI retry interval helps to discover this device. a Tachyon-based RAID array will reset itself and the port will be temporarily off line in the loop.2. 4.3 Change PLOGI Retry Timer This option is used to set the interval time for the PLOGI Retry Timer. B#D or B#W specifies Boot entry number with boot via DID or WWPN.

if there is boot device present. 4.2. If the BIOS doesn't fine the device within three minu tes. it will try Fabric point to point. It has to be set default first <d>. if it fails. then it will continue booting scanning algorithm. The other options are 2. In the fabric-attached case. First NOT LUN 0 device The above options are valid only if none of all the eight boot entries is configured.4 Topology Selection This menu is used to choose the Topology: (1) Auto Topology (Default): Loop first.2.5 Enable or Disable Spinup delay The default is disabled When the spinup delay was enable. the configured boot entry will override any above option was selected. if the boot devic e is not ready.2. 4. and hopefully another multi-bo ot device is available. we will attempt to boot from the lowest target AL_PA we find. 4. Any first device 3. boot immediately. it'll search for the first available boot devi ce. First LUN 0 device 4. then the autoscan can be set. In other words. The default is disabled.2. autoscan setting would not be allowed.2.6 Enable or Disable Auto Scan If there is a configured boot entry. If no boot devices have been defined. then wait for spin-up delay and keep searching for the bootable de vice for 3 minutes time period. we will attempt to boot from the first target found in the NameServer data. if it fails.2.6. (2) Auto Topology: Fabric point to point first. (3) FC-AL (Loop) only (4) Fabric point to point only 4.2. 100 msec will take 12 seconds. In the private loop case.2. Otherwise. it will try Loop.1 Any first device . then the BIOS will delay for 5 minutes before scanning for devices. 200 msec will take 22 seconds. and the Auto Scan flag option is enabled (defaults to disabled).below: 50 msec will take 5 to 6 seconds.

Therefore.10 Enable or Disable Auto Boot Sector User need to enable this option.2.6.2. "Enter two digits of starting LUN (hex):" has to be the known specific LUN and it will not display like the regular LUN scanning. and the new link speed now can support up to 4 Gigabaud.2 First LUN 0 device Same as 3.2.8 Enable or Disable Start Unit Command This option was disabled by default. 4.7 Enable or Disable EDD 3. 4.2.2. the user have to know the specific LUN to issue the SCSI Start Unit Command. * The first D_ID from Name Server Inquiry will become the boot device.11 Link Speed Selectioin User can select the desired link speed in the link speed selection menu.2. When it is enabled.The first adapter will: * Issue a Name Server Inquiry. 4. Public loop or Private loop configuration. It is used to set the boot controller order if the system support the Environment Variable. 4.6. the default was disabled.1 except auto scan the first LUN 0 as the boot device.2.2. This is because when the user configure boot device. The adapter will attempt to log in to a Public Loop first. the default link . It is used to automatic define the boot sector of the target disk in migration boot purpose.1 except auto scan the first NOT LUN 0 as the boot device. If there isn't any partition on the target.6.0 and it would hang the system during the Win2K installation.2.3 First NOT LUN 0 device Same as 3. This is because current Win2K does not support EDD 3.0 EDD 3. The first successful scan device will be the boot devi ce and only this one device will be exported to the Multi-Boot Menu. it is strongly recommended that you use the "Configure Boot Devices" option to configure at least one boot entry for Fabric. the default boot sector format is 63 sectors.2.2. 4.2.2.2. 4. If it fails.2.6.2. 4.9 Enable or Disable Environment Variable This option was disabled by default.2. It is used to issue SCSI Start Unit command.0 was disabled by default.2. it will log in to a Private Loop.

(3) Press [F6] within 5 seconds when the "Press F6 if you need to install a third party SCSI or RAID driver" message is displayed.2 Install Windows 2000 (1) Boot with Windows 2000 Setup Media (See Microsoft Documentation For Details) (2) Monitor the white bar on the bottom of the screen. Procedure to Build the Boot Disk from the LightPulse Adapter (1) Set the boot disk to be the lowest AL_PA in the loop or use BIOS Utility to configure the ALPA. Multi-boot BIOS allows a user to select any boot disk in the system BIOS setup menu. or you have chosen to manually specify an adapter. The system must have multi-boot system BIOS in order to take advantage of this feature. The boot disk can be a Fibre Channel drive. 6. (4) Format the C: drive from the floppy.1 Multi-Boot BIOS (BBS) Multi-boot BIOS is in compliance with BIOS Boot Specification (BBS). 6. This will allow you to configure and build your operating system on the drive connected to the Emulex adapter. (4) When the "Setup could not determine the type of one or more mass storage devices installed in your system.0 (1) Boot with Windows NT 4. 5. Advanced BIOS Features 7. insert the Emulex driver diskette. 6. insert the Emulex driver diskette. (3) Boot from floppy and use FDISK to create DOS primary partition. (5) Install DOS version 6. (6) Install WindowNT. Procedure to Install Windows on the Fibre Channel Disk Make sure the user always gets the latest version of Windows NT Port driver or Mini-Port driver." message is displayed. (3) Follow the instruction to complete the installation.1 Install Windows NT 4.0 Setup Media (See Microsoft Documentation For Details) (2) When the "Specify additional storage driver" message is displayed. you must disconnect or disable the other adapter. a SCSI drive.speed is Auto Select. an . * Your computer's system BIOS may require that another controller take precedence over the Emulex adapter during boot. (5) Follow the remaining instructions to complete the Windows 2000 installation 7. (2) Prepare a floppy disk that contains both DOS FDISK and FORMAT programs. If this occurs.00 or above.

However. Emulex BIOS will supply the first 16 drives to the system BIOS menu. Also. Added "link-speed" command to show the link speed of the current HBA device. Public loop. Added "set-post-linkup" command can either bring the linkup and init the HBA during the POST or do the normal init POST procedure. the default is FCODE will not bring the link up and init the HBA during the POST. 6. (4) It will be necessary to correlate the intended boot disk displayed by the 'probe-scsi-all' command to the devices displayed by the operating system. it supports multi-initiators and multi-LUNs (0 through 255). For example. The boot device will be Fibre Channel disk with ALPA 23 instead of ALPA 02 that is set in BIOS Utility. Changed "set-fdiag-switch" command into the debug mode only. the user can select ALPA 23 in the system BIOS setup menu. and swap slice of the local current boot disk. The multi-boot BIOS can override the Fibre Channel drive that is selected in the BIOS Utility. OpenBoot This version of OpenBoot supports FC-AL.10a0 -----------------------1.2 Driver Initialization after BIOS Boot.NEW CHANGES 3. (CR28386) 4.IDE drive or a floppy drive. (CR28384) 2. Private loop. --------------. The boot disk has ALPA 02. (CR28392) . -------------------------------------------------------------------------------------------. Added standard CLP (Command Line Protocol) support.NOTES and CAUTIONS --------------------** Ensure that critical files on local boot disk are backed up as a measure of protection. and Fabric Point to Point. (1) This procedure assumes there is already a 'local' boot disk. the system has only eight Fibre Channel disks. (2) The size of the intended (target) fibre channel disk should be big enough to hold all the file systems. (CR28385) 3. (3) As there will probably be more than one logical disk drive on the fibre channel adapter it will be necessary to use persistent binding ('nailing' a specific scsi id to a specific wwpn or did). ******************************************************************************** *** III.

(CR24936) ----------------------. Changed the display format on Fcode version number in . (CR25036) 3. Fixed the issue on some systems the probe-scsi-all command fails if the HBA has no link. Some variable in the scsidisk file was create as local variable.00a1 -----------------------1. the decode-unit is fails to convert text unit-string. and the Boot code is not configure to response the FC-CT Unsolicited. Added more compatible devices name property on compatible field for PCI and PCIex. (CR24735) 5. New implement added FC tape boot support. This release takes care this issue by set the BME bit on forever. and cause system is not bootable.NEW CHANGES 3.NEW CHANGES 3. (CR27598) ----------------------. Fixed the issue if the len size of the decode-unit on device path /fp is large than 2 digits. In dual channel HBA when one of the Bus Master Enable bit is cleared can cause other channel HBA DMA to be stuck.01a1 -----------------------1. If there is some unsolicited frame coming from the switch or service provider.01a0 -----------------------1. New implement added FC 520 bytes blocks disk boot support. and cause system hangs or failure during the boot time. (CR24737) link fixed 2 Gb/s on 4 Gb/s .properties command. In PCI Configuration Register there is a bit to control the HBA bus master capability (BME). and boot command disabled.NEW CHANGES 3.00a2 -----------------------1. (CR25233) 5. the new release removed the mailbox config_ring command. (CR24734) 4. this can cause the system hangs during boot or scan targets. Update the copyright date from . and cause system fail to boot with "Last Trap: Illegal Instruction" error message. the new removed the 4 Gb/s option on set-link-speed selection menu on or lower HBAs. if user selected 4 Gb/s speed on a 2 Gb/s HBA can cause link or boot failure. (CR24732) 2. The new fixed by change some variables to external variable instead of local variable. Support SLI-2 implementation.NEW CHANGES 3. (CR25617) 6. (CR25215) 2.----------------------. The 4 Gb/s link speed option is only available HBA only. Support 8Gb/s HBA. (CR24911)(CR25005) 4. (CR24733) 3. In order not to sent any FC-CT request. In the set-link-speed selection menu.properties screen from ASCII to Hex for IBM machine. ----------------------.

The new release fixed this issue by update the correct PCI device ID in make file. If the search eVPD data (V2) is located near at the end of 108 bytes in the VPD field. there will be a warning message "Cannot dump NVRAM" display during the POST. the second path is failing due to no retry on a reservation conflict. and set the numbers of retry on busy status to limits of 10 times. after "scan". To fix this display VPD data on V2 field issue. Fcode issue a "unmap-regs" at "close". (CR19585) 5. and this message sometimes can confuse user. the new fix changed the VPD dumped entry index to 20*n bytes. and change the VPD search area to 28 bytes. Fcode in loop mode display incorrect LUNs on show-children or probe-scsi-all command. In some special array. The new fix added support deferred error (71h & 73h) and current error (72h) on sense data returned to returning check condition status. (CR20261) 2. and system can continue complete setup the FC targets into the boot menu.NEW CHANGES 1. (CR18053) . and this special condition only apply to some systems only. thus sometimes can cause fails to display the whole string of eVPD (V2) data. (CR20267) ----------------------. (CR20262) 3. If the NVRAM data field is empty.NEW CHANGES 1. this will continue apply retry command. The new fix takes care this issue by adding the SCSI inquiry command before calling the show-luns command in show-children. and cause the system not able to recognize any FC devices during "check".6. and the warning message wouldn't display during the normal boot session. The new release re-update the sfs? flag bit in NVRAM after "set-sfs-boot" was called. The PCI device ID for Lpe11000 in make file wasn't a correct value. (CR20266) 7. somehow the re-maping FC device into the system virtual address spaces function is not working properly. The new fix removed the "unmap-regs" call at the "close".50a9 -----------------------1. In some blade server. The new fix set this error message display only in the verbose mode. and confuse user. In the multipath environment. the sfs? flag bit in NVRAM is not display correct value. After changed the boot mode from sd-boot to sfs-boot. but if removed out this warning message. (CR20264) 4. and cause probe process does not find the Fcode image during POST. then it will hard to debug in a real case. Fcode fails to issue a retry command with a check condition if the sense data returning a response code 71h (deffered errors). (CR24739) ----------------------.50a8 -----------------------1. then re-open again to "check" the FC device for setting up the FC targets into the SMS boot menu. Update the new Emulex Copyright display format. This release added retry on SCSI Reservation Conflict. (CR20265) 6. this can cover the whole maximum length of 80 bytes on V2 data field.

Re-adjust the string value of eVPD display to fix the segmentation fault iss ue during DR operation on some server which causing Fcode not to be loaded. and others for 30 seconds timeout.use select-dev to Open the Device". Fixed the bug on system hangs during "probe-scsi-all". Fixed the bug for mishandle the return value of TUR when the first FC target was not available or not connect properly during the Multi-path Fabric boot time and cause system not to continue boot on the 2nd target instead return with an error message of "STACK UNDERFLOW" issue. (CR17009) 12. fix has setup the report-luns not setup as external variable in fail to compile the report-luns into and result a boot failure. The new fix will be increased FCP Response Timeout to 100 seconds for Start/Stop Unit command. (CR17845) 13. (CR17835) 2. The new fix will remove this warning message. If user use "cd device-name" command to select the HBA. Added 60ms delay after PRLI and before the first Report Luns command is sent out. (CR17926) ----------------------. this caused the system the RAM during the boot time. the new fixed will issue a warning message to the user as "Device is not Opend . There are extra spaces shows on show-children's display format between LUN to LUN. The new as external variable. Update this readme document for how to setup the FC Multi-path Fabric boot method. then system OBP will issue an "Memory Address not Aligned" error message. (CR17843) 11. (CR17840) 7.----------------------. (CR17013) 10. Added the Report LUN before Test Unit Ready command. (CR17837) 4.50a6 -----------------------1.fcode to display the Fcode version number.version command to . (CR17946) . If the NVRAM never been initialize before. The command of report-luns is FCode. because the timeout for FCP completion was greater FCP Response. Fixed the bug for mishandle the return value of TUR when FC cable was not connect properly during boot time and result an error message of "STACK UNDERFLOW" issue. and this message will confuse user.50a7 -----------------------1. Rename the . The new fix remove those extra spaces between LUN to LUN. (CR17836) 3. (CR17842) 9. Changed the FCP Port Completion Timeout to 90 seconds for Start/Stop Unit command. there will be a warning message "Cannot dump NVRAM" display during the POST.NEW CHANGES 1. Fixed the issue to change the Fcode issues double PLOGIs down to one PLOGI in a normal FC boot condition. and others for 40 seconds timeout. (CR17838) 5. (CR17841) 8. and try to update the NVRAM. (CR17839) 6.NEW CHANGES 1.

(CR16558) 3. This system had a feature in obp to probe scan all the onboard devices during local boot time. the new link speed now can support up to 4 Gigabaud. Change the encode method from string to integer on some machine in their . (CR16564) 9.NEW CHANGES 1. then it will cause the system panic with the error message "<unknown>" module. Once the decode-unit returns unexpected result during boot time. Added Test Unit Ready on before sending a Start/Stop command to the target. and let the system continue to finish up the probe scan. Added the new link speed selection feature. and the default link speed is Auto Select. Fixed the bug for Some system results in panic during early stages of boot process. Added delay on fcp response for START/STOP command. (CR16566) 11. (CR16562) 7. (CR16567) ----------------------.NEW CHANGES 1. user can use command "set-link-speed" to select the desired link speed. and 0x0d (ESI Device). The new fixed removed "fc-boot-dev-portWWN" and "fc-boot-dev-portID" in . (CR16557) 2. Take care the new selective reset behavior. The new fix will set the proper return value for the "decode-unit" during boot time. 0x0c (Array Controller). The value of host "port-wwn" and "node-wwn" are missing in . 0x09 (Communications Device)." to "Copyright (c) 2005 Emulex".properties command when user use cd command to select the specified device node. Removed the 'Target none' display on probe-scsi-all or show-children command.(CR16565) 10. 0x07 (Optical Device). Display wrong "fc-boot-dev-portWWN" and "fc-boot-dev-portID" in reg property when using "probe-scsi-all" in OBP. (CR16559) 4. and this probing feature requires a method of decode-unit to converts a text representation of a unit-address into a numerical representation of a physical address within the address space defined by the device node. (CR16047) .property when using "probe-scsi-all" in private loop mode.50a5 -----------------------1.property field to display the proper fcode-version number. Increased fcp timeout for Port completion from 4 seconds to 60 seconds. (CR16560) 5. 0x08 (Medium Changer). don't send the Start/Stop Unit command. Re-adjust the # of retry on START/STOP command when the disk is not spinning up. Added new decode Peripheral Device Type for: 0x06 (Scanner Device). The new fix will show the host "port-wwn" and "node-wwn" value in the reg property when use either "cd" or "dev" command to select the specified device node. If the target is ready.50a4 -----------------------1. (CR16563) 8.14. (CR16561) 6. Changed new copyright from "Copyright (c) 2005 Emulex Design & Manufacturing Corporation. (CR17847) ----------------------.

50a3 -----------------------1. The new number of retry for Queue Full is up to 10 times and then give up. Change the new banner display on Fcode with the copyright. then display the new VPD HBA Model number.emlxs". (CR14633) 3.(CR16049) 5. So the XXX-Branded adapter can only boot with XXX Boot format only. (CR15521) 8. the detail debug error message will be print out during POST or boot time if there is any link/boot failure. (CR15513) 4. (CR15517) 7. Added the new Fcode Diag Switch feature. Per the FC-GS4 spec.50a2 ------------------------ . user can use this command to show the LUNs target with the desired WWPN only instead of the whole WWPNs and LUNs. (CR15522) 9.2. user can use command "set-fdiag-switch" to turn the diag switch on/off. (CR14497) 2. all CT commands shall have a timeout value of 3 x R_A_TOV instead of 2 times. Added new support HBA LP1005 on the Fcode boot list. Disable change the SD Boot format on XXX-Branded HBA.(CR16051) 7. if VPD HBA Model number info is present. Bug fixed on HBA did not retry under a LOGO response and cause fabric boot failure.(CR16053) ----------------------. Supported E-VPD. Changed new device name property for XXX Branded HBA from "emlxs" to "XXXW. (CR15524) ----------------------. Fixed the bug on fail to report fcp-lun on XXX software BOOT format. Changed the new number of retry condition for SCSI Busy to retry forever. Added the new feature "show-wwpn-child". Rename function call for setting the boot format from "set-XXX-on" to "set-XXX-boot" to boot with XXX Boot format. and "set-XXX-off" to "set-sd-boot" to boot with SD Boot format. (CR15516) 6. Bug fixed on HBA did not retry the START/STOP command on a SCSI Queue Full response and cause fabric boot failure. If the Diag switch is on. (CR15707) 4. the new release fixed this issue by change the different device path /fp when booting with "SD Boot" format.NEW CHANGES 1. Bug fixed on error message "Data Stack corrupted!!!" when booting with Fcode on SOME machine. (CR16052) 8. Added the host "port-wwn" and "node-wwn" of the HBA into the reg property during POST time which was required by XXX system to allow to collect the Host wwpn/wwnn info during XXX boot. if e-VPD fields are empty or blank on the HBA then the HBA will identified as it is today. Bug fixed on cannot to configure boot device using DID on XXX boot.(CR16048) 3. (CR15514) 5.NEW CHANGES 1. (CR16050) 6.

The default mode is Standard SCSI SD mode.properties menu. (CR14297) 5.50a0 -----------------------1. Able to share one common code on SUN "XXX" FC Boot and Standard SCSI SD Boot. Removed FCODE banner display message during POST for "XXX" FC boot. (CR14455) ----------------------. (CR13542) 4. and device type for "XXX" operation. to solve the issue for there's not local access of SCSI device when the "XXX" is enable on some system. FCODE will only bring the link up during the FC boot time or select the boot device by user. (CR14487) 2. Removed the "XXX" support status in Fcode . Changed new behavior for FCODE init POST procedure which FCODE will not bring the link up and init the HBA during the POST. This release supported the new FC boot with SUN "XXX" the "SAN Foundation Software". and device name. Added the new behavior on "decode-unit" in second device path "fp" of "XXX" boot. (CR13541) 3. Added new feature which user can able to select the boot method between the "XXX" and "SCSI SD" boot using the command "set-XXX-on" to boot with FC and "set-XXX-off" to boot with standard SCSI SD. (CR13110) 2. Created new device path "fp". thus FCODE will not wait for the link up when the HBA is not connect to the FC Target during init time. Added support for the XXX-Branded adapter. changed "XXX" operation device type from "SCSI" to "SCSI-fcp". changed the new Program ID. Bug fixed on cannot configure fcode boot target "fabboot" using the target WWPN on Storage array.properties menu "Copyright (C) 2004 Emulex Design and Manufacturing Corporation. (CR14298) ----------------------. 2. and let the system continue to finish up the probe scan includes setting up the local SCSI device path. 3. such as changed the XXX-branded Program ID with "0xFC00" for LP10000-x. changed the new input method on "set-boot-id" when configuring for the " XXX" fabboot using WWPN and LUN number without the Target ID.NEW CHANGES 1.NEW CHANGES 1.". Bug fixed on stack overflow issue. and "0xFC10" for LP11000-x. Emulex-branded to "emlx" for "XXX" mode. (CR14488) 3.1. Changed the new copyright display in Fcode . and changed the child note from "sd" to "disk". This new fix will set the proper return for the "decode-unit" if the wwpn and lun number are unavailable. replaced XXX-branded device name property to "emlxs". . and "lpfc" for "sd" mode.50a1 -----------------------1.

Added the new feature to boot "XXX" FC target with WWPN instead of target ID. CD-ROM. (3) To make an entry selection in the pop-up menu.0 or greater (found on the released diskette. Then use the Down arrow key to select the "Download. To move the block cursor. (4) To obtain the pop-up menu for Update Flash menu.PRG file. user can set the boot target with "set-boot-id" command using either WWPN. you can use the Up/Down arrow key. Open Boot Firmware Update Procedure The Open Boot is loaded in the same way as a firmware update is performed and is distributed as a . The operation should . It could download through DOS based Lp6util if the adapter is first installed in a PC. With each highlighted item. This image file is downloaded into the xOxxxx's FLASH. press Alt key. 7. Changed the display format for the wwpn from "2200.0020. 5." (5) Hit Tab to move the cursor to the desired box to make the selection on the Drive. Created the new decode-unit. (6) Hit OK to start download. (2) Run LP6DUTIL revision 9. 6. remember to hit <Enter> to make that selection. Added the "portWWN" and "portID" of the FC target into the reg property at the boot time which was required by XXX to allow "XXX" to collect the target ID in OS.. encode-unit and decode the wwpn into two parts of wwpn-hi and wwpn-lo to meet the requirement of XXX. The same goes for the adapter selection. Changed to new device-name "emlx" for "XXX" instead of "lpfc".. 8. A brief Introduction message is displayed with a menu bar on top of the screen. DID or Alpa. Created the new devalias name "fabboot" for booting the "XXX" FC target using the "boot fabboot" command in OBP. the Directory. ======================================================================== 1. then move the block cursor to that entry then hit Enter or you can hit the corresponding highlighted letter. hold down the Alt key and hit the "l" letter key. Then procedure under DOS as follow: (1) Boot the DOS on PCI system.ffd2" to "2200002037a5ffd2" on show-children command which makes easier to set the boot device using "copy" and "paste" command.4. 9.37a5. the File of the image. or FTP server) All adapters in the system are detected and reset.

(4) Run "/usr/sbin/lpfc/convert_path_lpfc" to convert the path into "lpfc" (5) Reboot the system. To reset into default value mode: ok set-default-mode b. in order to download Fcode and boot from FC disk. To select the multiple adapters: ok show-devs /* show all system devices */ ok " /pci@1f. Changes will not be saved if a reset is not performed first. and it has been use under the device path name "fibre-channel" other than "lpfc" in Sun Solaris system. And it must boot Sun Solaris from the local disk. Note: Please be aware. NOTE: The update operation must not be interrupted or the FLASH may become corrupted. once the path has been converted into "lpfc". 2. now the Open Boot is ready to use. If this occurs. Open Boot Setup Procedure on "lpfc" Note: Always reset the system before making any changes to your Fcode Open Boot settings. the procedure as follow: (1) Boot up the Sun Solaris local disk. However Open Boot can also download through UNIX based under Sun Solaris lputil utility. a. Otherwise. (7) Remove the Adapter from PC system. the Adapter must be returned to Emulex for FLASH update.0/pci@1/lpfc@#" select-dev /* select /lpfc@# */ Note: Under the show-devs.take less than minute to complete. unpredictable damage might happen. (1) Option 3 Firmware Maintenance (2) Option 1 Load Firmware Image ******** Note ********* If the Open Boot has never been loaded into the FC adapter before. we will found the path end with lpfc@#. convert the path name into "lpfc" is required. (3) Run the lputil @ "/usr/sbin/lpfc/lputil" and download the Fcode flash. it can't go back to the original ("fibre-channel") path. (2) Download the latest lpfc driver. usually when no LEDs turn on. only if the adapter and the latest lpfc driver is first installed in Sun Solaris System. This condition can be identified by POST failure. . where the # will be the actual number of FC adapter.

To set the link speed: ok set-link-speed e. the topology is set to auto-FCAL.0/pci@1/lpfc@1" select-dev /* select lpfc@1 (for example) */ ok . To display the all SCSI and Fibre Channel devices: ok probe-scsi-all .focde ok unselect-dev d. If only one card and device connects to the switch. the auto-sensing mode will comes on as point-to-point first.0/pci@1/lpfc@1" select-dev set-fc-al unselect-dev reset-all if auto topology with public or private loop first ok ok ok ok " /pci@1f.0/pci@1/lpfc@1" select-dev /* select lpfc@1 (for example) */ ok . f.0/pci@1/lpfc@1" select-dev set-auto-fcal unselect-dev reset-all if auto topology with point-to-point first ok ok ok ok " /pci@1f. FC-AL.c.0/pci@1/lpfc@1" select-dev set-auto-ptp unselect-dev reset-all Note: By default. or auto mode: if point-to-point (for connect to the switch) ok ok ok ok " /pci@1f.0/pci@1/lpfc@1" select-dev set-ptp unselect-dev reset-all if public or private loop (for connect to the hub) ok ok ok ok " /pci@1f. To display the topology of the current device: ok show-devs ok " /pci@1f. To display open boot driver version: ok show-devs ok " /pci@1f.topology For intended (target) fibre channel boot disk select appropriate topology either point-to-point.

g.boot-id j. to change decimal type d# <lun> <target id> : default is in hex. to change decimal type d# <lun> <target id> : default is in hex. did or alpa returned from the probe and copy down the corresponding boot entry.7f70 d# 140 d# 10 set-boot-id To use did (public loop): ok " /pci@1f.0/pci@1/lpfc@1" select-dev /* select lpfc@1 (for example) */ ok . To display the all WWPNs and LUNs: ok show-children h. to change decimal type d# Example: e1 d# 100 d# 10 set-boot-id .0/pci@1/lpfc@1" select-dev ok alpa <alpa> <lun> <target id> set-boot-id ok unselect-dev <alpa> : must in hex <lun> : default is in hex. To set boot device id: Make note of the actual wwpn.0/pci@1/lpfc@1" select-dev ok did <did> <lun> <target id> set-boot-id ok unselect-dev <did> : must in hex <lun> : default is in hex.0020. to change decimal type d# Example: 2200.3799. to change decimal type d# <lun> <target id> : default is in hex. to change decimal type d# Example: 2009e1 d# 100 d# 10 set-boot-id To use alpa (private loop): ok " /pci@1f.0/pci@1/lpfc@1" select-dev ok wwpn <wwpn> <lun> <target id> set-boot-id ok unselect-dev <wwpn> : must in hex <lun> : default is in hex. To use wwpn ( point to point): ok " /pci@1f. To display the current boot device id: ok show-devs ok " /pci@1f. To display the desired WWPN and LUNs: ok 2200002037997f70 show-wwpn-child i.

It can also save in the environment variable boot-device. To display all the current flag for open boot driver: ok show-devs ok " /pci@1f.0/pci@1/lpfc@1" select-dev ok set-default-mode /* to clear boot id settings */ ok unselect-dev k. . To set the F-Code Diag Switch: ok set-fdiag-switch /* print debug message during POST */ /* switch to XXX Boot Format*/ /* switch to SD Boot Format*/ m.0/pci@1/lpfc@1" select-dev /* select lpfc@1 (for example) */ ok . To switch between XXX and SD Boot Format: ok set-XXX-boot ok set-sd-boot l.To remove boot id : ok " /pci@1f.nvram The following information will be display Signature Vaild_flag Host_did Enable_flag SFS_Support Topology_flag Link_Speed_flag Diag_Switch Boot_id Lnk_timer Plogi_timer LUN DID WWPN /* /* /* /* /* /* /* /* /* /* /* /* /* /* open boot signature */ internal flag for open boot */ shows host did number */ internal flag for open boot */ support SFS flag */ topology flag for open boot */ set link speed */ set fcode diag switch */ shows target id number */ internal use for open boot */ internal use for open boot */ shows Boot LUN in use */ shows Boot ID in use */ shows Boot WWPN in use */ Note: Target id can be bind to either did (destination id) or wwpn (worldwide port name) and saved in the adapter nvram.0/pci@1/lpfc@1" select-dev ok remove-boot-id /* to clear boot id settings */ ok unselect-dev OR ok " /pci@1f. wwpn <wwpn> <lun> <target-id> set-boot-id : binding target-id with wwpn and lun. did <did> <lun> <target-id> set-boot-id : binding target-id with did and lun.

(b) Select partition option and partition disk as desired. lun 0) though any may be selected. copy then unmount the usr file system: mount /dev/dsk/c1t1d0s6 /usr2 . * If necessary. After boot from local system disk Run format utility (enter 'format') (a) Select logical drive to become boot disk. target 1. newfs -v /dev/rdsk/c1t1d0s0 newfs -v /dev/rdsk/c1t1d0s6 newfs -v /dev/rdsk/c1t1d0s7 (will become root) (will become usr) (will become export/home) Create temporary mount points for the new partitions.for example): installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev /rdsk/c1t1d0s0 Create a filesystem for each partition which will contain a mounted Filesystem.3. so they can be mounted for copying. This procedure also requires that a 'local' boot disk be used to build the fibre channel boot disk. Make Fibre Channel Bootable System "SCSI SD" Disk Note: If fibre channel disk(s) is not found when system is up it may be necessary to do one of both of the following: (a) Enter the following "touch /reconfigure" and then reboot (b) Edit the /kernel/drv/lpfc. First 'kill' the volume manager Enter ps -ef|grep vold /* to obtain the process id (PID) */ Enter kill -9 PID /* where PID is obtained above */ Enter umount /dev/fd Mount.conf file on boot disk and change the topology from 4 to 2 or the reverse. The Following example will assume that the user has selected logical drive designated as "c1t1d0" (controller 1. This procedure may be used to make a bootable system disk from any size logical disk. view man page on format utility ("man format") Install boot on partition 0 of target disk with the following command (c1t1d0 . mkdir /root2 mkdir /usr2 mkdir /export2 For the /dev/fd must be unmount to copy the root file system. (c) select label option and write volume label to target disk.

cpr_config . Create the additional mount points (filesystem name) cd /root2 mkdir usr mkdir export mkdir proc Repeat for any other mount unique mount point which was excluded in the copy procedure. Add the tar command to the file list so that the result looks like this: tar cvf . swap.. b. usr2. vi.) If multiple targets exist on fibre channel adapter it will . to edit root_copy and delete the following entries: .cd /usr tar cvf . and any other apparent filesystem displayed by the 'df' command. Edit /root2/etc/vfstab to point to "new" boot disk as physical location of mount points for root. Then join file names so that they are on one line using <shift><j> in vi. proc. tar xf .* | ( cd /usr2. export.dtprofile TT_DB devices doit etc firmware fun opt platform sbin timer tmp var tar xf . tar xf .Xauthority arg bak bin cdrom dev kernel lib mnt mt net vol xfn | (cd /root2. To build a file list first cd / ls -a > root_copy use the editor.. usr. export2. To Perform copy mount /dev/dsk/c1t1d0s0 /root2 chmod 777 root_copy sh root_copy c.* | (cd /export2.dt .) umount /export2 Copying the root file system a. and etc. Change the current entries from /dev/dsk/c0t0d0s1 to /dev/dsk/c0t0d0s0 & /dev/rdsk/c0t0d0s0 to /dev/dsk/c0t0d0s6 & /dev/rdsk/c0t0d0s6 to /dev/dsk/c0t0d0s7 & /dev/rdsk/c0t0s0s7 to show show show show c1t1d0s1 c1t1d0s0 c1t1d0s6 c1t1d0s7 (swap) (root) (usr) (export) . . export.) umount /usr2 To copy the export/home file system: mount /dev/dsk/c1t1d0s7 /export2 cd /export tar cvf . usr.

(3) System hangs for a long time after displaying diver information or reboots just after displaying diver information. (2) After entering 'boot disk'. 5. Possible incorrect topology in /kernel/drv/lpfc. 4. Sec.nvram display display display display display display current current current current current current system devices version of open boot FC topology SCSI & FC device boot device id flags for open boot {See {See {See {See {See {See Sec. EFIBoot . Sec. Sec. Sec.conf file on target disk. There probably not boot on target disk. 2b} 2c} 2e} 2f} 2i} 2m} ******************************************************************************** *** IV.boot-id . show-devs . or copy from local to correct target was not successful.fcode . the message appears that file which was loaded is not executable. At the ok Prompt TYPE: boot disk The system now should boot on the fibre channel disk.be necessary to edit /root2/kernel/drv/lpfc. See instructions in lpfc. the vfstab on fibre channel boot disk not updated correctly persistent binding not implemented or implemented incorrectly.topology probe-scsi-all . Sec.conf to set up 'persistent binding' which will ensure that the desired logical disk is always assigned the correct target ID. Useful monitor commands When in the system monitor ("ok") prompt. Disk is now ready to use as boot disk Shutdown system Setup Sparc monitor and lpfc host adapter for boot if not done already.conf file to set persistent binding. Troubleshooting (1) During boot process cannot mount or fsck /usr.

(5) In order to display Linkup speed.10 and EFI Source Code version 1.14. User must use LP6dutil or some other OS Utility to enable the EFIBoot in order to make this card bootable. : Setup and Firmware update supported. use the latest version of the firmware. (2) EFIBoot Bios was enabled to configure the adapter and No Link: EFIBoot will wait for 15 seconds/adapter to confirm a link. EFIBoot will load only one driver. FC-AL: Private loop and Public loop. The EFIBoot supports: (1) Multi-Topology (2) EFI Protocols : Fabric Point to Point. EFIBoot will load the highest version of the EFIBoot driver. (5) Multi-Initiators : Up to 128 adapters in a system. : Up to 4096 LUNs : Supported. this adapter will not be configured. Diagnostics and Firmware Update Supported. (4) Multi-Device path : Fibre/SCSI Device path Selectable through the Driver configuration Protocol. /*------------------------------------------------------------------------------*/ /* History */ /*------------------------------------------------------------------------------*/ . This EFIBoot supports EFI Specification 1. (6) Multi-Boot (7) Multi-LUNs (8) Multi-Mode (9) Multi-Utility : Eight targets selectable through the Driver configuration Protocol. (3) Operating System : Windows Server 2003 and Red-Hat Linux Supported. Component Name. (3) If two or more adapters have same EFIBoot driver version.61. (4) If there are adapters with different EFIBoot driver versions. : Configuration.The current EFI (Extensible Firmware Interface) Boot provides 64-bit System boot capability through the use of the EFI Shell.10. ***** Important Note ****** (1) EFIBoot was not enabled from loading to system memory: If the adapter EFIBoot is not enabled from loading to system.

21A1: .00A0: ---------------------------------------------------------------------------------(1) CR 27764 Add improper FRU format CLP workaround to EFI boot driver (2) CR 27765 Add support for processing netport 1 CLP strings (3) CR 27766 EFI Boot driver must increment the CLP Instance variable (4) CR 27767 CLP processor should write all changed flash areas even if write errors encountered (5) CR 27768 Correct endianness issue in CLP high speed signaling paramter TLV record Problems Fixed Since 3.Native ia64 code compile (sal64) of EFI Boot code has exceeded 256KB in size (4) CR 24194 EFI Boot Code Flash Update needs a check for images greater than 2 56KB (5) CR 24240 Add 16 bytes as valid CDB length in passthru packet validation (6) CR 25367 update utility batch mode menu header needs to account for branded adapters (7) CR 25848 Algorithm for unload older versions doesn't account for distributi on type.21a4 can't flash f/w image into HBA when size is > 256KB.21A5: ---------------------------------------------------------------------------------(1) CR 17828 Add DMTF CLP support to EFI Boot (2) CR 27051 EFI 3.Problems Fixed Since 4.20a2 display wrong device capacity w/ 1. (8) CR 25851 Change over to Tianocore 1. (11) CR 26283 Integrated flash utility needs to use V3 EVPD program IDs (12) CR 25856 Add Saturn Support (13) CR 25766 Boot Path Not Found when attempting to boot HPUX from a VA7410 LUN Problems Fixed Since 3.6TB LU connected.21A2: ---------------------------------------------------------------------------------(1) CR25063 .02 EDK (9) CR 26277 Emulex diagnostic protocol producing unwanted debug output (10) CR 23591 EFI 3.21a4 Diagnostic Help screens contain some typos (4) CR 24416 EFI 3.21A4: ---------------------------------------------------------------------------------(1) CR 26807 EFI Bios 3. (3) CR 26627 EFI 3.21a4 does not execute EFI Diskpart Clean command correc tly (2) CR 26655 EFI 3.21a4 gets a corrupted menu screen after Boot Scan From EFIFC ScanLevel is selected.21A3: ---------------------------------------------------------------------------------(1) CR 23832 LUN Blocksize is not acquired from capacity buffer correctly in Ge tMediaInfo (2) CR 23872 Set Service Action in byte 1 of read capacity 16 CDB (3) CR 24193 EFI Boot Code Reduction .Remove debug output from 3.21a5 menu doesn't display the EFI version correctly (3) CR 27343 Add Saturn 8GB Forced Link Speed and display correct PCIe Lane wid th (max) Problems Fixed Since 3. Problems Fixed Since 3.21A2 Problems Fixed Since 3.

Problems Fixed Since 3. (10) CR24243 . Features added or Other Updates Since 3.EFI Driver does not see storage on heterogeneous SAN with OpenVMS nodes.20A3: ---------------------------------------------------------------------------------(1) CR23576 .Hang of over 1 hour while enumerating VSA LUNs behind a switch (11) CR24244 . (3) CR24628 .EFI Boot info utility does not display SLI3 firmware on fw info s creen Problems Fixed Since 3. (5) CR23580 .Add support for VA field = Mfg.21a0 is unable to start EFI utility on certain HBA families (8) CR24611 .Add support for V6 EVPD field to suppress Diagnostics protocol GU I (8) CR24241 .PRG files (5) CR24626 .21A0: ---------------------------------------------------------------------------------(1) CR24630 .20A1: ---------------------------------------------------------------------------------(1) CR 21025 Add configuration save/restore feature to EFI Boot config utility (2) CR 21757 EFI Utility 3.Back out CR24242 (2) CR25061 .Add field to PCI-E adapter info for max lane width (7) CR24092 .Discovery of VSA LUNs on customer RAID controller not consistent. Features added or Other Updates Since 3.LUN endianness in FC and SCSI device path node is incorrect (3) CR23578 .20a2 (4) CR23651 . Problems Fixed.Avoid using function keys in EFI Boot utility.20a0 Topology Section enhancements to be consistent with x86 Boot.EFI: Drop down to EFI shell.20A2: ---------------------------------------------------------------------------------(1) CR 22027 EFI internal error when configured storage is disconnected.Fix issue with display of SLI3 fw version in info utility (7) CR24277 .Bump LUN_CTRL attributes protocol version to 4 Problems Fixed.Incorrect Link Width shown in VPD screen (6) CR23581 . (3) CR 21947 Misleading user screen directions (4) CR 23236 Changed EFI_FC_DRIVER_IMAGE_UPDATE_PROTOCOL per HP SISL specifica tion .---------------------------------------------------------------------------------(1) CR20509 . Data Code.Implement LUN_ATTRS protocol version 3 (2) CR23577 .Default behavior should be BIOS Enabled (6) CR24625 . (9) CR24242 .Drive firmware update using customer utility appear to be failing (2) CR24629 . back to main menu => boot fails (4) CR24627 .EFI 3.Fixed reported issue with flashing SLI3.Change VPD protocol to return 2 bytes of ASCII data for VPD check sum field (12) CR24245 .Lun control attributes protocol v4 returns wrong value for Port I D (9) CR24362 .VPD data disappears after update to EFI 3.Auto delay discovery for FCAL topology with Lumens card if 1 alpa in loop map.

11a4 changes the name of the LP11000 to LP11002 Update copyright notices for display. Helios. Features added or Other Updates Since 3. (3) CR15646 Fiber channel EFI boot configuration utility assumes a specific orde r of VPD fields in NVRAM Problems Fixed. Features added or Other Updates Since 3. (4) (5) (6) (7) (8) (9) CR CR CR CR CR CR 17385 17386 17387 17388 20689 15965 Add batch mode to flash update utility.00A9 and 3.11a4: ---------------------------------------------------------------------------------(1) CR17989 Integrated flash utility does not support update of OEM branded LP11 002 and LPe11002 adapters (2) CR18025 EFI Boot utility not reading VPD on LP11002 w/ 2.11a5: ---------------------------------------------------------------------------------(1) CR 14400 EFI 3. (6) CR 22847 Convert Enhanced and Manufacturing diagnostics to return results in a buffer.Problems Fixed.20a0 will generate an "Unexpcted Trap" if the Enter key is pressed on an un-Highlighted HBA (4) CR 21980 Need Clarification on the Batch Mode Update of Firmware. (7) CR 21833 When using the key to exit DRVCFG -v command in EFI Utility 3. Features added or Other Updates Since 3. Thor and Pegasus display various results. Problems Fixed.20a 0 takes multiple attempts.20A0: ---------------------------------------------------------------------------------(1) CR 17383 HP-4GIG:EFI diagnostics utility required (2) CR 21284 EFI utility fails to clear screen on exit when invoked w/ drvcfg -v (3) CR 21755 EFI Utility 3. Features added or Other Updates Since 3.11a3: ---------------------------------------------------------------------------------- .11a5 (and earlier) loads multiple EFI driver versions concu 20725 17696 20859 20947 20963 17790 Driver does LUN discovery by inquiry on RAID controllers EFI 3. Enhance EFI_SCSI_PASS_THRU_PROTOCOL GetNextDevice() function Enhance driver configuration protocol Add EFI_DISK_IO protocol Add support for flashing SLI3 overlays Problem mixing 3.10a6 EFI Boot code during installatio n (10) CR rrently (11) CR (12) CR (13) CR (14) CR (15) CR (16) CR 18237 EFI 3. and in source.10A7 fw. Configuration util menu item misspelled. Speed up screen update in EFIBoot configuration utility Add support for OEM Branded 11002 adapters Problems Fixed. (5) CR 22127 EFI VPD protocol firware version fields too short for 2 digit rel ease counts.10a6 hangs if other initiators are discovered in ELX menu (2) CR 15989 Add support for >2TB LUN (3) CR 16956 Add feature to EFI boot and config utility for forcing link speed .

(CR-15 617) .11a1: ---------------------------------------------------------------------------------(1) More comprehensive solution for delay device discovery aka Lost LUN issue. (4) CR16166 Add boot image type lookup table entries for new adapters. (3) CR16165 Remove byte swap for Helios and Zephyr binaries. (2) CR17316 EFI Boot integrated flash utility unable to flash . Features added or Other Updates Since 3. Workaround now includes support for other devices on the loop with failing RAID contr oller.11a2: ---------------------------------------------------------------------------------(1) CR15762 Cannot install windows 2003 in a SAN environment. (CR15381) Problems Fixed. Features added or Other Updates Since 3. Features added or Other Updates Since 3.(1) CR17315 Integrated flash update utility unable to flash LP1150 paired boot f irmware image.all files for Hel ios adapters (3) CR17415 Change mailbox timeouts to 30 seconds (4) CR17082 Add PCI segment to information displayed by EFI Boot configuration u tility (5) CR16614 Fiber channel EFI boot configuration utility does not display PCI ex press bus speeds correctly (shows 33Mhz) (6) CR17422 add missing break in mailbox code (7) CR17457 Change EFI Boot config utility adapter name display from 11000DC to 11002 for Helieos and Zephyr dual channel Problems Fixed. Problems Fixed. (2) CR16164 Add generic boot code type string to EFI boot config utility. (CR-15383) (5) Improve instructions for setting max lun and discovery delay timer.11a0: ---------------------------------------------------------------------------------(1) Can't do flash update (CR-15527) (2) Can't display the complete eVPD V2 HBA name (CR-15552) (3) Increase RATOV timeout (CR-15572) (4) Generic trap occurs on some systems when internal or external loopback tes t is invoked.

and 3rd party branded PCI device IDs. (2) Implemented Bus Interface Unit test (PCI Loopback) Diagnostics functions. Zepyr. (5) Several configuration utility text changes. (3) Fixed problem with Hard-alpa Display string as per reqest.Problems Fixed. (2) Added internal and external loopback tests to the driver diagnostic protoc ol. (3) Changed VPD version to "3". (CR-13564) (2) Changed "-e" and -"m" drvdiag levels to "not supported". Problems Fixed. Features added or Other Updates Since 3. Features added or Other Updates Since 3. (6) Added discover delay timer to EFI configuration utility as workaround for Lost LUN issue seens with RAID controller that fails to add devices to ALPA map on the fi rst link reset.txt.10a4: ---------------------------------------------------------------------------------(1) Fixed problem with Child Display in Diagnostics functions. (CR-13725) Problems Fixed.10a5 did not support Arbitrary Loop. (3) Added support for Helios.10a3: ---------------------------------------------------------------------------------(1) Implemented Power-on self test Diagnostics function. Features added or Other Updates Since 3.10a5: ---------------------------------------------------------------------------------(1) Fixed problem where EFI 3. IE copyright notice. Features added or Other Updates Since 3. (4) Added support for displaying V1 and V3 VPD fields in configuration utility . (CR-13492) Problems Fixed.10a6: ---------------------------------------------------------------------------------(1) Added config utility menu item to delay device discovery by a user selecta ble number of seconds. Problems Fixed.10a2: ---------------------------------------------------------------------------------- . Features added or Other Updates Since 3. (4) Removed "SAL" documentation from readme.

(2) Implemented Scsipassthrough functions if the driver is called by an external utility that uses Scsipassthru functions.10. (4) Implemented the supported function of driver configuration Protocol check for the revision number of the driver before claiming support. (5) EFIBoot Driver can boot all targets or specific targets selected with the Setup Utility.10a0: ---------------------------------------------------------------------------------(1) Fixed problem setting the topology to point-to-point. Features added or Other Updates Since 3. on menu had no mapping). The No Boot selection is also available in the Setup Utili ty. Features added or Other Updates Since 3. (6) Fixed problem with rediscovering targets and doing read/write When the li nk went down after targets discovered and device path created. (CR-13112) Problems Fixed. Problems Fixed.(1) Implemented Diagnostics function. (3) Fixed problem with adding Scsi Error Commands properly. (CR-12860) (2) Fixed Problem setting Boot scan to Discovered Targets. The EFI driver wa s unable to create device path for non LUN-0 targets. then Port driver 2. (2) Fixed problem where the LUN scan sub-menu hangs EFI with a Clariion 4500 connected to McData ES3016 with an LP982.10a1: ---------------------------------------------------------------------------------(1) Fixed problem where unable to boot from Port Driver with non-zero LUN tar gets. (CR-13109) (3) Fixed problem that when Device # 02. Features added or Other Updates Since 3.14. (3) Rearranged setup utility options. . was selected on the boot device menu (Device #01.62.01a0: ---------------------------------------------------------------------------------(1) Added support for all SCSI Commands. EFI driver login to a hub and display targets. (7) Added support for EFI Source Code version 1. (CR-13150) Problems Fixed.22a8/W2K3 could find no hard disks during OS installation.

2. Features added or Other Updates Since 3. (2) Added VPD Protocol.Emulex SCSI Pass Thru Driver 2. (3) Controllers detected based on PCI Protocol. For example. (5) Boot Bios displayed with Universal/Pair/EFI Boot/ X86 Boot/Open Boot in Firmware Update Utility. (6) Added LunCtrlAttrs Protocol. Firmware. .1. 2. This version of EFIBoot is executed from Flash. This version can verify Configuration. When EFIBoot is loaded in EFI Shell. 82 00030110 B X X 1 1 Emulex SCSI Pass Thru Driver Elxcli301a0 Elxcli301a0 (A) EMULEX SCSI PASSTHRU DRIVER: This driver produces a SCSI Pass through handle for each Emulex Adapter. Controller and Targe t Information through "Drvcfg" shell command. Vpd. If the EFI driver version 3.00a9: ---------------------------------------------------------------------------------(1) Combined 3 EFI drivers to one. 5. (4) Boot Bios displayed with Enabled/Disabled Info in setup Utility.1 Procedure to Install Windows Server 2003 on a Fibre Channel Disk. 3. No Target attached. 5. Procedure to Install Operating System on a Fibre Channel Disk This is only for the system with floppy disk drive. General descriptions: 1.Problems Fixed.01a0 or above then 1. 2. With Targets attached. /*------------------------------------------------------------------------------*/ 1. This version can download Firmware through "Drvcfg" shell command and Firmware Update Protocol. 4. Type "Drivers" <enter> to see whether the driver is loaded. 82 00030110 D X X 1 . This version can run configuration utility through "Drvcfg" shell command.

etc.img.gz (2) Uncompress the Driver Disk image file if necessary. but the first drive will be available at installati on. 2." is displayed. Please follow the instructions in this section if you want to install RedHat Linux Advanced Server onto a Fibre Channel boot disk attached to Emulex LightPulse HBA. # unzip as21-ia64-6. This is applicable for all Hard disks (IDE. use the "map" command to list all devices a nd file systems that the system recognizes.gz (3) Insert a diskette into the diskette drive and copy the uncompressed Dri ver Disk image file to diskette. (1) Download the Driver Disk image file appropriate for your RedHat distribution.00c. Create a GPT Partition if the user has more than one drive mapped as a boo t device.(1) Boot with Windows Server 2003 Setup Media (See Microsoft Documentation For Details) (2) Monitor the white bar on the bottom of the screen. Make sure to select the correct installable drive as the first boot drive. or you have chosen to manually specify an adapter. 2. the user can select 8 boot devices through the configuration utility.img. Note: 1.Fibre. Make sure the user always uses the latest version of Emulex's Windows Server 2003 Port driver or Miniport driver.) 3.00c.SCSI.2 Procedure to Install Red Hat Linux on 64-bit system. For Port drivers. (4) When the message "Setup could not determine the type of one or more mass storage devices installed in your system. An example of this is: as21-ia64-6.00c. insert the Emulex driver diskette.. (3) Press [F6] within 5 seconds when the "Press F6 if you need to install a third party SCSI or RAID driver" message is displayed. Shell> map . # dd if=as21-ia64-6. (5) Follow the remaining instructions to complete the Windows Server 2003 installation. (5) At the EFI prompt "Shell>".img of=/dev/fd0 bs=1440k (4) Load Red Hat installation CD-ROM disc 1 in the target machine and boot into the EFI shell.

Load the EFIBoot through Command Line.PRG file. Shell> fs1: (8) Type "elilo Linux dd" to boot into the installation program. when you are prompted: Do you have a driver disk? (10) You will then be prompted: Insert your driver disk and press ok continue insert the driver disk and press ENTER User can then install RedHat following the standard installation direction f rom RedHat. Emulex Configuration Tool : Windows Port Driver. LP6DUTIL. 5. or later. 3. 4. Command Line : EFI based Systems.EXE er interface how to download EFIBoot in DOS PCI systems. note the entry corresponding to the CD-ROM containing Red Hat installation CD-ROM disc 1. 2. : Windows Miniport Driver. : DOS based utility. Please refer to section 5 for user interface how to download EFIBoot in EFI based systems. "Drvcfg" : EFI based Systems. 1. to (11) Red Hat will print a message indicating it is loading the lpfc driver. Please refer to the elxcfg user manual for details on using the above tool. 3. "load elxcli301a0. This file may be download ed to the Adapter using the firmware upgrade procedure with the following Utility i n Various systems. fs1> elilo Linux dd (9) Select YES. documentation for us Please refer to the utility user manual for details on using the above tool . An example of thi s is: fs1 (7) To change to "fs1:" file system type "fs1:" at the prompt. EFIBoot Load Procedure The Light Pulse EFIBoot is distributed as a . LPUTILNT . Please refer to the LP6DUTIL version 9.0a13.efi" <Enter>.(6) In the output of the "map" command.

Emulex driver Handle number is 82. If the card does not have EFI Driver 3. Make a no te of the handle number for use later. after entering.00a1 or above. 3. Type "Unload 82" <enter>. fs0:\Emulex> drvcfg Configurable Components Drv[28] Ctrl[41] Lang[eng] Drv[4A] Ctrl[18] Lang[eng] Drv[4A] Ctrl[19] Lang[eng] Drv[4A] Ctrl[20] Lang[eng] Drv[4A] Ctrl[21] Lang[eng] Drv[4D] Ctrl[22] Lang[eng] Drv[91] Ctrl[24] Lang[eng] Drv[91] Ctrl[25] Lang[eng] In this case 91 is the Driver handle and 24 and 25 are the controller hand les. 4. For example T D D Y C I R P F A V VERSION E G G #D #C DRIVER NAME IMAGE NAME == ======== = = = == == ================================ ============ 82 00030110 D X X 1 . Write down the Emulex driver handle. "drivers" <enter>. 1. Display will show the following. Type "drivers" <enter>. Determine Emulex EFI driver Handle by typing. elxcli.4. Emulex EFI driver can be run with the "drvcfg" EFI Shell command. EFIBoot Unload Procedure. 5. If the EFI driver version 3.efi). Get the latest version of Firmware. To find the Controllers supported by the Emulex EFI driver. Type "drvcfg " <enter>. 5. Load the driver through Command Line (load elxcli. To display drvcfg options: type "drvcfg -?" <enter>. . 2. based on board and type of firmware fi les in case if you want to update firmware.01a0 or above then a. Follow the steps. For example. Procedure to run the Configuration tool with EFI Drivers. Type "drvcfg -s 91 24" <enter> to set controller options. Display will show the following. please get the Comma nd Line driver. After seein g Shell Prompt. For the above case.Emulex SCSI Pass Thru Driver Elxcli301a0 b. 1. 6.efi. This will help how to use the various options. c.

3. 2. Configure Boot Parameters. used to configure HBA parameters. In order to update Firmware. 2. PLOGI Retry Timer .is used to Enable or Disable the EFIBoot discover targets. Boot Target Scan . In order to configure the Adapter user shell select "Setup Utility". In order to Configure HBA Parameters user shell select "Configure HBA Parameters".is used to path.. Configure Boot Devices . used to configure Boot Parameters. After successful download. the next screen will allow user to do the following.is used to select Port Login retry timer . This will display the screen with all Emulex adapters. After selecting "Configure HBA Parameters". Maximum Luns/Target . After selecting the Adapter. 3. 1. Procedure to run Configuration tool to verify Adapter information with EFI select Fibre or SCSI Boot Device Select Maximum Luns/Boot Target.is used to Note: The Configuration protocol supports the English language only. Setup Utility . the next screen will allow user to do the following. 1.. 7. If the file is root directory type "\" <enter>.is used to discovered 4. etc.. Configure HBA Parameters . Firmware Update .is 3. 8. Default ALPA of this adapter . the next screen will allow user to do the following. Enable or Disable BIOS .1.is to 2.is used to 3. Utility will post Success/Error message. 6. 1. Wait . After selecting "Configure Boot Parameters". a. 10.is used to select the Topology..is used to select hard Alap of this Adapter. Type "File Name" <enter>. and follow the step s.is 4. Type "File directory Name" <enter>.is used to configure the Adapter parameters. b. 2. Select Boot from NVRAM or all targets or No target. 1. used to set the default values. 3. reset the system after completing the "Drvcfg" utility in order to use the new firmware. Topology Selection . Select the adapter you want to modify. 2. Device Path Selection . 9. Reset to Default Values . . configure up to the 8 boot devices. Next screen will allow the user to select the functions defined. Bios.is used to flash the Firmware. select "Firmware Update". In order to Configure Boot Parameters user shell select "Configure Boot Parameters". After selecting "Setup utility".

6. 1. Determine Emulex EFI driver Handle by typing. To display drvcfg options: type "drvcfg -?" <enter>. Make a no Info . Connected targets Information Info . 1. Display will show the following. "drivers" <enter>. To display about usage. This will display the screen with all Emulex adapters. To find the Controllers supported by the Emulex EFI driver. Adapter Vpd Information. Type "drvdiag -?" <enter>. Type "drvcfg " <enter>. Controller Information. Select the adapter user wants to verify the information. 1. Emulex EFI driver can be run with the "drvcfg" EFI Shell command. For example. 5. 3. 5.Drivers. Determine Emulex EFI driver Handle by typing. fs0:\Emulex> drvcfg Configurable Components Drv[28] Ctrl[41] Lang[eng] Drv[4A] Ctrl[18] Lang[eng] Drv[4A] Ctrl[19] Lang[eng] Drv[4A] Ctrl[20] Lang[eng] Drv[4A] Ctrl[21] Lang[eng] Drv[4D] Ctrl[22] Lang[eng] Drv[91] Ctrl[24] Lang[eng] Drv[91] Ctrl[25] Lang[eng] In this case 91 is the Driver handle and 24 and 25 are the controller hand les. Follow the steps below. "drivers" <enter>. 3. Procedure to run the Diagnostics Protocol with EFI Driver. Slim for the Port Driver. Next screen will allow the user to select the functions defined. After selecting the Adapter. Make a no te of the handle number for use later. Type "drvcfg -v 91 24" <enter> to set controller options. 2. 2. Follow the steps. This will help how to use the various options. 2. After seeing Shell Prompt. Config ers. 1.is used to display the Connected targets Information Firmware Vpd Ctrl Device Info Info Info Info is is is is used used used used to to to to display display display display the the the the Adapter Firmware Information. After seein g Shell Prompt. 4. Emulex EFI driver can now run with "drvdiag" EFI Shell command. 2. 3. . 7. This will define how to use the various options.is used to display the Adapter Configuration paramet .

go to www.com. LP1150 and LPe111 Version:2. LP11002. Type "drvdiag -s 91 24" <enter> to run Standard Diagnostics. Type "drvdiag -e 91 24" <enter> to run Enhanced Diagnostics. 6. ******************************************************************************** ****************************************************** RELEASE NOTES FOR FIRMWARE VERSION 2. New Feature in Firmware Version 2.emulex. Type "drvdiag -m 91 24" <enter> to run Manufacturing Diagnostics. For example. LPe1104. For the latest product documentation. 4.82A3 Date: June 2009 Product: Emulex® LightPulse® adapters: LPe11000. Lang[eng] Lang[eng] Lang[eng] Lang[eng] In this case 91 is the Driver handle and 24 and 25 are the controller hand Note: The Diagnostics protocol supports the English language only. LP11000 . If you have an y questions or require additional information.te of the handle number for use later. Note: A loopback connecter on each fibre channel port is required for this test. LPe11002. 3.82a3 Added Host Pointer SLIM (HPS) bit support. Manufact uring diagnostics perform an external loopback test. . 5.82a3 Firmware This document describes the known issues associated with this firmware build rel ease. LPe1150. Display will show the following. contact an authorized Emulex Corp oration technical representative. Enahanced dia gnostics perform an internal loopback test. To know the Controller supported by Emulex EFI driver. Type "Drvdiag" <enter>. fs0:\Emulex> drvdiag -c Available Diagnostics Drv[4A] Ctrl[18] Lang[eng] Drv[4A] Ctrl[18] Child[55] Drv[4A] Ctrl[18] Child[56] Drv[4A] Ctrl[19] Lang[eng] Drv[4A] Ctrl[19] Child[57] Drv[4A] Ctrl[20] Lang[eng] Drv[4A] Ctrl[21] Lang[eng] Drv[4D] Ctrl[22] Lang[eng] Drv[4D] Ctrl[22] Child[58] Drv[91] Ctrl[24] Lang[eng] Drv[91] Ctrl[25] Lang[eng] les.

A ©2009 Emulex Corporation. including but not limited to the implied warranties of merchantab ility or fitness for a particular purpose. nor for any infringements of paten ts or other rights of third parties that may result. Convergenomics.82a3 There are no known issues at this time. All Rights Reserved. The N_Port_ID now is handled correctly in REG_VPI after a link down followed by a link up. Eliminated spurious firmware interrupts[JB4]. HBAnyware. No lic ense is granted by implication or otherwise under any patent. Copyright © 2009 Emulex. Emulex disclaims any undertaking to give notice of such changes. BlockGuard.82a3 1. LP1150. 2. Adapters now handle IERR and link down reset automatically. 4. 5. EZPilot. Resolved general NPIV issues. AutoPilot Manager. Emulex. Corrected RSCN processing. Correct link speed is negotiated when directly connected to a specific OEM a rray. InSpeed. copyright or relat ed rights of Emulex.. Enhanced handling of multiple split errors. 11. 7. All other brand or product names referenced herein are trademarks or registered trademark s of their respective companies or organizations. Emulex provides this manual as is without any warranty of any kind. LightPulse. However . or for any infringements o f patents or other rights of third parties which may result from its use. 3. Improved internal retransmission of an FCP command during FC-Tape recovery. Emulex Secure. Emulex. OneConnect. No part of this document m ay be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex. One Company. the Emulex logo. A word check now correctly verifies that the Abort Sequence frame (ABTS) is t he first frame of exchange. Improved reset handling. The LPe1150 adapter now correctly saves the max_payload_size value across a warm system reboot (PCIE reset). no responsibility is assumed by Emulex for its use. 9. Information furnished by Emulex is believed to be accurate and reliable. 8. AutoPilot Installer. CA 92626 Emulex Corporation Technical Support / Phone: 800-854-7112 or 714-885-3402 P004633-01A Rev. the correct VNPid is sav ed into the entry VPIO when the ELS_REQUEST64 cmd is used with CT= 0 and RPI = 0 . MultiPulse. although these changes will be incorporated into new editions of this manual. either express ed or implied. Con nectivity Continuum. For LP11000. and VEngine are trademarks of Emulex. 10. Periodic changes are made t o information contained herein. . SBOD. Fib reSpy.Resolved Issues Firmware Version 2. Emulex assumes no responsibility for its use. Emulex Connect. The firmware had previously retur ned trap code 0x40000005 caused by multiple split errors from the host bus. 3333 Susan Street Costa Mesa. SLI. One N etwork. All rights reserved worldwide. 12. LPe11000 and LPe1150 adapters. Known Issues Firmware Version 2. OneCommand. 6. Emulex may make improvements and chan ges to the product described in this manual at any time and without any notice.