This README file contains the latest information about installing the IBM FAStT FC-2 and FC2-133 Host Bus Adapter (HBA) Device Driver version 8.2.3.66 on a Windows Server 2003 platform. (Microsoft certified) Refer to the IBM Support Web site or CD for the IBM FAStT FC-2 and FC2-133 Host Bus Adapter Installation and User's guide, the latest information, and updated readme file. Products supported: ----------------------------------------------------------------------------- | FAStT Adapter | Qlogic Adapter | IBM Feature Code | IBM Option P/N | ------------------------------------------------------------------------------ |FAStT FC2 | QLA2310FL-IBM-SP | FC2130 | 19K1246 | |FAStT FC2-133 | QLA2340-IBM-SP | FC2104 | 24P0960 | ----------------------------------------------------------------------------- Last Update: 03/11/2004 ======================================================================= 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 IBM FAStT FC-2 and FC2-133 Host Adapter Device Driver overview ------------------------------------------------------ The IBM FAStT FC-2 and FC2-133 Host Adapter Device Driver supports Fibre Channel point-to-point, F-port, FL-port, N-port, and Arbitrated Loop configurations. In addition, it also has the following features: - Support for Enhanced loop ID support (251 Loop IDs) in F port configuration - Support for Full-duplex operation in loop configuration - Support for Extended LUN - Support for Scan attached target device by port name - Support for Dynamic LUN Masking - Support for diagnostic loop back test - Support for QLogic Internet Protocol (IP) driver - Support for Fibre Channel Tape - Support for Reduced Interrupt Operation - Windows Server 2003/XP/2000 SCSI miniport PnP interface There are two Microsoft Windows driver files. The one that has "W32" string in the file name is for Windows 2000 and 32-bit versions of Windows Server 2003. The one that has "W64" string in the file name is for 64-bit versions of Windows Server 2003 only. ======================================================================= 1.2 Limitations --------------- N/A 1.3 Enhancements ---------------- This release of driver works with all 64-bit versions of Windows Server 2003. This driver will also install in Windows XP 64-bit. However, it is not tested by IBM nor certified by Microsoft in Windows 64-bit XP environment. The 32-bit versions of Windows Server 2003 driver is available in a separate HBA driver package. ======================================================================= 1.4 Prerequisites for the update --------------------------------- You can not update the adapter BIOS by booting to a DOS diskette in a IA-64 server like you would in an IA-32 server. In addition, the adapter BIOS file is referrred to as "EFI BIOS" in an IA-64 server environment. The adapter with IA-32 BIOS will function in a IA-64 server. However, you will not be able to modify the NVSRAM settings or to configure the adapter for "root boot" or "remote boot". You have to install the appropriate "EFI BIOS" file for your adapter to enable those functions. Note: Please refer to the readme files in the IA-64 EFI BIOS package for instructions to install the EFI BIOS in the adapter and to display/modify the adapter NVSRAM settings in the EFI shell. ======================================================================= 2.0 Change History ------------------ Version 8.2.3.66 03/11/04 * Risc Code v3.2.24 - Ensure that a single corrupted LISM frame does not result in LIP timeout. - Corrected problem, introduced by ER34071 in V3.02.22, that caused task management commands to be sent out with an invalid LUN value. This applies only to firmware builds that use FC-TAPE. - Ensure Immediate Notify IOCB contains correct OXID value when the Status code indicates Abort Task (20h)in Target Mode only - Multi-Id Only. Corrected LOGO handling when LOGO’s for several different ID’s are received in quick succession. - Corrected problem where timeout of task management commands could result in a corrupted firmware pointer, which could have unpredictable side effects. [ER34071] - Corrected SRR handling when ISP is operating in target mode and initiator supports Task Retry Id. - Modified firmware to work around an ISP2312 issue with PCI-X memory writes when these memory writes are intermixed with partial split completions for PCI-X memory reads. - Corrected problem where IOCB buffers were not getting properly de-allocated - Multi-Id Only. Corrected loop hang condition that could occur when operating in target mode - Corrected problem that could result in mailbox commands timing out when ISP is configured in Connection Mode 1 (Loop only) and connected to a switch configured as F-Port - Fix Diagnostic Echo Test (0044h) mailbox command timing out if the ECHO ACC frame had a CRC error. - Firmware has been modified to clearly indicate unrecoverable ISP hardware errors. A System Error (8002h) asynchronous event with Mailbox 0 register having a value of 8002h and Mailbox 1 register having a value of 0000h indicates an unrecoverable hardware error.Note: The driver should not use the ISP that reports an unrecoverable hardware error. - Add Host Memory Copy command - Fix problem that could result in mailbox command timing out when ISP is connected in certain "QuickLoop" configurations Version 8.2.3.63 12/18/03 * Fix problems in txtsetup.oem file. Version 8.2.3.61 08/15/03 * Modify inf file to automatically add buschange=0 * Fix problems that cause FAStT controllers to hang during failover tests. Version 8.2.2.61 06/17/03 * Add support for swing and emphasis control based on NVRam settings * Fix too many Registered State Change Notifications (RSCNs) * Fix high I/O hang with RSCN & LS_RJT * Fix Brocade name server not reporting Qlogic Symbol name * Fix device getting offline prior to port down retry count expires * Fix issue where HBA does not log back in * Continue the discovery process if register FC4 features fails * Disable ResetDetected notification to OS * Fix ACU displays error message 15007 after saving configuration * RISC code 3.1.19 TP/VI * Fixes related to the initiator driver: - SANMark SCD-2003 issues 1. 3.1.5 L_BIT_SET: FW not terminating outstanding GNNFT after LIP 2. 3.1.5 L_BIT_SET: GNNFT does not work after LIP reset 3. 3.1.4 TX_RFF_ID_POWER_ON: Add support for RFF_ID in SNS interface * Fix incorrect status when server cable is unplugged, should return DEGRADED/FAILURE instead of INITIALIZING * Fix driver does not install Pseudo driver during OS install (copy error) * Fix driver fails W2K SP3 OS install to boot device * Fix could not perform fresh OS install with .Net build 3716 (hang) * Close Link Down Timeout issue * Fix SANMark SCD-2003 issues on the driver side: 1. 3.2.1: Only perform RFT_ID after link down and up 2. 3.1.4: Use SNS interface to send RFF_ID * Back out .NET HCT 11.0 Untagged command handling to ensure w2k compatibility * Merge in NextRequests changes in ResetBus for specific OEM * Set TotalSenseDataBytes to 0xFF in INF * Handle the re-discovering the Initiator devices in Fabric * Renamed qlcspeudo.txt to qlcspeudo.inf * Change option "UseSameNN=0" in DriverParameters. * SANmark test related fixes. Version 8.1.5.62 11/20/02 * Includes RISC code 3.1.17 TP/IP * Call nextlu for tagged I/O and nextrequest for untagged I/O * Do not notify reset detected for a RSCN * Numerous FC_TAPE related issues fixed * Close HBA unplug/plug login to tape device issue Version 8.1.5.60 06/13/02 * NT40 & Win2k IP driver failed to ping each system if QLDirect is embedded. * win2k/ 2340 install the driver to 2nd HBA, system BSOD * For W2K/XP, add check for subsystem Ids for 2350/2352 HBAs * Includes RISC code 3.1.10 TP/IP * Address the issue when a target logs out the hba during RSCN processing caused by unplugging the HBA cable * Correct problem where the f/w could establish a link at the wrong speed (1Gb/2Gb) during cable unplug. * Fix HCT scsi verifier failure with untagged request * Firmware fix for the RNID issue with unplug/plug cable * Add support for subvendor 0x0E11 & 0x1028 * GAZS fails using ztest with > 2k buffer size * Add support for subsystem id x1028 and subvendor id x011A/x013B/0x13C * Install the api library during driver installation * Work around for Scsi verifier < 5 sec * Include 3 changes to 'harden' the driver 1. Shoot the adapter if firmware reload fails earlier 2. Ensure NextRequest is called after ResetBus() 3. Use tag * Add initial support for Rubah spec * Fix a bug in HCT driver verifier test failure code * Added CT pass thru related changes Version 8.1.4.60 02/22/02 * Includes RISC code 3.0.34 TP/IP * For W2K/XP, add check for subsystem Ids for 2340/2342/2344 HBAs * Fix the memory dump related to exceeding limit * Use non-device extension area to save target information * Fix map database issue with trivial fabric * Address the incorrect WWN issue * Reduce the failover timeout * Do want wait for the complete initialization timeout period if no cable is detected for 10 sec during boot * Work around for unsafe removal of devices * Fix serial number display in atf_paths ======================================================================= 3.0 Installation and Setup Instructions --------------------------------------- This section is divided into the following five sections. 3.1 Initial OS installation with the IBM FAStT FC-2 or FC2-133 HBAs as Boot 3.2 Adding the IBM FAStT FC-2 or FC2-133 Host Adapter to the Existing OS 3.3 Updating the existing IBM FAStT FC-2 or FC2-133 HBA Driver 3.4 Removing the IBM FAStT FC-2 or FC2-133 HBA Driver ======================================================================= 3.1. Initial Windows Server 2003 installation with the IBM FAStT FC-2 Host Bus Adapter as Boot. ------------------------------------------------------------------- Contact IBM Support for supported configurations and instructions for configuring the IBM FAStT FC-2 Host Adapter as the boot device. ======================================================================= 3.2 Adding the IBM FAStT FC-2 Host Adapter Driver to an Existing Windows Server 2003 System. ----------------------------------------------------------------------- Perform the following steps to add the driver to the existing Windows Server 2003 system. The IBM FAStT FC-2 and FC2-133 Host Bus Adapter is Plug and Play compatible to your computer. The step-by-step procedure to install a Plug-and-Play device is: 1. Install the adapter in the appropriate slot on your computer according to the server options installation instructions. 2. Restart or turn on your computer. 3. Windows Server 2003 will detect the newly installed device by displaying the Found New Hardware with SCSI controller message. The Found New Hardware wizard program will start and begin the device driver installation for the newly installed adapter. 4. Select Install from a List or specific location (Advanced). Click Next. 5. Insert the IBM Device Diskette or CD-ROM into floppy or CD-ROM drive, if applicable. 6. Select Search removable media (floppy, CD-ROM) and/or specify a directory to search for the best suitable driver. Click Next to start installing the driver. 7. Click Finish on the Completing the driver updating Wizard window to close the Wizard. 8. You may be prompted with the following 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? If this is the only adapter in the server, click Yes to restart the computer right away. Otherwise, repeat the process for the other newly added HBAs. Notes: If the driver has already been installed once, and you are adding an additional HBA onto the system, when the system comes up, it will detect the device correctly by displaying the Found New Hardware with QLogic QLA23xx PCI Fibre Channel Adapter message. ======================================================================= 3.3 Updating the Existing IBM FAStT FC-2 or FC2-133 Host Adapter Driver ----------------------------------------------------------------------- To update the IBM FAStT FC-2 or FC2-133 HBAs miniport driver on an installed Windows Server 2003 system, follow this procedure: 1. Open the Computer management window by clicking Start -> Administrative Tools -> Computer management. 2. When the Computer Management window opens, select Device Manager icon under System Tools. 2. On the right window pane, use the scroll bar to scroll down the list of hardware types, double click on the SCSI and RAID controllers to display the list of configured SCSI and RAID controller devices. 3. Right-click the QLogic QLA23xx PCI Fibre Channel Adapter from the displayed device list and select Update Driver from the pull-down menu. The hardware Update Wizard window opens. 4. Select Install from a List or specific location (Advanced). Click Next. 5. Insert the IBM Device Diskette or CD-ROM into floppy or CD-ROM drive, if applicable. 6. Select Search removable media (floppy, CD-ROM) and/or specify a directory to search for the best suitable driver. Click Next to start installing the driver. 7. Click Finish on the Completing the driver updating Wizard window to close the Wizard. 8. You may be prompted with the following 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? If this is the only adapter in the server, click Yes to restart the computer right away. Otherwise, repeat the process for the other newly added HBAs. Note: If you are installing the IBM FAStT FC-2 or FC2-133 HBA in a server that previously had a Qlogic QLA23xx Adapter, you will need to use the Updating the IBM FAStT FC-2 FC2-133 HBA procedure to ensure that the correct device driver ql2300.sys is loaded for the IBM FAStT FC-2 or FC2-133 Host Bus Adapters. ======================================================================= 3.4 Removing the IBM FC-2 or FC2-133 Host Bus Adapter Driver ----------------------------------------------------------------------- You can not remove the IBM FC-2 or FC2-133 Host Bus Adapter Driver once it is installed in an Windows Server 2003 server. You can either disabling or removing the HBA from the server if you do not have any more needs for the IBM FC-2 or FC2-133 Host Bus Adapter. To remove an HBA: Turn off your computer and remove the device from your computer according to the manufacturers instructions. At a later time, if you reinstall the same type of HBA in the server, it will be automatically recognized and installed with the saved driver. Note: It is best practice to use the Add/Remove hardware function to remove/uninstall the HBA(s) before you remove it from the server. ======================================================================= 4.0 Configuration Information ----------------------------- The configurable driver parameters are divided into System Registry Parameters and NVRAM Parameters sections. ======================================================================= 4.1 NVRAM Parameters --------------------- The default adapter NVRAM settings is optimized for Windows Server 2003 environments. However, modifications to the NVRAM settings many be required depending on a given server configuration. You can configure the adapter NVRAM settings using the Fast!UTIL utility. To access Fast!UTIL utility, press Ctrl+Q during host BIOS initialization. Refer to the IBM FAStT FC-2 Host Adapter Installation and User's Guide or IBM FAStT FC2-133 Host Adapter Installation and User's Guide for additional information on adapter NVRAM settings. 4.1.1 Hard Loop ID ------------------ It is recommended that you set different Hard Loop IDs for each IBM FAStT FC-2 or FC2-133 HBA port in a single Host or in each Node in a cluster. For example, in Host Adapter Settings, set the Hard Loop ID to 125 for the first host in a cluster and set the Hard Loop ID to 124 for the other host in the cluster. If you do not assign different Hard Loop IDs, the Fibre Channel protocol will automatically assign soft-loop IDs when their is a hard-loop ID conflict. 4.1.2 Port Down Retry Count --------------------------- From the Advanced Adapter Settings, change the Port Down Retry Count to 70 (if you have more than 5 devices on the fibre channel loop attached to the IBM FAStT FC-2 Host Adapter). Fibre Channel Host Adapters and Storage Subsystems are counted as fiber channel devices. You can configure the adapter using the Fast!UTIL utility. 4.1.3 Data Rate --------------- This setting determines the data rate. The default setting is 2, which allows the Host Adapter port to negotiate for the best connection speed. In certain cases, the adapter data rate must be locked at either 1Gbps or 2Gbps. Use the FAST!Util utility to change this setting in the Extended Firmware Setting window. ======================================================================= 4.2 System Registry Parameters ------------------------------ WARNING: - Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk. - Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedt32.exe. Below is a description of the registry parameters used by the driver: 4.2.1 MaximumSGList ------------------- Windows Server 2003/2000 includes an 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 results in the best overall performance. If you want to change this value, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: MaximumSGList:REG_DWORD:0x21 4. 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 33 (0x21). 5. Click OK. 6. Exit the Registry Editor, then shutdown and reboot the system. 4.2.2 Number Of Requests ------------------------ Windows Server 2003/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). CAUTION: DO NOT increase this parameter above 150. Doing so can result in a system failure. 4.2.3 Fabric Supported ---------------------- By default, the driver supports Fibre Channel fabric (switch). Should you wish to disable fabric support please use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:MSCS=2;UseSameNN=1 4. If the string FabricSupported= does not exist, append to end of string; FabricSupported=0 5. If the string FabricSupported=1 exists, change the value from 1 to 0. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.4 Portname --------------- By default, the driver track devices by their port names. To configure the driver to track devices by node names, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: KEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet ->Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:MSCS=2;UseSameNN=1 4. If the string Portname= does not exist, append to end of string; Portname=0 5. If the string Portname=1 exists, change the value from 1 to 0. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.5 Fibre Channel Tape ------------------------ To configure the driver to support Fibre Channel tape, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:MSCS=2;UseSameNN=1 4. If the string FCTape= does not exist, append to end of string; FCTape=1 5. If the string FCTape=0 exists, change the value from 0 to 1. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.6 MSCS ---------- In SAN configuration, the 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 reset 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 to SAN devices only if necessary 1 Upon receiving RSCN, always performs logins Cluster 2 Upon receiving RSCN, attempts to detect whether the system is running in the Cluster SAN/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, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:MSCS=2;UseSameNN=1 4. If the string MSCS= does not exist, append to end of string; MSCS=n where n = 0, 1, or 2. 5. If the string MSCS= exists, change the value to the desired value. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.7 UseSameNN --------------- By default, if you have multiple Fibre Channel HBAs on the same system, the driver will assign the world wide node name obtained from the first HBA to the rest of the HBAs. If you wish to have each HBAs to assume the world wide node name based on its own NVRAM content, you need to disable this feature by setting the UseSameNN parameter to 0. Please use the following procedure to change the UseSameNN parameter: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:MSCS=2;UseSameNN=1 4. If the string UseSameNN= does not exist, append to end of string; UseSameNN=0 5. If the string UseSameNN=1 exists, change the value from 1 to 0. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.8 Buschange --------------- To ensure proper operation when the HBA is used in a FAStT Storage Server environment, the buschange parameter must be set to 0. The default setting of the buschange parameter when it is not specified is 2. To set buschange parameter to 0, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the IBM driver as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Ql2300 -> Parameters -> Device 3. Double-click: DriverParameters:REG_SZ:UseSameNN=1 4. If the string buschange= does not exist, append to end of string; buschange=0 5. If the string buschange= exists, change the value to the desired value. 6. Click OK. 7. Exit the Registry Editor, then shutdown and reboot the system. 4.2.9 Disk TimeOutValue ---------------------- To ensure the driver function properly, the driver sets the system related registry - Disk TimeOutValue - to 60. When installing clustering service, the cluster install wizard changes this value to 20. You must change this value back to 60(0x3c) to ensure proper operation of the HBA when connecting to FAStT storage servers. To modify this registry value, use the following procedure: 1. Click Start -> Run. When the Run window opens, enter REGEDT32 and click open to start the Windows Server 2003 registry modification program. 2. Select HKEY_LOCAL_MACHINE and follow the tree structure down to the Disk TimeOutValue as follows: HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Disk 3. Double-click: TimeOutValue:REG_DWORD:0x3c 4. If the value is not 60 (ox3c), change it. 5. Click OK. 6. Exit the Registry Editor, then shutdown and reboot the system. ======================================================================= 4.3 Configuration Notes ------------------------ 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. Enhanced Loop ID ---------------- Of 0 - FFh Loop Ids, some are preallocated for special functions and are not available for use by devices: Loop IDs Functions -------- ---------- 7Eh FL_Port (S_ID=FFFFFEh) 7Fh Switch Fabric Controller (S_ID=FFFFFDh) 80h Switch Name Server (S_ID=FFFFFCh) 81h Switch Embedded Port (FFFc4xh) used for FC-4 probing (Brocade only) FFh IP Broadcast Connection options ------------------ The following connection options are supported: Value Connection ----- ----------------- 00 Start in loop mode, by transmitting Lip F7F7 01 Start in point-to-point mode, by transmitting NOS/OLS 02 Start in loop mode first, then switch to point- to-point mode if NOS is detected. The connection option is currently stored in the NVRAM and can be changed through the FastUtil. The default value of the connection mode is 2. Fibre Channel Tape support -------------------------- There are two ways to enable Fibre Channel (FC) tape support, the first method is to enable the FC tape support NVRAM setting in the HBA Extended Firmware Setting window. You can configure the adapter NVRAM settings using the Fast!UTIL utility. To access Fast!UTIL utility, press Ctrl+Q during host BIOS initialization. The second way is to set the Fibre Channel Tape Driver Parameters in the system registry to 1. - To ensure the driver function properly, the driver changes some of the system related registry entries such as the disk timeout value of the system disk driver during driver installation through the use of the oemsetup.inf file. Those values are not being restored upon driver removal. - Notes on LUN 0 issue: In order for NT4.0 to see the device properly, LUN 0 has to be configured. ======================================================================= 5.0 Unattended Mode -------------------- The driver supports the Unattended Mode. Please follow the instructions provided by Microsoft to create necessary files and prepare systems for unattended installation. ======================================================================= 6.0 WEB Sites and Support Phone Number -------------------------------------- 6.1 IBM TotalStorage Support Web Site: http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/disk 6.2 IBM TotalStorage Web Site: http://www.storage.ibm.com/ssg.html 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.ibm.com/planetwide ======================================================================= 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 registered 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.