File Name: Readme.txt This README file contains the latest information about installing IBM Netfinity Fibre Channel Host Bus Adapter for Windows 2000. Refer to the IBM Support Website for the latest information and updated readme file (See Section 6.1 below). Last Update: 06/01/00 CONTENTS -------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview -------------- 1.1 Overview This release has been tested with Windows 2000 (x86) release. Earlier versions of Windows NT/Windows 2000 are not supported. The new IBM Netfinity Fibre Channel Host Bus Adapater has the following supported features: - Windows 2000 SCSI PnP interface - Extended Lun Support - Support FL port and Arbitrated Loop configurations - Dynamic LUN Masking support - Device tracking by port name (default) and node name 1.2 Limitations N/A 1.3 Enhancements N/A 1.4 Recommendations and Prerequisites It is required to have Windows 2000 (x86) or greater installed. 1.5 Dependencies: TBD 2.0 Change History -------------------- This is the first release of the IBM Netfinity Fibre Channel Host Bus Adapter Device Driver for Windows 2000. 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 Instructions for Installing Code for First Time IBM Netfinity QLA2100 HBAs are devices that are Plug and Play compatible to your computer. The step-by-step procedure to install a Plug and Play device is: 1. Install the device to the appropriate slot on your computer according to the device manufacturer’s instructions. 2. Restart or turn on your computer. 3. When your computer comes up, the built in driver with the name IBM Netfinity QLA2100, 64 bit PCI-Fibre Channel Adapter will be installed automatically. 4. Please follow the procedure described in the Update Driver section to upgrade the driver to the latest version. 3.2 Instructions for Updating Code 1. Start the Device Manager by clicking Start, pointing to Settings, clicking Control Panel, double clicking System applet, clicking Hardware tab, and clicking the Device Manager button. 2. Use scroll bar to scroll down the list of hardware types, double click the SCSI and RAID controller. 3. Select IBM Netfinity QLA2100, 64 bit PCI-Fibre Channel Adapter or IBM Netfinity QLA2000/2100 PCI Fibre Channel Adapter from the devices list and then click Properties. 4. Click the Driver tab, and then click Update Driver to start the Upgrade Device Driver Wizard. Click Next. 5. Select Display a list of the known drivers for the device so that I can choose a specific driver and click Next. 6. Insert the IBM Software Diskette into drive A: and click Have Disk. 7. On the Copy manfacturer's files from, type in A:\W2K and click OK. 8. Click Next on the Upgrade Device Driver Wizard/Select a Device Driver screen. 9. Click Next on the Upgrade Device Driver Wizard/Start Device Driver Installation screen. 10. When the Digital Signature Not found screen appears, select Yes. 11. Click Finish on the Upgrade Device Driver Wizard/Completing the Upgrade Device Driver Wizard. 12. You will be prompted the message: Your hardware settings have changed. You must restart your computer for these changes to take effect. Do you want to restart your computer now? Click Yes to restart the computer right away. NOTE: IBM is in the processing of obtaining a Digital Signature for the driver through the official WHQL process from Microsoft. Once a valid Digital Signature has been obtained and put in the CAT file, the Digital Signature Not found screen should not appear. If you are updating the driver with the one that does not have a valid Digital Signature, you still can update the driver successfully for the QLA2100 HBA that are currently installed on the system. However, every time you add a new QLA2100 HBA on to the system, Windows 2000 will automatically install the QL2100 driver that comes with the Windows 2000 CD when you boot up the system. This will result in having some QLA2100 HBAs running the updated driver and the newly added QLA2100 HBA running with the embedded driver. This might likely cause undesirable result depending on your system configuration. It is advised to update immediately the older version driver with the latest one that you have to ensure system integrity. This situation most likely will not happen once IBM obtains a valid Digital Signature for the QL2100 driver. IBM QLA2100, 64 bit PCI-Fibre Channel Adapter is the name of the driver that is on the Windows 2000 CD. The current name of this driver is now IBM QLA2000/2100 PCI Fibre Channel Adapter. If you have performed at least one upgrade on this driver, please select the current name for further upgrade. 3.3 Instructions for Uninstalling Driver To uninstall a Plug and Play device: Turn off your computer and remove the device from your computer according to the manufacturer’s instructions. NOTE: You do not normally have to use the Device Manager or the Hardware wizard to uninstall a Plug and Play device. After you have removed the device from your computer, and you have restarted your computer, Windows 2000 will recognize that it has been removed. 4.0 Configuration Information ------------------------------- 4.1 General Notes 1. Support for more than 8 LUNs Windows 2000 uses the ANSI-approved version field of the Inquiry data returned by the target device to determine whether it should support only 8 LUNs or 255 LUNs. If the field indicates that the target device complies to SCSI-3 standard, the operating system will enable more than 8 LUNs support. Else, it will support only 8 LUNs. 2. Missing LUNs if more than 64 LUNs are connected to the HBA with NT4.0 SP5 and SP6. When a system is configured with LARGE LUN Support, for example on a Fibre Channel HBA, some of the LUNs assigned to disks or other devices are not visible to other system drivers and as a result are not available to the system. Of 256 possible LUNs, only 231 LUNs are visible. The missing LUNs include the following ranges: 64 to 71 128 to 135 192 to 199 255 This is a known issue already reported to Microsoft and is reportedly being fixed in Windows 2000 RC3. 3. Notes on using the IBM Optimizing & Multipath driver to do failover on JBOD To allow the failover feature to work properly with JBOD configuration using the IBM Optimizing & Multipath driver, you need to enable device tracking by node name. This can be done by setting the Portname value of the DriverParameters registry to 0, as described in the below section. 4.2 Registry Paramters for Drivers 1. MaximumSGList Windows 2000 includes enhanced scatter/gather list support for doing very large SCSI I/O transfers. Windows 2000 supports up to 256 scatter/gather segments of 4096 bytes each, allowing transfers up to 1048576 bytes. NOTE: the OEMSETUP.INF file has been updated to automatically update the registry to support 65 scatter/gather segments. Normally, no additional changes will be necessary as this typically results in the best overall performance. If you wish to alter this value, please use the following procedure: A. Click on "Start", select "Run", and open the REGEDT32 program. B. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Ql2100 Parameters Device C. Double click on MaximumSGList:REG_DWORD:0x41 D. Enter a value from 16 to 255 (0x10 hex to 0xFF). A value of 255 (0xFF) enables the maximum 1 MByte transfer size. Setting a value higher than 255 results with the default of 64K transfers. The default value is 65 (0x41). E. Click OK. F. Exit the Registry Editor, then shutdown and reboot the system. 2. NumberOfRequests Windows 2000 supports the "NumberOfRequests" registry Parameter to specify the maximum number of outstanding requests per adapter. When the IBM driver is installed, the registry will be automatically updated with this parameter set to a value of 150 (0x96). WARNING: DO NOT increase this parameter above 150. Doing so can result in a system failure. 3. FabricSupported By default, the driver supports Fibre Channel fabric (switch). Should you wish to disable fabric support please use the following procedure: A. Click on "Start", select "Run", and open the REGEDT32 program. B. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Ql2100 Parameters Device C. Double click on DriverParameters:REG_SZ:FabricSupported=1; FabricDeviceCount=64;ConfigRequired=0 D. If the string "FabricSupported=" does not exist, append to end of string ;FabricSupported=1 E. If the string "FabricSupported=1" exists, change the value from 1 to 0. F. Click OK. G. Exit the Registry Editor, then shutdown and reboot the system. 4. Portname By default, the driver track devices by their port names. To configure the driver to track devices by node names, please use the following procedure: A. Click on "Start", select "Run", and open the REGEDT32 program. B. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Ql2100 Parameters Device C. Double click on DriverParameters:REG_SZ:FabricSupported=1; FabricDeviceCount=64;ConfigRequired=0 D. If the string "Portname=" does not exist, append to end of string ;Portname=0 E. If the string "Portname=1" exists, change the value from 1 to 0. F. Click OK. G. Exit the Registry Editor, then shutdown and reboot the system. 5. MSCS In SAN configuration, driver is required to handle RSCN efficiently to avoid disruption of I/O because of unnecessary re-logins. However, in Microsoft Cluster environment, it is necessary for the driver performs re-logins because the shared storage subsystems may be reseted by other initiators through a ResetBus operation. The driver parameter MSCS is designed to accommodate the conflicting needs on how to handle RSCN in both environments. It accepts three values: Value RSCN Handling Environment ----- ------------- ----------- 0 Upon receiving RSCN, performs logins SAN to devices only if necessary 1 Upon receiving RSCN, always performs Cluster logins 2 Upon receiving RSCN, attempts to SAN/Cluster detect whether the system is running in the Cluster environment during boot. If yes, always performs logins upon receiving RSCN. If not, performs logins only if necessary By default, the Oemsetup.inf file is set up to have MSCS set to 2. To change the driver to handle RSCN differently, please use the following procedure: A. Click on "Start", select "Run", and open the REGEDT32 program. B. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Ql2100 Parameters Device C. Double click on DriverParameters:REG_SZ:FabricSupported=1; FabricDeviceCount=64;ConfigRequired=0 D. If the string "MSCS=" does not exist, append to end of string ;MSCS=n where n = 0, 1, or 2. E. If the string "Portname=" exists, change the value to the desired value. F. Click OK. G. Exit the Registry Editor, then shutdown and reboot the system. 4.3 Hardware Status and Information 4.4 Unsupported Configurations 5.0 Unattended Mode --------------------- N/A 6.0 WEB Sites and Support Phone Number ---------------------------------------- 6.1 IBM Support Web Site: http://www.pc.ibm.com/support 6.2 IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity 6.3 If you have any questions about this update, or problem applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QLY.html. 7.0 Trademarks and Notices ---------------------------- 7.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM Netfinity Qlogic is a registerd trademark of Qlogic Corporation. Microsoft and Windows are trademarks or registered Trademarks of Microsoft Corporation. Other company, product, and service names may be trademarks or service marks of others. 8.0 Disclaimer ---------------- 8.1 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. 8.2 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.