File Name: Readme.txt This README file contains the latest information about installing IBM Netfinity Fibre Channel Host Bus Adapter Device Driver for Windows NT4. 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 The new IBM Netfinity Fibre Channel Host Bus Adapater has the following supported features: - Extended Lun support - Support FL port and Arbitrated Loop configurations - Dynamic LUN Masking support - Device scanning by port name - Support for Alki and limited diagnostics 1.2 Limitations The following are limitations/unsupported features of the IBM Netfinity Fibre Channel Host Bus Adapter: - Reduced Interrupt Operation 1.3 Enhancements N/A 1.4 Recommendations and Prerequisites It is required to have Microsoft Service Pack 5 (or greater) installed on the server. 1.5 Dependencies: TBD 2.0 Change History -------------------- 2.1 IBM Netfinity Fibre Channel Host Bus Adapter Version 7.04.04.02 03/30/00 - Includes RISC code 1.19.3 TP/IP (See Note 1) - Fix hot add issues - Fix Volume Set Addressing issue 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 Instructions for Installing Code for First Time To initially install the QLogic miniport driver on an installed Windows NT system, follow this procedure: 1. Click on "Start". 2. Under "Settings", click on "Control Panel". 3. Select "SCSI Adapters" from the Control Panel. 4. Select the "Drivers" tab and then click on "Add". 5. Click on "Have Disk". 6. Insert the IBM software diskette. 7. Enter "A:\NT" for the path to NT driver and click "OK". 8. Choose "IBM QLA2000/QLA2100 PCI Fibre Channel Adapter" and click "OK". 9. Select "Yes" to restart system. 3.2 Instructions for Updating Code If the miniport driver is already installed and you are installing an updated version of the driver, follow this procedure: 1. Open a DOS Command Prompt window. 2. Change the current directory to the Windows NT driver directory: CD "SystemRoot"\SYSTEM32\DRIVERS 3. Make a backup copy of the old driver: COPY QL2100.SYS QL2100.SAV 4. Insert the diskette with updated driver and copy it over the old driver: COPY A:\NT\QL2100.SYS 5. Shutdown and reboot the system to use the updated driver. 3.3 Instructions for Uninstalling Driver Follow the procedure below to uninstall the IBM QLA2100 driver from Windows NT: 1. Click on "Start". 2. Under "Settings", click on "Control Panel". 3. Select "SCSI Adapters" from the Control Panel. 4. Select the "Drivers" tab and select driver to remove. 5. Click on "Remove". 6. Select "Yes" to restart system. 4.0 Configuration Information ------------------------------- 4.1 General Notes 1. When using LUN masking, masking off LUN 0 for a target will cause Disk Administrator to report an offline device representing LUN 0. This is because LUN 0 must be reported to NT to allow NT to scan for the remaining LUNs on the target. The LUN masking code in the driver will allow this, but mask off all other access to LUN 0. NT will interpret this as LUN 0 being online for some period of time, then going offline. Disk Administrator will show this as a device that now reports "Configuration information not available". 2. Missing QLogic Device(s) in the SCSI Adapters Applet with Service Pack 5 Sometimes when you open up the SCSI Adapters Applet, the IBM device(s) information is not being displayed even though the device(s) and the associated device driver(s) are working properly. This is a known issue already reported to Microsoft. 3. 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 A SP6 hot fix is available to address this issue. 4. 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 NT includes enhanced scatter/gather list support for doing very large SCSI I/O transfers. Windows NT 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 QLogic 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 NT 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 QLogic 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. LargeLuns - Support for more than 8 LUNs To support more than 8 LUNs it is recommended that the Windows NT service pack 4 or higher be installed. the OEMSETUP.INF file has been changed to automatically update the registry to enable up to 255 LUNs using NT 4.0 Service Pack 4 or higher. This is done via the 'LargeLuns' parameter in the registry. NOTE: IMPORTANT! If the OS support for large luns is enabled, the miniport's extended LUN support MUST be disabled! To disable the miniport's entended LUN support, run the Host Adapter's embedded FastUtil and set the 'Luns per Target' parameter to 0. Should you wish to disable OS support for more than 8 luns, 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 "LargeLuns:REG_DWORD:0x01" D. Change the data value from 1 to 0 E. Exit the Registry Editor, then shutdown and reboot the system. 5. 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. 6. 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 UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. 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.