This README file contains the latest information about installing the IBM eServer BladeCenter Fibre Channel Expansion Card Device Driver version 9.0.1.93 on a Windows 2003 or Windows 2000 platform Refer to the IBM eServer BladeCenter Fibre Channel Expansion Card Support CD and Installation and User's guide. Refer to the IBM Support Website listed in "Web Sites and Support" section in this ReadMe document for the latest information and updated README file. Products supported: IBM eServer BladeCenter Fibre Channel Expansion Card (IBM Option P/N 13N2203) IBM eServer BladeCenter Fibre Channel Expansion Card (IBM Option P/N 48P7061) IBM eServer BladeCenter SFF Fibre Channel Expansion Card (IBM Option P/N 26K4841) Last Update: 9/27/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 eServer BladeCenter Fibre Channel Expansion Card Device Driver Overview The IBM eServer BladeCenter Fibre Channel Expansion Card Device Driver supports Fibre Channel point-to-point, F-port, FL-port, N-port, and Arbitrated Loop configurations. - 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 loopback test - Support for QLogic Internet Protocol (IP) driver - Support for Fibre Channel Tape - Support for Reduced Interrupt Operation - Support for Windows Server 2003/XP/2000 SCSI PnP interface ====================================================================== 1.2 Limitations --------------- N/A 1.3 Enhancements ---------------- This release of driver works with all versions of Windows 2000 and all 32-bit versions of Windows Server 2003. This driver will also install in Windows XP Professional. However, it is not tested by IBM nor certified by Microsoft in Windows XP Professional environment. ====================================================================== 1.4 Prerequisites for the update --------------------------------- N/A ====================================================================== 2.0 CHANGE HISTORY ------------------ Version 9.0.1.93 9/27/04 * 15-93-3: Two servers in loop connections cannot co-exist. * 15-93-4: V9.0.0.1x generic drivers don't properly mask luns via SMS tool. * rQm 253340: Driver only return partial data on check condition when using passthrough commands. * QLogic MSA binding issue * Fixed link down timeout bug. * Return the correct data buffer when a check condition is detected * Close ER38311: ConfigRequired=1 setting will block all devices * Add check for the FCP response data field for error determination, fall out of DFCT118797. * ER37274: Fix host being deteted as a target device * Added Support for the IBM eServer BladeCenter SFF Expansion Card Version 8.2.3.93 2/25/04 * Update to Firmware v3.02.24 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.62 06/25/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.63 02/18/03 *Microsoft verified version of driver for HS20 FC Expansion Card. *Changed .inf file to recognize HS20 FC Expansion Card in Device Manager. Version 8.1.5.62 11/25/02 * Call nextlu for tagged I/O and nextrequest for untagged I/O * Do not notify reset detected for a RSCN Version 8.1.5.60 06/13/02 * Close ER18316: Win2k IP driver failed to ping each system if QLDirect is embedded. * Close ER18315: 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 * Fix ER17446: 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 * Close 94577: 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. Shot 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 * Close DFCT38061: Mark device offline * 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 (44072) * Reduce the failover timeout (44029) * 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 four sections. 3.1 Initial OS installation with the Fibre Channel Expansion Card as Boot 3.2 Adding the Fibre Channel Expansion Card Driver to the Existing OS 3.3 Updating the existing Fibre Channel Expansion Card Driver 3.4 Removing the Fibre Channel Expansion Card Driver ====================================================================== 3.1. Initial Windows 2003 installation with the Fibre Channel Expansion Card as Boot. ------------------------------------------------------------------- Contact IBM Support for supported configurations and instructions for configuring the IBM eServer BladeCenter Fibre Channel Expansion Card as the boot device. ====================================================================== 3.2 Adding the Fibre Channel Expansion Card Drivers to an Existing Windows 2003 or Windows 2000 System. ------------------------------------------------------------------ To install the Windows 2003 or Windows 2000 driver files for the Fibre Channel Expansion card you will need either a floppy diskette or CD containing the driver files. You can get the latest driver information and download the latest driver files from http://www.ibm.com/pc/support/ Perform the following steps to add the driver to the existing Windows 2003 or Windows 2000 system on a BladeCenter HS20 or HS40 blade server. 1. Install the IBM eServer BladeCenter Fibre Channel Expansion Card to a HS20/HS40 server blade per directions provided in IBM eServer BladeCenter Fibre Channel Expansion Card Installation and User's Guide publication. 2. Power on BladeCenter or install HS20/HS40 blade server (hot pluggable). Refer to HS20/HS40 blade server User's Guide documentation. 3. To associate the CD-ROM or diskette drive with the blade server, press the CD/diskette/USB select button on the blade server. For the location of the CD/diskette/USB button, see the illustration in the IBM eServer BladeCenter Fibre Channel Expansion Card Installation and User's Guide publication or BladeCenter User's Guide. The LED on the button flashes while the request is being processed, then is steady when the ownership of the CD-ROM or diskette drive is transferred to the blade server. 4. To associate the keyboard port, mouse port, and video port with the blade server, press the keyboard/mouse/video select button. The LED on this button flashes while the request is processed, then is steady when the ownership of the keyboard, mouse, and video is transferred to the blade server. 5. Insert either the CD with downloaded FC Expansion Card driver files into the BladeCenter CD-ROM drive or you can also insert a floppy diskette with downloaded Expansion Card driver files into the BladeCenter floppy diskette drive. 6. Windows 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 device. 7. Click Next. 8. 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. 9. Click Next. 10. From the Start Device Driver Installation screen, click Next. 11. Click Finish on the Upgrade Device Driver Wizard/Completing the Upgrade Device Driver Wizard. 12. You will 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?" Click Yes to restart the computer right away. Notes: If the driver has already been installed once on the blade server and installing or re-installing a FC expansion card, when the system comes up, it will detect the device correctly by displaying the Found New Hardware message with IBM eServer BladeCenter Fibre Channel Expansion Card identified. Follow the procedure below to complete the driver installation: 1. If the Digital Signature Not Found screen is displayed, click Yes. 2. When the Insert Disk message appears, insert either the CD with downloaded Expansion Card driver files into the BladeCenter CD-ROM drive or you can also insert a floppy diskette with downloaded Expansion Card driver files into the BladeCenter floppy diskette drive. Click OK. 3. 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. 4. Click Finish on the Found New Hardware Wizard/Completing the Found New Hardware Wizard screen. 5. 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. ====================================================================== 3.3 Updating the Existing Fibre Channel Expansion Card Driver ------------------------------------------------------------ To update the Windows 2003 or Windows 2000 driver files for the Fibre Channel Expansion card you will need either a floppy diskette or CD containing the driver files. You can get information and download the latest driver files from http://www.ibm.com/pc/support/. To update the Fibre Channel Expansion Card driver on an installed Windows 2003 or Windows 2000 system, follow this procedure: 1. Power on BladeCenter or install HS20/HS40 blade server (hot pluggable). Refer to HS20/HS40 blade server User's Guide documentation. 2. To associate the CD-ROM or diskette drive with the blade server, press the CD/diskette/USB select button on the blade server. For the location of the CD/diskette/USB button, see the illustration in the Fibre Channel Expansion Card Installation and User's Guide publication or BladeCenter User's Guide. The LED on the button flashes while the request is being processed, then is steady when the ownership of the CD-ROM or diskette drive is transferred to the blade server. 3. To associate the keyboard port, mouse port, and video port with the blade server, press the keyboard/mouse/video select button. The LED on this button flashes while the request is processed, then is steady when the ownership of the keyboard, mouse, and video is transferred to the blade server. 4. Start the Device Manager by clicking Start, pointing to Settings, clicking Control Panel, double clicking System, clicking Hardware tab, and clicking the Device Manager button. 5. Use the scroll bar to scroll down the list of hardware types, double click the SCSI and RAID controller. 6. Select IBM HS20 Fibre Channel Expansion Card or QLogic QLA2300 PCI Fibre Channel Adapter from the devices list and then click Properties. 7. Click the Driver tab, and then click Update Driver to start the Upgrade Device Driver Wizard. Click Next. 8. Click Display, a list of the known device drivers for this device appears. Click Next. NOTE: If upgrading the driver on Windows 2000/2003, you must select the "I will choose" or manual option and not allow Windows to search for an updated driver. Once you select the manual choice option, continue with the proceedure below. 9. Click the Have Disk button 10. Insert a CD with downloaded Expansion Card driver files into the BladeCenter CD-ROM drive or you can also insert a floppy diskette with downloaded Expansion Card driver files into the BladeCenter floppy diskette drive. 11. 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. 12. Click Next. From the Upgrade Device Driver Wizard/Select a Device Driver screen. 13. Click Next from the Upgrade Device Driver Wizard/Start Device Driver Installation screen. 14. Click Finish on the Upgrade Device Driver Wizard/Completing the Upgrade Device Driver Wizard. 15. You will 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? " 15. Click Yes to restart the HS20/HS40 blade server. ====================================================================== 3.4 Removing the Fibre Channel Expansion Card ---------------------------------------------- Refer to IBM eServer BladeCenter Fibre Channel Expansion Card Installation and User's Guide for directions on how to remove the IBM eServer BladeCenter Fibre Channel Expansion Card. 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 or Windows 2003 will recognize that it has been removed. ====================================================================== 4.0 CONFIGURATION INFORMATION ----------------------------- 4.1 Hard Loop ID ---------------- It is recommended that you set different Hard Loop IDs for each IBM eServer BladeCenter Fibre Channel Expansion card 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. You can configure the adapter using the Fast!UTIL utility. Access Fast!UTIL by pressing Ctrl+Q during host BIOS initialization. Refer to the IBM eServer BladeCenter Fibre Channel Expansion Card Installation and User's Guide for additional information on setting the Hard Loop ID. If you do not assign different Hard Loop IDs, the Fibre Channel protocol will automatically assign Loop IDs when their is a conflict. ====================================================================== 4.2 Driver Parameters --------------------- The driver parameters are divided into System Registry Parameters and NVRAM Parameters sections. ====================================================================== 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 2003/2000 includes an enhanced scatter/gather list support for doing very large SCSI I/O transfers. Windows 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, select Run, and open the REGEDT32 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 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, select Run, and open the REGEDT32 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, select Run, and open the REGEDT32 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, select Run, and open the REGEDT32 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 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 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, select Run, and open the REGEDT32 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 --------------- NOTE: BladeCenter server blade architecture only allows for single FC Expansion card for each blade server. The UseSameNN is for server systems that have multiple FC HBAs. This parameter does not apply to the IBM eServer BladeCenter Fibre Channel Expansion Card. ====================================================================== 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.2.10 NVRAM Parameters ---------------------- The NVRAM features described below are hard-coded in the driver. The changes made for the particular NVRAM feature in the Fast!Util do not take effect unless otherwise noted. None. ====================================================================== 4.3 Configuration Notes ------------------------ Support for more than 8 LUNs ---------------------------- Windows Server 2003/2000 uses the ANSI-approved version field of the Inquiry data returned by the target device to determin 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 conection 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 ---------------------------------------- IBM Support Web Site: http://www.ibm.com/pc/support IBM eServer xSeries BladeCenter Marketing Web Site: http://www.ibm.com/servers/eserver/bladecenter 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 -------------------------- The following terms are tradmarks of the IBM Corporation in the United States or other countries or both: IBM eServer BladeCenter 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.