FC HBA STOR Miniport Driver for Windows Release Notes February 19, 2008 This software license applies only to QLogic customers. QLogic Corporation. All rights reserved. Table of Contents 1. Version 2. Changes 3. Bug Fixes 4. Known Issues 5. History 6. Additional Information 7. Firmware (Embedded in Driver) 8. Trademarks 9. Notices 10. Contacting Support 1. Version These release notes describe the changes, fixes, known issues, and release details that apply to FC HBA STOR miniport driver, version 9.1.7.16. This driver package includes firmware versions 3.03.25 (2Gb HBAs), 4.03.01 (4Gb HBAs) and 4.03.01 (8Gb HBAs), as well as API version 1.28.0.57 (QLSDM). NOTE: Windows Server 2003 SP2 or later and KB932755/KB939315 (or later), or Windows Server 2003 SP1 and the KB932755/KB939315 (or later) update to the Microsoft Storport driver, are required. The Microsoft Storport update should be applied before installing or upgrading to this version of the miniport driver. For boot installation, Windows Server 2003 SP2 should be used and then followed by the KB update. 2. Changes The following changes have been made to the FC HBA STOR miniport driver between versions 9.1.7.15 and 9.1.7.16. Hardware Support None OS Support * Added support for the Windows Server 2008 operating system. Software/Driver None Industry Standards Compliance N/A 3. Bug Fixes The following fixes have been made to the FC HBA STOR miniport driver between versions 9.1.7.15 and 9.1.7.16. * Applied a fix to handle logout in the loop environment. 4. Known Issues None 5. History 9.1.7.15 QL - 10/30/07 * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_2432&SUBSYS_01081077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_015C1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_015D1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_015E1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_015F1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_0160107 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_01611077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_01621077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_01631077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_01641077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_3261103C (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_3262103C (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_3263103C (x86, IA64, x64) - PCI\VEN_1077&DEV_2532&SUBSYS_3264103C (x86, IA64, x64) NOTE: Microsoft requires x86 and x64 support for all HBAs. * Firmware versions: 3.03.25 (2Gb), 4.02.00 (4Gb). * API version: 1.28.0.50 (QLSDM). * Unique assignment of management server N-port handle values to be for each virtual port. * NPIV (N_Port ID Virtualization). * Target link speed (iiDMA). * PcieLinkCap/Stat to HbaDeviceChipProperty. * Flash layout regions for 4Gb and returned flash layout table from flash if it is valid. * Three Alternate Boot Devices and OOFR (out-of-order frame receive) * Removed QL2XHAI2: IHVs are required to use HBA API provided by Microsoft. * Preserved BIOS defaults when updating multi-boot image whose BIOS locations can be anywhere in the image. * Fixed checksum calculation in QLSDM when two-bios image is flashed. * Fixed ER50975: Initiator discovery problem caused a large burst of RSCN activity when the NetApp does its failover. A failed GPNID command occurring during ports discovery must not cause the termination of the discovery process. * Handled the case where the GNNFT command was failing due to incorrectly calculated the maximum data response length. * Setting the alternate WWN and enabling it in the NVRAM did not propagate through to the HBA. Reading the NVRAM and reinitializing the HBA will handle this case. 9.1.4.16 QL 3.03.21 4.00.26 - 02/02/07 * Adhered to Subsystem Id document v2.2m+. * Firmware versions: 3.03.21 (2Gb), 4.00.26 (4Gb). * API versions: 1.28.0.37 (QLSDM), 2.0.0.14 (QL2XHAI2). * Fixed ER50975: Initiator discovery problem caused a large burst of RSCN activity when the NetApp does its failover. A failed GPNID command occurring during ports discovery must not cause the termination of the discovery process. 9.1.4.15 QL 3.03.21 4.00.26 - 11/17/06 * Firmware versions: 3.03.21 (2Gb), 4.00.26 (4Gb). * API versions: 1.28.0.37 (QLSDM), 2.0.0.14 (QL2XHAI2). * Adhered to Subsystem Id document v2.2m+. NOTE: Microsoft requires both x86 and x64 support all HBAs. * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_2322&SUBSYS_01151077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2322&SUBSYS_01161077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2422&SUBSYS_1336103C (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_015B1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_5432&SUBSYS_01551077 (x86, x64) - PCI\VEN_1077&DEV_5432&SUBSYS_01561077 (x86, x64) - PCI\VEN_1077&DEV_2422&SUBSYS_014A1077 (IA64) - PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 (IA64) * Removed support for the following devices: - PCI\VEN_1077&DEV_6312&SUBSYS_01301077 (x86, x64) - PCI\VEN_1077&DEV_2422&SUBSYS_01471077 (IA64) - PCI\VEN_1077&DEV_2432&SUBSYS_01451077 (IA64) * Conformed QLSDM and the driver to the revised API for "Get/Set Target Link Speed". * Increased loop back test buffer size to 2048 bytes in QLSDM. * Closed ER49768: Loopback test always failed when the NVRAM frame size is set to 512 or 1024 (Windows). Pass in transfer size instead of hard coded value in QLSDM. * Handled the case where the device becomes not ready in the StartIO routine. * Closed ER48374: SANsurfer 5.0.0 Build 4 - Driver 9.1.3.10b2 - Windows IA64 SP1 - HP. The HBA model numbers do not show up on Information Tab. * Closed ER48117 (AR 48907, SR70415 [REF:609618455): Long Erase (0x019) issues with DLT S4 and QLE2462. Error occurs (most likely a bus reset) when running a long erase that takes longer than 110 minutes on the Quantum DLT-S4 (firmware:0808) drive, which exceeds the built in 4Gb firmware timeout limit. 9.1.3.16 QL 3.03.21 4.00.23 - 10/05/06 * This version replaces the invalid release 9.1.3.15. * Firmware versions: 3.03.21 (2Gb), 4.00.23 (4Gb). * API versions: 1.28.0.35 (QLSDM), 2.0.0.14 (QL2XHAI2). * Removed I/O Reduction support for the 4G HBA. 9.1.3.15 QL 3.03.21 4.00.23 - 09/19/06 * Firmware versions: 3.03.21 (2Gb), 4.00.23 (4Gb). * API versions: 1.28.0.35 (QLSDM), 2.0.0.14 (QL2XHAI2). * Added OEM specific support for assigning a Virtual World Wide Port Name via registry key. * Added "Get/Set" target link speed support. * Changed the INF to enable the I/O Reduction for the 4Gb HBA for the IA64 platform based on Microsoft document. * Added multiple BIOS support in QLSDM. * Initialize debug file name variable during DLL load (QL2XHAI2). * Closed EMC OPT23605: x64 Server hangs during boot at the 'Applying Computer Settings.' * Cleaned up code related to get Object text for OS Device Name (QL2XHAI2). * Closed ER47338: Attached target devices not visible to OS after server reboot (QLE220). * Closed ER47436: Driver not Login into Target Devices (QLE220). * Closed ER47530: Topology diagram is not displaying properly when LIP issued on QLA2462 port. 9.1.2.19 QL 3.03.19 4.00.23 - 06/30/06 * Firmware versions: 3.03.19 (2Gb), 4.00.23 (4Gb). * Closed ER46891: Bus Resets Under Heavy I/O Load. * API Versions: 1.28.0.33 (QLSDM), 2.0.0.12 (QL2XHAI2). * Closed ER47166: SANsurfer FC HBA Manager B83 showed only one port see the storage even though no zoning. * Closed OPT 235681: port failure after disconnecting and reconnecting ISL port used by Mirrorview. * Closed ER47235: SANsurfer FC HBA Manager does not display the topology view correctly when the HBAs are set to loop only until the system is rebooted. 9.1.2.18 QL 3.03.19 4.00.22 - 06/16/06 * Firmware versions: 3.03.19 (2Gb), 4.00.22 (4Gb). * API Versions: 1.28.0.33 (QLSDM), 2.0.0.12 (QL2XHAI2). * Added VPD update support for 2432 4-port adapter in 1.28.0.33 (QLSDM). * Recognized Asynchronous Event 8048h as a valid AEN. * Modified timer task to handle the case when HBA is in a stopped state. * 24xx only: Added support for NVRAM Nodename option bit. * 4Gb only: Added support for reading data from SFP (Small Form Factor Pluggable) optical transceivers via QLSDM. * Adhered to Subsystem Id document v2.2g. * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_2422&SUBSYS_014D1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_014C1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_01521077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_01531077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_01541077 (x86, IA64, x64) - PCI\VEN_1077&DEV_5432&SUBSYS_014E1077 (x86, x64) * Adhered to firmware dump procedure per 2400 Series Firmware Interface Specification version C. * Closed ER47113: RX2600 fails to boot Windows after 1MB bin flash - SANsurfer 2.0.30b84_windows. * Fixed: LUNs disappeared after DS4000 controller firmware download in direct attach. * Closed ER46586: "Bind By Port ID + Present Targets that are persistently bound only" is not working (in loop environment). * Changed to perform the full firmware dump when firmware error occurs. * Closed ER46141: JBOD disks turn offline in SANsurfer FC HBA Manager and SANsurfer FC HBA CLI when settings are Present targets that are persistently bound + Bind by Port id (in loop environment). * Corrected firmware region size in option ROM layout, i.e. firmware size in flash. * Closed ER45035: GPN_ID has wrong payload length after unplug/re-plug. * When using the QLSDM to retrieve the transceiver data, you may get SDMGT_CANNOT_GET_SFP_DATA error on system platforms using certain models of Supermicro Motherboard such as P3TDL3 and P3TDLE. The QLSDM retrieves the transceiver data using underlying 4Gb firmware (v4.00.21) that reports an error code of 4005 for this operation. * Verified support for Atmel flash chip AT26DF081A. 9.1.2.16 QL 3.03.19 4.00.18 - 03/16/06 * Firmware versions: 3.03.19 (2Gb), 4.00.18 (4Gb). * Adhered to Subsystem Id document v2.2f. * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_6312&SUBSYS_01191077 (x86, x64) - PCI\VEN_1077&DEV_6312&SUBSYS_011C1077 (x86, x64) - PCI\VEN_1077&DEV_6312&SUBSYS_01301077 (x86, x64) - PCI\VEN_1077&DEV_6322&SUBSYS_012F1077 (x86, x64) * Set additional firmware option bit 10 for 2Gb HBA so the firmware waits for the task management command, (such as reset LUN to complete.) * Closed OPT226506: HBA does not re-login to target after target sends LOGO to HBA. * Closed ER44735: The link status behave differently between QLE-2460 and QLA2342. * Closed ER45228: Incorrect HwVersion string is reported by QLogic IHV HBA_GetAdapterAttributes call. * Closed ER45230: Event Id 11 entries logged by ql2300 at offset x10 and offset x34 do not match the Error Codes published on the web. Since the Miniport uses the Microsoft's Storport.sys driver to actually log the error event, and it has been confirmed that the storport.sys driver logs the event incorrectly. A bug has been reported to Microsoft on this: SRX041110604850 (STORport - Incorrect event data is logged when storport's storportlogerror). Meanwhile, the Miniport driver is changed to log the event code at offset x10 by default. This workaround is controlled by the registry parameter "mevtwrkaround". Please see readme file for detail on this parameter. * Closed ER45232: Use memory map mechanism in the driver. 9.1.2.15 QL 3.03.19 4.00.17 - 02/13/06 * Firmware versions: 3.03.19 (2Gb), 4.00.17 (4Gb). * Adhered to Subsystem Id document v2.2e * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_5432&SUBSYS_013E1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_5432&SUBSYS_013F1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2422&SUBSYS_014A1077 (x86, IA64, x64) - PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 (x86, IA64, x64) * Added support to use combined 2Gb IPX firmware. * Added support for SST25VF080B flash part. * Added option for not to dump code section for 24xx firmware dump. * Closed ER44270: Serial number for the 4Gb HBA should be obtained from the VPD. * Closed ER38787: Windows 2000/qla2340/veritas tape backup long cable pull failed error message ERROR_DEVICE_NOT_CONNECTED. 9.1.1.15 QL 3.03.18 4.00.12 - 10/12/05 * Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb). * Closed PTR 90818: QLogic 4Gb driver returns selection timeout immediately after cable pull in an OEM special dual loop configuration. * Closed PTR 90652: QLogic Driver returns a selection timeout when rebooting a controller in an OEM special dual loop configuration. 9.1.0.18 QL 3.03.18 4.00.12 - 10/11/05 * Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb). * Adhered to Subsystem Id document v2.2d. * Added support for the following devices (supported platforms): - PCI\VEN_1077&DEV_2422&SUBSYS_12D7103C (x86, IA64, x64) - PCI\VEN_1077&DEV_2312&SUBSYS_01491077 (x86, IA64, x64) 9.1.0.17 QL 3.03.18 4.00.12 - 09/21/05 * Firmware versions: 3.03.18 (2Gb), 4.00.12 (4Gb). 9.1.0.16 QL 3.03.16 4.00.12 - 08/29/05 * Firmware versions: 3.03.16 (2Gb), 4.00.12 (4Gb). * Embedded 24xx firmware in the driver. * Closed ER43175: New driver could not detect any device to install as BOOT from SAN on one specific setup. 9.1.0.15 QL 3.03.16 - 08/10/05 * Firmware versions: 3.03.16 (2Gb), (Use onboard 4Gb firmware.) * Added 24xx support. * Closed ER42601: Need to change bit used to control LED mode. 9.0.2.17 QL 3.03.13 - 04/07/05 * Firmware versions: 3.03.16 (2Gb). 6. Additional Information None 7. Firmware (Embedded in Driver) See the HTML version of these release notes for changes and fixes made to the firmware embedded in this driver package. 8. Trademarks QLogic, the QLogic logo, QLA, SANbox, SANsurfer, and SANblade are registered trademarks of QLogic Corporation. SANtrack and SAN Express are trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. 9. Notices Information furnished in this document is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are only for illustrative purposes. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document. 10. Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: North America Contact Information Email: support@qlogic.com Phone: (952) 932-4040 Web: http://support.qlogic.com Support contact information for other regions of the world is available at the QLogic website: http://support.qlogic.com (c) Copyright 2008. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.