IBMtape driver supports the iostat system command, which reports I/O statistics for the supported tape drives in IBMtape.4.1.2.7 and later versions. Refer to man (1M) iostat for the command usage.
Reservation Conflict Logging
When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the Solaris system log of /var/adm/messages. Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name) and reserve key. If successful, the device driver will log this
information in the detail data below. After initially logging the reserving host WWPN, subsequent reservation conflicts from the same reserving host WWPN and reservation key will not be logged to prevent multiple entries in the system log until either the reserving host WWPN or reservation key is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs.
Here are the log examples:
1. The information is logged when the drive is reserved with a Persistent Reservation.
log_reserve: Reserving host key 46E48C49413E6EB1 WWPN 210000E08B118BB1
2. The information is logged when the drive is reserved with a SCSI-2 Reserve. log_reserve: Reservation Conflict: read full status failure (rc 16)
3. The information is logged when the drive is reserved but the host reservation information isn’t available.
Purpose . . . 163
Data Flow . . . 163
Product Requirements . . . 164
Hardware Requirements. . . 164
Software Requirements . . . 165
Installation and Configuration Instructions . . . 165
Windows NT Instructions . . . 165
Windows 2000, Windows Server 2003, and Windows Server 2008 Instructions . . . 177
Persistent Naming Support on Windows Server 2003 and Windows Server 2008 . . . 181
Control Path Failover Support for Tape Libraries 182 Configuring and Unconfiguring Control Path Failover Support . . . 182
Querying Primary and Alternate Path Configuration . . . 182
Checking Disablement of Control Path Failover Setting. . . 182
Data Path Failover Support for Tape Drives . . . 183
Configuring and Unconfiguring Data Path Failover Support . . . 183
Querying Primary and Alternate Path Configuration . . . 183
Checking Disablement of Data Path Failover Setting. . . 183
System-Managed Encryption . . . 184
Device Driver Configuration . . . 184
Configuration File . . . 184
Querying Tape Drive Configuration Settings . . 185
Problem Determination . . . 185
Windows NT Instructions . . . 185
Windows 2000/Windows Server 2003 Instructions . . . 186
Reservation Conflict Logging . . . 188
This chapter describes the hardware requirements, software requirements, and installation notes for the Microsoft Windows device drivers for IBM TotalStorage and System Storage tape devices.
Purpose
The Windows tape and medium changer device driver is designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges), as well as to the advanced functions needed by full tape management systems. Whenever possible, the driver is designed to take advantage of the device features transparent to the application
Data Flow
The software described in this chapter covers the Windows device driver and the interface between the application and the tape device.
Figure 15 illustrates a typical data flow process.
Application Program Windows Tape and Medium Changer Device Driver Host Bus Adapter Driver Tape Device a2500268
Product Requirements
The most current information on supported hardware and software configurations for the Windows tape and medium changer device driver can be found in the README files on the IBM Device Drivers FTP site, which is located at ftp://ftp.software.ibm.com/storage/devdrvr/Windows.
Hardware Requirements
One of more of the following processors is required by the IBMtape device driver: v For the Windows NT®operating system, Intel compatible processors with a
minimum processor level of Intel 486DX or Pentium®.
v For the Windows 2000, Windows Server 2003, and Windows Server 2008 operating systems, a 32-bit Intel compatible processor.
v For the Windows Server 2003 and the Windows Server 2008 operating systems, a 64-bit Itanium processor.
v For the Windows Server 2003 and the Windows Server 2008 operating systems, a processor that supports extended 64-bit architectures (Intel EM64T and AMD64). One or more of the following SCSI host adapters:
v Adaptec 2940U2W or IBM P/N 33L5000 for IBM System x (also known as xSeries®) (LVD)
v Adaptec 2944UW (HVD)
v Adaptec SCSI Adapter 29160 or IBM P/N 19K4646 for IBM System x (also known as xSeries) - Single Port LVD
v Adaptec SCSI Adapter 39160 - Dual Port LVD
v Adaptec SCSI Card 39320-R (LVD) and 39320D-R (dual port LVD) v Adaptec SCSI Card 29320ALP or IBM P/N 13N2249 (LVD)
v Symbios SYM22910 64-bit PCI-to-Ultra-2 SCSI Dual Channel Host Adapter (LVD) from LSI Logic Corporation
v IBM Ultra320 SCSI Controller 2 P/N 13N2249 (SCSI LVD) v IBM Ultra320 SCSI Controller 2 P/N 39R8743 (SCSI LVD)
One or more of the following SAS host bus adapters: v LSI Logic SAS3800X SAS Adapters
v IBM SAS Host Bus Adapter Controller Part Number 25R8060
One or more of the following Fibre Channel host bus adapters: v IBM xSeries and Netfinity®FAStT Host Adapter P/N 19K1246 v IBM xSeries and Netfinity FAStT Host Adapter P/N 24P0960 v DS4000®FC 4Gbps PCI-X Single Port HBA P/N 39M5894 v DS4000 FC 4Gbps PCI-X Dual Port HBA P/N 39M5895 v QLogic 4Gb FC Single-Port PCIe HBA P/N 39R6525 v QLogic 4Gb FC Dual-Port PCIe HBA P/N 39R6527 v Qlogic QLA2310
v Qlogic QLA2340 v Qlogic QLA2342 v Qlogic QLA2460 v Qlogic QLA2462
v Qlogic QLE2462 (not supported for Windows 2008 SPI for IA64 servers)
One or more of the following FC-AL host bus adapters:
v Qlogic QLE2460/2 4Gb PCI-E FC HBA, QLA2310FL, QLA2340, QLA2340L, QLA2342, QLA2342L, QLA2342L, QLA2460, QLA2462 Fibre Channel Adapters v Emulex LPe11000/2 4Gb PCI-E FC HBA, LP1150, LP8000 and LP9002L,
LP402DC, LP952L, LP9802, LP9802DC, LP10000, LP11000, LP11002 Fibre Channel Adapters
v IBM Netfinity P/N 00N6881, 19K1246, 24P0960, 39M5894, 39M5895
Attention: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. Tape and disk devices require incompatible HBA settings for reliable operation and optimal performance characteristics. Under stress conditions (high I/O rates for tape, disk, or both) where disk and tape subsystems share a common HBA, stability problems have been observed. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring server and storage configuration interoperability. It strongly
recommends that your implementation plan includes provisions for separating disk and tape workloads.
Software Requirements
The software requirements are supported: v SCSi or FC adapter device driver
v Microsoft Windows NT Version 4.0 with Service Pack 6 or later v Microsoft Windows 2000 Build 2195 or later, or
v Microsoft Windows Server 2003 Build 3790 or later v Microsoft Windows Server 2008 SP1 Build 6001 or later
Installation and Configuration Instructions
This section includes instructions for installing and configuring the Windows tape and medium changer device driver on Windows NT and Windows 2000/Windows Server 2003/Windows Server 2008.