IBMTape.W200x.Readme.txt - Windows 200x Tape Device Driver (C) Copyright IBM Corporation 2003-2008 See /derdrvr/Doc/IBM_Tape_Driver_IUG.pdf for installation instructions. See /derdrvr/Doc/UserLicense.pdf for the User License Agreement. The driver zip file contains a level of the device driver with its associated resource files and utilities. This driver will be installed in the Microsoft system directories. The Windows Server 2003 and Windows Server 2008 drivers have been qualified to run on the following architectures: Intel x86 (running Windows 32-bit systems) IBMTape.x86_nnnn.zip - Windows 2003 IBMTape.x86_w08_nnnn.zip - Windows 2008 Intel IA64 (Itanium) IBMTape.i64_nnnn.zip - Windows 2003 IBMTape.i64_w08_nnnn.zip - Windows 2008 Intel EM64T/AMD64 IBMTape.x64_nnnn.zip - Windows 2003 IBMTape.x64_w08_nnnn.zip - Windows 2008 There are two sections: General Items and HBA Restrictions ***************** * General Items * ***************** 1) For a listing of all supported configurations, please visit: http://www-03.ibm.com/systems/support/storage/config/ssic/displayesssearchwithoutjs.wss?start_over=yes 2) The tape device driver has a support limitation for 255 tape devices. 3) To backup data in IBM SAS drives in the fixed blocksize mode, the blocksize must be set to a multiple of 4; otherwise it will cause the open or set blocksize commands to fail. 4) A potential loss of data may occur if you are using V6.1.5.4 or V6.1.4.8 of the device driver with Data Path Failover enabled. This bug happens very rarely, but if you are using either of those versions, we recommend that you double-click DisableDPF.reg from the driver install package and reboot your system, or update your driver to the latest supported level on the FTP site. V6.1.4.80 is a driver derived from 6.1.4.8 and should contain all the same features, except that the data integrity bug referenced here does not exist in 6.1.4.80. 5) The device driver area of the FTP site now contains different installation folders for different kinds of drivers. Engineering drivers are drivers that contain five digits instead of four in the filename, as in 6.1.6.20. These drivers have not passed a complete test cycle within IBM but are released to the FTP site "as-is." These drivers may contain functions that need to be released before a general test cycle has been completed. Folders marked "Latest" contain drivers that have completed a test cycle within IBM and are fully supported drivers, but may not have passed Microsoft Logo testing. Folders marked with a "WHQL" designation have been approved by the Microsoft Windows Hardware Quality Laboratories and conain Microsoft Logo digital signatures. These drivers will install without warning messages in the Windows environment. 6) Version 6.1.6.2 and later versions of the device driver have an option for enforcing file names for tape drives that will persist across reboots of the operating system. For example, if your tape drive has the name \\.\tape3 and the persistent naming option is used, then \\.\tape3 will be reserved for use by that device after an operating system reboot. To take advantage of this feature, place a DWORD value in the registry called PersistentNaming and assign it a value 1 at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3 and reboot your system. 7) V6.1.3.8 and later versions of the IBM tape driver support application-managed encryption on TS1120 tape drives. For more information, see /derdrvr/Doc/IBM_Tape_Driver_IUG.pdf 8) When running in an environment that includes TS7510 virtual tape drives, DPF must be disabled. Install the driver, run DisableDPF.reg from the driver install package, and reboot your system. Since the TS7510 emulates the TS1120, the driver cannot distinguish between the two devices, and DPF must be disabled for the entire environment. 9) A crash resulting in a blue screen with bug check code 0xB8 has been observed when running Intel IA64 Itanium systems with QLogic driver version 9.1.2.16. To fix this issue, customers must install Microsoft hotfix KB912944. At this time, customers must contact Microsoft directly to obtain this hotfix. For further information, see http://support.microsoft.com/?kbid=912944. 10) When running Emulex HBA driver 1.20a3 for Windows 2003, after the HBA driver is loaded, any reset by a utility or firmware download will cause the new PRLI frame sent to fail to advertise FCP-2 tape recovery support. Once the driver is in this state, the workaround is to disable/enable the driver in the device manager window. This causes a new instance of the driver to be loaded that does contain the correct PRLI data. 11) A unique method has been introduced for obtaining library dumps in the IBM TS3100 Tape Library. For most libraries, you issue a READ_BUFFER to obtain the dump. For the TS3100 Tape Library, you must use LOG_SENSE. Log Sense page 0x07 should be used to obtain the event log. Log Sense page 0x33 should be used to obtain the error log. NTUTIL option 83 may be used to issue a LOG_SENSE command. 12) *********************************************************************************************** **** **** **** IMPORTANT NOTE ABOUT VERSION 6.1.0.9 AND LATER VERSIONS OF THE TAPE DRIVER **** **** **** *********************************************************************************************** V6.1.0.9 and later versions of the IBM tape driver support Data Path Failover (DPF) on 3592 tape drives, while V6.1.1.2 and later versions support DPF on LTO tape drives. Major architectural changes were made to the driver to include this support, and these changes are in effect regardless of whether your environment includes support for the DPF feature. A new procedure for installing the driver has been introduced. In particular, the tape driver on any given platform requires installation of three .sys files with their corresponding .inf files: ibmtpbsxx.sys (installed by ibmtpbs.inf) ibmtpxx.sys and ibmtpftxx.sys (installed by exctape.inf or magtape.inf) ('xx' in the filenames refers to either 2k or 2k3.) In order to reduce complexity, the file install.exe is included in the driver package to perform the installation steps automatically. Simply double-click the install.exe icon from within the driver install directory. The virtual and actual hardware will be installed correctly on your system. Please refer to the Installation and User's Guide for more details. Aside from the installation, all architectural changes to the driver are transparent. 13) *********************************************************************************************** **** **** **** IMPORTANT NOTE ABOUT VERSION 6.0.8.2 AND LATER VERSIONS OF THE LIBRARY/CHANGER DRIVER **** **** **** *********************************************************************************************** V6.0.8.2 and later versions of the IBM medium changer driver support Control Path Failover (CPF). Major architectural changes were made to the driver to include this support, and these changes are in effect regardless of whether your environment includes support for the CPF feature. A new procedure for installing the driver has been introduced. In particular, the changer driver on any given platform requires installation of three .sys files with their corresponding .inf files: ibmcgbsxx.sys (installed by ibmcgbs.inf) ibmcgxx.sys and ibmcgftxx.sys (installed by magchgrf.inf) ('xx' in the filenames refers to either 2k or 2k3.) Instructions on how to install ibmcgbsxx.sys are included in the document CPF_install.doc. Installation of the other two .sys files follows the instructions in the Installation and User's Guide. In order to reduce complexity, the file install.exe is included in the driver package to perform the steps in CPF_install.doc automatically. Simply double-click the install.exe icon from within the driver install directory. The virtual and actual hardware will be installed correctly on your system. Aside from the installation, all architectural changes to the driver are transparent. 14) Attention users of 3570 and 3575 devices: Support for these devices has been dropped in the converged Windows 2003 driver. 15) Levels of the Windows device driver from 6.1.2.4 to 6.1.5.3 contain two installer options. One is an option that causes the driver to issue automatic reserves on open and also prevents multiple open handles from existing from a host to a drive at the same time. This option is the default option and is approved for use with Tivoli Storage Manager. If you are running applications such as Microsoft Removable Storage Manager, however, you will need to run without the exclusivity restrictions. Option 2 in the installer may be used if you intend to run with RSM. Versions 6.1.5.4 thru 6.1.6.6 have one option used for the installer, the default option with exclusive access to the drive enforced. If these levels are used to run with Microsoft Removable Storage Manager, then the user must double click the file nonexclusive.reg from the reg folder of the install package and reboot. In versions 6.1.6.7 thru 6.1.8.8 of the device driver, the non-exclusive option for use with RSM is implemented through an installer option. Run install.exe with the -n option from a command line if you want to run with RSM. For example, c:\>install -n Beginning in driver package 6.1.8.9, there are two install executables to choose from. install_exclusive.exe: With install_exclusive.exe, the driver will issue automatic reserves on open and also prevent multiple open handles from the host to a drive to exist at the same time, as is required by applications such as Tivoli Storage Manager. Note: This option replaces the previous default installation of install.exe install_nonexclusive.exe: With install_nonexclusive.exe, the driver will permit open handles from the host to a drive to exist at the same time, as is required by applications such as DPM or RSM. Note: This option replaces the previous command line installation of install.exe -n 16) All files with the zip extension need to be downloaded to your workstation in binary mode. 17) Tivoli Storage Manager customers (and others, perhaps, depending on their application) using the IBM 3582 Library, need to set the barcode scanning mode to Extended to have the barcodes seen correctly by their application. To do so, from the operator panel, go to Setup -> Scanner -> set Enable to ON. Then set the Mode to Extended. 18) Restriction for various SAN components when certain QLogic HBAs are also in your SAN fabric. If you have the IBM TotalStorage SAN Switch or the Brocade SAN switch or McData SAN products or InRange SAN products and certain QLogic HBAs in your SAN, IBM recommends that you quiesce any jobs running through the QLogic HBAs before creating or modifying zones in your SAN. This is because when a zone is created or modified, an RSCN is sent to all HBA ports in the fabric registered for RSCN notification. If there is active I/O on certain Qlogic HBAs, I/O will fail when the HBA receives the RSCN. Devices are not loss. This has been observed on the following OSes and HBAs: - Windows NT/2003 -- only with the Qlogic QLA2200 19) Check this readme file for the latest information, which supercedes information in the Installation and User's Guides. ******************** * HBA Restrictions * ******************** 1) For LSI Logic SAS3800X and IBM SAS HBA controller (25R8060) the following changes to adapter BIOS settings is needed for CPF and DPF support. ReportDeviceMissingDelay: 2032 IoDeviceMissingDelay: 8