Installation and User s Guide

Transcription

1 IBM Tape Deice Driers Installation and User s Guide GC

2

3 IBM Tape Deice Driers Installation and User s Guide GC

4 Note! Before using this information and the product that it supports, be sure to read the general information under Notices on page 323. Tenth Edition (March 2010) This ninth edition of the IBM Tape Deice Driers Installation and User s Guide, GC , replaces and makes obsolete the following manuals: IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM Tape Deice Driers Installation and User s Guide, GC IBM TotalStorage and System Storage Tape Deice Driers Installation and User s Guide, GC IBM Ultrium Deice Driers Installation and User s Guide, GC Copyright IBM Corporation 2007, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii Preface ix Related Information ix How to Send Your Comments xi Special Printing Instructions x Chapter 1. Introduction Purpose IBM Tape Products Chapter 2. Common Extended Features 9 Purpose Supported Hardware Supported Applications Path Failoer and Load Balancing Dynamic Load Balancing Supported Deices and Feature Codes Data Encryption Chapter 3. AIX Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Installation and Configuration Instructions Tape Drie, Media, and Deice Drier Parameters 26 Special Files Persistent Naming Support Control Path Failoer Support for Tape Libraries.. 36 Data Path Failoer and Load Balancing Support for Tape Dries System-Managed Encryption Problem Determination Tape Drie Serice Aids Performance Considerations Chapter 4. HP-UX Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Installation and Configuration Instructions Supported Configuration Parameters Special Files Persistent Naming Support Control Path Failoer Support for Tape Libraries.. 79 Data Path Failoer and Load Balancing Support for Tape Dries Problem Determination Chapter 5. Linux Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Installation and Configuration Instructions Tape Drie, Media, and Deice Drier Parameters 99 Special Files Control Path Failoer Support for Tape Libraries 106 Data Path Failoer and Load Balancing Support for Tape Dries Open Source Deice Drier - lin_tape System-Managed Encryption Problem Determination Chapter 6. Solaris Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Installation and Configuration Instructions Special Files Persistent Naming Support Control Path Failoer Support for Libraries Data Path Failoer and Load Balancing Support for Tape Dries System-Managed Encryption Problem Determination Chapter 7. Windows Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Installation and Configuration Instructions Persistent Naming Support on Windows Serer 2003 and Windows Serer Control Path Failoer Support for Tape Libraries 170 Data Path Failoer Support for Tape Dries System-Managed Encryption Problem Determination Chapter Enterprise Tape Library Support Purpose MTLIB Program MTEVENT Program Library Drier Information Library Emulation AIX HP-UX Linux Solaris Windows Copyright IBM Corp. 2007, 2010 iii

6 Chapter 9. IBM Tape Diagnostic Tool (ITDT) Purpose Accessing ITDT Supported Systems Supported Equipment Standard Edition - Installation Standard Edition - Initial Startup Standard Edition - Known Issues and Limitations 243 Standard Edition - Start Menu Commands Standard Edition - Scan Menu Commands Standard Edition - Tapeutil Menu Commands Standard Edition - Tapeutil Scripting Commands 271 Graphical Edition - Installation Graphical Edition - Known Issues and Limitations 288 Graphical Edition - User Interface Description Graphical Edition - Scan Menu Commands Graphical Edition - Tapeutil Menu Commands Appendix A. Accessing Documentation and Software Online. 317 Appendix B. Verifying Proper Attachment of Your Deices Appendix C. Managing the Microcode on the IBM Tape Drie Notices Trademarks Index i IBM Tape Deice Driers Installation and User s Guide

7 Figures 1. Current Attachment Array Example of an IBM Tape Enironment Multiple HBA and multi-port deices Multiple HBA and single ports Single HBA and multi-port deices Sample Encryption Configuration File Data Flow for AIX Deice Drier (Atape) Data Path for AIX Deice Drier (Atape) Data Flow for HP-UX Deice Drier (ATDD) Example of atdd_d.log Output Data Flow for Linux Deice Drier (lin_tape) Data Flow for Solaris Deice Drier (IBMtape) Example of Control Path Failoer Support Command Output Example of Data Path Failoer Support Command Output Data Flow for Windows Deice Drier (IBMmag) Installation Application in Windows Explorer Windows Logo Testing screen Checked folder Syntax Diagram for mtlib program Deice Query Volume Query Expanded Volume Query Expanded Volume Data with Usage Inentory Count Data Tape Library Deice Number Expanded Tape Library Deice List Library Data Statistical Data Inentory Query Category Inentory Query Resere Category Command Resere Category List Category Attribute List Library Address Information /SMC Library Data Flow LIBSMC and OS Components Data Flow for AIX 3494 Enterprise Tape Library Drier SMIT Main Menu SMIT Deices Menu SMIT Tape Drie Menu Tape Drie Type Menu Add an LMCP Logical Deice Menu LMCP COMMAND STATUS Window Configure an LMCP Selection List Configure a Defined LMCP COMMAND STATUS Window Data Flow for HP-UX 3494 Enterprise Tape Library Drier Data Flow for Linux 3494 Enterprise Tape Library Drier Data Flow for Solaris 3494 Enterprise Tape Library Drier Data Flow for Windows 3494 Enterprise Tape Library Drier Welcome/Startup screen License screen Machine credentials screen Installation progress screen Installation complete screen Start Screen Menu Scan Menu More Scan Options Deice List Screen Data Delete Question Test Running Test Results Dump Firmware Update screen Scrollable Data screen Encryption Start screen Full Write Results Tape Usage Screen System Test Results Graphical Edition User Interface Graphical Edition Preferences Graphical Edition Interface Main Program Menu Items Toolbar Buttons Scan Function Test Menu Test Results Dump Menu Dump Results Encryption Function Oerwrite Data Transfer Size Tape Usage System Test Tapeutil Control Center Tape Drie Commands Command Parameters Command Parameter Results Copyright IBM Corp. 2007, 2010

8 i IBM Tape Deice Driers Installation and User s Guide

9 Tables 1. Ultrium Product Comparison Supported Deices and Feature Codes Interoperability between IP4 and IP6 Clients and Serers Feature Codes (Encryption) Special Files for Tape Deices Special Files for Medium Changer Deices Error Description Deice-Specific Parameter Definitions Drier-Specific Parameters (Global) Special Files New Special Files in HP-UX 11i Trace Flags Problems, Reasons, and Solutions Troubleshooting (Problems and Solutions) Components Created During lin_tape Installation Special Files for IBM TotalStorage Tape Deices IBMtape and lin_tape Comparison SCSI Supported Deices IBMtape Components IBMtape Install or Update Solaris Deice Drier - IBMtape - Equipment Listing Example Solaris Deice Drier - IBMtape - Equipment Listing Example Solaris Deice Drier - IBMtape - Equipment Listing Example Solaris Deice Drier - IBMtape - Equipment Listing Example Configuration Parameters Recognized by IBMtape IBM SCSI Tape/Medium Changer Special Files for Solaris Tracing Facility Definitions of Abort Codes Supported Platforms Drier Descriptions Copyright IBM Corp. 2007, 2010 ii

10 iii IBM Tape Deice Driers Installation and User s Guide

11 Preface Related Information These publications and URLs proide user information and installation assistance for IBM tape drie, medium changer, and library deice driers. Reference material, including the Adobe PDF ersion of this publication, is aailable at the following url: dociew.wss?rs=577&uid=ssg1s A companion publication coering programming aspects for the deice driers is: IBM Tape Deice Driers: Programming Reference, GA Current Products IBM TotalStorage Enterprise Tape System 3592 Publications The following publications relate to the IBM TotalStorage Enterprise Tape System 3592: IBM TotalStorage Enterprise Tape System 3592 Operator Guide, GA IBM TotalStorage Enterprise Tape System 3592 Introduction and Planning Guide, GA IBM TotalStorage Silo Compatible Tape Frame 3592 Introduction, Planning, and User's Guide, GA IBM TotalStorage Enterprise Tape System 3592 Hardware Reference, GA IBM System Storage TS1120 Tape Drie The following publications relate to the IBM System Storage TS1120 Tape Drie: IBM System Storage TS1120 Tape Drie and Controller Introduction and Planning Guide, GA IBM System Storage TS1120 Tape Drie and Controller Operator Guide, GA IBM System Storage TS3500 Tape Library Operator Guide, GA IBM System Storage TS3500 Tape Library Introduction and Planning Guide, GA IBM System Storage 3953 Library Manager Model L05 Operator Guide, GA IBM System Storage 3953 Tape System Introduction and Planning Guide, GA IBM Ultrium Tape Drie Models T800 and T800F The following publications relate to the IBM Ultrium Tape Drie Models T800 and T800F: IBM Ultrium Tape Drie Models T800 and T800F Setup, Operator, and Serice Guide, GC IBM LTO Ultrium 3-H Tape Drie The following publications relate to the IBM LTO Ultrium 3-H Tape Drie: IBM LTO Ultrium 3-H Tape Drie Setup, Operator, and Serice Guide, SC IBM System Storage TS2230 Tape Drie The following publications relate to the IBM System Storage TS2230 Tape Drie: Copyright IBM Corp. 2007, 2010 ix

12 IBM System Storage TS2230 Tape Drie Setup, Operator, and Serice Guide, GC IBM System Storage TS2230 Tape Drie Installation Quick Reference, GC IBM TotalStorage 3580 Tape Drie Models L33/L3H The following publications relate to the IBM TotalStorage 3580 Tape Drie Models L33/L3H: IBM TotalStorage 3580 Tape Drie Models L33/L3H Setup, Operator, and Serice Guide, GC IBM TotalStorage 3580 Tape Drie Models L33/L3H Quick Reference, GC IBM System Storage TS2340 Tape Drie The following publications relate to the IBM System Storage TS2340 Tape Drie [also known as IBM LTO4 (TS2340)]: IBM System Storage TS2340 Tape Drie Models L43/S43 Setup, Operator, and Serice Guide, GC IBM System Storage TS2340 Tape Drie Models L43/S43 Quick Reference Card, GC IBM System Storage TS3500 Tape Library (also known as IBM TotalStorage UltraScalable Tape Library 3584) The following publications relate to the IBM System Storage TS3500 Tape Library: IBM System Storage TS3500 Tape Library Planning and Operator Guide, GA IBM System Storage TS3500 Tape Library Maintenance Information, 19P2440 IBM Virtualization Engine TS7520 The following publications relate to the IBM Virtualization Engine TS7520: IBM Virtualization Engine TS7520 Hardware, Installation, Setup, and Problem Determination Guide, GC IBM Virtualization Engine TS7520 Introduction and Planning Guide, GC IBM Virtualization Engine TS7500 User Guide, GC IBM System Storage TS3400 Tape Library The following publications relate to the IBM System Storage TS3400 Tape Library: IBM System Storage TS3400 Tape Library Installation Quick Reference, GA IBM System Storage TS3400 Tape Library Planning and Operator Guide, GC IBM System Storage TS3400 Tape Library Maintenance Information, GA IBM System Storage TS3310 Tape Library The following publications relate to the IBM System Storage TS3310 Tape Library: IBM System Storage TS3310 Tape Library Setup and Operator Guide, GA IBM System Storage TS3310 Tape Library Maintenance Information, GA IBM System Storage TS3310 Tape Library SCSI Reference, GA IBM System Storage TS3100 Tape Library The following publications relate to the IBM System Storage TS3100 Tape Library: IBM System Storage TS3100 Tape Library and TS3200 Tape Library Setup, Operator, and Serice Guide, GA IBM System Storage TS3100 Tape Library and TS3200 Tape Library Installation Quick Reference, GA IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference, GA x IBM Tape Deice Driers Installation and User s Guide

13 IBM System Storage TS3200 Tape Library The following publications relate to the IBM System Storage TS3200 Tape Library: IBM System Storage TS3100 Tape Library and TS3200 Tape Library Setup, Operator, and Serice Guide, GA IBM System Storage TS3100 Tape Library and TS3200 Tape Library Installation Quick Reference, GA IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference, GA AIX The following URL points to information about IBM System p (also known aserserer pseries ) serers: HP-UX The following URL relates to HP HP-UX systems: Linux The following URLs relate to Linux distributions: Solaris The following URL relates to Sun Solaris systems: Microsoft Windows The following URL relates to Microsoft Windows systems: Legacy Products IBM TotalStorage Ultrium External Tape Drie 3580 The following publications relate to the IBM TotalStorage Ultrium External Tape Drie 3580: IBM 3580 Ultrium Tape Drie Setup, Operator, and Serice Guide, GA IBM TotalStorage Ultrium Tape Autoloader 3581 The following publication relates to the IBM TotalStorage Ultrium Tape Autoloader 3581: IBM 3581 Ultrium Tape Autoloader Setup, Operator, and Serice Guide, GA IBM TotalStorage 3581 Tape Autoloader (also known as IBM TotalStorage Ultrium Tape 2U Autoloader 3581) The following publication relates to the IBM TotalStorage 3581 Tape Autoloader: IBM 3581 Tape Autoloader Models L28/L38/L3H and F28/F38/F3H Setup, Operator, and Serice Guide, GA Preface xi

14 IBM TotalStorage 3582 Tape Library (also known as IBM TotalStorage Ultrium Tape Library 3582) The following publications relate to the IBM TotalStorage 3582 Tape Library: IBM TotalStorage 3582 Tape Library Setup, Operator, and Serice Guide, GA IBM TotalStorage 3583 Tape Library (also known as IBM TotalStorage Ultrium Scalable Tape Library 3583) The following publications relate to the IBM TotalStorage Ultrium Scalable Tape Library: IBM 3583 Tape Library Setup and Operator Guide, GA IBM 3583 Tape Library Serice Guide, GA IBM Storage Area Network Data Gateway Module Setup, Operator, and Serice Guide, GA IBM Virtualization Engine TS7510 The following publications relate to the IBM Virtualization Engine TS7510: IBM Virtualization Engine TS7510 Hardware, Installation, Setup, and Problem Determination Guide, GC IBM Virtualization Engine TS7510 Introduction and Planning Guide, GC IBM Virtualization Engine TS7510 User Guide, GC IBM TotalStorage Enterprise Automated Tape Library 3494 The following publications relate to the IBM TotalStorage Enterprise Automated Tape Library (3494): IBM TotalStorage Enterprise Automated Tape Library (3494) Introduction and Planning Guide, GA IBM TotalStorage Enterprise Automated Tape Library (3494) Operator Guide, GA IBM TotalStorage 3494 Tape Library Maintenance Information, SA IBM 3490E Tape Subsystem The following publications relate to the IBM 3490E Tape Subsystem: IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models C10, C11, C1A, C22, and C2A Hardware Reference, GA IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models E01 and E11 User s Guide, GA IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models C10, C11, C1A, C22, and C2A Maintenance Information, SA IBM 3490E Tape Subsystem, Models F01, F1, F11, and FC0, Installation, Planning, and Operator's Guide, GA IBM Magstar MP 3570 Tape Subsystem The following publications relate to the IBM Magstar MP 3570 Tape Subsystem: IBM Magstar MP 3570 Tape Subsystem Operator s Guide, GA IBM Magstar MP 3570 Tape Subsystem Introduction and Planning Guide, GA IBM Magstar MP 3570 Tape Subsystem Hardware Reference, GA IBM Magstar MP 3570 Tape Subsystem Hardware Reference C-Series Models, GA IBM Magstar MP 3575 Tape Subsystem The following publications relate to the IBM Magstar MP 3575 Tape Subsystem: xii IBM Tape Deice Driers Installation and User s Guide

15 IBM Magstar MP 3575 Tape Library Dataserer Introduction and Planning Guide, GA IBM Magstar MP 3575 Tape Library Dataserer Operator Guide, GA IBM Magstar MP 3575 Tape Library Dataserer Hardware Reference, GA IBM TotalStorage Enterprise Tape System 3590 The following publications relate to the IBM TotalStorage Enterprise Tape System 3590: IBM TotalStorage Enterprise Tape System 3590 Introduction and Planning Guide, GA IBM TotalStorage Enterprise Tape System 3590 Operator Guide, GA IBM TotalStorage Enterprise Tape System 3590 Hardware Reference, GA IBM TotalStorage Enterprise Tape System 3590 Operator s Quick Guide, GA IBM mm Tape Library The following publications relate to the IBM mm Tape Library: IBM mm Tape Library Installation Guide, SA IBM mm Tape Library Operator Guide, SA IBM mm DDS-2 Tape Cartridge Autoloader The following publications relate to the IBM mm DDS-2 Tape Cartridge Autoloader: IBM mm DDS-2 Tape Cartridge Autoloader Model 005 Installation Guide, SA IBM mm DDS-2 Tape Cartridge Autoloader Model 005 Operator Guide, SA IBM mm DDS-2 Tape Cartridge Autoloader Model 005 Serice Guide, SA IBM 7332 Model 220 External 4mm Tape Autoloader The following publications relate to the IBM 7332 Model 220 External 4mm Tape Autoloader: 7332 Model 220 4mm Tape Autoloader, Setup and Operator Guide, SA Model 220 4mm Tape Autoloader Serice Guide, SY IBM mm Tape Library The following publications relate to the IBM mm Tape Library: 7334 Model 410 8mm Tape Library Setup and Operator Guide, SA Model 410 8mm Tape Library Serice Guide, SY IBM mm Tape Library The following publication relates to the IBM mm Tape Library: IBM mm Tape Library Model 205 Operator and Setup Guide, SA IBM 3447 and 7337 Digital Linear Tape Library The following publications relate to the IBM 3490E Tape Subsystem: 3447 and 7337 Digital Linear Tape Library Setup and Operator Guide, GA and 7337 Digital Linear Tape Library Serice Guide, GA Model 360 Digital Linear Tape Library Setup and Operator Guide, SA Preface xiii

16 Tru64 The following URL points to information about Tru64 systems: SGI The following URL relates to SGI systems: Other Publications IBM Storage Area Network Data Gateway Installation and User's Guide, SC Additional Information The following publication contains additional information related to the IBM tape drie, medium changer, and library deice driers: How to Send Your Comments American National Standards Institute Small Computer System Interface X3T9.2/ X3.180, X3B5/91-173C, X3B5/91-305, X X Reision 10H, and X3T9.9/91-11 Reision 1 Your feedback is important in helping us proide the most accurate and best quality information. If you hae comments or suggestions for improing this publication, you can send us comments electronically by using these addresses: Internet: starpubs@us.ibm.com IBMLink from U.S.A.: STARPUBS at SJEVM5 IBMLink from Canada: STARPUBS at TORIBM IBM Mail Exchange: USIB3VVD at IBMMAIL Fax from U.S.A., Canada, and other countries: xi IBM Tape Deice Driers Installation and User s Guide

17 Special Printing Instructions This Tape Deice Driers Installation and User's Guide contains different sections for each type of operating system/platform; for example, AIX, Tru64, HP-UX, Linux, Sun Solaris, Windows; and a separate section on these operating systems for the 3494 Enterprise Tape Library. Note: When selecting the page range for the section you wish to print, note that the print page range is based on the page controls for Adobe Acrobat, not the page printed on the actual document. Enter the Adobe page numbers to print. Important printer note This area indicates the pages that will actually print in your specified range of pages. Ignore the page number appearing on the page itself when entering page ranges for your printer. If you wish to print one or more separate sections of the manual, follow these steps: 1. Naigate to the beginning of the section and note the page number. 2. Naigate to the last page in the section and note that page number. 3. Select File > Print, then choose "Pages" and enter the page range for the section. Only the page range entered prints. 4. Repeat these steps to print additional sections. Attention: There is only one Table of Contents and one Index for this entire book. If you wish to print those items, you must repeat the process aboe, entering the page range for the Table of Contents and the Index page range, respectiely. Preface x

18 xi IBM Tape Deice Driers Installation and User s Guide

19 Chapter 1. Introduction This publication describes the IBM Tape and Medium Changer Deice Driers and IBM Tape Diagnostic Tool (ITDT) for arious operating systems. Not all deices are supported by ITDT and all operating systems driers. Refer to the specific chapters for details. Purpose The IBM tape and medium changer deice driers are designed specifically to take adantage of the features proided by the IBM tape dries and medium changer deices. The goal is to gie applications access to the functions required for basic tape functions (such as backup and restore) and medium changer operations (such as cartridge mount and demount), as well as to the adanced functions needed by full tape management systems. Wheneer possible, the drier is designed to take adantage of the deice features transparent to the application. Please note that some independent software endor (ISV) applications hae certain deice drier requirements. Before you install the deice driers, please refer to the ISV web site for their support to find out what deice driers should be used for the ISV. IBM Tape Products The IBM Tape product family proides an excellent solution for customers with small to large storage and performance requirements. Current Products Figure 1 on page 2 illustrates the attachment of arious current products to an open systems serer. Copyright IBM Corp. 2007,

20 System Storage System Storage Introduction dd Figure 1. Current Attachment Array 1 Open Systems Serer 2 IBM Virtualization Engine TS7520/TS IBM Virtualization Engine TS IBM TS2230/TS2240/TS2250 Ultrium 3/4/5 Half-High Tape Drie 5 IBM TS2340/TS2350 (or 3580) Ultrium 3/4/5 Full-High Tape Drie 6 IBM TS1120/TS1130 Tape Drie [also known as Enterprise] 7 IBM TS3200 Tape Library 8 IBM TS3500 Tape Library 9 IBM TS3310 Tape Library 10 IBM TS3400 Tape Library 11 IBM TS3100 Tape Library Figure 2 on page 3 illustrates an Ultrium enironment that could include an IBM 3583 Tape Library and an IBM TS3500 Tape Library. 2 IBM Tape Deice Driers Installation and User s Guide

21 Introduction Open Systems Serer IBM Tape Deice Drier IBM Tape Drie IBM Tape Drie Medium Changer Robot IBM Tape Library Tape Cartridges a Figure 2. Example of an IBM Tape Enironment IBM Virtualization Engine TS7520 The IBM Virtualization Engine TS7520 product is a irtual-tape solution designed to help optimize tape processing. Through the implementation of an integrated, tiered storage hierarchy of disk and tape, the benefits of both technologies can be leeraged to help enhance performance and proide the capacity needed for today's tape processing requirements. Deploying this innoatie offering can help reduce batch processing time and management oerhead. IBM Virtualization Engine TS7650 Disk storage can be expensie, and simply increasing disk capacity year after year is a no-win strategy. IBM Virtualization Engine TS7650 with ProtecTIER tackles the problem by eliminating the abundance of redundant data creating more capacity in the disks: up to 25 times more capacity. ProtecTIER, featuring HyperFactor technology, uses powerful algorithms to filter out duplicate data so that only new data items are stored. The result is superior inline performance, unmatched scalability and enterprise data integrity. ProtecTIER employs blazing fast performance, able to process up to 900 megabytes per second in a clustered configuration, and it's done in-line, de-duplicating data in real time as it is written to your back-up deice. IBM System Storage TS2230/TS2240/TS2250 Tape Drie The IBM System Storage TS2230 Tape Drie Model H3L (Machine Type 3580, Model H3L, SAP part number 3580L3E) is a high-performance, high-capacity data-storage deice that is designed to backup and restore open systems applications. This model incorporates the Linear Tape Open (LTO) IBM Ultrium 3 Half-High Tape Drie. It is aailable with a Small Computer Systems Interface (SCSI) or with a Serial Attached SCSI (SAS) interface. The drie has a natie storage capacity of 400 GB per cartridge (800 GB at 2:1 compression) on the Ultrium 3 data cartridge. The IBM System Storage TS2240 Tape Drie is an excellent tape storage solution for businesses requiring backup or low-cost, real-time archial storage of their data. The TS2240, with a half-high form factor, offers the same high capacity of full-high LTO 4 tape dries. The TS2240 has a physical storage capacity of up to 1.6 TB (with 2:1 compression) in conjunction with the IBM System Storage LTO Ultrium 800 GB data cartridge, which proides up to double the capacity of Ultrium 3 cartridges. The natie data transfer performance of the TS2240 Tape Drie has increased oer the preious LTO half-high generation to up to 120 MB/sec. The TS2240 Tape Drie continues to proide an excellent alternatie to Chapter 1. Introduction 3

22 Introduction slower and smaller capacity 1/4-inch, 4 mm and 8 mm DLT/SDLT tape dries. The TS2240 proides added security features by supporting encryption of data with 3 Gbps SAS connectiity. The IBM System Storage TS2250 Tape Drie is an excellent tape storage solution for businesses requiring backup or low-cost, real-time archial storage of their data. The TS2250, with a half-high form factor, offers the same high capacity of full-high LTO 5 tape dries. The TS2250 has a physical storage capacity of up to 3.0 TB (with 2:1 compression) in conjunction with the IBM System Storage LTO Ultrium 1500 GB data cartridge for LTO5, which proides nearly double the capacity of IBM System Storage LTO Ultrium 800 GB data cartridge for LTO4. The natie data transfer performance of the TS2250 Tape Drie has increased oer the preious LTO half-high generation to up to 140 MB/sec. The TS2250 Tape Drie continues to proide an excellent alternatie to slower and smaller capacity 1/4-inch, 4 mm and 8 mm DLT/SDLT tape dries. The TS2250 proides added security features by supporting encryption of data with 6 Gbps SAS connectiity. IBM System Storage TS2340/TS2350 Tape Drie The IBM System Storage TS2340 Tape Drie [also known as IBM LTO4] is a high-performance, high-capacity data-storage deice for the midrange open systems enironment. It is designed to increase maximum tape drie throughput natie data rate performance up to 120 MB/sec compared to the IBM LTO generation 3 Tape Drie (Ultrium 3) at 80 MB/sec natie data transfer rate. In addition, with the use of the new IBM LTO Ultrium 800 GB Data Cartridge, the Ultrium 4 Tape Drie doubles the tape cartridge capacity up to 800 GB natie physical capacity (1600 GB with 2:1 compression). It is aailable with Small Computer System Interface (SCSI) or Serial Attached SCSI (SAS) interface. The Ultrium 4 SAS Tape Drie is encryption-capable and designed to support Application Managed Encryption. The IBM System Storage TS2350 Tape Drie [also known as IBM LTO5] is a high-performance, high-capacity data-storage deice for the midrange open systems enironment. It is designed to increase maximum tape drie throughput natie data rate performance up to 140 MB/sec compared to the IBM LTO generation 4 Tape Drie (Ultrium 4) at 120 MB/sec natie data transfer rate. In addition, with the use of the new IBM LTO Ultrium 1500 GB Data Cartridge, the Ultrium 5 Tape Drie doubles the tape cartridge capacity up to 1500 GB natie physical capacity (3000 GB with 2:1 compression). It is aailable with Small Computer System Interface (SCSI) or Serial Attached SCSI (SAS) interface. The Ultrium 5 SAS Tape Drie is encryption-capable and designed to support Application Managed Encryption. IBM TotalStorage 3580 (Ultrium) Tape Drie (Models L33 and L3H) The IBM TotalStorage 3580 Tape Drie Model L33/L3H offers high-capacity, performance, and technology designed for the midrange open systems enironment. This model incorporates the Linear Tape Open (LTO) IBM TotalStorage Ultrium Tape Drie (Generation 3), which more than doubles maximum tape drie performance oer the Generation 2 LTO Ultrium Tape Drie (Ultrium 2). This tape drie comes with a SCSI Ultra160 LVD attachment, for connection to a wide spectrum of open system serers. The IBM LTO Ultrium 3-H Tape Drie and IBM LTO Ultrium 4 Half-High Tape Drie are high-performance, high-capacity data-storage deices in a half-height form factor that are designed to backup and restore open systems applications. Both dries can be integrated into an enclosure, such as a desktop unit, tape 4 IBM Tape Deice Driers Installation and User s Guide

23 Introduction autoloader, or tape library. They are aailable with a Small Computer Systems Interface (SCSI) or with a Serial Attached SCSI (SAS) interface. The IBM LTO Ultrium 3-H Tape Drie has a natie storage capacity of 400 GB per cartridge (800 GB at 2:1 compression). The IBM LTO Ultrium 4 Half-High Tape Drie has a natie storage capacity of 800 GB per cartridge (1600 GB at 2:1 compression). IBM System Storage TS1120/TS1130 Tape Drie (Enterprise) The IBM System Storage TS1120 Tape Drie is the second generation of the 3592 tape drie. It proides higher leels of performance, reliability, and cartridge capacity than the IBM TotalStorage Tape System 3590 and the 3592 tape drie. The TS1120 tape drie has a dual-ported 4-Gbps Fibre Channel interface, Fibre Channel attachment, and a new high-technology design that increases the natie data rate to 100 MB/sec. The IBM System Storage TS1130 Tape Drie features storage capability to help you establish easy access to data, better security, long-term retention and data goernance and regulatory compliance. The TS1130 tape drie offers high-performance flexible data storage with support for data encryption. IBM System Storage TS3200 Tape Library The IBM System Storage TS3200 Tape Library Express Model offers high capacity and performance technology for the midrange open systems enironments. The TS3200 Tape Library is an external 4U standalone or rack-mountable unit that can house both IBM LTO Ultrium full and half high tape dries. IBM System Storage TS3500 Tape Library (also known as IBM TotalStorage UltraScalable Tape Library 3584) The IBM System Storage TS3500 Tape Library is a highly scalable, automated tape library combining IBM automation technology for midrange to enterprise open systems enironments. The TS3500 Tape Library supports logical partitioning and can house both IBM LTO Ultrium and IBM TotalStorage Enterprise 3592 Tape Dries (in separate frames). With scalability of one to sixteen frames and up to 192 tape dries, the TS3500 tape library can hae an expanded aailable storage capacity of oer 5000 TB (with 3:1 compression) using TotalStorage Enterprise 3592 Tape Dries. IBM System Storage TS3310 Tape Library The IBM System Storage TS3310 Tape Library is a modular, scalable tape library designed to scale ertically with expansion for Linear Tape Open (LTO) tape cartridges, dries, and redundant power supplies. The base library module, model L5B, is the entry point for the product family. It contains all of the necessary robotics and intelligence to manage the 5U high library system, which houses up to 36 cartridges (30 storage slots and 6 Input/Output slots) and two LTO generation 3 tape dries. The TS3310 model L5B can be expanded with the addition of expansion units, the model E9U. Each model E9U contains 92 physical LTO cartridge storage cells and space for up to four LTO generation 3 tape dries. Additionally, the E9U has space for up to two (one redundant) power supply modules (At least one power supply module must be installed if a drie is present in the E9U). IBM System Storage TS3400 Tape Library The IBM System Storage TS3400 TAPE LIBRARY is designed to offer high performance drie technology and automation for the open systems enironment. The TS3400 Tape Library is an addition to the family of IBM System Storage tape library offerings. The TS3400 Tape Library is an external 5U stand-alone or rack-mountable unit that incorporates up to two IBM System Storage TS1120 Tape Chapter 1. Introduction 5

24 Introduction Dries Model 3592-E05 (Machine Type 3592, Model E05), which are ordered separately. It comes with 4 Gbps dual-ported switched fabric Fibre Channel attachment. The TS1120 Tape Drie has a natie data transfer rate of up to 100 MB/ sec. per drie. IBM System Storage TS3100 Tape Library The IBM System Storage TS3100 (Machine Type 3573) Tape Library proides a compact, high-capacity, low-cost solution for simple, unattended data backup. This unique design houses up to 22 tape cartridges in a compact 2U form factor with easy access to tape cartridges ia two remoable magazines and an Input/Output (I/O) Station. Legacy Products IBM TotalStorage Ultrium Scalable Tape Library 3583 The IBM TotalStorage Ultrium Scalable Tape Library 3583 is an automated tape library that incorporates IBM Ultrium tape dries in either a stand alone or optional rack mount configuration. Three different library models are aailable with storage capacities of 18 through 72 slots and one to six Ultrium tape dries. The IBM TotalStorage Ultrium Scalable Tape Library 3583 can be used for sae, restore and mass storage archies where multi-terabyte capacities are required. IBM TotalStorage Ultrium Tape Library 3582 The IBM TotalStorage Ultrium Tape Library 3582 is an entry tape library incorporating high-performance IBM TotalStorage Ultrium generation 2 Tape Dries for the midrange open systems enironment. It can accommodate one or two Ultrium generation 2 Tape Dries and comes standard with a one-cartridge I/O station and 23 data cartridge slots giing a natie library capacity of 4.8 TB uncompressed natie storage. IBM TotalStorage Ultrium Tape 2U Autoloader 3581 The Ultrium Tape 2U Autoloader 3581 is an external 2U stand-alone or rack-mountable unit that incorporates a single IBM LTO Ultrium 2 tape drie. The Ultrium Tape 2U Autoloader 3581 capacity is eight tape cartridges, proiding a media capacity of up to 1.6 TB (3.2 TB with 2:1 compression) data storage per unit. The Model L28 comes with a LVD Ultra160 SCSI attachment, while the Model F28 comes with a Natie Switched Fabric Fibre Channel attachment, for connection to a wide spectrum of open systems serers. IBM TotalStorage Ultrium Tape Autoloader 3581 The IBM TotalStorage Ultrium Tape Autoloader 3581 is an external, stand-alone, or rack-mounted tape autoloader that incorporates one IBM Ultrium Tape Drie. The autoloader has seen storage slots giing the autoloader up to 1,400 GB of uncompressed data storage. The autoloader can be used with compatible software applications to automate backup/recoery or other data storage actiities. IBM TotalStorage Ultrium External Tape Drie 3580 The IBM TotalStorage Ultrium External Tape Drie 3580 is a stand alone, large capacity, high performance tape drie that adheres to the Linear Tape Open (LTO) specifications and supports the IBM Ultrium format tape. The drie supports natie tape capacities of up to 200 GB with uncompressed data transfer rates of up to 35 MB per second. With both Low Voltage Differential (LVD) Ultra-2 SCSI and High Voltage Differential (HVD) Ultra SCSI attachments, this deice is suitable for a ariety of sae, restore, and archiing requirements for PC and Open Systems operating systems. 6 IBM Tape Deice Driers Installation and User s Guide

25 Introduction StorageSmart by IBM Ultrium Products The StorageSmart by IBM Ultrium family of products is compatible with the IBM branded ersions of the Ultrium family products. In this manual, where there is no specific mention of the StorageSmart by IBM Ultrium branded set of products, the documentation pertaining to the IBM branded family of products should be used. Table 1 cross references the StorageSmart by IBM Ultrium product set to the IBM Ultrium product set. Table 1. Ultrium Product Comparison StorageSmart by IBM Ultrium StorageSmart by IBM Ultrium External Tape Drie TX200 StorageSmart by Ultrium Tape Autoloader SL7 StorageSmart by Ultrium Scalable Tape Library SL72 No equialent in the IBM Ultrium product set IBM Version of Ultrium IBM TotalStorage Ultrium External Tape Drie 3580 IBM TotalStorage Ultrium Tape Autoloader 3581 IBM TotalStorage Ultrium Scalable Tape Library 3583 IBM TotalStorage UltraScalable Tape Library 3584 IBM TotalStorage Enterprise Automated Tape Library 3494 The IBM TotalStorage Enterprise Automated Tape Library 3494 is an automated tape library, proiding an automated tape solution to a ariety of system enironments. It proides a solution for automating tape operations such as sae/restore, migration of data between direct access storage deices (DASD) and tape, and other mass data applications. IBM TotalStorage Enterprise Tape System 3590 The IBM TotalStorage Enterprise Tape System 3590 consists of a tape drie combined with an automatic cartridge facility (ACF). In addition to the functions that the ACL or CSL proide for the IBM 3490E Magnetic Tape Subsystem, the ACF on the Enterprise Tape System 3590 can operate as an integrated medium changer deice to proide random access of cartridges in the magazine cells under program control. Note: The 3590 drie has two Fibre Channel addressing modes. When attaching an open systems serer to a 3590 Fibre Channel drie, you must use the hard addressing mode. When attaching a 3590 drie directly to a host (without a switch), use lower addresses for hosts and higher addresses for dries. IBM TotalStorage Virtual Tape Serer (Models B10, B18, and B20) The IBM TotalStorage Virtual Tape Serer (VTS) product deliers an increased leel of storage capability to the traditional storage product hierarchy. To the host software, a VTS subsystem looks like a 3490E Enhanced Capability Tape Subsystem with associated Cartridge System Tape or Enhanced Capacity Cartridge System Tape. IBM Magstar MP 3570 Tape Subsystem The IBM Magstar MP 3570 Tape Subsystem consists of one or two tape dries (depending on the model) integrated with a full capability medium changer robotic facility, which proides random access of cartridges in the storage cells under program control. Chapter 1. Introduction 7

26 Introduction IBM Magstar MP 3575 Tape Library Dataserer The IBM Magstar MP 3575 Tape Library Dataserer is a scalable family of high-performance tape libraries that use the IBM Magstar MP tape dries. The IBM deice driers control both the Magstar MP tape dries and the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. IBM Virtualization Engine TS7510 The IBM Virtualization Engine TS7510 product deliers and increased leel of storage capability to the traditional storage product hierarchy. To the host software, the IBM Virtualization Engine TS7510 looks like a 3584 library with associated tape dries. IBM 3490E Magnetic Tape Subsystem The IBM 3490E Magnetic Tape Subsystem consists of one or two tape dries (depending on the model) combined with an automatic cartridge loader (ACL) or cartridge stack loader (CSL). The ACL or CSL can load the next tape from the cartridge stack into the tape drie either automatically when a tape is unloaded, or when the tape drie is under program control. IBM mm Tape Cartridge Autoloader The IBM Magstar MP 3575 Tape Library Dataserer is a scalable family of high-performance tape libraries that use the IBM Magstar MP tape dries. The IBM deice driers control both the Magstar MP tape dries and the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. IBM 7331, 7334, 7336, or 7337 Tape Medium Changer The IBM 7331 and 7334 products are 8mm Tape Medium Changer Library deices. The IBM 7336 product is a 4mm Tape Medium Changer Library deice. The IBM 7337 product is a DLT Tape Medium Changer Library deice. The AIX Enhanced Deice Drier controls the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. Access to the tape dries within these libraries is through the natie operating system AIX Tape Deice Drier. 8 IBM Tape Deice Driers Installation and User s Guide

27 Chapter 2. Common Extended Features Purpose Supported Hardware Supported Applications Path Failoer and Load Balancing Automatic Failoer Multiple HBA and Multi-Port Deices Multiple HBA and Single Ports Single HBA and Multi-Port Deices Dynamic Load Balancing Supported Deices and Feature Codes Data Encryption Tape and Library Requirements Planning for Application-Managed Tape Encryption Planning for System-Managed Tape Encryption 16 Planning for Library-Managed Tape Encryption 18 Feature Codes (Encryption) Purpose Supported Hardware This chapter proides general information about the IBM Deice Driers. Refer to the specific operating system chapters for details on deice support. The tape driers are deeloped to support arious ersions of different platforms. For details on supported tape attachment please refer to the System Storage Interoperation Center website at Supported Applications If you use a third party application, consult with your application proider as to the compatibility with IBMtape. ftp://serice.boulder.ibm.com/storage/tape/lto_is_matrix.pdf For detailed requirements for each operating system, refer to the appropriate chapter. To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Path Failoer and Load Balancing Deice drier path failoer support configures multiple physical paths to the same deice within the deice drier and proides two basic functions: 1. Automatic failoer to an alternate physical path when a permanent error occurs on one path. 2. Dynamic load balancing for tape deices using multiple Host Bus Adapters (HBA). Path Failoer is supported on certain tape products with the latest IBM deice driers aailable on the following website: Instructions for downloading driers can be found in Appendix A, Accessing Documentation and Software Online, on page 317. Some deices require a path failoer feature code to be installed prior to enabling the path failoer support in the deice drier. Refer to Table 2 on page 13 for a list of supported deices and what path failoer feature code may be required for your machine type. Copyright IBM Corp. 2007,

28 Path Failoer Automatic Failoer The automatic failoer support proides error recoery on an alternate path when a permanent error occurs on the primary path. This is transparent to the running application. There are two types of Path Failoer, Data Path Failoer (DPF) and Control Path Failoer (CPF). They are closely related howeer the difference is that DPF is an automatic failoer support for the transfer of data, which proides error recoery for systems connected to tape dries while CPF is an automatic failoer support for the transfer of commands to moe tape cartridges. Below are examples of different configurations that can be constructed. Multiple HBA and Multi-Port Deices Consider a multipath connection that consists of two Host Bus Adapters (HBA) connected through a fabric to a multi-port deice. By haing two connections from each deice to the fabric, a configuration of four different physical paths can be set up. e.g. HBA A to port 1, HBA A to port 2, HBA B to port 1, and HBA B to port 2. One path is the primary path and the other three would be alternate paths. If the primary path should hae a failure, the Automatic Failoer would try switching to another configured path. Without path failoer support, if a permanent path error occurs (because of an HBA or cable failure, for example), the application fails. Howeer should that occur with this configuration there would still be two alid physical paths for the data to be transmitted on and the running application wouldn t be affected. Dual HBA Mulit-Port Drie (DPF) X Library (CPF) Drie Fabric X Drie Library Controller Drie X Virtual Tape Library (DPF and CPF) a Figure 3. Multiple HBA and multi-port deices Multiple HBA and Single Ports For another example, consider the same multipath connection that consists of two Host Adapters connected through a fabric to a single port deice. This configuration would supply two physical paths to the same deice, howeer, if the port or cable from the deice fails the automatic failoer would not work as that connection is seered and a permanent path error occurs. If howeer the failure was with one of the HBAs or their cables the automatic data path failoer would select the other HBA and the information would continue through the alternate path. 10 IBM Tape Deice Driers Installation and User s Guide

29 Path Failoer Dual HBA (DPF and CPF) Single-Port Drie X Fabric Library Drie Drie Library Controller Drie Virtual Tape Library a Figure 4. Multiple HBA and single ports Chapter 2. Common Extended Features 11

30 Path Failoer Single HBA and Multi-Port Deices Yet for another example, consider a single path from the HBA through the fabric to a multi-port deice. This also proides a failoer path unless the failure is with the HBA or the HBA s cable, at which point the connection is seered and a permanent path error occurs. Whereas, if the failure should occur on the deice side there is still an alternatie path aailable for the information to go through. Single HBA Mulit-Port Drie (DPF) X Library (CPF) Drie Fabric X Drie Library Controller Drie X Virtual Tape Library (DPF and CPF) a Figure 5. Single HBA and multi-port deices At startup or configuration, the system detects multiple logical deices of the tape drie. Each logical deice is a physical path to the same tape drie. A backup and restore application can open and use only one logical deice at a time because they represent the same physical deice. Without path failoer support, if a permanent path error occurs (because of an HBA or cable failure, for example), the application fails. It is possible to initiate manual failoer by restarting the application on the alternate logical deice, but the application has to be restarted from the beginning. A long back up or restore operation may hae been in progress when the path error occurred. Sometimes manual failoer may require operator interention to reset the drie because a SCSI Reseration could still exist on the failing HBA path. When the path failoer support is enabled on all logical deices, the deice drier configures them internally as a single deice with multiple paths. The application can still open and use only one logical deice at a time. If an application opens the primary deice and a permanent path error occurs, the deice drier initiates failoer error recoery automatically on an alternate path. If successful, the current operation continues on an alternate path without interrupting the application. The data path failoer error recoery first restores the preious deice state, SCSI Reseration, and tape position, and then retries the failing operation. 12 IBM Tape Deice Driers Installation and User s Guide

31 Path Failoer Dynamic Load Balancing The dynamic load balancing support optimizes resources for tape deices that hae physical connections to multiple Host Bus Adapters (HBA) in the same machine. When an application opens a deice that has multiple HBA paths configured, the deice drier determines which path has the HBA with the lowest usage, and assigns that path to the application. When another application opens a different deice with multiple HBA paths, the deice drier again determines the path with the lowest HBA usage and assigns that path to the second application. The deice drier updates the usage on the HBA assigned to the application when the deice is closed. Dynamic load balancing uses all Host Bus Adapters wheneer possible and balance the load between them to optimize the resources in the machine. For example, consider a machine with two Host Bus Adapters, HBA1 and HBA2, with multiple tape dries attached. Each tape drie is connected to both HBA1 and HBA2. Initially, there are no tape dries currently in use. When the first application opens a tape drie for use, the deice drier assigns the application to use HBA1. When a second application opens a tape drie for use, the deice drier assigns the second application to use HBA2. A third application would be assigned to HBA1 and a fourth application would be assigned to HBA2. There would be two applications using HBA1 and two applications using HBA2. If the first application finishes and closes the deice, there would now be one application using HBA1 and two applications using HBA2. When the next application opens a tape drie, it would be assigned to HBA1, so again there would be two applications using HBA1 and two applications using HBA2. Likewise, if the second application finishes and closes the deice, HBA2 would hae one application using it and the next application that opens a tape drie would be assigned to HBA2. The dynamic load balancing support is independent from the automatic failoer support. Regardless of the path assigned initially for load balancing, if that path fails, the automatic failoer support attempts recoery on the next aailable path. Supported Deices and Feature Codes Path failoer is supported only for the deices listed in Table 2. Path failoer includes Control Path Failoer (CPF) for tape libraries and Data Path Failoer (DPF) for tape dries. In order to use path failoer support, some deices require feature codes as listed in Table 2. Table 2. Supported Deices and Feature Codes Supported Tape Library/Drie Feature Code (FC), if required TS3500/3592 Standard, no FC required (CPF and DPF) TS3500/LTO FC 1682 (CPF and DPF) TS3400/3592 Standard, no FC required (CPF and DPF) TS3310/LTO FC 1682 (CPF and DPF) TS3200/LTO FC 1682 (CPF and DPF) TS3100/LTO FC 1682 (CPF and DPF) TS7520/Al FC 1682 (CPF and DPF) TS7650/All Standard, no FC required (DPF only) 3583 FC 1680 (CPF), FC 1681 (DPF) Chapter 2. Common Extended Features 13

32 Path Failoer Table 2. Supported Deices and Feature Codes (continued) Supported Tape Library/Drie Feature Code (FC), if required 3582 FC 1680 (CPF), FC 1681 (DPF) Note: 1. Path failoer is not supported on parallel SCSI (except for some parallel SCSI dries on AIX operating systems). Path Failoer is only supported on SAS deices attached to Windows and Linux for Intel/AMD processor based serers. 2. Path failoer is not supported on Virtual Tape Libraries (except for those listed in Table 2 on page 13) that emulate IBM tape deices. Data Encryption Tape and Library Requirements Encryption support is aailable in the IBM encryption-capable TS1120 and Ultrium LTO4 and LTO5 (Fibre Channel or SAS) tape dries that support encryption. If system-managed or library-managed encryption is used, the Transparent LTO Encryption feature code is required for the library with Ultrium LTO4 and LTO5 tape dries. This feature code is not required for TS1120 tape dries. Application-managed encryption does not require this feature code for any of encryption-capable tape dries. Refer to Feature Codes (Encryption) on page 19 for the feature code numbers. In the open system enironment, there are three methods of encryption management to choose from. These methods differ in where you choose to locate your encryption key manager application. Your operating enironment determines which is the best for you, with the result that key management and the encryption policy engine may be located in any one of the three enironmental layers: application layer, system layer, and library layer. Application-Managed Tape Encryption This method is best where operating enironments run an application already capable of generating and managing encryption policies and keys, such as Tioli Storage Manager (TSM). Policies specifying when encryption is to be used are defined through the application interface. The policies and keys pass through the data path between the application layer and the Encryption is the result of interaction between the application and the encryption-enabled tape drie, and is transparent to the system and library layers. Please refer to Planning for Application-Managed Tape Encryption on page 15 for details on the hardware and software requirements for application-managed encryption. For details on setting up application-managed tape encryption refer to the Tioli Storage Manager documentation or for more information, isit the following site: It is required to use the latest deice driers aailable. Please refer to Appendix A, Accessing Documentation and Software Online, on page 317 for downloading driers. 14 IBM Tape Deice Driers Installation and User s Guide

33 Data Encryption System-Managed Tape Encryption In this method, key generation and management is performed by an encryption key manager (EKM). Policy controls and keys pass through the data path between the system layer (deice driers) and the encryption-capable tape dries. Encryption is transparent to the applications. Note: The abbreiation EKM for the drier configuration file is used generically to refer to any encryption key manager. It is required to use the latest deice driers aailable on our web site. Please see Appendix A, Accessing Documentation and Software Online, on page 317 for instructions. Refer to Planning for System-Managed Tape Encryption on page 16 for details on the hardware and software requirements for system-managed encryption. For details on setting up system-managed encryption in different operating system enironment, refer to the applicable chapter for each operating system. Library-Managed Tape Encryption This method is best for encryption-capable tape dries in an open attached IBM tape libraries. Scratch encryption policies specifying when to use encryption are set up through the IBM System Storage Tape Library Specialist Web interface. Policies are based on cartridge olume serial numbers. Key generation and management is performed by an encryption key manager. Policy control and keys pass through the library-to-drie interface, therefore encryption is transparent to the applications. Please refer to Planning for Library-Managed Tape Encryption on page 18 for details on the hardware and software requirements for library-managed encryption. For details on setting up library-managed encryption on encryption-capable tape dries, please refer to the IBM System Storage Tape Library Operator's Guide for your library. Planning for Application-Managed Tape Encryption Note: Please contact your IBM Representatie for additional information about encryption on the IBM encryption-capable tape drie. In order to perform encryption on the encryption-capable tape drie, the following is required: Encryption-capable tape drie(s) Encryption configuration features: Library code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 and LTO5 dries Tape drie code updates Application-Managed Tape Encryption Setup Tasks Any task not identified as an IBM serice task is the responsibility of the customer. 1. Install, cable, and configure the encryption-capable tape drie (refer your IBM System Storage Tape Drie or Library Operator's Guide ) 2. Install appropriate IBM tape deice drier leel (Atape, for example). 3. Set up encryption policies. Refer to the appropriate TSM documentation. 4. Perform write/read operation to test encryption. Chapter 2. Common Extended Features 15

34 Data Encryption 5. Verify encryption of the test olume by Autonomic Management Engine (AME): issue QUERY VOLUME FORMAT=DETAILED Verify that Drie Encryption Key Manager is set to Tioli Storage Manager. Planning for System-Managed Tape Encryption Note: Please contact your IBM Representatie for additional information about encryption on the IBM encryption-capable tape drie. In order to perform encryption on the encryption-capable tape drie, the following is required: Encryption-capable tape drie(s) Keystore (Refer to documentation on Tioli Key Lifecycle Manager (TKLM)) Encryption configuration features: Tioli Key Lifecycle Manager (TKLM) Tape drie code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 and LTO5 dries Tape system library code updates Setup Tasks for System-Managed Tape Encryption on Open Systems Operating System Any task not identified as an IBM serice task is the responsibility of the customer. 1. Install, erify, and configure: a. Keystore b. EKM (Refer to documentation on Tioli Key Lifecycle Manager (TKLM)) Note: The SSL protocol in TKLM isn't supported with SME. 2. Install, cable, and configure encryption-capable tape drie (refer your IBM System Storage Tape Drie or Library Operator's Guide). 3. Install and enable appropriate Deice Drier Leel (refer to the appropriate operating system chapter in this document for more details) 4. Edit /etc/ibmekm.conf file. 5. Use [38] Test Encryp. Path (Test Encryption Key Path/Setup) on page 268 or Test Encryption Path on page 314 to erify. System-Managed Encryption Configuration Note: The tape drie must be set to system-managed encryption from the drie panel or library user interface before using deice drier system-managed encryption. After installing the deice drier, then an encryption key manager needs to be configured. The serers are configured in a text file ibmekm.conf that is installed in the /etc directory by the deice drier if a current configuration file does not already exist. Figure 6 on page 17 is an example of the sample configuration file installed. 16 IBM Tape Deice Driers Installation and User s Guide

35 Data Encryption # IBM Encryption Key Manager Configuration File # # (C) COPYRIGHT International Business Machines Corp # All Rights Resered # Licensed Materials - Property of IBM # # US Goernment Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # This file contains the TCP/IP address(s) and port(s) for the Encryption Key # Serer with a configuration entry in the following formats. The IP4 address # entered as x.x.x.x:port. The IP6 address entered as x:x:x:x:x:x:x:x port. # The serer is for information only and is not used. The timeout alue is # specified in seconds. # # The format for IP4 address: # serer timeout address:port # for example, # ekmtest :8050 # # The format for IP6 address: # serer timeout address port # for example, # ekmtest 10 fe80::207:30ee:edcb:d05d 8050 # # The Encryption Key Serer address and port can be a local loop back # address :port in IP4 format or ::1 port in IP6 format if the serer # is on the same host or a network address and port if external to the host. # Up to 16 serer address and port entries are supported if there are multiple # TCP/IP connections to the same serer and/or multiple serers. # # Interoperability between IP4 and IP6 ersions running on dual-stack hosts: # IP4 Client <--> IP4/IP6 Serer using IP4 address for EKM serer # IP6 Client <--> IP4 Serer using IP4 address for EKM serer # IP6 Client <--> IP6 Serer using IP6 address for EKM serer # # Sample entry for a local serer with a 10 second timeout using port 8050 # in IP4 format # ekmtest :8050 # # in IP6 format # ekmtest 10 :: Figure 6. Sample Encryption Configuration File The following shows the different entry formats for IP4 and IP6 addresses in the ibmekm.conf configuration file: IP4 format: EKMserer timeout IP4_address Port_number IP6 format: EKMserer timeout IP6_address Port_number To set up an IP address for an encryption key manager serer, use Table 3 to choose an appropriate IP address type and then add the IP address in the entry of the encryption configuration file. Table 3. Interoperability between IP4 and IP6 Clients and Serers IP4 EKM serer IP4-only host IP4 Client/IP4-only host IP6 EKM serer IP6-only host IP4 EKM serer dual-stack host IP4 (no) IP4 IP4 IP6 EKM serer Dual-stack host Chapter 2. Common Extended Features 17

36 Data Encryption Table 3. Interoperability between IP4 and IP6 Clients and Serers (continued) IP4 EKM serer IP4-only host IP6 Client/IP6-only host IP4 Client dual-stack host IP6 Client dual-stack host IP6 EKM serer IP6-only host IP4 EKM serer dual-stack host (no) IP6 (no) IP6 IP4 (no) IP4 IP4 IP4 IP6 (no) IP6 IP6 EKM serer Dual-stack host The timeout alue in seconds is used when a request is sent to the serer and the time for the serer to respond in case no response is receied. A maximum of 16 serer connections can be configured for failoer. When a connection can not be made or is lost on the current serer being used, the operation is retried on the next configured serer. After configuring serers in the ibmekm.conf file then specific tape dries need to be configured to the deice drier for system-managed encryption. The deice drier default does not enable encryption. Refer to the following sections for specific information depending on the operating system. Planning for Library-Managed Tape Encryption Note: Please contact your IBM Representatie for additional information about encryption on the IBM encryption-capable tape drie. In order to perform encryption on the encryption-capable tape drie, the following is required: Encryption-capable tape drie(s) Keystore (Refer to documentation on Tioli Key Lifecycle Manager (TKLM)) Encryption configuration features: Tioli Key Lifecycle Manager (TKLM) Tape system library code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 and LTO5 dries. Tape drie code updates Library-Managed Tape Encryption Tasks Any task not identified as an IBM serice task is the responsibility of the customer. 1. Install, erify, and configure a. Keystore b. EKM (Refer to documentation on Tioli Key Lifecycle Manager (TKLM)) for more information on both. 2. Install and cable the encryption-capable tape drie (IBM serice task for TS1120 Tape Drie). 3. Use IBM System Storage Tape Library Specialist to enable the tape drie for library-managed tape encryption (refer to your IBM System Storage Tape Drie or Library Operator's Guide). 4. Use library diagnostic functions to erify. 18 IBM Tape Deice Driers Installation and User s Guide

37 Bulk Rekey For customers using Library-Managed Encryption with 3592 Enterprise Tape Dries and IBM tape and changer driers running on open systems operating system (AIX, HP-UX, Linux, Solaris, Windows), sample code for performing bulk rekey operations is aailable. The sample code packages are proided "as-is" with limited testing, and are proided to gie customers guidance on bulk rekey operations. For Unix operating systems, a sample script (rekey_unix.sh) is proided and must be used in conjunction with the tapeutil ersion bundled in the same package. For Windows operating systems, a sample c program (rekey_win.c) is proided. Both of these sample programs must be used in conjunction with both the IBM tape and changer driers. In addition, data cartridges must be located in storage cells, not in I/O station cells or tape dries. For more information and to download the sample code packages, see Data Encryption Feature Codes (Encryption) In order to use system-managed and library-managed encryption, the Transparent LTO Encryption feature codes listed in Table 4 are required for the associated IBM tape libraries with Ultrium LTO4 and LTO5 tape dries. If the dries in use are TS1120 Tape Dries, this feature code is not required for system-managed or library-managed encryption. If you are using application-managed encryption, no feature code is required on any encryption-capable tape dries. Table 4. Feature Codes (Encryption) Tape Library Feature Code TS3500 FC 1604 TS3400 Standard Feature TS3310 FC 5900 TS3100/3200 FC 5900 Chapter 2. Common Extended Features 19

38 Data Encryption 20 IBM Tape Deice Driers Installation and User s Guide

39 Chapter 3. AIX Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Hardware Requirements Software Requirements Installation and Configuration Instructions Installation Procedure Configuring Tape and Medium Changer Deices 25 Deconfiguring Tape Deices Deconfiguring Medium Changer Deices Uninstalling Tape Drie, Media, and Deice Drier Parameters 26 Configuration Parameters Media Parameters Special Files Special Files for Tape Deices Special Files for Medium Changer Deices Persistent Naming Support Changing the Logical Name After Initial Boot.. 35 Control Path Failoer Support for Tape Libraries.. 36 Configuring and Unconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configurations Configuring and Unconfiguring Primary and Alternate Deices Data Path Failoer and Load Balancing Support for Tape Dries Installing Data Path Failoer License Key Configuring and Unconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configuration Configuring and Unconfiguring Primary and Alternate Deices System-Managed Encryption Deice Drier Configuration Querying Tape Drie Configuration Testing Data Encryption Configuration and Connectiity Error Logging Field Support Information Problem Determination Using the Dump Support Deice and Volume Information Logging Log File Tape Log Utility Reseration Conflict Logging Error Logging Error Log Templates Automatic Dump Facility Trace Facility Atape System Trace (ATRC) Utility Component Tracing Atape Component Trace (ACTRC) Utility Tape Drie Serice Aids Details of Tape Serice Aids Performance Considerations Data Path Common AIX Utilities AIX iostat Utility for Tape Performance Before Calling Support This chapter describes the IBM AIX Enhanced Tape and Medium Changer Deice Drier (Atape) for IBM tape deices. Purpose The IBM AIX Enhanced Tape and Medium Changer Deice Drier is designed specifically to take adantage of the features proided by the IBM tape dries and medium changer deices. The goal is to gie 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 adanced functions needed by full tape management systems. Wheneer possible, the drier is designed to take adantage of the deice features transparent to the application. Please note that some independent software endor (ISV) applications hae certain deice drier requirements. Before installing the deice driers, please refer to the ISV web site or their support to find out what deice driers should be used for the ISV. Copyright IBM Corp. 2007,

40 AIX Deice Drier (Atape) Data Flow The software described in this chapter coers the AIX Enhanced Deice Drier (Atape deice drier) and the interface between the application and the tape deice. For data flow, refer to Figure 7. Product Requirements Figure 7. Data Flow for AIX Deice Drier (Atape) The following hardware and software components are supported by IBM. Hardware Requirements The following hardware is supported by the Atape deice drier: One or more of the following IBM RS/6000 or System p (also known as pseries) SCSI host bus adapters for libraries containing Ultrium tape dries: PCI-X DDR Dual -x4 SAS Adapter (FC 5900 and FC 5912) PCI Dual Channel Ultra-3 SCSI Adapter (LVD) (FC 6203) PCI Differential Ultra SCSI Adapter (HVD) (FC 6207) PCI Uniersal Differential Ultra SCSI Adapter (HVD) (FC 6204) Integrated Ultra2 SCSI Adapter for LVD attachment (with a VHDCI connector): - System p (also known as pseries) 620 (7025-6F0, 6F1) F80 - System p (also known as pseries) 660 (7026-6H0, 6H1, 6M1) - System p (also known as pseries) 640 ( B80) H80, M , 270 Integrated Ultra3 SCSI Adapter for LVD attachment (with a VHDCI connector): - System p (also known as pseries) 610 (7028-6C1, 6E1) - System p (also known as pseries) 630 (7028-6C4, 6E4 - System p (also known as pseries) 650 (7038-6M2) - System p (also known as pseries) 655 ( ) PCI Dual Channel Ultra-2 SCSI Adapter (LVD) (FC 6205) PCI-X Dual Ultra320 SCSI Blind Swap Adapter (FC 5710) PCI-X Dual Channel Ultra 320 SCSI Adapter (FC 5712) PCI-X Dual Channel Ultra 320 SCSI Adapter (FC 5736) One or more of the following IBM RS/6000 or System p (also known as pseries) FC-AL host bus adapters for TS1120 tape dries and all IBM libraries: Gigabit Fibre Channel Adapter (PCI) (FC 6227) Gigabit Fibre Channel Adapter for 64 bit PCI bus (FC 6228) 22 IBM Tape Deice Driers Installation and User s Guide

41 AIX Deice Drier (Atape) Two Gigabit Fibre Channel Adapter (PCI X) (FC 6239) Two Gigabit Fibre Channel Adapter (PCI-X) (FC 5716) Four Gigabit Fibre Channel Adapter (PCI-X) (FC 5758 and FC 5759) Four Gigabit Fibre Channel Adapter (PCI-E) (FC 5773 and FC 5774) For the 3490E and Magstar deices, one of the following RS/6000 or System p (also known as pseries) host adapters: Micro Channel SCSI Adapters - RS/6000 or System p (also known as pseries) FC 2412 Enhanced SCSI-2 Differential Fast/Wide Adapter/A - RS/6000 or System p (also known as pseries) FC 2416 SCSI-2 Differential Fast/Wide Adapter/A - RS/6000 or System p (also known as pseries) FC 2420 SCSI-2 Differential High Performance External I/O Controller (limited to seen SCSI IDs) PCI SCSI Adapters - RS/6000 or System p (also known as pseries) FC 2409 PCI SCSI-2 Differential Fast/Wide Adapter - RS/6000 or System p (also known as pseries) FC 6209 PCI SCSI-2 Differential Fast/Wide Adapter - RS/6000 or System p (also known as pseries) FC 6207 PCI Differential Ultra SCSI Adapter - RS/6000 or System p (also known as pseries) FC 6204 PCI Uniersal Differential Ultra SCSI Adapter For 733x deices, refer to the specific product document for hardware attachment requirements. The IBM TotalStorage Enterprise Tape System 3590 Model E and Model H Tape Dries with Fibre Channel Attachment, is supported with the System p (also known as pseries) FC 6227 or FC 6228 Gigabit Fibre Channel Adapters and FC Gigabit Fibre Channel PCI-X Adapters. The following SCSI-attached deices are supported through the IBM 2108-G07 (SAN Data Gateway) attached to the FC 6227 or FC 6228 Gigabit Fibre Channel Adapters and FC Gigabit Fibre Channel PCI-X Adapters: IBM TotalStorage Enterprise Tape System 3590, Models B11, B1A, E11, E1A, H11, and H1A IBM TotalStorage Virtual Tape Serer (Models B10, B18, and B20) IBM Magstar MP 3570 Tape Subsystem Model C IBM Magstar MP 3575 Tape Library Dataserer The IBM TotalStorage Enterprise Tape System 3592 Model J is supported with FC Gigabit Fibre Channel PCI-X Adapters. Four Gigabit Fibre Channel Adapter (PCI-E) (FC 5773 and FC 5774) The 8 Gigabyte Fibre Channel Adapter (FC 5735) is supported on pseries for the following tape dries and libraries. This adapter also supports N_Port ID Virtualization (NPIV) and AIX VIOS clients if the AIX VIOS serer with this adapter is configured for NPIV to run on the VIOS clients. TS1130 (3592 E06) Enterprise Drie IBM Enterprise Tape Library - TS3400 (3577) Library - TS3500 (3584) Library TS1120 (3592 E05) Enterprise Drie IBM Enterprise Tape Library Chapter 3. AIX Tape and Medium Changer Deice Drier 23

42 AIX Deice Drier (Atape) - TS3400 (3577) Library - TS3500 (3584) Library Ultrium TD4 LTO dries - TS3100 (3573-L2U) Library - TS3200 (3573-L4U) Library - TS3500 (3584) Library Ultrium TD3 LTO dries - TS3100 (3573-L2U) Library - TS3200 (3573-L4U) Library - TS3500 (3584) Library Note: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is generally not recommended. Tape and disk deices require incompatible HBA settings for reliable operation and optimal performance characteristics. Under stress conditions (high I/O rates for either tape, disk, or both) where disk and tape subsystems share a common HBA, stability problems hae been obsered. These issues are resoled by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring serer/storage configuration interoperability. We strongly recommend that your oerall implementation plan includes proisions for separating disk and tape workloads. Software Requirements The AIX Enhanced Deice Drier (Atape deice drier) supports AIX 5L Version 5.3 and later releases on IBM POWER-based AIX serers. To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Installation and Configuration Instructions The recommended procedure for installing a new ersion of the deice drier is to uninstall the preious ersion. Instructions for uninstalling the deice drier are outlined below in Uninstalling on page 26. Attention: At the end of the installation procedure, the installp facility automatically runs the AIX bosboot command to update the boot record with the newly installed Atape files. When the bosboot command completes, the following messages are displayed: This update does not fully take effect until after a system reboot. installp: bosboot process completed. This message is referring to the updates to the boot record only. If the installation summary shows that the Atape drier was installed successfully, it is not necessary to reboot the machine at this time. If the installation summary shows that the install failed, you should reboot the machine and attempt to install the Atape drier a second time. 24 IBM Tape Deice Driers Installation and User s Guide

43 AIX Deice Drier (Atape) Installation Procedure For information on obtaining the latest ersion of deice driers and the latest documentation, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Preinstallation Considerations Before proceeding with the installation, erify the following items: 1. The tape deice is properly functioning, properly attached to the serer, and is powered up. 2. You hae logged onto the serer on an account which has root authority. 3. You hae a command shell window open on the serer to perform the installation procedure. 4. Make sure the current path is defined in the command shell PATH ariable. This can be accomplished in the korn shell using the following command: EXPORT PATH=.:$PATH 5. If the tape deice was configured preiously by another deice drier (not Atape), remoe any existing deice definitions for it. The following command is an example: rmde -l ost1 -d Installation Procedure Enter the following command to list the currently installed Atape.drier ersion: lslpp -l Atape.drier Enter the following command to install the Atape drier in the current directory for example installp -acxd Atape.x.x.x.x Atape.drier This installs and commits the Atape drier on the system. Configuring Tape and Medium Changer Deices After the drier software is installed and a tape deice is connected to the adapter, the deice can be configured and made aailable for use. Access to the deice is not proided until the deice is configured. Note: If the tape deice was configured preiously by another SCSI deice drier, such as OST (Other SCSI Tape), issue the following command to remoe the deice definition before performing the following steps: rmde -l [deice] Configure a tape deice using one of the following procedures: Enter the following command with no parameters: cfgmgr The command configures all deices automatically (including any new tape or medium changer deices). or Power Off your subsystem and reboot the system to configure it automatically and make aailable any new tape or medium changer deices on the system. Chapter 3. AIX Tape and Medium Changer Deice Drier 25

44 AIX Deice Drier (Atape) Deconfiguring Tape Deices Note: In the following examples, replace the letter n with the appropriate number for the chosen deice. Deconfigure the tape deice using one of the following procedures: 1. The first method leaes the tape deice defined in the configuration database. It is similar to bringing the deice offline (not in use). Enter the following command to bring the /de/rmtn tape deice offline, but leae it defined in the deice database: rmde -l rmtn 2. The second method brings the tape deice offline and remoes its definition from the deice database. Enter the following command: rmde -l rmtn -d The deice drier is not unloaded from the kernel until the last deice is deconfigured. Deconfiguring Medium Changer Deices Uninstalling Note: In the following examples, replace the letter n with the appropriate number for the chosen deice. Deconfigure the medium changer deice using one of the following procedures: 1. The first method leaes the deice defined in the configuration database. It is similar to bringing the deice offline. Enter the following command to bring the /de/smcn medium changer deice offline, but leae it defined in the deice database: rmde -l smcn 2. The second method brings the medium changer deice offline and remoes its definition from the deice database. Enter the following command: rmde -l smcn -d The deice drier is not unloaded from the kernel until the last deice is deconfigured. Attention: All deices that use the Atape drier must be closed and cannot be in use when Atape is uninstalled or the uninstall fails. You can uninstall the Atape deice drier using the smit command menu to uninstall software and selecting Atape.drier or using the following installp command: installp -u Atape.drier Tape Drie, Media, and Deice Drier Parameters This chapter describes the parameters that control the operating modes of the AIX Enhanced Tape and Medium Changer Deice Drier. 26 IBM Tape Deice Driers Installation and User s Guide

45 AIX Deice Drier (Atape) Configuration Parameters The operating parameters for the tape drie and deice drier are set and changed by configuration parameters. The installation defaults are proided for all parameters initially. The AIX smit command is used to set these parameters when configuring a deice or to change these parameters. The AIX chde command is used to change the configuration parameters. The configuration parameters are used to set the operating mode of the tape drie and deice drier when a deice is opened. These parameters can be queried by an application. Some parameters can be temporarily changed during the open subroutine by an application, but they are always restored to the configuration alues when a deice is closed. The configuration parameters are: Alternate Pathing Autoloading Emulate autoloader (359x deices only) Block size Buffered mode (359x deices only) Compression Fail degraded media (359x deices only) Logging Maximum size of the log file New logical name Read error recoery time (359x deices only) Record space mode Reseration key Reseration type Rewind immediate System encryption System encryption for Write Commands Trailer labels Alternate Pathing This parameter enables or disables the path failoer support when a deice is configured. Data Path Failoer and Load Balancing Support for Tape Dries on page 38 for a description of the path failoer and failoer support. The installation default is no (path failoer is not enabled). Autoloading This parameter enables the autoloading feature of the deice drier. It is used with the autoloading capability of the autoloader, ACF, ACL, or CSL installed on the tape deice. Note: The autoloading feature is not supported on the IBM 3584 UltraScalable Tape Library and the IBM 3583 Ultrium Scalable Tape Library with more than one IBM 3580 Ultrium Tape Drie installed. Note: The autoloading feature is supported only on the following deice types and configurations: IBM 3490E Models C11, C22, E01, E11, F01, and F11 IBM TotalStorage Enterprise Tape System 3590, Models B11, E11, and H11 Chapter 3. AIX Tape and Medium Changer Deice Drier 27

46 AIX Deice Drier (Atape) IBM Magstar MP 3570 Models B01, C01, B11, and C11 IBM Magstar MP 3570 Models B02, B12, C02, and C12 (configured in split mode only) IBM 7332 (all models) Do not enable autoloading if one of the following conditions is true: The deice is used by an application that proides library medium changer support for the IBM 3581 or IBM The deice is installed in a 3494 Enterprise Tape Library. The deice is used by an application with stack loader support. The application is MKSYSB. The tapes being read were not written using the autoloading feature. Tapes created with AUTOLOAD=YES may not be readable in configurations without Atape autoload enabled, or on other UNIX operating systems, or on deice types/models that are different from the backup deice type/model. If the parameter is set to on, then the tape stacker acts as one large irtual tape. During a read, write, or forward space file operation, no end of tape is detected by the application. When the end of tape is reached, the deice drier automatically rewinds and unloads the tape, loads the next tape, then continues reading or writing the next tape. The following conditions are required to use this feature: The autoloading parameter must be set to On. The cartridge stacker must be loaded with one or more tapes. The ACF, ACL, or CSL must be set to Automatic, System, or Random mode. This feature allows multiolume backups (with commands such as tar) without prompting for a olume change. The installation default is Off (no autoloading). Emulate Autoloader This parameter controls how the deice drier operates when the ACF on the IBM TotalStorage Enterprise Tape System 3590, the IBM Magstar MP tape deice, or the IBM 3490E Model Fxx is set to Random mode. If this parameter is set to On and the ACF is in Random mode, the deice drier emulates an autoloading tape drie. When an unload command is sent to the deice drier to unload a tape, the tape is unloaded, returned to the magazine, and the next tape in the magazine is loaded automatically into the tape drie. If this parameter is set to Off, the normal unload operation occurs, and the tape remains in the drie. The emulate autoloader parameter can be used for legacy applications written for the IBM 3490E Automated Cartridge Loader (ACL) when the IBM TotalStorage Enterprise Tape System 3590, the IBM Magstar MP 3570, or the IBM 3490 Model F autoloader is set to Random mode. This eliminates the need to re-configure the autoloader of the deice Random or Automatic operation. The installation default is Off (do not emulate autoloader). Note: On IBM Magstar MP 3570 Models B02, C02, and C12, this feature is supported only when the two dries are configured in Split mode, or in Base mode with only one drie configured and aailable to AIX. This feature does not work in Base mode if both dries are in the aailable state to AIX. 28 IBM Tape Deice Driers Installation and User s Guide

47 Block Size This parameter specifies the block size used for read and write operations. A alue of zero is the ariable block size. Any other alue is a fixed block size. The installation default is zero (use ariable length) except for the IBM mm Tape Cartridge Autoloader, for which the default is a fixed block size of 1024 bytes. Buffered Mode When a write command is processed, the data is either stored directly on the physical tape or buffered in the tape deice. Buffering can increase the deice performance. The installation default is On (use Buffered mode). Compression Hardware compression is implemented in the deice hardware. This parameter turns the compression feature On and Off. If compression is enabled, then the effectie performance can increase based on the compressibility of the data. The installation default is On (use compression). Fail Degraded Media This parameter controls whether the deice drier fails a tape operation when degraded media is detected by the IBM TotalStorage Enterprise Tape System If a tape is loaded and the IBM 3590 cannot read the positioning information from the tape, the deice drier is notified when the first command is sent to the tape drie. If this parameter is set to On, the deice fails the command and returns a media error to the application. If this parameter is set to Off, the deice drier does not fail the command. Degraded media is a correctable condition that preents the IBM TotalStorage Enterprise Tape System 3590 from performing high speed Locate operations. A Locate command can take oer 20 minutes, depending on the desired position and the amount of data on the tape. This parameter is intended for use by real time applications that cannot tolerate long Locate commands. The installation default is Off (do not fail the tape operation if degraded media is detected). Logging This parameter turns the olume information logging on and off. If logging is set to On, the statistical information about the deice and media is saed in a log file when a tape is unloaded. If logging is set to Off, the information is not saed. This parameter has no effect on error logging because error logging is always enabled. For more information, refer to Deice and Volume Information Logging on page 42. The installation default is Off (no logging). AIX Deice Drier (Atape) Maximum Size of the Log File This parameter specifies the number of entries made before the log file starts to wrap. Each entry is approximately 2 KB (2048 bytes). After the log file starts to wrap, the number of entries stays constant. Each time a new entry is made, the oldest entry is oerlaid. For more information, refer to Deice and Volume Information Logging on page 42. Chapter 3. AIX Tape and Medium Changer Deice Drier 29

48 AIX Deice Drier (Atape) The installation default is 500. New Logical Name Setting this parameter changes the logical name of the deice to a new name as specified. After the logical name is changed, the new logical name parameter is cleared. For more information, refer to Persistent Naming Support on page 35. There is no installation default alue for this parameter. Read Error Recoery Time This parameter controls the read error recoery time for the IBM TotalStorage Enterprise Tape System If this parameter is set to On, the recoery time for read errors is limited to a maximum of 5 seconds. If this parameter is set to Off, full recoery is used by the deice and can take up to 10 minutes. This parameter is intended for use by real-time applications that cannot tolerate long delays when reading data from the tape. The installation default is Off (do not limit the read error recoery time). Record Space Mode This parameter specifies how the deice drier operates when a forward or backward space record operation encounters a filemark. The two modes of operation are SCSI and AIX. The SCSI mode is the default mode of operation. When a forward or backward space record operation is issued to the drier and a filemark is encountered, the deice drier returns -1 and the errno ariable is set to input/output error (EIO). The tape is left positioned after the filemark (the end-of-tape side of the filemark on the forward space and the beginning-of-tape side of the filemark on the backward space). The AIX mode returns the same EIO errno alue as the SCSI mode when a filemark is encountered except that the tape is left positioned before the filemark (the beginning-of-tape side of the filemark on the forward space and the end-of-tape side of the filemark on the backward space). The installation default is SCSI mode. Reseration type This parameter specifies the SCSI Reseration type that will be used by the deice drier, either a SCSI Resere 6 command or a SCSI Persistent Resere command. Note: This parameter is not used if the Alternate Pathing (path failoer) parameter is set to yes. The deice drier will use SCSI Persistent Resere when the Alternate Pathing parameter is set to yes. The installation default is SCSI Resere 6. Reseration key This parameter specifies the SCSI Persistent Reseration key that will be used by the deice drier when either the Reseration Type parameter is SCSI Persistent Resere and the Alternate Pathing parameter is set to no or when the Alternate Pathing parameter is set to yes. The default for this attribute is blank (NULL). 30 IBM Tape Deice Driers Installation and User s Guide

49 AIX Deice Drier (Atape) If the Reseration Key parameter is specified as blank (NULL) then the deice drier will use an internal unique key for all deices on the host they are configured on. Another AIX host sharing the same deices would also hae an internal unique key for all deices if the Reseration Key parameter was blank (NULL). If the default aboe is not used then the Reseration Key alue can be specified as either a 1-8 character ASCII alphanumeric key or a 1-16 hexadecimal key that has the format 0xkey. If less than 8 characters are used for an ASCII key such as host1, the remaining characters will be set to 0x00 (NULL). If less than a 16 hexadecimal key is used, the remaining bytes will be set to 0x00. Note: When specifying a Reseration Key on each host sharing a deice, the key must be unique to each host. Rewind Immediate This parameter turns the immediate bit On and Off in rewind commands. If it is set to On, then the rewind tape operation executes faster, but the next command takes a long time to finish unless the rewind operation is physically complete. Setting this parameter reduces the amount of time that it takes to close a deice for a Rewind on Close special file. The installation default is Off (no rewind immediate) except for the IBM mm Tape Cartridge Autoloader, for which the default is On (rewind immediate). System encryption This parameter specifies if System-Managed Encryption should be used. For more information refer to System-Managed Encryption on page 40. The installation default is no. System encryption for Write Commands This parameter controls if System-Managed Encryption will be used for Write commands. For more information refer to System-Managed Encryption on page 40. The installation default is custom. Trailer Labels If this parameter is set to On, then writing a record past the early warning mark on the tape is allowed. The first write operation to detect EOM fails, and the errno ariable is set to ENOSPC. No data is written during the operation. All subsequent write operations are allowed to continue until the physical end of the olume is reached and EIO is returned. This parameter can also be selected using one of three deice special files that allow trailer-label processing. The special files are rmtx.40, rmtx.41, and rmtx.60, where x is the name of the deice (for example, rmt0.40). The installation default is Off (no trailer labels). Media Parameters The ability to set or change media parameters is a tape diagnostic and utility function, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Chapter 3. AIX Tape and Medium Changer Deice Drier 31

50 AIX Deice Drier (Atape) The media parameters can be queried and set by ITDT or the tape diagnostic and utility function using the Query/Set Parameters option in the window. These parameters cannot be set or changed by the configuration procedures. The media parameters are: Capacity scaling Logical write protect Volume ID for logging Capacity Scaling This parameter sets the capacity or logical length of the current tape on IBM TotalStorage Enterprise Tape System 3590, IBM TotalStorage Enterprise Tape System 3592, or Magstar MP tape subsystems. By reducing the capacity of the tape, the tape drie can access data faster at the expense of data capacity. Capacity scaling can be set at 100% for the entire tape (which is the default) or set at 75%, 50%, or 25% of the tape or any deice specific hexadecimal alue. For example on IBM 3592, to change capacity scaling from a 300 GB format tape (100%) to a 60 GB format tape, select the capacity scaling option, then select the option to enter a hexadecimal alue and enter 35. Capacity scaling remains with the tape across mounts until it is changed. Notes: 1. The tape position must be at the start of the tape to change this parameter from its current alue. 2. Changing this parameter destroys any existing data on the tape. 3. Attempting to set capacity scaling that is not supported by a deice or the current media loaded always returns 100% and cannot be changed. For example, 60 GB media for the IBM 3592 cannot be capacity scaled and is always 100%. Logical Write Protect This parameter sets or resets the logical write protect of the current tape on IBM TotalStorage Enterprise Tape System 3590, IBM TotalStorage Enterprise Tape System 3592, or Magstar MP tape subsystems. The three types of logical write protect are: associated protect, persistent protect, and write-once read-many (WORM) protect. Associated protect remains only while the current tape is mounted or associated with the tape drie. It is reset when the tape is unloaded or the tape drie is reset. Persistent protect remains or persists with the tape across mounts until it is reset. WORM protect also remains with the tape across mounts, but (unlike persistent protect) it cannot be reset on the tape. After a tape is WORM protected, it can neer be written on again. Notes: 1. The tape position must be at the start of the tape to change this parameter from its current alue. 2. Attempting to set logical write protect that is not supported by a deice or the current media loaded always returns "No" and cannot be changed. 32 IBM Tape Deice Driers Installation and User s Guide

51 AIX Deice Drier (Atape) Volume ID for Logging This parameter is the olume ID of the current loaded tape. It is used in the log file entry (if olume logging is actie) to identify the entry with a particular olume. The deice drier sets the olume ID to UNKNOWN initially and when the tape is unloaded. Special Files Once the drier is installed and a tape deice is configured and aailable for use, access is proided through the special files. These special files, which consist of the standard AIX special files for tape deices (with other files unique to the Atape drier), are in the /de directory. Special Files for Tape Deices Each tape deice has a set of special files that proides access to the same physical drie but to different types of functions. As shown in Table 5, in addition to the tape special files, a special file is proided for tape deices that allows access to the medium changer as a separate deice. Table 5. Special Files for Tape Deices Note: The asterisk (*) represents a number assigned to a particular deice (such as rmt0). For tape dries with attached SCSI medium changer deices, the rmt*.smc special file proides a separate path for issuing commands to the medium changer. When this special file is opened, the application can iew the medium changer as a separate SCSI deice. Both this special file and the rmt* special file can be opened at the same time. The file descriptor that results from opening the rmt*.smc special file does not support the following operations: Read Write Open in Diagnostic mode Commands designed for a tape drie If a tape drie has a SCSI medium changer deice attached, then all operations (including the medium changer operations) are supported through the interface to the rmt* special file. For detailed information, refer to Table 5. Special File Name Rewind on Close (Note 1) Retension on Open (Note 2) Bytes per Inch (Note 3) Trailer Label Unload on Close /de/rmt* Yes No N/A No No /de/rmt*.1 No No N/A No No /de/rmt*.2 Yes Yes N/A No No /de/rmt*.3 No Yes N/A No No /de/rmt*.4 Yes No N/A No No /de/rmt*.5 No No N/A No No /de/rmt*.6 Yes Yes N/A No No /de/rmt*.7 No Yes N/A No No /de/rmt*.10 (Note 4) No No N/A No No Chapter 3. AIX Tape and Medium Changer Deice Drier 33

52 AIX Deice Drier (Atape) Table 5. Special Files for Tape Deices (continued) Special File Name Rewind on Close (Note 1) Retension on Open (Note 2) Bytes per Inch (Note 3) Trailer Label Unload on Close /de/rmt*.20 Yes No N/A No Yes /de/rmt*.40 Yes No N/A Yes No /de/rmt*.41 No No N/A Yes No /de/rmt*.60 Yes No N/A Yes Yes /de/rmt*.null (Note 5) Yes No N/A No No /de/rmt*.smc (Note 6) N/A N/A N/A N/A N/A Notes: 1. The Rewind on Close special files write filemarks under certain conditions before rewinding. 2. The Retension on Open special files rewind the tape on open only. Retensioning is not performed because these tape products perform the retension operation automatically when needed. 3. The Bytes per Inch options are ignored for the tape deices supported by this drier. The density selection is automatic. 4. The rmt*.10 file bypasses normal close processing, and the tape is left at the current position. 5. The rmt*.null file is a pseudo deice similar to the /de/null AIX special file. The input/output control (ioctl) calls can be issued to this file without a real deice attached to it, and the deice drier returns a successful completion. Read and write system calls return the requested number of bytes. This file can be used for application deelopment or debugging problems. 6. The rmt*.smc file can be opened independently of the other tape special files. Special Files for Medium Changer Deices After the drier is installed and a medium changer deice is configured and made aailable for use, access to the robotic deice is proided through the smc* special file in the /de directory. Table 6 shows the attributes of the special file. The asterisk (*) represents a number assigned to a particular deice (such as smc0). The term smc is used for a SCSI medium changer deice. The smc* special file proides a path for issuing commands to control the medium changer robotic deice. For more information, refer to Table 6. Table 6. Special Files for Medium Changer Deices Special File Name Description /de/smc* Access to the medium changer robotic deice /de/smc*.null Pseudo medium changer deice Note: The smc*.null file is a pseudo deice similar to the /de/null AIX special file. The commands can be issued to this file without a real deice attached to it, and the deice drier returns a successful completion. This file can be used for application deelopment or debugging problems. The file descriptor that results from opening the smc special file does not support the following operations: Read Write Commands designed for a tape deice 34 IBM Tape Deice Driers Installation and User s Guide

53 AIX Deice Drier (Atape) Persistent Naming Support Persistent naming support is used to ensure that attached deices are always configured with the same logical name based on the SCSI ID, LUN ID, and host bus adapter (HBA), een when the system is rebooted. When the AIX operating system is booted, the HBA performs a deice discoery and assigns a default logical name to each deice found in a sequential order. For example, if there are three tape dries attached to a parallel SCSI adapter, each with a LUN ID of 0 and a target address of 0, 1, and 2 respectiely, the HBA would initially configure them as Aailable with the following logical names: rmt0 target 0, lun 0 Aailable rmt1 target 1, lun 0 Aailable rmt2 target 2, lun 0 Aailable On the next reboot, for example, if the existing rmt1 target 1 deice is powered off or not connected, the HBA would initially configure two deices as Aailable with the following logical names: rmt0 target 0, lun 0 Aailable rmt1 target 2, lun 0 Aailable If the preious rmt1 target 1 deice is powered on after reboot and the cfgmgr command is run, the HBA configures the deice as rmt2 instead of rmt1: rmt2 target 1, lun 0 Aailable This is one example, but there are other cases where the logical names of deices could change when the system is rebooted. For applications that need a consistent naming conention for all attached deices, this is accomplished with persistent naming support by defining a unique logical name (other than the AIX default names) that are associated with the specific SCSI ID, LUN ID, and HBA that the deice is connected to. Changing the Logical Name After Initial Boot The logical name of a deice can be changed after an initial boot and configured. This can be done using the SMIT menu or the chde command from a script or command line. For example, a default rmt0 logical name for a tape drie could be changed to rmt-0, tape0, or any descriptie name desired. In this example, if the three tape dries are changed to rmt-0, rmt-1, and rmt-2 respectiely, and the system is then rebooted with rmt-1 powered off, the HBA detects that there are unique names predefined for the attached deices, and the HBA uses those names. In this case, the deices would configure as follows: rmt-0 target 0, lun 0 Aailable rmt-1 target 1, lun 0 Defined rmt-2 target 2, lun 0 Aailable Since rmt-1 is not detected by the HBA but has been predefined at the SCSI ID and LUN ID, it remains in the defined state and is not configured for use, but the next rmt-2 tape drie configures as the same name at the same location after reboot. Chapter 3. AIX Tape and Medium Changer Deice Drier 35

54 AIX Deice Drier (Atape) Using SMIT to Change the Logical Name To change the logical name using SMIT, perform the following steps: 1. Run SMIT from a command line and select Deices. 2. Select Tape Drie. 3. Select Change/Show Characteristics of a Tape Drie. 4. Select the logical deice to be changed from the list displayed. 5. In the New Logical Name field, enter a non-aix default logical name. 6. Press Enter to process the change. Using chde Command to Change the Logical Name The logical name of a deice can be changed using the chde command. For example, to change the logical name of the deice rmt0 to rmt-0, run: chde l rmt0 a new_name=rmt-0 The output of this command displays rmt0 changed. Note: When path failoer is enabled, changing the logical name for either a primary or alternate deice only changes that indiidual deice name. Control Path Failoer Support for Tape Libraries Note: The library control path failoer feature code must be installed prior to enabling the path failoer support in the Atape deice drier. Refer to Automatic Failoer on page 10 for what feature codes may be required for your machine type. The Atape deice drier path failoer support configures multiple physical control paths to the same logical library within the deice drier and proides automatic failoer to an alternate control path when a permanent error occurs on one path. This is transparent to the running application. Configuring and Unconfiguring Path Failoer Support Path failoer support is not enabled automatically when the deice drier is installed. It must be configured initially on each logical deice after installation. When path failoer support is enabled for a logical deice, it remains set until the deice is deleted or the support is unconfigured. The alternate path failoer setting is retained een if the system is rebooted. To enable or disable the support on a single logical deice, use the smit menu to Change/Show Characteristics of a Tape Drie, select the logical deice to change such as smc0, smc1, and so on, then select Yes or No for Enable Path Failoer Support. The support can also be enabled or disabled using the chde command, for example: chde -l smc0 -aalt_pathing=yes chde -l smc1 -aalt_pathing=yes chde -l smc0 -aalt_pathing=no chde -l smc1 -aalt_pathing=no Primary and Alternate Paths When the deice drier configures a logical deice with path failoer support enabled, the first deice configured always becomes the primary path. On SCSI attached deices, -P is appended to the location field. On Fibre attached deices, -PRI is appended to the location field of the deice. 36 IBM Tape Deice Driers Installation and User s Guide

55 AIX Deice Drier (Atape) When a second logical deice is configured with path failoer support enabled for the same physical deice, it configures as an alternate path. On SCSI attached deices, -A is appended to the location field. On Fibre attached deices, -ALT is appended to the location field of the deice. A third logical deice is also configured as an alternate path with either -A or -ALT appended, and so on. The deice drier supports up to 16 physical paths for a single deice. The labeling of a logical deice as either a primary or alternate path is for information only, in order to: 1. Be able to identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled as the primary path for each physical deice. Howeer, there can be many (multiple) logical deices labeled as an alternate path for the same deices. 2. Proide information about which logical deices configured on the system hae path failoer support enabled. Querying Primary and Alternate Path Configurations You can display the primary and alternate path configuration for all deices with the lsde command. There can be two or more logical deices configured for a single physical deice, but the first deice configured is labeled the primary deice. All other logical deices configured after the first deice are labeled as alternate deices. To see this, run the lsde -Cc tape command and look at the location field in the data. Run the following command: lsde -Cc tape grep P For example, you can easily determine how many physical deices are configured with path failoer support. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Configuring and Unconfiguring Primary and Alternate Deices Logical deices configured as alternate paths can be unconfigured and reconfigured at any time after the initial configuration is run. Unconfiguring an alternate path deice remoes that deice from the primary deice path list, remoes the -A or -ALT appended to the location field, and changes the deice to the Defined state. The primary and any other alternate deices are still aailable. Likewise, configuring a new alternate path deice or reconfiguring an existing one in the Defined state adds that deice to the primary deice path list, appends -A or -ALT to the location field, and makes the deice aailable. Logical deices that are configured as primary paths can also be unconfigured and reconfigured at any time after initial configuration is run. Howeer, the operation is different for a primary deice. When a primary deice is unconfigured, the following eents occur: 1. All alternate deices are unconfigured as described preiously. 2. The primary deice is unconfigured. 3. The -P or -PRI appended to the location field is remoed. Chapter 3. AIX Tape and Medium Changer Deice Drier 37

56 AIX Deice Drier (Atape) 4. The deice is changed to the Defined state. 5. All alternate deices that were unconfigured are reconfigured. The first deice that is reconfigured becomes the new primary deice. All remaining alternate deices are reconfigured as alternate paths. These methods proide the ability to unconfigure and reconfigure physical deices on the system when deice connections or addressing changes are made. Data Path Failoer and Load Balancing Support for Tape Dries Notes: 1. Some deices require a path failoer feature code installed prior to enabling the path failoer support in the Atape deice drier. Refer to Automatic Failoer on page 10 for what feature code may be required for your machine type. 2. DPF keys do not need to be added if you are running the latest drie code on Ultrium-3 and Ultrium-4 dries. 3. This function is not supported for deices that are attached through an IBM San Data Gateway or on the IBM Virtualization Engine TS The AIX operating system only supports a static configuration of deices, which also applies to the Path Failoer and Failoer Support. When deices are initially configured at a specific SCSI ID and physical connection (drie port, host bus adapter, and switch number/port, if applicable) and in the Aailable state, changing the physical deice address/connection without either rebooting or unconfiguring and reconfiguring the deices has unpredictable results and is not supported. Installing Data Path Failoer License Key Use the following command line script to query, add, or delete license keys for this feature before enabling the path failoer feature as described below. The key is a 16-digit hexadecimal alue, for example, abcdef. All key alues A-F should be entered in lowercase letters as a-f. Query installed keys: dpf_keys Install a license key: dpf_keys -a key Delete a license key: dpf_keys -d key Configuring and Unconfiguring Path Failoer Support Path failoer support is not enabled automatically when the deice drier is installed. It must be configured initially on each logical deice after installation. When path failoer support is enabled for a logical deice, it remains set until the deice is deleted or the support is unconfigured. The path failoer setting is retained een if the system is rebooted. Path failoer support can be enabled on all configured deices at one time, or it can be enabled or disabled selectiely by logical deice. It may be desirable at times to configure some, but not all, logical paths to a deice with the support enabled. To enable the support globally on all currently configured deices, run the command: /usr/lpp/atape/instatape -a 38 IBM Tape Deice Driers Installation and User s Guide

57 AIX Deice Drier (Atape) This unconfigures all deices that hae path failoer set to No, and reconfigures all deices, setting path failoer to Yes. To enable or disable the support on a single logical deice, use the smit menu to Change/Show Characteristics of a Tape Drie, then select Yes or No for Enable Path Failoer Support. The support can also be enabled or disabled using the chde command, for example: chde -l rmt0 -aalt_pathing=yes chde -l rmt0 -aalt_pathing=no Primary and Alternate Paths When the deice drier configures a logical deice with path failoer support enabled, the first deice configured always becomes the primary path and PRI is appended to the location field of the deice. When a second logical deice is configured with path failoer support enabled for the same physical deice, it configures as an alternate path and ALT is appended to the location field. A third logical deice is configured as the next alternate path with ALT appended, and so on. The deice drier supports up to 16 physical paths for a single deice. For example, if rmt0 is configured first, then rmt1, the lsde -Cc tape command output is similar to the following: rmt0 Aailable PRI IBM 3590 Tape Drie and Medium Changer (FCP) rmt1 Aailable ALT IBM 3590 Tape Drie and Medium Changer (FCP) If rmt1 is configured first, then rmt0, the command output is similar to the following: rmt0 Aailable ALT IBM 3590 Tape Drie and Medium Changer (FCP) rmt1 Aailable PRI IBM 3590 Tape Drie and Medium Changer (FCP) The labeling of a logical deice as either a primary or alternate path is for information only, in order to: 1. Be able to identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled the primary path for each physical deice. Howeer, there may be many (multiple) logical deices labeled as an alternate path for the same deices. 2. Proide information about which logical deices configured on the system hae path failoer support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices with the lsde command. There may be two or more logical deices configured for a single physical deice, but the first deice configured is labeled the primary deice. All other logical deices configured after the first deice are labeled as alternate deices. To see this, run the lsde -Cc tape command and look at the location field in the data. By running lsde -Cc tape grep PRI, for example, you can easily determine how many physical deices on the RS/6000 or System p (also known as pseries) serer are configured with path failoer support. Chapter 3. AIX Tape and Medium Changer Deice Drier 39

58 AIX Deice Drier (Atape) Configuring and Unconfiguring Primary and Alternate Deices Logical deices configured as alternate paths can be unconfigured and reconfigured at any time after the initial configuration is run. Unconfiguring an alternate path deice remoes that deice from the primary deice path list, remoes the ALT appended to the location field, and changes the deice to the Defined state. The primary and any other alternate deices are still aailable. Likewise, configuring a new alternate path deice or reconfiguring an existing one in the Defined state adds that deice to the primary deice path list, appends ALT to the location field, and makes the deice aailable. System-Managed Encryption Logical deices that are configured as primary paths can also be unconfigured and reconfigured at any time after initial configuration is run. Howeer, the operation is different for a primary deice. When a primary deice is unconfigured, the following eents occur: 1. All alternate deices are unconfigured as described preiously. 2. The primary deice is unconfigured. 3. The PRI appended to the location field is remoed. 4. The deice is changed to the Defined state. 5. All alternate deices that were unconfigured are reconfigured. The first deice that is reconfigured becomes the new primary deice. All remaining alternate deices are reconfigured as alternate paths. These methods proide the ability to unconfigure and reconfigure physical deices on the system when deice connections or addressing changes are made. Deice Drier Configuration System-Managed Encryption can be set on a specific tape drie using the standard SMIT panels to Change/Show Characteristics of a tape deice or the command line chde command. There are 2 new attributes added for encryption: sys_encryption yes/no wrt_encryption off/on/custom Use System Encryption FCP Proxy Manager System Encryption for Write Commands at BOP The sys_encryption attribute enables deice drier system-managed encryption for a tape drie by setting the alue to yes. The wrt_encryption attribute controls whether the deice drier can set the tape drie to encryption enabled for write commands. When set to off, the tape drie uses encryption for read operations; write operations do not use encryption. When set to on, the tape drie uses encryption for both read/write operations. When set to custom, the deice drier does not modify current tape drie setting. The custom setting is intended for applications using system-managed encryption to control write encryption without deice drier interention. Note: If wrt_encryption is set to on, an application can not open a tape drie using the append mode. Querying Tape Drie Configuration This is a tape diagnostic and utility function, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page IBM Tape Deice Driers Installation and User s Guide

59 Testing Data Encryption Configuration and Connectiity There is a data encryption test aailable to alidate the ibmekm.conf file serer entries and test tape drie to serer connectiity operations. This is a tape diagnostic and utility function, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231 Error Logging Encryption errors are logged along with other tape operation errors using the standard TAPE_ERR1 Template Tape Operation Error with associated sense data in the detail data. An encryption failure is indicated when the asc/ascq in the sense data is EFxx or EExx. Refer to the tape drie hardware reference for specific information on the asc/ascq being reported. The asc/ascq can be found in the first column of the second row in detail sense data. For example: Detail Data SENSE DATA 0A A08 25FF FF FF F EF11 FF02 D A FFFF FF FFF0 B7E A Field Support Information When encryption failures require field support and/or deelopment analysis the following data should be proided for a problem on a specific tape drie from the machine (rmt1 for example) for the deice drier. Tape drie dumps and EKM serer logs may be needed in addition to this information. Problem Determination errpt a > errpt.rmt1 lsattr El rmt1 > lsattr.rmt1 All Atape files in /ar/adm/ras/atape* A set of tools is proided with the deice drier to determine if the deice drier and the tape deice are functioning correctly. The standard AIX interface is proided for problem determination. Using the Dump Support Dump support is proided through the dump entry point in the drier. Refer to appropriate AIX manuals for a description of how to use the dump deices and how to read the dump data. Dump Deice Commands To list the current dump deices, enter the following command: sysdumpde -l AIX System-Managed Encryption To establish the rmt1 tape deice as a secondary dump deice, enter the following command: sysdumpde -s /de/rmt1 To perform a dump operation, use the sysdumpstart command. To send the dump data to the secondary dump deice, enter the following command: Chapter 3. AIX Tape and Medium Changer Deice Drier 41

60 AIX Deice Drier (Atape) sysdumpstart -s Note: This command stops the system. Use the sync command to ensure that the cache is flushed before issuing the sysdumpstart -s command. To list the last dump data, enter the following command: sysdumpde -z After the dump data is placed on the tape, copy it to a file on the disk before using the crash command to process it. For example: dd if=/de/rmt1 of=tapedump1 ibs=4096 obs=512 crash tapedump1 Note: The ibs alue is the input block size. If the block size of the tape deice is larger than the block size sent during the dump process, the dump operation fails. Set the block size to zero on the tape deice and experiment with the ibs alue for the dd command. Deice and Volume Information Logging An optional logging utility is proided to log the information about the deice and the media. The information is extensie for some deices and limited for other deices. If set to On, the logging facility gathers all aailable information through the SCSI Log Sense command. This process is a separate facility from error logging. Error logging is routed to the system error log. Deice information logging is sent to a separate file. The following parameters control this utility: Logging Maximum size of the log file Volume ID for logging Refer to Tape Drie, Media, and Deice Drier Parameters on page 26 for a description of these parameters. Each time the rewind and unload sequence occurs or the STIOC_LOG_SENSE ioctl command is issued, an entry is added to the log. Each time a new cartridge is loaded, the alues in the deice log buffers are reset with the Log Sense command. The log data is gathered on a per-olume basis. Log File The data is logged in the /usr/adm/ras directory. The file name is dependent on each deice; therefore, each deice has a separate log. An example of the rmt1 deice file is: /usr/adm/ras/atape.rmt1.log The files are in binary format. Each entry has a header followed by the raw Log Sense pages as defined for a particular deice. The first log page is always page 0x00. This page, as defined in the SCSI-2 ANSI specification, contains all pages the deice supports. Page 0x00 is followed by all pages specified in page 0x00. The format of each following page is defined in the SCSI specification and the deice manual. 42 IBM Tape Deice Driers Installation and User s Guide

61 AIX Deice Drier (Atape) Tape Log Utility A tape log utility is installed with the tapelog deice drier that displays the contents of the log file in ASCII text. The log pages are displayed as hexadecimal alues in dump format. The syntax for the tape log utility is: tapelog -l Name [-d] or tapelog -f File [-d] Notes: 1. Name is the logical name of the deice (such as rmt0). 2. File is the name of a log file (such as Atape.rmt0.log). 3. The -d parameter, if used, deletes the log file for the specified deice. The contents of the log file are displayed as standard output. To sae the log in a file, use the AIX redirection function. For example: tapelog -l rmt0 > rmt0.log Reseration Conflict Logging When the deice drier receies a reseration conflict during open or after the deice has been opened it will log a reseration conflict in the AIX error log. Prior to logging the error the deice drier will issue a Persistent Resere In command to determine if a SCSI Persistent Reseration is actie on the resering host to get the resering host initiator WWPN (World Wide Port Name) and resere key. If successful, the deice drier will log this information as follows: Resering host key xxxxxxxx WWPN xxxxxxxx Where the first xxxxxxxx is the actual resere key and the second xxxxxxxx is the resering host initiator WWPN. After initially logging the resering host WWPN, subsequent reseration conflicts from the same resering host WWPN will not be logged to preent multiple entries in the error log until either the resering host WWPN is different than the one initially logged or the deice drier has resered the deice and then another reseration conflict occurs. If the Persistent Resere In command fails then the detail data will contain the following entry with the errno from the failing Persistent Resere In command: Unable to obtain resering host information, errno x The possible errno alues are: ENOMEM - Deice drier cannot obtain memory to perform the command EINVAL - Deice has a Persistent Reseration but does not support the Persistent Resere In serice action EBUSY - Deice has failed the command with reseration conflict and has a SCSI-2 Resere actie EIO - Unknown I/O failure occurred Error Logging The deice drier proides logging to the AIX system error log for arious errors. The error log can be iewed for specific deices using the Error Log Analysis utility proided with the tape drie serice aids. Refer to Error Log Analysis on page 49. The error log can also be iewed using the smit or the errpt command. Chapter 3. AIX Tape and Medium Changer Deice Drier 43

62 AIX Deice Drier (Atape) Error Log Templates The error log templates the deice drier uses follow the same format as the default AIX tape error log entries. Each error log entry is identified by an error label and contains detail data associated with the type of error. The following items describe the error labels and detail data for the templates used for logging tape deice, media, and SCSI adapter related errors in the AIX system error log. Error Labels Errors are logged with an associated error label and error ID. The error label indicates the basic type of error: TAPE_ERR1 Tape media error TAPE_ERR2 Tape hardware error TAPE_ERR4 SCSI Adapter detected error TAPE_ERR5 Unknown error RECOVERED_ERROR Temporary tape hardware or media error SIM_MIM_RECORD_ Serice/Media Information Message (Log Page X'31') TAPE_SIM_MIM_RECORD Tape drie Serice/Media Information Message (Log Page X'31') DEV_DUMP RETRIEVED Deice dump retrieed TAPE_DRIVE_CLEANING Tape drie needs cleaning RESERVE_CONFLICT Reseration conflict Detail Data Detail data is logged with the associated error that identifies the cause of the error. Detail data for the SIM_MIM_RECORD_3590 or TAPE_SIM_MIM_RECORD entries contain the raw data from Log Sense Page X'31'. Refer to the hardware reference manual for the format of this entry. All other error log entries use the following format for detail data: Detail Data SENSE DATA aabb xxxx ccdd eeee eeee eeee eeee eeee ffgg hhxx ssss ssss ssss ssss ssss ssss ssss ssss ssss ssss... Where: aa Length of the command descriptor block (CDB) bb SCSI target address xx Unused or resered cc Start of CDB, cc is the operation code (byte 0) dd Logical unit (byte 1) in the CDB 44 IBM Tape Deice Driers Installation and User s Guide

63 AIX Deice Drier (Atape) ee ff gg Bytes 2 through 12 in the CDB Status alidity field. If this field is 01, then a SCSI error was reported, and byte gg indicates the type of error. If this field is 02, then an adapter error was reported, and byte hh indicates the type of error. This byte indicates the type of SCSI error that occurred: 02 CHECK CONDITION - Deice reported a check condition. 08 BUSY STATUS - Target is busy. 18 RESERVATION CONFLICT - Target is resered to another initiator. 22 COMMAND TERMINATED - Deice terminated the command. 28 QUEUE FULL - Deice command queue is full. hh This byte indicates the type of adapter error that occurred. For parallel SCSI adapters, this is the general_card status code as defined in /usr/include/sys/scsi.h: 01 HOST IO BUS ERROR - Host I/O bus error during data transfer. 02 SCSI BUS FAULT - SCSI bus protocol or hardware error. 04 COMMAND TIMEOUT - Command timed out before completion. 08 NO DEVICE RESPONSE - Target did not respond to selection phase. 10 ADAPTER HARDWARE FAILURE - Adapter indicated a hardware failure. 20 ADAPTER SOFTWARE FAILURE - Adapter indicated a microcode failure. 40 FUSE OR TERMINAL PWR - Blown terminator fuse or bad termination. 80 SCSI BUS RESET - Adapter indicated SCSI bus has been reset. For FCP or SAS adapters, this is the adapter_status code as defined in /usr/include/sys/scsi_buf.h: 01 HOST IO BUS ERROR - Host I/O bus error during data transfer. 02 TRANSPORT FAULT - Failure in the transport layer. 03 COMMAND TIMEOUT - Command timed out before completion. 04 NO DEVICE RESPONSE - Target did not respond to attempts to select it. 05 ADAPTER HARDWARE FAILURE - Adapter indicated a hardware failure. 06 ADAPTER SOFTWARE FAILURE - Adapter indicated a microcode failure. 07 WW NAME CHANGE - Adapter detected a new worldwide name for the deice. 08 FUSE OR TERMINAL PWR - Blown terminator fuse or bad termination. 09 TRANSPORT RESET - Adapter detected an external SCSI bus reset. 0A TRANSPORT BUSY - The transport layer is busy. 0B TRANSPORT DEAD - The transport layer is currently inoperatie. ss If byte gg indicates a check condition, the ss byte is the sense data from the deice. Refer to the appropriate deice reference manual for the specific format and content of these bytes. Chapter 3. AIX Tape and Medium Changer Deice Drier 45

64 AIX Deice Drier (Atape) Automatic Dump Facility The deice drier proides an automatic dump facility for deices that support reading a dump and indicating when a dump is aailable in deice sense data. Wheneer a check condition occurs and the sense data indicates that a dump is aailable, the deice drier reads the dump from the deice and stores it in the /ar/adm/ras directory. A maximum of three dumps for each deice are stored in this directory as: Atape.rmtx.dump1 Atape.rmtx.dump2 Atape.rmtx.dump3 Note: X is the deice number, for example, rmt0. When the deice is first configured, the dump name is set to dump1. If more than three dumps occur, the drier starts oer at dump1; therefore the last three dumps are always kept. Trace Facility The AIX trace facility is supported for the deice drier. The trace eent is identified with a hookword. The hookword used by the deice drier is 326. The trace can be initiated at any time before an operation on a tape deice. Enter the following AIX command to start the trace: trace -a -j 326 This command starts the trace in the background and collects only the trace eents with the 326 hookword (Atape deice drier). Enter the following AIX command to stop the trace: trcstop This command stops the trace after the tape operations are performed. Enter the following AIX command to iew the trace: trcrpt > trace.out This command formats the trace output into a readable form and places it into a file for iewing. Atape System Trace (ATRC) Utility The atrc trace utility is also installed with the deice drier to start, stop, and format a deice drier trace. To start the trace, enter the atrc command. To stop and format the trace, enter the atrc command again. The trace is formatted to an atrc.out AIX file in the current directory. Component Tracing Later releases of AIX 5.3 and aboe support component tracing. Unlike system tracing that needs to be started and stopped, component tracing by default is on all the time and runs continually. To determine if component tracing is aailable run the command ctctrl -q to display a list of supported components with their default settings. You must hae root authority to run this command. Refer to the AIX ctctrl man page for a complete description of the ctctrl command and parameters. 46 IBM Tape Deice Driers Installation and User s Guide

65 AIX Deice Drier (Atape) To dump and format the current component trace to a file (for example, actrc.out) into the current directory, run the following commands: ctctrl -D -c Atape trcrpt -l Atape -o actrc.out The Atape component trace can also be retrieed from a system dump. This eliminates the need to start the Atape system trace prior to a system dump or to recreate an AIX system dump when a system trace is not running. The AIX system dump is normally stored in the /ar/adm/ras directory as a mcore.x.bz file, where x is a dump number 1, 2, and so on. To retriee and format the Atape component trace from a dump file (for example, mcore.1.bz) to a file (for example, actrc.dump) into the current directory, run the following commands: dmpuncompress /ar/adm/ras/mcore.1.bz trcdead -c /ar/adm/ras/mcore.1 trcrpt -l Atape -o actrc.dump Atape Component Trace (ACTRC) Utility The actrc component trace utility is also installed with the deice drier to dump and format the current Atape component trace. To dump and format the component trace, run the command actrc. The trace is formatted to an actrc.out file in the current directory. Tape Drie Serice Aids The serice aids described in the following sections are accessible through the AIX diagnostic subsystem using the AIX diag command and in the Task Selection menu selecting IBM Tape Drie Serice Aids. Refer to Details of Tape Serice Aids below. Tape drie serice aids are also aailable using the "IBM Tape Diagnostic Tool (ITDT)". Refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Details of Tape Serice Aids The following serice aid utilities are installed with the deice drier: Force Microcode Dump Read Dump Microcode Load Error Log Analysis Reset Drie Create an FMR Tape Force Microcode Dump This utility forces a dump operation on the tape drie. After the dump operation is performed, the dump data can be transferred from the tape drie using the Read Dump utility. To access this utility: 1. Open the Serice Aids window. 2. Select Force Microcode Dump from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBM Tape Drie Selection window, then press Enter. Chapter 3. AIX Tape and Medium Changer Deice Drier 47

66 AIX Deice Drier (Atape) The Force Microcode Dump operation starts, and a window opens when the operation is completed. Read Dump This utility transfers the dump data from the deice to a file, a diskette, or a tape cartridge. To access this utility: 1. Open the Serice Aids window. 2. Select Read Dump from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBM Tape Drie Selection window, then press Enter. 4. Enter the destination file name or deice in the Prompting for Destination window. The default destination is the /de/rfd0 diskette drie. To transfer the dump data to a tape cartridge, enter the deice name of the tape drie (for example, /de/rmt0). To transfer the dump data to a file, enter the file name. Press F7 to commit. Note: On certain terminal types, it may be necessary to press the Esc key and the number 7 key instead of F7. The Read Dump operation starts, and a window opens when the operation is completed. Microcode Load This utility downloads microcode to the deice from a file or a diskette (AIX format only). Note: To download the microcode from a DOS diskette, you must first use the AIX dosread command to transfer the file from the DOS diskette to the AIX file. Then you can use the Microcode Load utility to download the AIX file to the tape drie. To access this utility: 1. Open the Serice Aids window. 2. Select Microcode Load from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBM IBMTape Drie Selection window, then press Enter. 4. Enter the source file name or deice on the Prompting for Source File window. The default source is the /de/rfd0 diskette drie. To load from a file, enter the file name. Press F7 to commit. Note: On certain terminal types, it may be necessary to press the Esc key and the number 7 key instead of F7. 5. If the current microcode on a tape drie is Federal Information Processing Standard (FIPS) code, then a window opens and displays the following: Warning: The drie is currently using FIPS code. Press Enter to continue with downloading new drie code. If you do not want to download the new code, press either F3 to cancel or F10 to exit without downloading new code. Otherwise, press Enter to continue with the download code procedure. 48 IBM Tape Deice Driers Installation and User s Guide

67 AIX Deice Drier (Atape) The Microcode Load operation starts, and a window opens when the operation is completed. Error Log Analysis This utility displays and analyzes the system error log entries for a specific tape drie and can be used for problem determination. The type of error, the SCSI command, and the sense data (if applicable) are displayed for each entry in the error log (one screen at a time). To access this utility: 1. Open the Serice Aids window. 2. Select Error Log Analysis from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBM Tape Drie Selection window, then press Enter. 4. If entries are listed in the error log for the selected deice, then the first entry is displayed. Press Enter to display the next entry. 5. After all entries are displayed, a window opens, and the operation is completed. Reset Drie This utility resets the tape drie. Performance Considerations To access this utility: 1. Open the Serice Aids window. 2. Select Reset Drie from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBM IBMTape Drie Selection window, then press Enter. The Reset Drie operation starts, and a window opens when the operation is completed. Create an FMR Tape This utility creates a field microcode replacement (FMR) cartridge tape using the loaded functional microcode in the tape drie. To access this utility: 1. Open the Serice Aids window. 2. Select Create an FMR Tape from the IBM Tape Drie Serice Aids window, then press Enter. 3. Select the deice from the IBMTape Drie Selection window, then press Enter. The Create an FMR Tape operation starts, and a window opens when the operation is completed. This chapter describes the parameters and issues that may affect the perceied performance of the tape drie. In general, AIX applications that operate at a file leel to moe data between disk storage deices and tape do not exploit the full capabilities of a high end tape deice. The goal of this discussion is to gie an oeriew of the data path components inoled in moing data between disk storage deices and tape. The following chapter describes basic techniques and common utilities in a specific enironment that can be used to understand how a Chapter 3. AIX Tape and Medium Changer Deice Drier 49

68 AIX Deice Drier (Atape) deice is performing. Performance issues encountered by adanced application deelopers are beyond the scope of this document. Refer to the hardware reference for the specific deice for performance specifications. Refer to the application documentation for information on deice-specific application configuration. Refer to the operating system documentation for information on disk storage deice striping and other techniques for improing file system performance. Data Path The simplified model in Figure 8 shows the components inoled in the data path for moing data at a file leel between disk storage deices and tape. Performance analysis must be approached by determining which component of the data path impacts performance. Typically, a performance problem can be isolated by looking at one leg of the data path at a time. The goal of this analysis is to confirm that the tape data path is not impacting the performance adersely. Figure 8. Data Path for AIX Deice Drier (Atape) Common AIX Utilities The most commonly reported cause for poor tape performance is the use of small block sizes or the modification of the installation defaults for the tape deice. Note: The deice parameters should not be changed from the defaults for most applications. The following guidelines typically result in good tape path performance for use with AIX utilities: 1. Hardware compression should be enabled for maximum performance if the data sent to the deice is uncompressed. 2. The block_size parameter should be set to ariable (block_size=0) and command or application parameters specified to a block size appropriate for the deice. 3. Block sizes of 128 KB or greater should be used to improe performance. AIX iostat Utility for Tape Performance In releases of AIX 5.3 and earlier, the AIX iostat utility supports tape performance statistics in addition to other supported deices (such as disk). To determine if the iostat utility supports the configured tape dries, run the command iostat -p. If the configured tape dries are supported, a list of configured tape dries are displayed with the statistics listed for each drie. Refer to the AIX iostat man page for a complete description of the iostat command and parameters. When using the Data 50 IBM Tape Deice Driers Installation and User s Guide

69 AIX Deice Drier (Atape) Path Failoer feature, only the primary path for the tape drie is listed. The statistics apply to both the primary and alternate paths that are used. Before Calling Support System performance tuning is not a support responsibility. If tests indicate raw tape performance is below specifications, record the exact failing command and collect the output from the commands in Table 7 before contacting support. Table 7. Error Description Information Command Configuration lscfg - Deice parameters lsattr -E -l rmtn Error log. Call hardware support if errors errpt -a are found for TAPE_ERR* or SCSI* error labels. Drier ersion lslpp -l Atape.drier Trace of failing command Refer to Trace Facility on page 46 Chapter 3. AIX Tape and Medium Changer Deice Drier 51

70 AIX Deice Drier (Atape) 52 IBM Tape Deice Driers Installation and User s Guide

71 Chapter 4. HP-UX Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements ATDD Implementation Hardware Requirements Software Requirements Software Interface to the Deice Drier Installation and Configuration Instructions Installation and Configuration for PCI Driers.. 56 Installation and Configuration of Precision Bus Driers Supported Configuration Parameters Configuration Parameter Definitions Special Files Persistent Naming Support Control Path Failoer Support for Tape Libraries.. 79 Configuring and Unconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configurations Disable and Enable Primary and Alternate Paths 80 Data Path Failoer and Load Balancing Support for Tape Dries Configuring and Unconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configuration Disable and Enable Primary and Alternate Paths 83 Problem Determination Error Logging Reseration Conflict Logging Sense Data Logging Support_info Script Tracing Facility Atdd_d Log Daemon Problems and Solutions This chapter proides an oeriew of the IBM Tape and Medium Changer Deice Drier for HP-UX that proides support for IBM tape dries and medium changer deices. For tape diagnostic and utility functions refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Purpose This deice drier product proides SCSI-3 attachment for the IBM tape deices to selected Hewlett-Packard Precision Bus and PCI-based operating systems running HP-UX 10.20, 11.0, 11i 1, 11i 2, and 11i 3. The HP-UX installed name of this deice drier is Adanced Tape Deice Drier (ATDD). ATDD is used throughout this section to identify this drier. ATDD is designed specifically to take adantage of the features proided by the IBM tape deices (refer to Supported Hardware on page 9. The goal is to gie applications access to the functions required for basic operations (such as backup and restore) and the adanced functions needed by full tape management systems. Wheneer possible, the deice drier is designed to take adantage of the IBM tape system features transparent to the application. Data Flow Both data and commands flow between the application program and the tape subsystem by way of the IBM Tape and Medium Changer Deice Drier for HP-UX (ATDD). Figure 9 on page 54 shows the relationships between the IBM Tape and Medium Changer Deice Drier for HP-UX, the application program, the SCSI or Fibre Channel adapter deice drier, and the IBM tape subsystem. Copyright IBM Corp. 2007,

72 HP-UX Deice Drier (ATDD) Application Program ATDD Deice Drier SCSI or Fibre Channel Adapter Deice Drier IBM Tape Subsystem a Figure 9. Data Flow for HP-UX Deice Drier (ATDD) Product Requirements The following hardware and software components are required and supported by the IBM Tape and Medium Changer Deice Drier for HP-UX (ATDD). ATDD Implementation ATDD is actually a set of deice drier implementations for operation in the following HP-UX operating system enironments: HP Precision Bus - HP-UX (32 bit) - ersions of this drier are identified by leels ATDD 2.9.x.x. HP Precision Bus - HP-UX (32 bit) - ersions of this drier are identified by leels ATDD 4.9.x.x. HP PCI Bus - HP-UX (64 bit) - ersions of this drier are identified by leels ATDD 1.x.x.x. HP PCI Bus - HP-UX 11i 1 (64 bit) - ersions of this drier are identified by leels ATDD 3.x.x.x. HP PCI Bus - HP-UX 11i 2 (64-bit for Itanium 2) - ersions of this drier are identified by leels ATDD 5.5.x.x. HP PCI Bus - HP-UX 11i 2 (64-bit for PA-RISC) - ersions of this drier are identified by leels ATDD 5.6.x.x. HP PCI Bus - HP-UX 11i 3 (64-bit for Itanium 2) - ersions of this drier are identified by leels ATDD IA.6.x.x.x. HP PCI Bus - HP-UX 11i 3 (64-bit for PA-RISC) - ersions of this drier are identified by leels ATDD PA.6.x.x.x. Hardware Requirements ATDD supports the following HP SCSI host bus adapters: HP A4800A PCI Ultra SCSI Host Bus Adapter (HVD) HP A5159A PCI Dual Port FWD SCSI Host Bus Adapter (HVD) HP A5149A PCI to Ultra 2 SCSI Host Bus Adapter (LVD Single Port) HP A5150A Dual Channel PCI to Ultra 2 SCSI Host Bus Adapter (LVD Dual Port) HP A6828A Ultra 160 SCSI Adapter (LVD Single Port) HP A6829A Ultra 160 SCSI Adapter (LVD Dual Port) HP-PB FWD SCSI-2 Host Adapter (HP 28696A) with firmware reision 3543 or later (ATDD Precision Bus driers) HP PCI-X Dual Port Ultra320 SCSI Host Bus Adapter (HP A7173A, LVD) HP PCI-X 2-P SCSI/1000Base-T Multifunction Adapter (HP AB290A, LVD) (11i 3 only) HP PCI 1000Base-T and 1000Base-SX Adapter (HP A6794A, LVD) (11i 3 only) 54 IBM Tape Deice Driers Installation and User s Guide

73 HP-UX Deice Drier (ATDD) HP PCIe SC44Ge SAS Host Bus Adapter (HP AH303A, SAS) (11i 3 only) ATDD supports the following HP Fibre Channel adapter: HP A5158A Fibre Channel Mass Storage adapter HP A6795A Fibre Channel PCI Tachyon XL2 host bus adapter HP AB378A/B and AB379A/B PCI-X Fibre Channel Adapter HP A6826A PCI-X Fibre Channel Adapter Notes: 1. ATDD does not support tape deices that are attached to HSC/GSC bus architectures. 2. For attachment of Enterprise Tape System 3590 and IBM Magstar MP deices to HP rp8400 (formerly V-Class) platforms, a feedthrough SCSI terminator, which attaches to the A4800A Host Bus Adapter, is required. This feedthrough SCSI terminator is aailable as FC 9798 for Enterprise Tape System 3590 and FC 5098 for the 3575 Tape Library Dataserer or MP 3570 C model tape subsystem. Attach the male end of the feedthrough SCSI terminator to the host adapter and connect the host end of the standard FC 51xx SCSI cable to the feedthrough terminator. Terminate the SCSI bus at the last deice on the bus as usual. 3. The low leel FC-Tape protocol standard is not supported in the HP A5158A HBA firmware and users should restrict their SAN configurations. The jobs are aborted with HP-UX A5158A HBA configurations when errors are detected in the SAN. The HP A5158A host adapter is not compliant with the Fibre Channel Protocol for SCSI, second ersion (FCP-2), dated 17 Noember 2000, a draft proposed by the American National Standard of Accredited Standards Committee (NCITS). 4. Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. Tape and disk deices 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 hae been obsered. These issues are resoled by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring serer and storage configuration interoperability. It strongly recommends that your implementation plan includes proisions for separating disk and tape workloads. 5. The HP A6826A HBAs need the Qlogic firmware leel B or later. If the adapter is directly connected to a 3592 without a switch, then the topology on the drie port needs to be set to L-port. The most recent supported HBA information can be found at the following site: Software Requirements The following software is required and supported by ATDD: HP-UX operating system ersion 10.20, 11.0, 11i 1, 11i 2, and 11i 3. SCSI and FC Host Bus Adapter (HBA) is supplied by HP. Refer to HP s documentation for the SCSI and FC adapter to determine which patch is required. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 55

74 HP-UX Deice Drier (ATDD) The latest drier information can be found on our fix central website, which is explained in Appendix A, Accessing Documentation and Software Online, on page 317. Attention: To install ATDD in HP-UX 11i 3, some HP-UX patches must be applied first on the system. For the detailed information, refer to the atdd.readme file which is downloaded with the drier. Software Interface to the Deice Drier The IBM Tape and Medium Changer Deice Drier for HP-UX proides the following standard HP-UX entry points for IBM tape systems: Open Write Read Close IOCTL This entry point is drien by the open system function call. This entry point is drien by the write system function call. This entry point is drien by the read system function call. This entry point is drien explicitly by the close system function call and implicitly by the operating system at program termination. This entry point is drien by the input/output control (ioctl) system function call. It proides a set of tape deice, medium changer deice, and SCSI specific operations. It allows HP-UX applications to access and control the features and attributes of IBM SCSI tape subsystems programmatically. For programming information, refer to the IBM Tape Deice Driers Programming Reference, GA Installation and Configuration Instructions The following sections describe the installation and configuration for three types of HP-UX deices. Installation and Configuration for PCI Driers This chapter describes how to install, configure, and uninstall the IBM Tape and Medium Changer Deice Drier for HP-UX (ATDD) for PCI-based systems. By default, ATDD automatically configures all supported IBM tape dries that are attached and powered On when the system starts. ACDD, the changer part of ATDD, does not configure IBM Medium Changer deices by default because many applications use either their own changer driers or the natie schgr or sctl driers. In HP-UX 11.0, 11i 1 and 2, the ATDD package includes with atdd tape drier and acdd changer drier dynamic loadable kernel modules (DLKM). In HP-UX 11i 3, the ATDD package consists of fie modules in the kernel: atdd - static tape drier kernel module acdd - static changer drier kernel module atdd_leg - static legacy tape drier kernel module acdd_leg - static legacy changer drier kernel module atdd_core - DLKM core kernel module Oeriew of the Installation Process During and after the ATDD is installed, ACDD, the changer part of ATDD, can be set to configure (CLAIM) all attached IBM Medium Changer deices. Additionally, selected IBM Medium Changer deices can be configured by running the swinstall 56 IBM Tape Deice Driers Installation and User s Guide

75 HP-UX Deice Drier (ATDD) command with the -x ask=true command option, or by running /opt/atdd/bin/atdd_claim c c in 11.0, 11i 1 and 2. The installation process depends on whether all IBM tape dries are to be configured by ATDD or only selected ones, and whether configured tape dries exhibit default behaior or require specific configuration settings. Additionally, for IBM Medium Changers, installation selection or post-installation configuration can determine whether all IBM Medium Changers should be configured, selectiely configured, or NOT configured at all. Preinstallation Considerations Make sure your system is ready to install ATDD before you begin. Follow these steps to perform the install: 1. Copy the software from the distribution medium to the depot. 2. Check the README file and erify that your system is configured appropriately for installing ATDD. 3. Ensure that the tape dries to be managed by ATDD are powered on. 4. Install and configure the software. The following describes facts about the command sequences: In some of the examples, filenames gien on the command-line must be referenced with an absolute path. Using 'pwd'/filename to reference a file instead of filename ensures this. All the software distributor commands (for example, swinstall or swcopy) can be run first with the -p flag to preiew the command. After obsering the preiew output, you can reissue the command without the -p flag to perform the actual operation. The software distributor commands are moderately complex scripts that frequently require seeral steps. The steps are typically Selection, Analysis, and Execution. Each step may produce useful information and error messages, so it is a good idea to carefully obsere the results of the installation process as it occurs. If you encounter unexpected results during the installation, check the associated log file. While using the software distributor commands, you may encounter the following error about mounted file systems: ERROR: "hostname/": One or more filesystems that appear in the filesystem table are not mounted and cannot be mounted. Many commands (for example, swinstall and swremoe) attempt to mount all file systems in the /etc/fstab file at the start of the analysis phase. This ensures that all listed file systems are mounted before proceeding. This also helps ensure that files are not loaded into a directory that may be below a future mount point, but it often causes an error with NFS mounted file systems. This error can be oerridden using '-x' to set the mount_all_filesystems option to FALSE. When this option is used, the command finishes with a warning that indicates no attempt is made to mount all file systems. For example: # swinstall -x mount_all_filesystems=false -x ask=true -x autoreboot=true atdd WARNING: "hostname:/": There will be no attempt to mount filesystems that appear in the filesystem table. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 57

76 HP-UX Deice Drier (ATDD) Create the Drie Configuration File, (Optional) If you are not using the standard deice drier defaults, you must create a configuration file that directs the deice drier on how to customize drier behaior for particular IBM TotalStorage and System Storage deices. If all configured deices are to use the deice drier configuration defaults, it is not necessary to create a configuration file before installing the drier for ATDD. The Drie Configuration File is required if: You are running a leel of ATDD before leel on HP-UX You do not use the deice drier configuration defaults. If you do not need to create a Drie Configuration File, skip to the instructions in Power Off the Tape Dries on page 59. If you do need to create a Drie Configuration File, consult the following instructions. The configuration file is named sbin/init.d/atdd and has the following syntax: ATDD_global_parameter=alue ATDD_deice_parameter[index]=alue Note: Blank lines and lines starting with # are ignored. No spaces may appear within each entry. No trailing comments may appear on a ariable definition line. Determine the Deice Hardware Path for IBM Tape Dries: To determine the deice hardware path for IBM tape dries with a SCSI attachment, perform the following steps: 1. Run ioscan to determine the hardware path (i.e., the SCSI adapter) the tape drie is connected to. # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter: For example: 0/10/0/0 3. Determine the SCSI target address of the tape drie. HWPATH = adapterpath.drietargetaddress.0 (tape drie) For a tape drie at SCSI target address 3, the deice hardware path is: 0/10/0/0.3.0 To determine the deice hardware path for IBM tape dries with the Fibre Channel attachment, perform the following steps: 1. Run ioscan to determine the hardware path (i.e., the Fibre Channel) the tape drie is connected to. # ioscan -f -C tape 2. Record the hardware path entry of the Fibre Channel: For example: HWPATH = 0/5/0/ Create the Hardware Path Entry: You must tell the drier which hardware path you want to attach to if you are not using the installation defaults for drier behaior. Create an entry in the /etc/rc.config.d/atdd configuration file for each deice you want the drier to attach. For example: 58 IBM Tape Deice Driers Installation and User s Guide

77 HP-UX Deice Drier (ATDD) ATDD_HWPATH[0]=0/10/0/0.1.0 ATDD_HWPATH[1]=0/10/0/0.6.0 ATDD_HWPATH[2]=0/5/0/ Note: This example shows that three deices are CLAIMED by the ATDD. If you hae a single 3590 deice operating in one LUN mode, then you would hae only a single ATDD_HWPATH entry. If you hae four tape deices attached, four ATDD_HWPATH entries are required in the configuration file. Create the Deice Specific Configuration Entries (Optional): The ATDD is shipped with default settings for all configuration parameters. To change these settings, an entry is made in the configuration file assigning an appropriate alue to the desired configuration ariable. Each deice may hae a different alue for each configuration ariable. The index number associated with the configuration ariable associates the parameter setting with the deice at the hardware path with the same index. Example 1: ATDD_IMMEDIATE[0]=1 This parameter allows application control to return from the deice before the rewind completes for the deice at hardware path 0/10/0/0.1.0 (based on the hardware path entry in Create the Hardware Path Entry on page 58). Example 2: ATDD_TRAILER[1]=1 This parameter allows write operations after an early end-of-tape warning for the deice at hardware path 0/10/0/ Refer to Table 8 on page 74 and Table 9 on page 75 for a description of all configuration parameters. Note: If you experience difficulties with your tape deice, check the /etc/rc.log for errors and correct the problem. Power Off the Tape Dries When the ATDD software is initially installed, it attaches itself to all tape dries that are in the CLAIMED state as shown by entering the command: # ioscan -fk -C tape Before you continue, make sure all deices CLAIMED with the preceding command are deices you want this deice drier to manage. To list deice file names in the /de directory and its subdirectories, enter: # ioscan -func tape In HP-UX 11i 3, you can also enter: # ioscan -funnc tape To remoe a tape drie from the CLAIMED state so it is not configured by this drier, power Off the tape drie and run ioscan without the '-k' argument as follows: # ioscan -f -C tape Chapter 4. HP-UX Tape and Medium Changer Deice Drier 59

78 HP-UX Deice Drier (ATDD) Install the Drier Using the ATDD Installation Script An installation script (InstallAtdd) is proided to automate drier installation and perform some checking functions. It copies the latest ersion of the drier to the software depot and installs the latest drier ersion. To install ATDD with the script, download the install script with the drier at fix central, then run the install script. When the installation script runs, the customer is prompted with the question, "Would you like to actiate the Medium Changer support by ATDD (Y/N)?". Enter "Y" to allow the ATDD to configure all attached IBM Medium Changer deices, or answer "N" to allow the HP natie changer drier to configure these Medium Changer deices. Notes: 1. If a preious ersion of ATDD is installed on your system, uninstall it before attempting to install the latest ersion. Refer to Uninstalling the software on page The system reboot is required to install ATDD in HP-UX 11i 3. To install ATDD manually, follow the steps in Install Driers Manually. Install Driers Manually Installing the driers manually requires the steps detailed in the following sections. 1. Copy the Software to the Software Depot on page Install the ATDD Software on page If a preious ersion of ATDD is installed on your system, uninstall it before attempting to install the latest ersion. Refer to Uninstalling the software on page 64. Copy the Software to the Software Depot: Attention: If you do not copy the ATDD software into a depot, you will not be able to uninstall the product readily. Copy the appropriate drier to the Software Depot. For example: # swcopy -p -s /drier_location/atdd.x.x.x.x atdd (preiew option) # swcopy -s /drier_location/atdd.x.x.x.x atdd Use swlist to erify that the ATDD software is in the depot: # swlist -d atdd Install the ATDD Software: When the software is in the depot and only the appropriate dries are powered on, the ATDD software can be installed to the root file system using the HP-UX swinstall command. If the target root file system is the primary, the ATDD software is configured automatically upon installation. If the target is an alternate root file system, then the ATDD software is not configured automatically. 60 IBM Tape Deice Driers Installation and User s Guide

79 HP-UX Deice Drier (ATDD) Note: If an earlier ersion of the product is already installed on the target root file system, the existing ersion is replaced. This is true een if the ersion already installed is more recent than the ersion being installed. The following commands install ATDD from the depot to the default root file system by issuing the swinstall command with the ask options set as follows: # swinstall -p -x ask=true atdd (preiew option) # swinstall -x ask=true atdd in HP-UX 11.0, 11i 1, and 2 # swinstall -x autoreboot=true -x ask=true atdd in HP-UX 11i 3 Running the swinstall command with the ask option set to TRUE prompts the customer, "Would you like to actiate the Medium Changer support by ATDD (Y/N)?". Enter "Y" to allow the ATDD to configure all attached IBM Medium Changer deices, or answer "N" to allow the HP natie changer drier to configure these Medium Changer deices. You can use swlist to list the software installed on the default root file system as follows: # swlist atdd You can erify correct installation to the default root file system with the swerify command as follows: # swerify atdd After the installation is completed, run the ioscan command to list the tape dries found: # ioscan -fknc tape Class I H/W Path Drier S/W State H/W Type Description ============================================================================================ tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11 /de/rmt/0m /de/rmt/0mn /de/rmt/c4t5d0best /de/rmt/c4t5d0bestn /de/rmt/0mb /de/rmt/0mnb /de/rmt/c4t5d0bestb /de/rmt/c4t5d0bestnb tape 1 0/3/0/0.6.0 atdd CLAIMED DEVICE IBM 03590B11 /de/rmt/1m /de/rmt/1mn /de/rmt/c4t6d0best /de/rmt/c4t6d0bestn /de/rmt/1mb /de/rmt/1mnb /de/rmt/c4t6d0bestb /de/rmt/c4t6d0bestnb tape 4 0/5/0/ atdd CLAIMED DEVICE IBM ULT3580-TD1 /de/rmt/4m /de/rmt/4mn /de/rmt/c6t0d2best /de/rmt/c6t0d2bestn /de/rmt/4mb /de/rmt/4mnb /de/rmt/c6t0d2bestb /de/rmt/c6t0d2bes If you hae enabled ACDD, run the following ioscan command to iew the medium changers found: # ioscan -fnkc autoch Class I H/W Path Drier S/W State H/W Type Description ======================================================================= autoch 0 0/3/0/0.5.1 acdd CLAIMED DEVICE IBM 03590E11 /de/rmt/0chng autoch 2 0/6/0/ acdd CLAIMED DEVICE IBM 03590E11 /de/rmt/2chng autoch 4 0/5/0/ acdd CLAIMED DEVICE IBM ULT3583-TL /de/rmt/4chng In HP-UX 11i 3, run # ioscan -funnc tape or autoch to display the tape deices configured with ATDD and ACDD driers. Run #ioscan -func tape or autoch to show the tape deices bound with the legacy atdd_leg and acdd_leg driers. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 61

80 HP-UX Deice Drier (ATDD) Configure all IBM Tape Dries/Media Changers with ATDD/ACDD: By default, ATDD automatically configures all supported IBM tape dries that are attached and powered on when the ATDD package is installed. The ACDD drier does not configure IBM Medium Changer deices by default. To configure all IBM Medium Changer deices on the system during the install of ATDD package, run the swinstall command with the -x ask=true command option and answer "Yes" to allow the ACDD to claim these deices. To configure all IBM Medium Changer deices on the system after the install of the ATDD package: In HP-UX 11.0, 11i 1 and 2, run the command: # /opt/atdd/bin/atdd_claim -c In HP-UX 11i 3, do the following: 1. Bind each changer deice with the ACDD drier: # ioscan -b -M acdd -H hw_path 2. Reboot the system to configure the changer deices: # shutdown -ry now To remoe the claim with ACDD after the next reboot: In HP-UX 11.0, 11i 1 and 2, run the command: # /opt/atdd/bin/atdd_claim -u In HP-UX 11i 3, do the following: 1. Bind each changer deice with a changer drier: # ioscan -b -M acdd -H hw_path 2. Reboot the system to unconfigure the changer deices: # shutdown -ry now Configure Selected IBM Tape Deices with ATDD/ACDD in HP-UX 11.0, 11i 1 and 2: Attaching Selected IBM Tape Deices to ATDD/ACDD During Auto Booting: To claim a specific tape deice with atdd/acdd during reboot, edit the "Claiming Deice" section in the file of /sbin/init.d/atdd. For example, to attach IBM 3590E11 medium changer with acdd drier: 1. To determine the HW path: # ioscan -fnkgrep IBM autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11 2. Comment out the command line(s) in the init script of /sbin/init.d/atdd: For tape dries: /opt/atdd/bin/atdd_claim -t For medium changers: /opt/atdd/bin/atdd_claim -c 3. Add a command line in the "Configuring Deice" section in /sbin/init.d/atdd: /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1 Attaching Selected IBM Tape Deices to ATDD/ACDD Dynamically: To dynamically attach selected IBM tape deice after the ATDD installation, run the following commands. 1. To determine the HW path of the deice: 62 IBM Tape Deice Driers Installation and User s Guide

81 HP-UX Deice Drier (ATDD) # ioscan -fnkgrep IBM autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11 2. To claim the deice with ATDD/ACDD: # /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1 Note: The dynamic attachment may be lost after the system reboots. Attaching Selected IBM Tape Deice with a Particular Drier: Use the system ioscan and rmsf commands to force a non-atdd/acdd drier to bind an IBM tape deice. For example, force bind the IBM 3590E media changer with the HP natie changer drier schgr with these steps: 1. Determine the HW path of the deice: # ioscan -fnk grep IBM tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11 autoch 0 0/3/0/0.5.1 acdd CLAIMED DEVICE IBM 03590E11 2. Remoe the I/O configuration from the system: # rmsf -H 0/3/0/ Force binding: # ioscan -M schgr -H 0/3/0/ Create the deice special files: # insf -H 0/3/0/ Verify the force binding: # ioscan -fnk grep IBM tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11 autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11 Note: The force binding is lost after the system reboots. To keep the binding to a selected deice with a particular drier after a reboot, add these command-lines in steps 2 4 in "Claiming Deice" section in /sbin/init.d/atdd file. For example, # Configuring Deice Section: # add specific deice claim here, for example # /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1 # /opt/atdd/bin/atdd_claim -H 0/6/0/ rmsf -H 0/3/0/0.5.1 ioscan -M schgr -H 0/3/0/0.5.1 insf -H 0/3/0/0.5.1 Configure Selected IBM Tape Deices with ATDD/ACDD in HP-UX 11i 3: By default, atdd drier automatically configures all supported IBM tape dries that are attached and powered on when the ATDD package is installed. The acdd drier does not configure IBM medium changer deices by default. All of IBM medium changers are claimed if you use acdd and acdd_leg as the changer driers during ATDD are installed. To attach a selected IBM tape deice with a particular drier, run the system ioscan command to force a non-atdd/acdd drier to bind an IBM tape deice, and then reboot the system. For example, to force bind the IBM 3592E05 tape drie with the HP natie tape drier estape, perform these steps: 1. Determine the HW path of the deice: # ioscan -fnk grep IBM tape /0xfa00/0x7 atdd CLAIMED DEVICE IBM 03592E05 2. Force the binding: # ioscan -b -M estape -H 64000/0xfa00/0x7 3. Reboot the system: Chapter 4. HP-UX Tape and Medium Changer Deice Drier 63

82 HP-UX Deice Drier (ATDD) # shutdown -ry now 4. Create the deice special files if it does not exist after the system bootup: # insf -H 64000/0xfa00/0x7 5. Verify the force binding: # ioscan -fnk grep IBM tape /0xfa00/0x7 estape CLAIMED DEVICE IBM 03592E05 Uninstalling the software: Attention: Do not try to uninstall the ATDD software by simply deleting the files that make up the ATDD fileset. This causes a number of inconsistencies on the system. It is best to use the swremoe command. To uninstall ATDD (from the root file system): # swremoe atdd in HP-UX 11.0, 11i 1 and 2 # swremoe -x autoreboot=true atdd in HP-UX 11i 3 Other Administratie Tasks: To determine whether the current ersion of ATDD is installed or configured on the default root file system: # swlist -a state atdd To determine the ersions of ATDD stored in the default depot: # swlist -d atdd To remoe ATDD from the depot: # swremoe -d atdd If more than one leel of ATDD exists in the depot, explicitly specify the leel to remoe it. For example: # swremoe -d atdd,r= To iew the fileset of ATDD installed on the system: # swlist -l file atdd To display and manage ATDD kernel modules and kernel-tunable parameters, run kmadmin, kmsystem, kmtute and kmadmin commands in HP-UX 11.0 and 11i 1 and kcmodule, kctune commands in HP-UX 11i 2 and 3, or go to the Kernel Configuration in sam utility. Refer to the system manual for more detail. For an example, print out the ATDD drier module status entering the command: # kcmodule -d atdd Module State Cause Description atdd static explicit Adanced Tape Deice Drier Installation and Configuration of Precision Bus Driers This chapter describes how to install, configure, and uninstall the IBM Tape and Medium Changer Deice Drier for HP-UX (ATDD) for HP Precision Bus (HP-PB) systems. Preinstallation Considerations Make sure your system is ready to install ATDD before you begin. Follow these steps to perform the install: 1. Copy the software from the distribution medium to the depot. 64 IBM Tape Deice Driers Installation and User s Guide

83 HP-UX Deice Drier (ATDD) 2. Check the README file and erify that your system is configured appropriately for installing ATDD. 3. Ensure that the tape dries to be managed by ATDD are powered on. 4. Install and configure the software. Note the following facts about the command sequences described in this section: In some of the examples, filenames gien on the command-line must be referenced with an absolute path. Using 'pwd'/filename to reference a file instead of filename ensures this. All the software distributor commands (for example, swinstall or swcopy) can first be run with the -p flag to preiew the command. After obsering the preiew output, you can reissue the command without the -p flag to perform the actual operation. The software distributor commands are moderately complex scripts that frequently require seeral steps. The steps are typically Selection, Analysis, and Execution. Each step may produce useful information and error messages. It is a good idea to obsere carefully the results of the installation process as it occurs. If you encounter unexpected results during the installation, check the associated log file. While using the software distributor commands, you may encounter the following error about mounted file systems: ERROR: "hostname/": One or more filesystems that appear in the filesystem table are not mounted and cannot be mounted. Many commands (for example, swinstall and swremoe) attempt to mount all file systems in the /etc/fstab file at the start of the analysis phase. This ensures that all listed file systems are mounted before proceeding. This also helps ensure that files are not loaded into a directory that may be below a future mount point, but it often causes an error with NFS mounted file systems. This error can be oerridden using '-x' to set the mount_all_filesystems option to FALSE. When this option is used, the command finishes with a warning indicating that no attempt is made to mount all file systems. For example # swinstall -x mount_all_filesystems=false -x autoreboot=true atdd WARNING: "hostname:/": There will be no attempt to mount filesystems that appear in the filesystem table. Create the Configuration File A configuration file must be created that tells the deice drier how to customize your configuration. The file is named etc/rc.config.d/atdd.cfg and has the following syntax: ATDD_global_parameter=alue ATDD_deice_parameter[index]=alue Note: Blank lines and lines that start with # are ignored. No spaces can appear within each entry. No trailing comments can appear on a ariable definition line. Determine the Deice Hardware Path for Enterprise Tape System 3590: determine the deice hardware path, follow these steps: To Chapter 4. HP-UX Tape and Medium Changer Deice Drier 65

84 HP-UX Deice Drier (ATDD) 1. Run ioscan to determine which SCSI adapter the 3590 drie is connected to. # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter: for example, 56/40 3. Determine the SCSI target address of the 3590 drie. The panel on the front of the 3590 drie displays the selected target address. HWPATH = adapterpath.drietargetaddress.0 (3590 one LUN mode) or HWPATH = adapterpath.drietargetaddress.0 HWPATH = adapterpath.drietargetaddress.1 (3590 random 2 LUN mode) For a 3590 at SCSI target address 3 in random 2 LUN mode, the deice hardware paths are: 56/ / Determine the Deice Hardware Path for Magstar MP 3570 Tape Subsystem: The Magstar MP 3570 product family consists of stand alone tape dries (Models B00 and C00) and library models with one or two tape dries. Models B01, B02, B11, B12, C01, C02, C11, and C12 support a 20 cartridge, random access cartridge loader and are known as library units. To control the operation of the library mechanism, SCSI Medium Changer commands are issued to LUN 1 of one or both of the drie ports depending on the library configuration. Base configuration is intended for attachment of one or two drie libraries on a single SCSI bus. Control of the library is accomplished by sending Medium Changer commands to LUN 1 of drie 1 (the drie on the left as iewed from the rear of the library). The hardware path definitions present in the atdd.cfg file must include a definition for drie 1 LUN 1 for operation of the library mechanism. Models B02, B12, C02, and C12 can operate in a split configuration where each drie and a subset of the cartridge slots are iewed as an independent library. In this case, a definition for LUN 1 for each drie must be present in the atdd.cfg file to control each logical library independently. Typically, independent SCSI buses are used for operation of each logical library. To determine the deice hardware path, follow these steps: 1. Run ioscan to determine which SCSI adapter the Magstar MP library drie is connected to. # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter: for example, 56/40 3. Determine the SCSI target addresses of the Magstar MP dries. The panel on the front of the Magstar MP library displays the selected target addresses. HWPATH = adapterpath.drietargetaddress.0 (Magstar MP drie) HWPATH = adapterpath.drietargetaddress.1 (Magstar MP library changer) For a Magstar MP library with a single drie at target address 3 in base configuration, the deice hardware paths are: 66 IBM Tape Deice Driers Installation and User s Guide

85 HP-UX Deice Drier (ATDD) 56/ / Determine the Deice Hardware Path for Magstar MP 3575 Tape Libraries: Each drie in a 3575 library can support an automation path for the logical library of which it is a member by sending SCSI Medium Changer commands to LUN 1 of the drie port. The 3575 Model L06 supports one logical library. The other 3575 tape libraries (Models L12, L18, L24, and L32) can support two or three logical libraries depending on the specific model. The first drie in each logical library must hae LUN 1 configured to operate the automation for that logical library (drie 1 for logical library 1, drie 3 for logical library 2, and drie 5 for logical library 3). Other dries may hae LUN 1 configured, but this is optional. LUN 1 control of the library mechanism can be configured for any drie by way of the front panel on the library. Conceiably, LUN 1 could be configured for two dries in the same logical library, but this is unnecessary in most instances. In that case, the automation conforms to the SCSI-3 Primary Commands standard for multiple port behaior (except for the handling of reserations). Access to a logical library is on a first-come, first-sered basis for hosts accessing the same logical library on different ports. Each port can accept commands while the library is in use by another host by way of another port. The 3575 deiates from the SCSI-3 specification in that deice and element reserations issued on one port apply only to those hosts that access that port. Initiators connected to the same logical library through an alternate port are not subject to those reserations. Special files for operation of the 3575 automation are based on the hardware path definitions present in the atdd.cfg file. Target deice LUN 1 also needs to be enabled at the library operator panel for dries other than the first drie in each logical library if they are used to accept automation commands. LUN 1 for the first drie in each logical library is mandatory and is enabled automatically by the library firmware. To determine the deice hardware path, follow these steps: 1. Run ioscan to determine which SCSI adapter the Magstar MP library drie is connected to. # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter: For example, 56/40 3. Determine the SCSI target addresses of the Magstar MP dries. The panel on the front of the 3575 library displays the selected target addresses. HWPATH = adapterpath.drietargetaddress1.0 (Magstar MP drie) HWPATH = adapterpath.drietargetaddress2.0 (Magstar MP drie) HWPATH = adapterpath.drietargetaddress1.1 (3575 library control path) For a 3575 library with two dries in one logical library (drie 1 at SCSI target 3 and drie 2 at SCSI target 4), the deice hardware paths are: 56/ / / Chapter 4. HP-UX Tape and Medium Changer Deice Drier 67

86 HP-UX Deice Drier (ATDD) Determine the Drie Hardware Path for IBM 3580 Ultrium Tape Drie, 3581 Tape Autoloader with SCSI Attachment: To determine the hardware path for the 3580 Tape Drie and the 3581 Tape Autoloader with SCSI attachment, follow this procedure: 1. Run ioscan to determine which SCSI adapter the IBM Ultrium drie or autoloader is connected to: # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter, for example, 0/4/0/0. 3. Determine the SCSI target address of the IBM Ultrium drie (3580) or the drie in the IBM 3581 Ultrium Tape Autoloader. The switch on the rear of the IBM 3580 Ultrium Tape Drie displays the selected SCSI target address. The LCD panel on the front of the unit can display the drie (and medium changer SCSI address) for the IBM 3581 Ultrium Tape Autoloader. HWPATH=adapterpath.drietargetaddress.0 (3580 drie) or HWPATH=adapterpath.drietargetaddress.0 (3581 drie) For an IBM 3581 Ultrium Tape Autoloader at SCSI target address 3, the drie deice hardware path is: 0/4/0/0.3.0 Determine the Drie Hardware Paths for IBM Ultrium Tape Libraries with SCSI Attachment: To determine the hardware path for the 3582, 3583, and 3584 Tape Libraries with SCSI attachment, follow this procedure: 1. Run ioscan to determine which SCSI adapter the IBM Ultrium Tape Library is connected to: # ioscan -f -C ext_bus 2. Record the hardware path entry of the adapter, for example: 1/8/0/0 3. Determine the SCSI target addresses of the IBM Ultrium dries in the Tape Library. The LCD panel on the front of the unit can display the drie (and medium changer) SCSI addresses. HWPATH=adapterpath.drietargetaddress.0 (drie 1) HWPATH=adapterpath.drietargetaddress.0 (drie n) The drie hardware paths for an IBM Ultrium 3583 Tape Library with a drie at SCSI ID 3 and SCSI ID 5 are: 1/8/0/ /8/0/0.5.0 Determine the Drie Hardware Paths for IBM 3580 Ultrium Tape Drie, IBM Ultrium Tape Libraries with Fibre Channel Attachment: To determine the hardware path for the 3580 tape drie and the 3582, 3583, and 3584 tape library with fibre channel attachment, follow this procedure: 1. Run ioscan to determine which hardware path the IBM Ultrium drie is connected to: # ioscan -f -C tape 2. Record the hardware path entry of the IBM Ultrium Fibre Channel drie. For example, 0/5/0/ (3580 stand alone tape drie) 0/8/0/ (3583 drie 1) 0/8/0/ (3583 drie 2) 68 IBM Tape Deice Driers Installation and User s Guide

87 HP-UX Deice Drier (ATDD) Create the Hardware Path Entry for Ultrium Tape Dries: If deices are to be configured with settings other than the defaults, entries defining the hardware deice paths must be placed in the /etc/rc.config.d/atdd configuration file. Create an entry for each deice that requires further configuration settings. The format for the entries is HW_PATH[index]=DeiceHardwarePath. The index is used to identify the deice for control of the configuration settings in the next section. For example: ATDD_HWPATH[0]=0/4/0/0.1.0 (3580 stand alone SCSI drie) ATDD_HWPATH[1]=1/10/0/0.5.0 (3581 SCSI drie 1) ATDD_HWPATH[2]=1/10/0/0.6.0 (3581 SCSI drie 2) ATDD_HWPATH[3]=0/5/0/ (3580 stand alone FC drie) ATDD_HWPATH[4]=0/8/0/ (3583 SCSI drie 1 with SDG) ATDD_HWPATH[5]=0/8/0/ (3583 SCSI drie 2 with SDG) This example shows that four deices are CLAIMED by the ATDD. The first deice, 3580 Stand Alone SCSI Tape Drie at SCSI target address 1, LUN 0, has index=0. The second deice, 3581 with two 3580 SCSI Tape Dries inside at SCSI target addresses 5 and 6, LUN 0, has index=1 and 2. The third deice, 3580 Stand Alone FC Tape Drie at target 9, LUN 0, has index=3. The last one is 3583 with SAN Data Gateway (SDG) Module and two 3580 SCSI Tape Dries at target 0, LUN2and3(index=4 and 5). Create the Hardware Path Entry: You must tell the drier which hardware path you want to attach to. Create an entry in the /etc/rc.config.d/atdd.cfg configuration file for each deice you want the drier to attach. For example ATDD_HWPATH[0]=56/ ATDD_HWPATH[1]=56/ Note: This example shows that two deices are CLAIMED by ATDD. If you hae a single 3590 deice operating in one LUN mode, then you would hae only a single ATDD_HWPATH entry. If you hae three tape deices attached, three ATDD_HWPATH entries are required in the configuration file. For 3590 deices configured in random 2 LUN mode, two hardware path entries are required. One is needed for the drie (LUN 0), and one is needed for the ACF (LUN 1). At least one hardware path entry is required in the configuration file. Create the Deice Specific Configuration Entries (Optional): The ATDD is shipped with default settings for all configuration parameters. To change these settings, an entry is made in the configuration file assigning an appropriate alue to the desired configuration ariable. Each deice may hae a different alue for each configuration ariable. The index number associated with the configuration ariable associates the parameter setting with the deice at the hardware path with the same index. Example 1: ATDD_IMMEDIATE[0]=1 This allows application control back from the deice before rewind is complete for the deice at hardware path 56 / (based on the hardware path entry in Create the Hardware Path Entry on page 69). Example 2: Chapter 4. HP-UX Tape and Medium Changer Deice Drier 69

88 HP-UX Deice Drier (ATDD) ATDD_TRAILER[1]=1 This allows write operations after an early end-of-tape warning for the deice at hardware path 56 / Refer to Table 8 on page 74 and Table 9 on page 75 for a description of all configuration parameters. Note: If you experience difficulties with your tape deice, check the /etc/rc.log for errors and correct the problem. Power Off the Tape Dries When the ATDD software is initially installed, it attaches itself to all tape dries that are in the CLAIMED state as shown by entering the command: # ioscan -fk -C tape Before you continue, make sure all deices that report CLAIMED with the preceding command are deices you want this deice drier to manage. To list deice file names in the /de directory and its subdirectories, enter: # ioscan -func tape To remoe a tape drie from the CLAIMED state so it is not be configured by this drier, power Off the tape drie and run ioscan without the '-k' argument as follows: # ioscan -f -C tape Install the Drie Using the ATDD Installation Script An installation script (Install Atdd) is proided to automate drier installation and perform some checking functions. It copies the latest ersion of the drier to the software depot and installs the latest drier ersion. To install ATDD with the script, download the install script with the drier at fix central, then run the install script. When the installation script runs, the customer is prompted with the question, "would you like to actiate the Medium Changer support by ATDD (Y/N)?" Enter "Y" to allow the ATDD to configure all attached IBM Medium Changer deices, or answer "N" to allow the HP natie changer drier to configure these Medium Changer deices. Note: If a preious ersion of ATDD is installed on your system, uninstall it before attempting to install the latest ersion. To install ATDD manually, follow the steps in Install Driers Manually on page 60. Copy the Software to the Software Depot Attention: If you do not copy the ATDD software into a depot, you will not be able to uninstall the product readily. # swcopy -p -s /drier_location/atdd.x.x.x.x atdd (preiew option) # swcopy -s /drier_location/atdd.x.x.x.x atdd 70 IBM Tape Deice Driers Installation and User s Guide

89 HP-UX Deice Drier (ATDD) Use swlist to erify that the ATDD software is in the depot: # swlist -d atdd Reiew the ATDD README File After copying the ATDD software to the depot, use the swlist command to iew the README file under the directory /opt/omimag/readme. # swlist -d -a readme atdd The README file lists the system configuration requirements, including required system software patches and required tape related firmware ersions. The file also documents any changes in the installation, use, and administration of the software that occurred after this documentation was completed. It is therefore ery important that you reiew it before proceeding with the software installation. Install the ATDD Software When the software is in the depot and only the appropriate dries are powered on, the ATDD software can be installed to the root file system using the HP-UX swinstall command. If the target root file system is the primary, the ATDD software is configured automatically upon installation. Configuration requires restarting the system and rebuilding the kernel. This requires you to issue the swinstall command with the -x autoreboot option set to TRUE, as described below. If the target is an alternate root file system, the ATDD software is not configured automatically. Note: If an earlier ersion of the product is already installed on the target root file system, the existing ersion is replaced. This is true een if the ersion already installed is more recent than the ersion being installed. The following commands install ATDD from the depot to the default root file system: # swinstall -p atdd (preiew option) # swinstall atdd If you get an error message stating that this product needs to restart the system, reissue the swinstall command with the autoreboot option set as follows: # swinstall -p -x autoreboot=true atdd (preiew option) # swinstall -x autoreboot=true atdd You can use swlist to list the software installed on the default root file system as follows: # swlist atdd You can erify correct installation to the default root file system with the swerify command as follows: # swerify atdd Chapter 4. HP-UX Tape and Medium Changer Deice Drier 71

90 HP-UX Deice Drier (ATDD) After the installation is completed, run the ioscan command to list the tape dries found: # ioscan -fknc tape Class I H/W Path Drier S/W State H/W Type Description ============================================================================================ tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11 /de/rmt/0m /de/rmt/0mn /de/rmt/c4t5d0best /de/rmt/c4t5d0bestn /de/rmt/0mb /de/rmt/0mnb /de/rmt/c4t5d0bestb /de/rmt/c4t5d0bestnb tape 1 0/3/0/0.6.0 atdd CLAIMED DEVICE IBM 03590B11 /de/rmt/1m /de/rmt/1mn /de/rmt/c4t6d0best /de/rmt/c4t6d0bestn /de/rmt/1mb /de/rmt/1mnb /de/rmt/c4t6d0bestb /de/rmt/c4t6d0bestnb tape 4 0/5/0/ atdd CLAIMED DEVICE IBM ULT3580-TD1 /de/rmt/4m /de/rmt/4mn /de/rmt/c6t0d2best /de/rmt/c6t0d2bestn /de/rmt/4mb /de/rmt/4mnb /de/rmt/c6t0d2bestb /de/rmt/c6t0d2bestnb If you hae enabled ACDD, run the following ioscan command to iew the medium changers found: # ioscan -fnkc autoch Class I H/W Path Drier S/W State H/W Type Description ======================================================================= autoch 0 0/3/0/0.5.1 acdd CLAIMED DEVICE IBM 03590E11 /de/rmt/0chng autoch 2 0/6/0/ acdd CLAIMED DEVICE IBM 03590E11 /de/rmt/2chng autoch 4 0/5/0/ acdd CLAIMED DEVICE IBM ULT3583-TL /de/rmt/4chng Adding an IBM Tape Deice Using the Currently Installed ATDD To add an IBM tape deice using the currently installed ATDD, perform the following steps: 1. Modify the /stand/system file, adding a stanza in the form of: drier 56/ atdd with the adapter/drie path for your deice. 2. Modify /etc/rc.config.d/atdd.cfg, adding the hardware path and instance: ATDD_HWPATH[#]=56/ Where: # denotes the next instance and the adapter/drie path for your deice. 3. Build the kernel as root: # mk_kernel -o /stand/munix -s/stand/system 4. Restart the system: # shutdown -ry now or # reboot 5. After the system is up, run /opt/omimag/bin/atdd_mksf to create the new special files for the deice. atdd_mksf -ti <instance> Where: <instance> is the number from the ioscan output for the newly installed deice. This command echoes to console but does NOT create special files. To create the special files, pipe the command to sh as follows: # atdd_mksf -ti <instance> sh Note: A manual process is required for applications using the HP natie spt or sctl driers as a changer drier (the sctl drier for the ext_bus C700 or C720, the spt for the other ext_bus). This manual process requires haing the right 72 IBM Tape Deice Driers Installation and User s Guide

91 HP-UX Deice Drier (ATDD) drier in the kernel, possibly a binding statement in the kernel, and making a deice file. Related man pages are scsi_ctl (7) and scsi_pt (7). Other Administratie Tasks To determine the ersions of ATDD currently installed on the default root file system: # swlist -a state atdd To determine the ersions of ATDD stored in the default depot: # swlist -d state atdd To iew the set of files that is installed with ATDD: # swlist -l file atdd To remoe ATDD from the depot: # swremoe -d atdd If more than one leel of ATDD exists in the depot, explicitly specify the leel to remoe it. For example: # swremoe -d atdd,r= Supported Configuration Parameters This chapter describes the supported configuration alues for multiple deice types being configured on the same system. The configuration parameters are global. Because the configuration parameters are global to all deices, it is necessary to use configuration alues that perform reliably on all deices attached to your system. If you are experiencing difficulties, ensure that your drier is configured properly. To check your current configuration, use the atdd_cfg program located in /opt/omimag/bin for the static PB drier and in /opt/atdd/bin for the PCI drier. For program usage, execute as follows: For PB drier: # /opt/omimag/bin/atdd_cfg -h For PCI drier: # /opt/atdd/bin/atdd_cfg -h Configuration Parameter Definitions This section describes the configuration parameters and alues. Modifying the default settings is not recommended unless instructed to do so. The ATDD is shipped with default alues that allow the most reliable execution across arious deice types. Deice-Specific Parameters Some of the configuration parameters are deice-specific, while others are drier-specific. Table 8 on page 74 shows the parameters that are deice-specific, what they mean, and their alues. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 73

92 HP-UX Deice Drier (ATDD) Table 8. Deice-Specific Parameter Definitions Parameter Meaning Values DENSITY Density to use when writing/reading tape In hexadecimal SILI Suppress Incorrect Length 0=Off (do not suppress, by default) Indicator 1=On (suppress) FORCE_NARROW (Precision Bus Drier only) DISABLE_COPYIN_THRESHOLD (Precision Bus Drier only) COPY_THRESHOLD (Precision Bus Drier only) Width at which the drier negotiates for data transfers Protect against nonaligned buffers Minimum buffer size to start checking for proper alignment 0=Wide (16 bit wide data transfers, by default) 1=Narrow (8 bit wide data transfers) 0=Off (check buffers for alignment, by default) 1=On (use buffers without checking alignment) Size in bytes to force alignment check, 0 by default. BLOCKSIZE Block Size Size in bytes, 0 by default. COMPRESSION Compression Mode 0=Off (do not use compression at drie) 1=On (use compression at drie, by default) BUFFERING Buffering Mode 0=Off (do not buffer data) 1=On (buffer data to hardware buffers, by default) IMMEDIATE Immediate Mode 0=Off (wait for rewind completion, by default) 1=On (return before rewind is complete) TRAILER Trailer Label Processing 0=Off (do not allow writes past early EOT warning, by default) ERRNO_LEOT Error Number return for Logical End Of Tape) 1=On (allow writes past early EOT warning) Value returned for writes past EOM, 28 by default. RESERVE Multiple open for the deice 1=On (resere the deice after to open, by default) RESERVE_KEY WFM_IMMEDIATE The user specifies the Persistent Reseration key that will be used by the deice drier when the Persistent Reseration is used. Immediate Mode for Write File Mark 0=Off (do not resere the deice after to open) (multiple open support) 0 (the drier assigns the key by default) A string of 1-8 character ASCII alphanumeric key such as "key12345". If less than 8 characters are used, the remaining characters will be set to 0x00(NULL) 0=Off (wait for write file mark completion, by default) 1=On (return before write file mark is complete) 74 IBM Tape Deice Driers Installation and User s Guide

93 HP-UX Deice Drier (ATDD) Table 8. Deice-Specific Parameter Definitions (continued) Parameter Meaning Values PRE_V3_COMPAT Use to share tapes with blocksize > 256kb with HP-UX 11i 2 or earlier. Supported in HP-UX 11i 3 only. 0=Off (always write or read the date using the blocksize defined by user, by default) 1=On (split the blocksize less than 256 kb during the read or write) Drier-Specific Parameters Some of the configuration parameters are deice-specific, while others are drier-specific. Table 9 shows the parameters that are drier-specific, what they mean, and their alues. Table 9. Drier-Specific Parameters (Global) Parameter Meaning Values INSTANCE ATDD Deice Number (Read Only) DEVICES Number of Configured Deices (Read Only) MINPHYS (Precision Bus Drier only) Check/Adjust Transfer Count 0=Use OMI minphys 1=Use HP-UX minphys Modifying Configuration Parameters To change a configuration parameter, use the atdd_cfg program located in /opt/omimag/bin for the PB drier and in /opt/atdd/bin for the PCI drier. You can update the current alue. In HP-UX 11.0, 11i 1 and 2: For example, if you want to change the COMPRESSION parameter to 0 for the deice at hardware path 0/4/0/0.1.0, do the following: # atdd_cfg -g INSTANCE 0/4/0/0.1.0 INSTANCE: 2 The ATDD instance number for this deice is returned. You must use this INSTANCE alue (1) to set the COMPRESSION alue for this deice. # atdd_cfg -s COMPRESSION 0 2 Or, to get or modify COMPRESSION by using the hardware path: # atdd_cfg -g COMPRESSION 0/4/0/0.1.0 # atdd_cfg -s COMPRESSION 0 0/4/0/0.1.0 In HP-UX 11i 3: The usage of atdd_cfg command is: atdd_cfg -d special_file [-o parameter [-w alue]] All configurable parameters for the specified deice are displayed by entering #atdd_cfg -d special_file only For instance: # /opt/atdd/bin/atdd_cfg -d /de/rtape/tape14_best DENSITY=0 SILI=1 BLOCKSIZE=0 COMPRESSION=1 BUFFERING=1 REWIND_IMMEDIATE=0 Chapter 4. HP-UX Tape and Medium Changer Deice Drier 75

94 HP-UX Deice Drier (ATDD) TRAILER=1 SCALING=0 WRITEPROTECT=0 ERRNO_LEOT=28 WFM_IMMEDIATE=0 RESERVE=1 PRE_V3_COMPAT=0 To display a specific parameter, run #atdd_cfg -d special_file -o parameter For example, #/opt/atdd/bin/atdd_cfg -d /de/tape/tape14_bestn -o COMPRESSION COMPRESSION=1 To set a specific parameter, run #atdd_cfg -d special_file -o parameter -w alue For example, # atdd_cfg -d /de/rtape/tape14_bestn -o COMPRESSION -w 0 Success To set a new BOOT default alue for the configuration parameter, you must modify or add an entry in the atdd.cfg configuration file located in /etc/rc.config.d for the static drier or the atdd configuration file located in /sbin/init.d. For example, if you want the COMPRESSION default set to 0 for the deice at ATDD_HWPATH[0] or tape14_bestn, add the following line to your configuration file: In HP-UX 11.0, 11i 1 and 2: ATDD_COMPRESSION[0]=0 In HP-UX 11i 3: /opt/atdd/bin/atdd_cfg -d /de/rtape/tape14_bestn -o COMPRESSION -w 0 Note: The configuration parameters are prefixed with ATDD_ in the configuration file. For additional instructions about using the configuration program, use the -h option as follows: # atdd_cfg -h Configurable Kernel Parameters (Tunable) ATDD proides the following ariety of configurable kernel parameters that allow the users to customize for specific setup: atdd_log_trace Log the sense data in syslog when a hardware or medium error is occurred, see Sense Data Logging on page 84 for additional details. This parameter is enabled by default on 11i 3 and later, but disabled by default in 11i3 and earlier. alternate_pathing/atdd_alternate_pathing Enable or disable the alternate path support for CPF/DPF (see the specific operating system section that coers CPF and DPF support for detail). This parameter is enabled by default. atdd_disable_resere/atdd_disable_res Allows the user to disable the reseration management from ATDD. This parameter off by default. atdd_loadbalance 76 IBM Tape Deice Driers Installation and User s Guide

95 HP-UX Deice Drier (ATDD) Allows the user to disable automatic load balancing from ATDD. This parameter is On (1) by default and supported on 11i3 only atdd_resere_type The drie is resered in the SCSI-2 Resere command when Data Path Failoer (DPF) is disabled by default. To resere the drie using Persistent Resere In and Out commands, the user can set the alue of atdd_resere_type to 3. The default alue for the tunable: 1 - Resere(6) command; 2 - Resere(10) command (Unsupported); 3 - Persistent Resere In/Out commands To change the alue of tunable, run the command kctune/kmtune or SAM (System Administration Manager) tool. Special Files For each drie configured by ATDD, twele or thirteen special files are created: twele special files are generated for a 3590 with ACF set to Manual, Automatic, System, Accumulate, Random, or Library mode. A thirteenth special file is created for independent operation of the ACF, if the 3590 mode is set to Random 2 LUN operation (/de/rmt/<instance#>chng). ATDD creates the tape deice special files in three forms: the standard or long file name, an alternatie short file name based on the instance number, and an alternatie short file name not based on the instance number. BEST represents the operational capabilities likely to be required, including the highest density/format and data compression, if supported by the deice. Each set of special file names (long and short) contains four special files that hae all combinations of n and b options, as shown in Table 10 and Table 11. For more information, refer to the mt(7) man pages. Table 10. Special Files Special File Name BSD Compatibility Rewind on Close /de/rmt/<instance#>m No Yes /de/rmt/<instance#>mb Yes Yes /de/rmt/<instance#>mn No No /de/rmt/<instance#>mnb Yes No /de/rmt/s<#>m No Yes /de/rmt/s<#>mb Yes Yes /de/rmt/s<#>mn No No /de/rmt/s<#>mnb Yes No /de/rmt/<instance#>t<target>d<lun>best No Yes /de/rmt/<instance#>t<target>d<lun>bestb Yes Yes /de/rmt/<instance#>t<target>d<lun>bestn No No /de/rmt/<instance#>t<target>d<lun>bestnb Yes No /de/rmt/<instance#>chng N/A N/A Table 11. New Special Files in HP-UX 11i 3 BSD Rewind on Special File Name Compatibility Close /de/rtape/tape#_best No Yes Chapter 4. HP-UX Tape and Medium Changer Deice Drier 77

96 HP-UX Deice Drier (ATDD) Persistent Naming Support Table 11. New Special Files in HP-UX 11i 3 (continued) Special File Name BSD Compatibility Rewind on Close /de/rtape/tape#_bestb Yes Yes /de/rtape/tape#_bestn No No /de/rtape/tape#_bestnb Yes No /de/rchgr/autoch# N/A N/A In HP-UX 11.0, 11i 1 and 2: atdd_lssf in /opt/omimag/bin for the static drier and in /opt/atdd/bin for the DLKM drier lists information about a special file. For example: #atdd_lssf /de/rmt/393mnb atdd card instance 30 aailable at address Major = 79 Minor = Ox1E90C0 settings = No Rewind, Berkeley, Best Format, IBM 03590H1A /de/rmt/393mnb In HP-UX 11i 3: ATDD supports the HP-UX lssf, insf and rmsf commands. To display special file information, enter the lssf command. For example, # lssf /de/rtape/tape14_bestnb atdd Berkeley No-Rewind best density aailable at address 64000/0xfa00/0x32 /de/rtape/tape14_bestnb # lssf /de/rchgr/autoch1 acdd section 0 at address 64000/0xfa00/0x21 /de/rchgr/autoch1 If the deice special files are not created on the system, use the # insf command to generate them. Persistent naming support is used to ensure that attached deices are always configured with the same logical name across system reboots. For this purpose, the HP-UX tape drier creates an additional set of deice special files with a prefix of s for the configured tape dries in HP-UX 11.0, 11i 1 and 2, such as s55m in the following example. # ioscan -func tape Class I H/W Path Drier S/W State H/W Type Description =================================================================================== tape 103 1/0/0/ atdd CLAIMED DEVICE IBM 03592E05 /de/rmt/103m /de/rmt/c10t7d0bestn /de/rmt/s55mb /de/rmt/103mb /de/rmt/c10t7d0best /de/rmt/s55mn /de/rmt/103mn /de/rmt/c10t7d0bestb /de/rmt/s55m /de/rmt/103mnb /de/rmt/c10t7d0bestnb /de/rmt/s55mnb In HP-UX 11i 3, HP introduces the natie multi-pathing and path-independent persistent Deice Special Files (DSFs) and the auto discoery of deices greatly to enhance the oerall manageability. The ATDD does not create the additional set of deice special files with a prefix of s. The persistent DSF format for tape deices introduced with the Agile iew in HP-UX 11i 3 is: # ioscan -funnc tape Class I H/W Path Drier S/W State H/W Type Description =================================================================== tape /0xfa00/0x7 estape CLAIMED DEVICE IBM 03592E05 /de/rtape/tape1_best /de/rtape/tape1_bestn 78 IBM Tape Deice Driers Installation and User s Guide

97 HP-UX Deice Drier (ATDD) /de/rtape/tape1_bestb /de/rtape/tape1_bestnb # ioscan -funnc autoch Class I H/W Path Drier S/W State H/W Type Description ================================================================= autoch /0xfa00/0xa acdd CLAIMED DEVICE IBM 03584L22 /de/rchgr/autoch8 To map a persistent DSF to its legacy DSF, enter the following: # ioscan -m dsf /de/rtape/tape1_bestb Persistent DSF Legacy DSF(s) ======================================== /de/rtape/tape1_bestb /de/rmt/c3t15d0bestb /de/rmt/c9t6d0bestb Control Path Failoer Support for Tape Libraries Notes: 1. The library control path failoer feature code must be installed prior to enabling the path failoer support in the HP-UX ATDD deice drier. Refer to Automatic Failoer on page 10 for what feature code may be required for your machine type. 2. It is a requirement that applications must open the primary path for CPF Configuring and Unconfiguring Path Failoer Support Path failoer support is enabled automatically when the deice drier is installed; howeer, the drier proides a kernel parameter you can use to enable library control path failoer. To enable the failoer support in the ATDD drier, perform the following steps after installing the drier: In HP-UX 11.0, 11i 1 and 2: 1. Set the alternate_pathing parameter: # /opt/atdd/bin/atdd_failoer -a 1 2. Reconfigure CPF for the deices: # /opt/atdd/bin/atdd_claim In HP-UX 11i 3: Run kctune to enable the kernel tunable of atdd_alternate_pathing. ATDD handles the CPF in the next open. # kctune atdd_alternate_pathing=1 * The automatic backup configuration has been updated. * The requested changes hae been applied to the currently running configuration. Tunable Value Expression Changes atdd_alternate_pathing (before) 0 0 Immed (now) 1 1 You can check if the drier has recognized multiple control paths for your library by running: #ioscan -func autoch If you see.altpath next to one of the special files in HP-UX 11.0, 11i 1 and 2, then you hae successfully enabled the control path failoer feature for your library. In HP-UX 11i 3, use the # ioscan -m dsf command and [11] Display All Paths on page 265 or Display All Paths on page 308 in tapeutil to erify that the multiple path is configured by the system and ATDD. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 79

98 HP-UX Deice Drier (ATDD) After the path failoer support is enabled, it remains set until atdd_claim is run with the alternate_pathing drier parameter set to OFF. The path failoer setting is retained een if the system is rebooted. If you want to turn off the control path failoer feature in the ATDD drier, perform the following steps: In HP-UX 11.0, 11i 1 and 2: 1. Clear the alternate_pathing parameter: # /opt/atdd/bin/atdd_failoer -a 0 2. Reconfigure CPF for the deices: # /opt/atdd/bin/atdd_claim In HP-UX 11i 3: Run kctune to disable the kernel tunable of atdd_alternate_pathing. ATDD manages the CPF in the next open. # kctune atdd_alternate_pathing=0 * The automatic backup configuration has been updated. * The requested changes hae been applied to the currently running configuration. Tunable Value Expression Changes atdd_alternate_pathing (before) 1 1 Immed (now) 0 0 Primary and Alternate Paths When ATDD is loaded into the kernel, the first logical medium changer deice that it sees in the system is the primary path for that medium changer. The other logical medium changers that ATDD attached for the same medium changer are configured as alternate paths. The deice drier supports up to 16 physical paths for a single deice. On HP-UX 11i 3, the HP-UX system always selects the best path for ATDD to open so the primary path is dynamically assigned from the system. ATDD does not proide any.altpath special file. The primary and alternate path information can be obtained by using the following command on HP-Ux 11.0, 11i 1 and 2: # ioscan -func autoch The following is an example of what you might see: autoch 0 0/1/0/ acdd CLAIMED DEVICE IBM ULT3582-TL /de/rmt/0chng autoch 1 0/1/0/ acdd CLAIMED DEVICE IBM ULT3582-TL /de/rmt/1chng.altpath Querying Primary and Alternate Path Configurations You can display the primary and alternate path configuration for all deices by running the ioscan command, as explained in section Determine the Deice Hardware Path for IBM Tape Dries on page 58. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Disable and Enable Primary and Alternate Paths When you load the ATDD deice drier with the alternate_pathing parameter set to ON, by default, all the aailable paths for a physical deice are enabled. 80 IBM Tape Deice Driers Installation and User s Guide

99 HP-UX Deice Drier (ATDD) If it is necessary to disable a path and not perform path fail oer (for example due to maintenance), run commands to disable and then later enable the primary and alternate paths. The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. Note: See Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Data Path Failoer and Load Balancing Support for Tape Dries The HP-UX deice drier path failoer support configures multiple physical paths to the same deice within the deice drier and proides two basic functions: 1. Automatic failoer to an alternate physical path when a permanent error occurs on one path. 2. Dynamic load balancing for deices using multiple Host Bus Adapters (HBA). On HP-UX 11i 3, HP-UX system always pickups a best path for ATDD to open; ATDD doesn't perform a dynamic load balancing in open. Notes: 1. Data Path Failoer is not supported when using block sizes greater than 256K, except in HP-UX 11i It is required that applications must open the primary path for Data Path Failoer (not in HP-UX 11i 3). 3. Data Path Failoer is supported for 3592 tape dries on HP-UX 11.0, 11i 1, 2 and 3, and for Ultrium-3 and Ultrium-4 dries on HP-UX 11i 1, 2 and 3. Configuring and Unconfiguring Path Failoer Support Path failoer support is turned on automatically when the deice drier is installed. Howeer, you need to proide the data path failoer feature key and reclaim the deices using the atdd_claim script. The feature key is a string with 16 characters and numbers. To enable the failoer support in the IBMtape deice drier software, perform the following steps after installing the drier: 1. Edit the following line in your /sbin/init.d/atdd file: DPF_KEYS=" ; " Notes: a. " " is an example of a data path failoer feature key. If you hae multiple 3584 libraries and multiple data path failoer feature keys, input your keys as follows:dpf_keys="key1; key2;..." b. A DPF key is required for Ultrium-3 tape dries only. No DPF key needs to be added into the /sbin/init.d/atdd file if you are running the most recent drie code. 2. Sae the file, then run the following command in HP-UX 11.0, 11i 1 and 2: # /opt/atdd/bin/atdd_claim 3. In HP-UX 11.0, 11i 1 and 2, you can check whether the drier has recognized multiple data paths for your dries by running: #ioscan -func tape If you see a ".altpath" next to one of the special files, then you hae successfully enabled control path failoer feature for your library. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 81

100 HP-UX Deice Drier (ATDD) In HP-UX 11i 3, use the # ioscan -m dsf command to erify that the multiple path is configured by the system and ATDD. Note: See Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page After path failoer support is enabled, it remains set until atdd_claim or kctune is run with the alternate_pathing drier parameter set to OFF. The path failoer setting is retained een if the system is rebooted. If you want to turn off the data path failoer feature in the ATDD drier, perform the following steps: In HP-UX 11.0, 11i 1 and 2: 1. Clear the alternate_pathing parameter. (You can ignore the message about rebooting the system.)# /opt/atdd/bin/atdd_failoer -a 0 2. Reconfigure DPF for the deices: # /opt/atdd/bin/atdd_claim In HP-UX 11i 3: Run kctune to disable the kernel tunable of atdd_alternate_pathing. ATDD handles the DPF in the next open. # kctune atdd_alternate_pathing=0 * The automatic backup configuration has been updated. * The requested changes hae been applied to the currently running configuration. Tunable Value Expression Changes atdd_alternate_pathing (before) 1 1 Immed (now) 0 0 If you want to turn the data path failoer feature back on in the ATDD drier, perform the following steps: In HP-UX 11.0, 11i 1 and 2: 1. Set the alternate_pathing parameter. (You can ignore the message about rebooting the system.) # /opt/atdd/bin/atdd_failoer -a 1 2. Reconfigure DPF for the deices: # /opt/atdd/bin/atdd_claim In HP-UX 11i 3: Run kctune to enable the kernel tunable of atdd_alternate_pathing. ATDD handles the DPF in the next open. # kctune atdd_alternate_pathing=1 * The automatic backup configuration has been updated. * The requested changes hae been applied to the currently running configuration. Tunable Value Expression Changes atdd_alternate_pathing (before) 0 0 Immed (now) 1 1 Primary and Alternate Paths When ATDD is loaded into the kernel, the first logical deice that it sees in the system is the primary path for that medium changer. The other logical paths that ATDD attached for the same tape drie are configured as alternate paths. The deice drier supports up to 16 physical paths for a single deice. In HP-UX 11i 82 IBM Tape Deice Driers Installation and User s Guide

101 HP-UX Deice Drier (ATDD) 3, the HP-UX system always pickups a best path for ATDD to open so the primary path is dynamically assigned from the system. ATDD does not proide any.atlpath special file. The primary and alternate path information can be obtained by issuing the following command except in HP-UX 11i 3: # ioscan -func tape The following is an example of the output for this command: /home/root# ioscan -func tape Class I H/W Path Drier S/W State H/W Type Description =============================================================================== tape 0 0/1/0/ atdd CLAIMED DEVICE IBM ULT3580-TD3 /de/rmt/0m tape 1 0/1/0/ atdd CLAIMED DEVICE IBM ULT3580-TD3 /de/rmt/1m.altpath Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices by running ioscan, as explained in section Primary and Alternate Paths on page 82. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Disable and Enable Primary and Alternate Paths If it is necessary to disable a path and not perform path fail oer (for example due to maintenance), run commands to disable and then later enable the primary and alternate paths. Problem Determination The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. Note: See Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page A set of tools is proided with the deice drier to determine if the deice drier and the tape deice are functioning correctly. Error Logging Read the system log file (typically /ar/adm/syslog/syslog.log) and the ATDD log file (/ar/adm/atdd/atdd_d.log) if you are haing problems. The ATDD logs messages to this file which proide information regarding the problem. Reseration Conflict Logging When the deice drier receies a reseration conflict during open or after the deice has been opened it will log a reseration conflict in the HP-UX system log of /ar/adm/syslog/syslog.log. Prior to logging the error the deice drier will issue a Persistent Resere In command to determine if a SCSI Persistent Reseration is actie on the resering host to get the resering host initiator WWPN (World Wide Port Name) and resere key. If successful, the deice drier will log this information in the detail data below. After initially logging the resering host WWPN, subsequent reseration conflicts from the same resering host WWPN and reseration key will not be logged to preent multiple entries in the system log Chapter 4. HP-UX Tape and Medium Changer Deice Drier 83

102 HP-UX Deice Drier (ATDD) until either the resering host WWPN or reseration key is different than the one initially logged or the deice drier has resered the deice and then another reseration conflict occurs. Here are the log examples: 1. The information is logged when the drie is resered with a Persistent Reseration. atdd: deice=rtape41 Resered. Resering host key DF E627E6 WWPN 21:00:00:E0:8B:11:8B:B1 2. The information is logged when the drie is resered with a SCSI-2 Resere. atdd: deice=rtape41 Resered. Deice resered with legacy resere. Sense Data Logging When the tape drie responds with CHECK CONDITION status and associated sense keys of 0x1 (Recoery Error), 0x3 (Medium Error), 0x4 (Hardware Error) and 0xB (Aborted Command) for a hardware or medium error, the sense data is logged into the system log file (typically /ar/adm/syslog/syslog.log). The sense data logging feature is disabled by default on 11.0, 11i 1 and 11i 2 and enabled by default on 11i 3. To enable the support dynamically, run /opt/atdd/bin/atdd_cfg with the -c option. # /opt/atdd/bin/atdd_cfg -c 1 * The requested changes hae been applied to the currently running system. Tunable Value Expression Changes atdd_log_trace (before) 0 Default Immed (now) 1 1 Support_info Script Run the support_info script, located in the /opt/omimag/bin directory for the static drier and in /opt/atdd/bin for the DLKM drier. This script gathers important system and configuration information. There are seeral sections with the keyword VERIFY, indicating information that should be erified for correctness. Log in as userid "root" on the system which experienced a problem. Then run the script and redirect the output to an end of a file: Static: /opt/omimag/bin/support_info > support_info.out DLKM /opt/atdd/bin/support_info > support_info.out Tracing Facility Running the ATDD_trace utility, located in the /opt/omimag/bin for the static drier and in /opt/atdd/bin for the DLKM drier, displays debug information. The utility traces can be started at any time before an operation on a tape deice. The default debug leel is 0x , which shows drier configuration and per instance drie attribute configuration and errors. You can increase the amount of debug information displayed by enabling more trace flags. Issuing atdd_trace -f 0x1fffffff turns on eery trace. Enter the following commands to start the trace: 1. First, determine which items need to be traced and set the trace flags using the atdd_trace command. For example, to trace eerything: 84 IBM Tape Deice Driers Installation and User s Guide

103 HP-UX Deice Drier (ATDD) For the Static drier:/opt/omimag/bin/atdd_trace -f 0x1fffffff For the DLKM drier:/opt/atdd/bin/atdd_trace -f 0x1fffffff In HP-UX 11i3, run the sam utility or # kctune atdd_trace_leel=1 command to set the trace leel to 1. The default set is 3. The set of trace flags is displayed in Table 12. Table 12. Trace Flags COMMAND Configuration General errors Routine entry points Returns TRACE_DBG information Open/Close routine Trace motion commands Read/Write Strategy Open/Close states IOCTLs Trace deice config routines Trace SCSI leel stuff Configuration Entry point General information Memory VALUE 0x x x x x x x x x x x x x x x x x Clear the trace buffer: For the Static drier:/opt/omimag/bin/atdd_trace -c For the DLKM drier:/opt/atdd/bin/atdd_trace -c 3. To hae trace data displayed immediately in a readable format as it is collected: For the Static drier:/opt/omimag/bin/atdd_trace -b For the DLKM drier:/opt/atdd/bin/atdd_trace -b 4. Start the operations on a tape deice. 5. To display collected trace data in a readable format at any time: For the Static drier:/opt/omimag/bin/atdd_trace -d For the DLKM drier:/opt/atdd/bin/atdd_trace -d 6. The atdd_trace output can be redirected to place the trace data in a readable format into a file, by entering: For the PB drier:/opt/omimag/bin/atdd_trace >trace.txt For the PCI drier:/opt/atdd/bin/atdd_trace >trace.txt 7. In HP-UX 11i 3, the ATDD trace is logged into syslog of /ar/adm/syslog/ syslog.log once the kernel tunable of atdd_direct_trace is enabled. To set a alue (0 or 1) to atdd_direct_trace, run # kctune atdd_direct_trace=alue. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 85

104 HP-UX Deice Drier (ATDD) Atdd_d Log Daemon The deice drier proides a log daemon (atdd_d) facility for the Enterprise Tape System 359x to automatically store drie dumps, to retriee and store SIM/MIM (Serice and Media Information Messages) data, and to log error messages into the /ar/adm/atdddirectory. The atdd_d log daemon is not automatically started in 11.0, 11i 1 and 2 but not in 11i 3, when the drier is installed. The following steps document how to start and configure the daemon: 1. Start the daemon by running: For the Static drier: #/opt/omimag/bin/atdd_d For the DLKM drier: #/opt/atdd/bin/atdd_d 2. Check whether the daemon is running by entering: #ps -ef grep atdd_d 3. To iew and/or modify the settings for the daemon, enter: For the Static drier: # /opt/omimag/bin/atdd_d -h usage: atdd_d [options] For the DLKM drier: # /opt/atdd/bin/atdd_d -h usage: atdd_d [options] [-d <log directory>] default is /ar/adm/atdd [-n <maximum number of dumps>] default is 10 [-z <maximum size of a dump>] default is [-s <maximum size of a log>] default is For example, to decrease the number of drie dumps to store from 10 to 6 and change the log directory to /tmp/drie_dump, do the following: For the Static drier: #/opt/omimag/bin/atdd_d -n 6 -d/tmp/drie_dump For the DLKM drier: #/opt/atdd/bin/atdd_d -n 6 -d/tmp/drie_dump 4. View the atdd_d.log, which proides information about the daemon start time, message type (1 for the drie dump, 2 for SIM/MIM data, and 3 for Error message), time stamp, H/W path, and size. Refer to an example in Figure 10 on page IBM Tape Deice Driers Installation and User s Guide

105 HP-UX Deice Drier (ATDD) Figure 10. Example of atdd_d.log Output Note: No entry is made in the log file when the daemon stops. Run #ps -ef grep atdd_d to check if the daemon is stopped. 5. Stop the daemon by using the following commands: Get the daemon process id: kill the daemon process: Problems and Solutions #ps -ef grep atdd_d #kill -9 process_id Table 13 describes problems and possible solutions for errors you may encounter with the DLKM drier. Table 13. Problems, Reasons, and Solutions Problem The system hangs running rmsf -H on HP-UX 11i. ATDD DLKM modules are not loaded in the running kernel. A message in the file /ar/adm/syslog/syslog.log "munix: WARNING: modpath: DLKM is not initialized" A message in the file /ar/adm/syslog/syslog.log "modld: Attempt to load unregistered module " Reason and Solution DLKM Infrastructure does not set the correct flag in the deice switch table entry for a DLKM drier that uses. Install HP patch PHKL_29818 The current kernel is not matching the symbol table (DLKM) in /stand/dlkm Need to rebuild the kernel by running the following commands: #cd /stand/build #/usr/lbin/sysadm/system_prep -s /stand/build/system #/usr/sbin/mk_kernel -s /stand/build/system #m /stand/system /stand/system.pre #m /stand/build/system /stand/system #kmupdate /stand/build/munix_test #shutdown -ry now ATDD DLKM Module's component files are not copied to certain subdirectories of /usr/conf and /stand Remoe ATDD and try to install it again. Chapter 4. HP-UX Tape and Medium Changer Deice Drier 87

106 HP-UX Deice Drier (ATDD) Table 13. Problems, Reasons, and Solutions (continued) Problem # kmtune grep atdd kmtune: Cannot open file -- /stand/.kmsystune_lock IBM tape deices not claimed in ioscan -fnk display No special files found in /de/rmt The special files for a deice are duplicates. No special files are created by HP Stape and Schgr after installing ATDD Cannot open Special File and the system log has the following message: Inalid SCSI request in data at bit 7 of byte 4 An attempt to read data times out and returns an error and the system log has the following messages: A SCSI command timed out and was aborted. Reason and Solution The file.kmsystune_lock was remoed manually. Use the following command to create the.kmsystune_lock file again: # touch /stand/.kmsystune_lock As "root", erify the driers loaded in the running kernel using `kmadmin -s` If status is "LOADED" then run atdd_claim -b to claim all IBM deices, then run atdd_claim -t to claim the tape dries, then run atdd_claim -c to claim the changers. If status is "UNLOADED" then run kmadmin -L atdd to load the ATDD, then run kmadmin -L acdd to load the ACDD, then run atdd_claim to claim the tape deices. If status is still "UNLOADED", then check the entries of the files 'atdd' and/or 'acdd' in /etc/loadmods If no atdd and/or acdd file entries exist, the drier may be statically bound to the kernel or the ATDD package may not be installed. Check the installation running the following command: # swlist atdd Execute the atdd_mksf and acdd (if you hae changers managed by the acdd drier) scripts found in /opt/atdd/bin atdd_mksf and acdd_mksf Note: The script prints out the commands that are necessary to create the special files. To create the files you must "pipe" the output to shell (sh), using the following commands: atdd_mksf sh acdd_mksf sh Remoe all of the special files for the deice in /de/rmt Create the special files again by running the commands atdd_mksf or acdd_mksf Create the special files by running the command: # insf -e Wrong DENSITY setting. Check the current alue by running the command: atdd_cfg -g DENSITY Try setting alue to 0 (zero) by running the command: atdd_cfg -s DENSITY 0 Make sure the SILI configuration parameter is "1". This can be checked by running the command: atdd_cfg -g SILI If the alue of SILI = 0, try setting the alue to 1, by running the following command: atdd_cfg -s SILI 1 Table 14 on page 89 describes problems and possible solutions for errors you may encounter with the static drier. 88 IBM Tape Deice Driers Installation and User s Guide

107 HP-UX Deice Drier (ATDD) Table 14. Troubleshooting (Problems and Solutions) Problem No special files found in /de/rmt If you are using the PB driers or are not using the standard deice drier defaults with PCI driers: Claimed by HP Stape drier Cannot open Special File. The system log has the following message: Inalid SCSI request in data at bit 7 of byte 4 An attempt to read data times out and returns an error. The system log has the following messages: A SCSI command timed out and was aborted. LLIO: Detected PowerFail (probably caused by SCSI bus or deice reset). An attempt to read data times out and returns an error. The system log has the following messages: A SCSI command timed out and was aborted. scsi3:...date code... scsi3:...timestamp... Solution Issue the following commands: cd /opt/omimag/bin atdd_mksf sh Verify that the hardware path for the deice is listed in the configuration file: /etc/rc.config.d/atdd.cfg If the hardware path is missing or incorrect, the drier was not installed properly. Run the command: # lsde to check that the atdd is in the current kernel: 1. If the atdd is not in the output, rebuild the kernel or reinstall atdd; 2. If the atdd is in the output: a. Rebuild the system I/O configuration: 1) Remoe /stand/ioconfig and /etc/ioconfig after to backup the files; 2) Reboot the system; 3) On System Console, enter the command: # /sbin/ioinit -c while the autobooting is halted; 4) Run the command: # /sbin/insf -e 5) Enter the command: #^Dto exit the I/O configuration b. Consider reinstalling the HP-UX operating system if the system is new or this is a new update. Wrong DENSITY setting. Check the current alue by: atdd_cfg -g DENSITY <atdd_inst> Try setting it to 0 (zero): atdd_cfg -s DENSITY 0 <atdd_inst> Check that the SILI configuration parameter is 1 by executing: atdd_cfg -g SILI <atdd_inst> If the SILI parameter is zero, try setting it to 1: atdd_cfg -s SILI 1 <atdd_inst> Check that the FORCE_NARROW parameter is alid for this deice by executing: atdd_cfg -g FORCE_NARROW <atdd_inst> If FORCE_NARROW is 1, try setting it to 0: atdd_cfg -s FORCE_NARROW 0 <atdd_inst> Chapter 4. HP-UX Tape and Medium Changer Deice Drier 89

108 HP-UX Deice Drier (ATDD) 90 IBM Tape Deice Driers Installation and User s Guide

109 Chapter 5. Linux Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Hardware Requirements for Intel and AMD Opteron Processors Hardware Requirements for IBM System p Models Hardware Requirements for IBM System z Models Software Requirements for Intel and AMD Opteron Processors Software Requirements for IBM System p Models 94 Software Requirements for IBM System z Models 94 Installation and Configuration Instructions Conentions Used Components Created During Installation Installation Procedure Updating Procedure Querying the Installed Package Configuring Tape and Medium Changer Deices on Intel-Compatible Systems Configuring Tape and Medium Changer Deices on IBM System p Models Configuring Tape and Medium Changer Deices on IBM System z Models Uninstall Procedure Tape Drie, Media, and Deice Drier Parameters 99 Configuration Parameters Nonchangeable Parameters Changeable Parameters Special Files Special Files for the Tape Deice Special Files for the Medium Changer Deice 104 Persistent Naming Support Control Path Failoer Support for Tape Libraries 106 Configuring and Unconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configuration Disable and Enable Primary and Alternate Paths 107 Data Path Failoer and Load Balancing Support for Tape Dries Primary and Alternate Paths Querying Primary and Alternate Path Configuration Disable and Enable Primary and Alternate Paths 109 Tape Resere Type Open Source Deice Drier - lin_tape IBMtape and lin_tape Comparison Installation Drier parameters and special deice files Path Failoer Support lin_taped Daemon System-Managed Encryption Deice Drier Configuration Querying Tape Drie Configuration Problem Determination Configure and Run lin_taped Daemon Reseration Conflict Logging This chapter describes the IBM Linux Tape and Medium Changer Deice Drier (lin_tape). For tape diagnostic and utility functions refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Purpose Data Flow The lin_tape and medium changer deice drier is designed specifically to take adantage of the features proided by the IBM tape dries and medium changer deices. The goal is to gie 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 adanced functions needed by full tape management systems. Wheneer possible, the drier is designed to take adantage of the deice features transparent to the application. The software described in this chapter coers the Linux Deice Drier (lin_tape deice drier) and the interface between the application and the tape deice. Figure 11 on page 92 illustrates a typical data flow process. Copyright IBM Corp. 2007,

110 Linux Deice Drier (lin_tape) Application Program IBMtape Deice Drier Host Bus Adapter Drier Tape Deice a Figure 11. Data Flow for Linux Deice Drier (lin_tape) Product Requirements More current information on supported hardware and software configurations for lin_tape can be found on our System Storage Interoperation Center website: Hardware Requirements for Intel and AMD Opteron Processors One or more of the following processors is required by the lin_tape deice drier: 32-bit Intel-compatible processors (uniprocessor or SMP) capable of running the Linux operating system 64-bit Intel Itanium processors (uniprocessor or SMP) capable of running the Linux operating system Intel processors that support Extended Memory 64 Technology (EM64T) AMD Opteron processors capable of running the Linux operating system One or more of the following host bus adapters: Adaptec 2940U2W (LVD; Ultrium dries only) Adaptec 2944UW (HVD) SCSI Host Bus Adapter Adaptec SCSI Adapter or IBM P/N 19K4646 for IBM System x - Single Port LVD Adapted SCSI Adapter Dual Port LVD Adaptec SCSI Adapter Single Port LVD Adaptec SCSI Adapter Dual Port LVD LSI Logic SAS3800X SAS Adapters IBM SAS Host Bus Adapter Controller Part Number 25R8060 QLogic QLA2200F, QLA2300F, QLA2310FL, QLA2340L, QLA2342L, QLA2460, QLA2462, QLE2560, and QLE2562 Fibre Channel Adapters Emulex LP1150, LP9002L, LP9802, LP10000, LP11000, LP11002, LPe12000, LPe12002, and LPe1250 Fibre Channel Adapters IBM 42D0485, 42D0494, 42D0501, and 42D GB Adapters Hardware Requirements for IBM System p Models One or more of the following processors is required by the lin_tape deice drier: IBM low, middle, or high range System p (also known as pseries) serers running a 64-bit Linux operating system IBM POWER5 serers running a 64-bit Linux operating system One or more of the following host bus adapters: PCI-X DDR Dual -x4 SAS Adapter (FC 5900) 92 IBM Tape Deice Driers Installation and User s Guide

111 Linux Deice Drier (lin_tape) System p (also known as pseries) Feature Code 5712 PCI-X Dual Channel Ultra320 SCSI Adapter System p (also known as pseries) Feature Code 5736 (571A) or 1912 PCI-X DDR Dual Channel Ultra320 SCSI Adapter System p (also known as pseries) Feature Code 6228 Fibre Channel Adapter System p (also known as pseries) Feature Code 6239 Fibre Channel PCI-X Adapter System p (also known as pseries) Feature Code 5716 Fibre Channel PCI-X Adapter System p (also known as pseries) Feature Code 5758 and 5759 Fibre Channel PCI-X Adapter System p (also known as pseries) Feature Code 5773 and 5774 Fibre Channel PCI-E Adapter System p (also known as pseries) Feature Code GB Fibre Channel Adapter Hardware Requirements for IBM System z Models One or more of the following processors is required by the lin_tape deice drier running Linux on System z in 31-bit or 64-bit: IBM System z 800 (z800) or 900 (z900) models IBM System z 890 (z890) or 990 (z990) models IBM System z9 models One or more of the following host bus adapters with Fibre Channel Protocol support: FICON Express card (feature 2315 or 2318) FICON Express card (feature 2319 or 2320) FICON Express2 card (feature 3319 or 3320) FICON Express4 card (feature 3321, 3322, or 3324) Note: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. Tape and disk deices 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 hae been obsered. These issues are resoled by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring serer and storage configuration interoperability. IBM strongly recommends that your implementation plan includes proisions for separating disk and tape workloads. Software Requirements for Intel and AMD Opteron Processors The lin_tape deice drier supports the following Linux distributions: Red Hat Enterprise Linux Serer SUSE LINUX Enterprise Serer Asianux Chapter 5. Linux Tape and Medium Changer Deice Drier 93

112 Linux Deice Drier (lin_tape) Software Requirements for IBM System p Models The lin_tape deice drier supports the following Linux distributions for Linux for System p (also known as pseries) (64-bit kernel): Red Hat Enterprise Linux SUSE LINUX Enterprise Serer Asianux Software Requirements for IBM System z Models The lin_tape deice drier supports the following Linux distribution for Linux on System z 31-bit and 64-bit: Red Hat Enterprise Linux SUSE LINUX Enterprise Serer Installation and Configuration Instructions The lin_tape deice drier for Linux is proided in a source rpm package. The utility tools for lin_tape are supplied in binary rpm packages. Refer to Appendix A, Accessing Documentation and Software Online, on page 317. They will be downloaded with the drier. The following sections describe installation, configuration, uninstalling, and erification procedures for lin_tape and its utility tools. Refer to Linux documentation for tar command information and any Linux distribution supporting rpm for rpm command information. You must hae root authority to proceed with the installation of the drier. See the README file that can be downloaded with the drier at Fix Central. For more information about downloading driers please see Appendix A, Accessing Documentation and Software Online, on page 317. This file contains the latest drier information and supersedes the information in this publication. Conentions Used In subsequent pages, you see file names with x.x.x in them. The x.x.x refers to the ersion of the drier, which changes as IBM releases new drier leels. Use the actual drier ersion numbers as you perform the instructions. Commands that you are to type are indicated with a leading ">" character, which indicates the shell prompt. Note: This is performed using tape diagnostic and utility functions. Components Created During Installation The lin_tape package consists of the deice drier and a number of associated files. Components created during lin_tape installation (from the rpm package) are listed in Table 15. Table 15. Components Created During lin_tape Installation Component /lib/modules/(your system's kernel name)/kernel/driers/scsi/lin_tape.ko Description Deice drier module for current kernel ersion 94 IBM Tape Deice Driers Installation and User s Guide

113 Linux Deice Drier (lin_tape) Table 15. Components Created During lin_tape Installation (continued) Component /usr/bin/lin_taped /etc/lin_taped.conf /usr/share/doc/lin_tape-xxx/ lin_tape_359x.readme (for Red Hat) Description lin_taped daemon lin_taped daemon configuration file ReadMe file for lin_tape using IBM TotalStorage deices /usr/share/doc/packages/lin_tape/ lin_tape_359x.readme (for SUSE LINUX) /usr/share/doc/lin_tape-xxx/lin_taped.readme (for Red Hat) ReadMe file for lin_taped daemon /usr/share/doc/packages/lin_tape/ lin_taped.readme (for SUSE LINUX) /usr/share/doc/lin_tape-xxx/copying (for Red Hat) License documentation for lin_tape /usr/share/doc/packages/lin_tape/copying (for SUSE LINUX) Installation Procedure If lin_tape is already installed on your system, refer to the Updating Procedure on page 96 in this chapter. This section assumes you are installing the lin_tape deice drier onto a system where it is not currently installed. If you are installing lin_tape on a system running Linux for S/390 or Linux for zseries, ensure that the OpenFCP adapter deice drier zfcp is loaded in the kernel. Please refer to the section Configuring Tape and Medium Changer Deices on IBM System z Models on page 97 in this chapter for how to configure and install zfcp. Make sure that the C/C++ deelopment and kernel deelopment packages are installed on your system. To install the lin_tape drier with all the added alue of the lin_taped daemon, perform the following steps: 1. Download the appropriate leel of the source RPM package to a directory of your choice on the Linux kernel for which you wish to install it. 2. Run rpmbuild --rebuild <filename>, where: <filename> is the name of the RPM file. This creates a binary RPM package for your kernel from the source RPM package. For example: >rpmbuild --rebuild lin_tape-1.x.x.x.0-1.src.rpm 3. Output from the build is printed to your screen. Near the end of the output, there is a line that indicates the filename and location of your binary RPM package. For example, a line similar to the following is output to your screen: Wrote: /usr/src/redhat/rpms/i386/lin_tape-1.x.x.x.0-1.i386.rpm 4. To install the lin_tape drier from the binary package, run >rpm -ih <filename> For example: >rpm -ih /usr/src/redhat/rpms/i386/lin_tape-1.x.x.x.0-1.i386.rpm 5. To install the lin_taped daemon, download it to your Linux filesystem and run rpm -ih on the daemon RPM file. Chapter 5. Linux Tape and Medium Changer Deice Drier 95

114 Linux Deice Drier (lin_tape) For example: >rpm -ih /usr/src/redhat/rpms/i386/lin_taped-1.x.x.x.0-rhel5.i386.rpm Updating Procedure If your current lin_tape deice drier was installed from a rpm package preiously, you may uninstall the drier first, then install the newer ersion. For example: >rpm -e lin_tape >rpmbuild --rebuild lin_tape.x.x.x.i386.rpm >rpm -i lin_tape.x.x.x.i386.rpm Note: All tape deices that use the lin_tape deice drier must be closed and cannot be in use when lin_tape is uninstalled. Querying the Installed Package The query is supported for the lin_tape deice drier rpm package only. The installed rpm package can be queried by running the following commands to display information associated with the package. To display information about lin_tape: >rpm -qi lin_tape To display the file list, enter the command: >rpm -ql lin_tape To display the states of files in the package, for example, normal, not installed, or replaced: >rpm -qs lin_tape Configuring Tape and Medium Changer Deices on Intel-Compatible Systems If you hae not physically attached your tape and medium changer deices to your Linux serer, perform the following steps: 1. Halt the Linux serer. 2. Power down the Linux serer. 3. Physically attach the tape and medium changers to the host bus adapter cards. Consult your hardware documentation for details. 4. Power on the tape and medium changer deices. Verify that they hae completed the initialization process. 5. Power on and boot the Linux serer. Note: Hot plugging SCSI deices while the Linux serer is running may cause hardware damage. After the drier software is installed and a tape deice is connected to the adapter, the deice can be configured and made aailable for use. Access to the deice is not proided until the deice is configured. If your system is attached to an IBM 3583 Tape Library with the integrated router, before installing the Qlogic drier, set the host type of the router to solaris and make sure that the logical unit numbers of the control unit, medium changer, and the connected tape dries are contiguous (otherwise, the Qlogic deice drier does 96 IBM Tape Deice Driers Installation and User s Guide

115 Linux Deice Drier (lin_tape) not recognize all of the attached deices). To iew the LUNs of attached deices, log onto the router and use the fcshowdes command. If the LUNs are not contiguous, use the mapcompressdatabase command to delete the inalid LUNs and make the alid LUNs contiguous. If you hae the StorWatch Specialist installed, you can use the Specialist to do this configuration. For further information about the StorWatch Specialist, refer to the IBM Storage Area Network Data Gateway Installation and User's Guide. You can download the guide from the Web at: Document/sdgdoc.htm When you run the lin_tape kernel module, it creates special files in the /de directory. Configuring Tape and Medium Changer Deices on IBM System p Models Follow the same instructions as documented in the preious section. You need to configure the Emulex Linux deice drier if you hae fibre channel tape deices attached to your System p (also known as pseries) system. Configuring Tape and Medium Changer Deices on IBM System z Models The fibre channel topology supported for System z is point-to-point and fabric. Please refer to the Linux on System z fibre channel documents for more details on the supported configurations for fibre channel deice attachment. The Linux fibre channel adapter deice drier zfcp is aailable in the kernel that supports zseries Fibre Channel Protocol. The zfcp deice configuration methods in 2.6 and 2.4 kernels are different. For 2.6 kernels, refer to appropriate chapter in the Linux on System z document entitled "Linux on System z: Deice Driers, Features, and Commands". For 2.4 kernels, there are three ways to load the zfcp deice drier in order to see the attached tape deices. 1. Create a /etc/zfcp.conf file and make a ramdisk to statically attach tape deices into your system. You can use this method only if you hae a persistent mapping in a SAN enironment. Eery time you reboot the system, the zfcp is automatically loaded and the tape deices can be seen from the system. First you need to add the deice map into this file. The following is an example of zfcp.conf: 0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x The zfcp deice drier uses the "map" module parameter to recognize a physically attached tape deice. "map" takes the following format: map="<deno><port scsi-id>:<wwpn><unit-scsi-lun>:<fcp-lun>;..." Where: deno The deice number of the host bus adapter (16 bits, see /proc/subchannels). It is "0xf1c0" or "0xf1c1" in the preious example. port scsi-id Linux internal SCSI ID assigned to the Fibre Channel port of the SCSI Chapter 5. Linux Tape and Medium Changer Deice Drier 97

116 Linux Deice Drier (lin_tape) target deice (32-bit, must not be 0, must be a unique one-to-one mapping for each World Wide Port Name. It is "0x1" in the preious example. wwpn World Wide Port Name identifying the Fibre Channel port of the SCSI target deice (64-bit). It is "0x " in the preious example. unit scsi-lun Linux internal SCSI Logical Unit Number (32-bit). It is "0x0" in the preious example. fcp-lun Logical Unit Number associated with the SCSI target deice (64-bit). In the preious example, "0x " is the Logical Unit Number 0, and "0x " is the Logical Unit Number 1. We recommend, for tape attachment, that each logical unit number be associated with a unique deno. If you use the same deno numbers for seeral logical units, you should ensure that each <unit-scsi-lun> is unique. After /etc/zfcp.conf is created, run the following commands: >mk_initrd>zipl Then, reboot the system. After it is booted up, your tape deice should be shown in /proc/scsi/scsi file. 2. Modify the /etc/modules.conf file to add the zfcp module parameters; then run the "depmod A" and "modprobe zfcp" command. Note: Do not use this choice together with the first one, otherwise it causes conflicts. The zfcp map in /etc/modules.conf always takes higher priority than the map in /etc/zfcp.conf. The following example demonstrates the zfcp configuration in /etc/modules.conf: options zfcp map="\ 0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x " The map arguments are the same as the ones listed in for the /etc/zfcp.conf file. After modifying the /etc/modules.conf file, sae and close it. Then run the following command: >depmod -A >modprobe zfcp This installs the zfcp deice drier and all of its prerequisite kernel modules. Now you can check the file /proc/scsi/scsi to see if all of the attached tape deices are shown in this file. If not, then check the fibre channel connection, such as the fibre cables, or if the deices are powered on, etc. Then run the following commands to install zfcp: >rmmod zfcp >modprobe zfcp 3. Run the "modprobe zfcp" command first, then dynamically add a tape deice into the system after you physically attach a fibre channel tape deice to the switch. If you physically attach a tape deice on the switch and zfcp is already loaded, you do not need to reboot the Linux system in order to add this entry in the /proc/scsi/scsi file. The zfcp deice drier proides an "add_map" proc system entry under the directory /proc/scsi/zfcp to allow you to dynamically add the 98 IBM Tape Deice Driers Installation and User s Guide

117 Linux Deice Drier (lin_tape) deice into the system. For example, to add two logical units from the example in Step 2 into the system, you may issue the following commands; > echo "0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x " > /proc/scsi/zfcp/add_map > echo "scsi add-single-deice 0010">/proc/scsi/scsi > echo "scsi add-single-deice 1011">/proc/scsi/scsi The "scsi add-single-deice" takes four parameters, corresponding to the four parameters "scsi", "Channel", "Id", and "Lun" in the /proc/scsi/scsi file. The alue of "scsi" is 0 for the first deno, 1 for the second deno (if it is different from the first deno), and so on. The alue of "Channel" can start from 0 for each different "scsi" alue. The alue of "Id" is the one you use for <unit scsi-lun> in the preious mapping. The alue of "Lun" is the logical unit number of the target deice, for example, the last number in the preious mapping. Currently, the zfcp deice drier does not support dynamically remoing the attached deices. If you need to remoe the tape deices from the system, do "rmmod zfcp". Then you can delete the entry in /etc/modules.conf and reload zfcp, or reload zfcp first and dynamically add the deices you want. After you hae done all the mapping, if you can see all of the attached tape deices in /proc/scsi/scsi, you hae successfully attached those deices to your system. Next you may install the lin_tape deice drier. Refer to the " Installation Procedure on page 95" section in this chapter for the instructions on how to install lin_tape. Uninstall Procedure Note: All tape deices that use the lin_tape drier must be closed and cannot be in use when lin_tape is uninstalled or the uninstall fails. Run the following command: >rpm -e lin_tape ---to remoe Tape Drie, Media, and Deice Drier Parameters This chapter describes the parameters that control the operating modes of the IBM Linux Tape and Medium Changer Deice Drier. Configuration Parameters The configuration parameters are used to set the operating mode of the tape drie and deice drier when a deice is opened. The installation defaults are proided for all parameters initially. These parameters are kept on reopen, but are always restored back to the default alues when the lin_tape deice drier is reinstalled. Note: This is performed using tape diagnostic and utility functions. The nonchangeable configuration parameters are: Autoloading Density code Emulate autoloader Hook word Maximum block size Minimum block size Medium type Chapter 5. Linux Tape and Medium Changer Deice Drier 99

118 Linux Deice Drier (lin_tape) Read SILI bit Record space mode Volume ID for logging Write protect The changeable configuration parameters are: Block size Buffered mode Capacity scaling Compression Disable auto drie dump Disable SIM logging Logging Logical write protect Maximum SCSI transfer length Read past filemark Rewind immediate Trace Trailer labels Nonchangeable Parameters The configuration parameters are used to set the operating mode of the tape drie and deice drier when a deice is opened. The nonchangeable parameters are detailed as follows: Autoloading This parameter enables the autoloading feature of the deice drier. It is disabled by default and cannot be changed. Capacity Scaling This parameter sets the capacity or logical length of the current tape. By reducing the capacity of the tape, the tape drie can access data faster at the expense of data capacity. Capacity Scaling is not supported currently but might be supported in future releases of lin_tape. Density Code This parameter is the density setting for the currently loaded tape. Some tape deices support multiple densities and report the current setting in this field. It cannot be changed by the application. Emulate Autoloader This parameter currently is not supported and should be ignored. Hook Word This parameter is not supported in the lin_tape deice drier. Logical Write Protect This parameter sets or resets the logical write protect of the current tape. This feature is not supported currently but might be supported in future releases of the lin_tape. 100 IBM Tape Deice Driers Installation and User s Guide

119 Maximum Block Size This parameter is the maximum block size for the deice. Minimum Block Size This parameter is the minimum block size for the deice. Linux Deice Drier (lin_tape) Medium Type This parameter is the media type of the current loaded tape. Some tape deices support multiple media types and different alues are reported in this field. Read SILI Bit SILI bit currently is not supported due to limitations associated with the Linux enironment. SILI bit support may be enabled in future releases of the lin_tape. Record Space Mode This parameter specifies how the deice drier operates when a forward or backward space record operation encounters a filemark. Only the SCSI mode is supported by lin_tape. When a forward or backward space record operation is issued to the drier and a filemark is encountered, the deice drier returns -1 and the errno ariable is set to input/output error (EIO). On the forward space operation, the tape is left-positioned after the filemark (the end of tape side of the filemark). On the backward space operation, the tape is positioned before the filemark (the beginning of tape side of the filemark). Volume ID for Logging This parameter is the olume ID of the currently loaded tape. The lin_tape deice drier ignores this field. Write Protect This parameter is set to TRUE if the currently mounted tape is logically or physically write protected. Changeable Parameters The configuration parameters are used to set the operating mode of the tape drie and deice drier when a deice is opened. The changeable parameters are detailed as follows: Block Size This parameter specifies the block size used for read and write operations. A alue of zero means a ariable block size. Any other alue is a fixed block size. The installation default is zero (ariable length block size). Refer to Maximum SCSI Transfer Length on page 103 for additional guidance. Buffered Mode This parameter specifies if read and write operations should be buffered by the tape deice. The default (recommended) alue is TRUE. Capacity Scaling This parameter sets the capacity or logical length of the current tape on Enterprise Tape System 3590 or 3592 tape subsystems. By reducing the capacity of the tape, the tape drie can access data faster at the expense of data capacity. Capacity scaling can be set at 100% for the entire tape (which is the default), or set at 75%, 50%, or 25% of the 3590 tape cartridge and more aailable capacity scaling for the 3592 standard 300 GB rewritable data cartridge. Capacity scaling remains with the tape across mounts until it is changed. Chapter 5. Linux Tape and Medium Changer Deice Drier 101

120 Linux Deice Drier (lin_tape) Note: 1. The tape position must be at the start of the tape to change this parameter from its current alue. 2. Changing this parameter destroys any existing data on the tape. 3. For 3592 media types, capacity scaling is only supported for the standard 300 GB rewritable data cartridge. Attempting to set capacity scaling that is not supported by a deice or the current media loaded always returns 100% and cannot be changed. For example, the 60GB (Economy Data) cartridge for the IBM 3592 cannot be capacity scaled and is always 100%. Compression Hardware compression is implemented in the deice hardware. This parameter turns the hardware compression feature On and Off. If compression is enabled, the effectie performance can increase, based on the compressibility of the data. The installation default is On (use compression). Disable Auto Drie Dump This parameter is proided in the lin_tape ersion or later. It is set to FALSE by default. If it is FALSE and the lin_taped daemon is running and if an error occurs in the drie which creates a drie dump, the lin_tape deice drier automatically retriees the drie dump and saes it under the /ar/log directory by default. You may specify another directory in the /etc/lin_taped.conf file. Please refer to Configure and Run lin_taped Daemon on page 114 in this chapter for details. Disable SIM logging This parameter is proided in the lin_tape ersion or later. It is set to FALSE by default. If it is FALSE and the lin_taped daemon is running and SIM/MIM data is generated by the drie, the lin_tape deice drier automatically retriees the data and saes it in a formatted text file under the /ar/log directory by default. You may specify another directory in the /etc/lin_taped.conf file. Please refer to Configure and Run lin_taped Daemon on page 114 in this chapter for details. This capacity is not applicable to IBM Ultrium tape dries. Logging (Volume Logging) This parameter turns the olume information logging On or Off. With the lin_tape ersion and later, the lin_tape deice drier proides this support. It is set to On by default. If logging is On and the lin_taped daemon is running, the lin_tape deice drier retriees the full log sense data from the drie wheneer a tape is unloaded, or the drie reaches a log threshold. The log file is saed in binary format under the directory /ar/log by default. You may specify another directory in /etc/lin_taped.conf file. Please refer to Configure and Run lin_taped Daemon on page 114 in this chapter for details. Note: This is olume logging, which is different from error logging. lin_tape proides error logging wheneer the lin_taped daemon is running. Please refer to Configure and Run lin_taped Daemon on page 114 in this chapter for details on error logging. Logical Write Protect This parameter sets or resets the logical write protect of the current tape on Enterprise Tape System 3590 tape subsystems. The three types of logical write protect are: associated protect, persistent protect, and write-once read-many (WORM) protect. 102 IBM Tape Deice Driers Installation and User s Guide

121 Linux Deice Drier (lin_tape) 1. Associated protect remains only while the current tape is mounted or associated with the tape drie. It is reset when the tape is unloaded or the tape drie is reset. 2. Persistent protect remains or persists with the tape across mounts until it is reset. 3. WORM protect also remains with the tape across mounts, but unlike persistent protect it cannot be reset on the tape. After a tape is WORM protected, it can neer be written on again. Note: The tape position must be at the start of the tape to change this parameter from its current alue. Maximum SCSI Transfer Length In the lin_tape driers with leel lower than 3.0.3, the maximum transfer length per deice per SCSI command is bytes (256 KB) by default. Variable block read/write requests with transfer length greater than the maximum transfer length fails [errno: EINVAL]. When a fixed block size has been defined, large write requests are subject to both the granularity of the block size and the maximum transfer length. For example, with a fixed block size of bytes and maximum transfer length of , a write request for bytes (5 blocks of each) is written to tape in two transfers. The first transfer is bytes (3 blocks) and the second transfer is (the remaining two blocks). You may increase the maximum transfer length to enhance the data throughput. This can be done using ITDT using the Query/Set Parameters option, or a customized STIOCSETP input/output control (ioctl) call. Howeer, setting the transfer length greater than the default 256 KB does not guarantee a noticeable increase in data throughput. Maximum transfer length of 256 KB is highly recommended. In lin_tape drier with leel or higher and the open source drier lin_tape, the maximum transfer length is defined as the minimum length that the host bus adapter and the tape drie can support. This number is usually greater than 256KB. It can not be changed by the STIOCSETP ioctl call any more. Read Past Filemark If this parameter is set to true, when a read operation encounters a filemark, it returns the number of bytes read before encountering the filemark and positions the tape head after the filemark. If the read_past_filemark parameter is set to false, when the read operation encounters a filemark, if data was read, the read function returns the number of bytes read, and positions the tape head before the filemark. If no data was read, then the read returns 0 bytes read and positions the tape head after the filemark. This installation default is FALSE. Rewind Immediate This parameter sets the immediate bit for rewind commands. If it is set to On, the rewind tape operation executes faster, but the next command takes a long time to finish unless the physical rewind operation has completed. Setting this parameter reduces the amount of time it takes to close a deice for a Rewind on Close special file. The installation default is Off (no rewind immediate). Trace This parameter turns the trace facility On or Off. With the lin_tape ersion and later, the lin_tape deice drier proides this support. It is set to On by Chapter 5. Linux Tape and Medium Changer Deice Drier 103

122 Linux Deice Drier (lin_tape) Special Files default. If trace is On and the lin_taped daemon is running, the lin_tape deice drier retriees the trace from the drier if trace leel is set to 1 or 2 in the /etc/lin_taped.conf file. The trace file is saed under the directory /ar/log by default. You may specify another directory in /etc/lin_taped.conf file. Please refer to Configure and Run lin_taped Daemon on page 114 for details. Trailer Labels If this parameter is set to On, then writing records past the early warning mark on the tape is allowed. The first write operation after detecting the early warning mark fails and the errno ariable is set to ENOSPC. No data is written during the operation. All subsequent write operations are allowed to continue until the physical end of the olume is reached and errno EIO is returned. If this parameter is set to Off, then writing records past the early warning mark is not allowed. Errno ariable is set to ENOSPC. The installation default is On (with trailer labels). After the drier is installed and a deice is configured and made aailable for use, access is proided through the special files. These special files, which consist of the standard Linux special files for deices, are in the /de directory. Special Files for the Tape Deice Each tape deice has a set of special files proiding access to the same physical drie but proiding different attributes. Table 16 shows the attributes of the special files. Note: The asterisk (*) in IBMtape* represents a number assigned to a particular deice, such as IBMtape0. For tape dries with attached medium changer deices, the IBMchanger* special file proides a separate path for issuing commands to the medium changer. When this special file is opened, the application can iew the medium changer as a separate deice. Both the tape and changer special file can be opened at the same time. Table 16. Special Files for IBM TotalStorage Tape Deices Special File Name /de/ibmtape* /de/ibmtape*n Rewind on Close YES NO Special Files for the Medium Changer Deice After the drier is installed and a medium changer deice is configured and made aailable for use, access to the robotic deice is proided through the IBMchanger special file in the /de directory. The asterisk (*) represents a number assigned to a particular deice, such as IBMchanger0. The term IBMchanger is used for a SCSI medium changer deice. The IBMchanger* special file proides a path for issuing commands to control the medium changer robotic deice. The file descriptor that results from opening the IBMchanger special file does not support the following operations: Read 104 IBM Tape Deice Driers Installation and User s Guide

123 Linux Deice Drier (lin_tape) Write Open in Append mode Commands designed for a tape deice Persistent Naming Support Lin_tape persistent naming is implemented through the Linux ude utility. Ude is a serice that monitors changes in system hardware configuration and performs actions based on what deices are attached to the Linux system. It can be configured to create symbolic links (persistent names) to a deice based on attributes that a drier exports for that deice. The persistent name may then be used as the deice name to open and perform IO to a tape drie or medium changer. This will make it possible to reference a static name, such as /de/lin_tape/by-id/lin_tape , which will always be associated with the same physical deice, rather than being required to reference the deice name /de/ibmtape0, which may change names and become /de/ibmtape1 after the drier is reinstalled. Lin_tape exports seeral attributes that can be used as the basis to create persistent names. These attributes can be reported to the user through udeadm info on recent Linux kernels, or udeinfo on older Linux kernels. Please refer to the man pages for udeadm or udeinfo for details on usage. Ude, udeinfo, and udeadm are not implemented or maintained by the lin_tape drier, and the man pages for a gien system will supercede all information in this document. For questions on using these utilities you should contact your Linux support representatie. Howeer, this section proides an example on using ude for implementing a persistent name. The example should be customized to fit a user s needs and enironment. If there is a tape deice attached to the Linux system with world-wide port name 0x ABCDEF0 with a current deice name of /de/ibmtape0, a user could run udeadm info to obtain information on exported attributes for this deice. This could be done as follows: >udeadm info --attribute-walk --name /de/ibmtape0 The output of this command should include something similar to the following: ATTRS{serial_num}==" " ATTRS{ww_node_name}=="0x ABCDEF1" ATTRS{ww_port_name}=="0x ABCDEF0" Note: Variations exist between kernels. For example, if you are using udeinfo, you should enter the preious command as >udeinfo -a -p `udeinfo -q path -n /de/ibmtape0` Also, on some kernels an attribute ATTRS{xxx} will be replaced by SYSFS{xxx}. Furthermore, some kernels use a '=' (single equal sign) to indicate an attribute match as well as an assignment, whereas other kernels use a '==' (double equal sign) for a match and '=' for assignment. You should place the attribute from the attribute list into your rules file exactly as it appears in the attribute list, as described below. We can use the ww_port_name in a.rules file that will assign a symbolic link to a deice that has the listed world-wide port name. The file will typically be placed in /etc/ude/rules.d, but this location may be changed by the ude_rules Chapter 5. Linux Tape and Medium Changer Deice Drier 105

124 Linux Deice Drier (lin_tape) directie in the /etc/ude/rules.conf file. In this example, we create a file called /etc/ude/rules.d/98-lin_tape.rules and write a single line to the file: KERNEL=="IBMtape*", ATTRS{ww_port_name}=="0x ABCDEF0", SYMLINK="lin_tape/by-id/lin_tape Assuming that the ude serice is running and configured correctly, the user can install or reinstall lin_tape using modprobe, and the symbolic link should be created in the /de/lin_tape/by-id folder. One line should be added to the 98-lin_tape.rules file for each symbolic link desired. Control Path Failoer Support for Tape Libraries Note: The library control path failoer feature code must be installed prior to enabling control path failoer support in the Linux lin_tape deice drier. Refer to Automatic Failoer on page 10 to determine which feature code is required for your machine type. The Linux lin_tape deice drier control path failoer support configures multiple physical control paths to the same logical library within the deice drier and proide automatic failoer to an alternate control path when a permanent error occurs on one path. This is transparent to the running application. Configuring and Unconfiguring Path Failoer Support Control path failoer support is not enabled automatically when the deice drier is installed. The Linux lin_tape deice drier proides a drier parameter alternate_pathing for you to enable the library control path failoer. To enable the failoer support in the lin_tape deice drier software, you need do the following steps after installing the lin_tape rpm package: 1. lin_taped stop (stop the lin_taped daemon) 2. rmmod lin_tape (unload the lin_tape drier from the memory) 3. Add the following line in your /etc/modules.conf file for 2.4 kernels or /etc/modprobe.conf.local file for 2.6 kernels: options lin_tape alternate_pathing=1 4. depmod 5. modprobe lin_tape (re-load the lin_tape drier into memory) 6. lin_taped (re-start lin_taped daemon) You can ignore the "Unresoled symbols in /lib/modules/<your kernel name>/driers/scsi/lin_tape.ko" message after the "depmod" command. You can check if the lin_tape drier has recognized multiple control paths for your library by reading the /proc/scsi/ibmchanger file. cat/proc/scsi/ibmchanger If your library lists "Primary" or "Alternate" under "FO Path", you hae successfully enabled control path failoer feature for your library. If it is "NA" listed under "FO Path", then the control path failoer is not enabled. After control path failoer support is enabled, it remains set until the lin_tape drier is reloaded with the alternate_pathing drier parameter set to OFF. The path failoer setting is retained een if the system is rebooted. If you want to turn off the control path failoer feature in the lin_tape deice drier, you can perform the following steps: 1. lin_taped stop 2. rmmod lin_tape 3. Delete the following line in your /etc/modules.conf file: 106 IBM Tape Deice Driers Installation and User s Guide

125 Linux Deice Drier (lin_tape) options lin_tape alternate_pathing=1 4. depmod 5. modprobe lin_tape 6. lin_taped Primary and Alternate Paths When lin_tape is loaded into kernel memory, the first logical medium changer deice that lin_tape sees in the system is the primary path for that medium changer. The other logical medium changers that lin_tape attached for the same medium changer are configured as alternate paths. The deice drier supports up to 16 physical paths for a single deice. The primary and alternate path information can be obtained by the following command: cat /proc/scsi/ibmchanger The following is an example of a /proc/scsi/ibmchanger file: lin_tape ersion: lin_tape major number: 253 Attached Changer Deices: Number Model SN HBA FO Path L22 IBM qla2xxx Primary L22 IBM qla2xxx Alternate L22 IBM qla2xxx Alternate The labeling of a logical deice as either a primary or alternate path is for information only, in order to: Be able to identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled as the primary path for each physical deice. Howeer, there can be multiple logical deices labeled as an alternate path for the same deices. Proide information about which logical deices configured on the system hae path failoer support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices by reading the /proc/scsi/ibmchanger file, as explained in section Primary and Alternate Paths. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Disable and Enable Primary and Alternate Paths Once you load the lin_tape deice drier with the alternate_pathing parameter to be ON, by default, all the aailable paths for a physical deice are enabled. If it is necessary to disable a path and not perform path fail oer (for example due to maintenance), run commands to disable and then later enable the primary and alternate paths. Chapter 5. Linux Tape and Medium Changer Deice Drier 107

126 Linux Deice Drier (lin_tape) The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. Note: See Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Data Path Failoer and Load Balancing Support for Tape Dries Data path failoer support is not enabled automatically when the deice drier is installed. The Linux lin_tape deice drier proides a drier parameter alternate_pathing for you to enable the data path failoer. To enable the failoer support in the lin_tape deice drier software, you need to perform the following steps after installing the lin_tape rpm package. >lin_taped stop (stop the lin_taped daemon) >rmmod lin_tape (unload the lin_tape drier from the memory If you hae IBM 3592 tape dries, add the following line in your /etc/modules.conf file for 2.4 kernels or /etc/modprobe.conf.local file for 2.6 kernels: options lin_tape alternate_pathing=1 If you hae IBM LTO tape dries, the library needs to hae path failoer feature code. The data path failoer license keys are needed to enable the failoer if you are running LTO2 dries or if you are running LTO3 dries with old leels of drie code. DPF keys do not need to be added if you are running the latest drie code on LTO3 or LTO4 dries. Add the following line in your /etc/modules.conf file for 2.4 kernels or /etc/modprobe.conf.local file for 2.6 kernels: options lin_tape alternate_pathing=1 dpf_keys="abcdefghijklmnop" "abckdefghijklmnop" is an example of a data path failoer feature key. If you hae multiple libraries and multiple data path failoer feature keys, input your keys as follows: dpf_keys="key1;key2;..." Sae the file, then run the following commands: >depmod >modprobe lin_tape (re-load the lin_tape drier into memory) >lin_taped (re-start lin_taped daemon) You may ignore the "Unresoled symbols in /lib/modules/<your kernel name>/driers/scsi/lin_tape.ko" message after the depmod command. You can check if the lin_tape drier has recognized multiple paths for your tape drie by reading the /proc/scsi/ibmtape file: >cat /proc/scsi/ibmtape If your tape drie lists "Primary" or "Alternate" under "FO Path", you hae successfully enabled data path failoer feature for your tape drie. If it is "NA" listed under "FO Path", then the data path failoer is not enabled. After the path failoer support is enabled, it remains set until the lin_tape drier is reloaded with the alternate_pathing drier parameter set to OFF. The path failoer setting is retained een if the system is rebooted. If you want to turn off the data path failoer feature in the lin_tape deice drier, you may do the following steps: 108 IBM Tape Deice Driers Installation and User s Guide

127 Linux Deice Drier (lin_tape) >lin_taped stop >rmmod lin_tape Delete the following line in your /etc/modules.conf file: options lin_tape alternate_pathing=1 >depmod >modprobe lin_tape >lin_taped Primary and Alternate Paths When the lin_tape deice drier is loaded into kernel memory with path failoer support enabled, the first logic deice that lin_tape sees always becomes the primary path. The other logical deices that lin_tape sees are configured as the alternate paths. The deice drier supports up to 16 physical paths for a single deice. The primary and alternate path information can be obtained by the following command: >cat /proc/scsi/ibmtape The following is an example of a /proc/scsi/ibmtape: lin_tape ersion: lin_tape major number: 253 Attached Tape Deices: Number Model SN HBA FO Path IBM qla2xxx Primary IBM qla2xxx Alternate The labeling of a logical deice as either a primary or alternate path is for information only to: Be able to identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled the primary path for each physical deice. Howeer, there may be many (multiple) logical deices labeled as an alternate path for the same deices. Proide information about which logical deices configured on the system hae path failoer support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices by reading the /proc/scsi/ibmtape file, as explained in section Primary and Alternate Paths. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Disable and Enable Primary and Alternate Paths If it is necessary to disable a path and not perform path fail oer (for example due to maintenance), run commands to disable and then later enable the primary and alternate paths. Chapter 5. Linux Tape and Medium Changer Deice Drier 109

128 Linux Deice Drier (lin_tape) The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. Note: See Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Tape Resere Type This parameter will cause lin_tape to issue SCSI-3 persistent reseres to a tape drie wheneer a reseration is attempted. Note that persistent reseres are automatically issued if data path failoer is used, and therefore setting the parameter should be unnecessary. This parameter can only be set when lin_tape is installed. To set it, add the following line to /etc/modprobe.conf (or /etc/modprobe.conf.local): options lin_tape tape_resere_type=persistent Open Source Deice Drier - lin_tape The lin_tape deice drier is the new deice drier for the Linux 2.6 kernels to replace the closed-source drier IBMtape. In most respects, it behaes the same as the closed-source IBMtape deice drier. This section coers significant differences between the IBMtape drier and the lin_tape drier. IBMtape and lin_tape Comparison Table 17 compares the names for arious components of the IBMtape and lin_tape deice driers. Table 17. IBMtape and lin_tape Comparison Component IBMtape Lin_tape Drier name IBMtape lin_tape Module name IBMtape.ko lin_tape.ko Special files /de/ibmtape0 No change /de/ibmchanger0, etc. proc entry /proc/scsi/ibmtape No change /proc/scsi/ibmchanger Daemon name IBMtaped lin_taped Daemon configuration file /etc/ibmtaped.conf /etc/lin_taped.conf Daemon trace files /ar/log/ibmtape.trace /ar/log/ibmtape.errorlog /ar/log/lin_tape.trace /ar/log/lin_tape.errorlog Installation Installation of the lin_tape drier is the same as for the IBMtape drier, except that IBMtape should be replaced with lin_tape in all of the installation instructions. Refer to the section Installation and Configuration Instructions on page 94 of this chapter for details. The lin_tape drier cannot be installed if the IBMtape drier is already installed. If the IBMtape drier is installed, first uninstall the IBMtape drier, and then install the lin_tape drier. With RHEL4 and SLES10, drier remoal also requires a reboot of the serer, since the IBMtape drier module is "permanent" in these distributions. 110 IBM Tape Deice Driers Installation and User s Guide

129 Drier parameters and special deice files The drier parameters hae not changed for the lin_tape drier. Howeer, it is important to note that the module parameters, such as "alternate_pathing" and "dpf_keys", must now be applied to the lin_tape module, instead of the IBMtape module. For example, in the /etc/modprobe.conf (for Red Hat) or /etc/modprobe.conf.local (for SUSE) file, add the following line for LTO library's path failoer: options lin_tape alternate_pathing=1 dpf_keys="abcdefghijklmnop" abckdefghijklmnop is an example of a data path failoer feature key. The special deice files for the lin_tape drier are the same as for the IBMtape drier. Refer to Special Files for the Tape Deice on page 104 and Special Files for the Medium Changer Deice on page 104 of this chapter for details on special deice files. Path Failoer Support Path failoer support in lin_tape is the same, except that with the lin_tape drier, failoer support is proided through the lin_taped daemon. If the lin_taped daemon is not running, neither control path failoer nor data path failoer is attempted. The lin_taped daemon is started automatically when the lin_tape drier is loaded. To check if the lin_taped daemon is running, run the following command: lin_taped status This command indicates if the lin_taped daemon is running or not. If the /proc/scsi/ibmtape and /proc/scsi/ibmchanger files indicate "NA" for "FO Path", this indicates that failoer support for that deice is not enabled. If all other settings are correct, but "FO Path" is incorrectly indicating "NA", confirm that the lin_taped daemon is running. For details about the path failoer support, refer to the sections " Control Path Failoer Support for Tape Libraries on page 106" and " Data Path Failoer and Load Balancing Support for Tape Dries on page 108" of this chapter. lin_taped Daemon The lin_taped daemon uses the same command-line arguments as the IBMtaped daemon. The lin_taped configuration file is the same as the IBMtaped configuration file, but has been renamed to lin_taped.conf. Refer to Configure and Run lin_taped Daemon on page 114 of this chapter for detailed information. System-Managed Encryption Deice Drier Configuration Linux Deice Drier (lin_tape) Note: System-managed encryption (SME) on Linux requires that the lin_taped daemon is running. Chapter 5. Linux Tape and Medium Changer Deice Drier 111

130 Linux System-Managed Encryption The deice drier SME settings can be set for all dries at once using the "default_sys_encryption_proxy" and "default_sys_encryption_write" module options. If no options are specified in the registry, the drier uses the default alues for the parameters. The default alue for default_sys_encryption_proxy is 1. This alue causes the deice drier to handle encryption key requests, if the drie is set up for system-managed encryption. This alue should not need to be changed. A alue of 0 causes the deice drier to ignore encryption key requests for system-managed encryption dries, and is not desirable. The default alue for default_sys_encryption_write is 2. This alue causes the deice drier to leae the encryption write-from-bop settings alone. It does not turn on or turn off encryption writing, but instead uses the settings that are already in the drie. If encryption has not been set up preiously, then the drie writes unencrypted data. A alue of 0 causes the deice drier to write unencrypted data. A alue of 1 causes the deice drier to write encrypted data. The module options can be specified in the /etc/modprobe.conf or /etc/modeprobe.conf.local files, the same as other lin_tape module parameters. For example, to turn on SME to write/read encrypted data: 1. Add the following line: options lin_tape default_sys_encryption_write=1 2. Then run the following commands: >lin_taped stop >rmmod lin_tape >depmod >modprobe lin_tape (reinstall back) >lin_taped (restart the daemon) The default settings are used to initialize the settings for all connected dries. To modify the settings for indiidual dries, the settings are "sys_encryption_write" and "sys_encryption_proxy", and hae the same definitions and alues as the similarly named "default" parameters, except that the settings only apply to indiidual dries. These settings are aailable as part of the sysfs infrastructure. For each drie, there are two files, named "sys_encryption_write" and "sys_encryption_proxy", in the /sys/class/lin_tape/{device}/ directory, where: {DEVICE} is the deice name, such as IBMtape0. The contents of these files indicate the current setting for the parameter for that particular drie. The setting can be changed by writing a different alue for the parameter to the file. For example, to change the "sys_encryption_write" setting for IBMtape0 to ON (which has a alue of 1), enter the following at a command prompt: echo 1">/sys/class/lin_tape/IBMtape0/sys_encryption_write Note: The drier encryption parameters for indiidual dries are not persistent between loads of the lin_tape drier. If you remoe the lin_tape drier, and then reload it, the indiidual settings for all dries are the same as the "default" settings in /etc/modprobe.conf or /etc/modprobe.conf.local. 112 IBM Tape Deice Driers Installation and User s Guide

131 Linux System-Managed Encryption The ibmekm.conf file, which contains the configuration that the EKM serers use, is installed in the /etc/ directory when lin_tape is installed. Instructions for modifying this file are found within the file itself. Querying Tape Drie Configuration The following is an example of the output when the drie is configured for system-managed encryption, with encryption turned on: issuing query encryption status... encryption capable...yes encryption method...method_system encryption state...on Chapter 5. Linux Tape and Medium Changer Deice Drier 113

132 Linux System-Managed Encryption Problem Determination A set of tools is proided with the deice drier to determine if the deice drier and the tape deice are functioning correctly. Configure and Run lin_taped Daemon Starting with lin_tape ersion 1.2.5, the lin_tape deice drier proides an error diagnostic daemon (lin_taped) which proides the following capabilities: 1. Error logging and tracing 2. When drie dumps, log sense data, and/or SIM/MIM error information are created by the tape drie, the daemon automatically retriees that data and saes it to the hard drie on your Linux system. 3. Failoer and load balancing 4. Encryption Because lin_taped requires a minimal amount of system resource and because it proides these necessary diagnostic capabilities, IBM recommends that you leae the daemon enabled at all times. Install lin_taped lin_taped is automatically installed at /usr/bin/lin_taped when you install the lin_tape deice drier using the rpm or tar package. Refer to Installation and Configuration Instructions on page 94 for instructions on installing the lin_tape deice drier. Configure lin_taped You can customize the operation of lin_taped by modifying its configuration file, which is located at /etc/lin_taped.conf. The daemon only reads the configuration file when it starts; consequently, if you make modifications to the configuration file, then stop the daemon and restart it so that your modifications are recognized by the daemon. Tracing: Three leels of tracing are supported for the lin_tape deice drier and are defined as follows: 0 With tracing set to 0, ery minimal tracing is recorded from the lin_tape deice drier. 1 With tracing set to 1, lin_taped records information associated with each ioctl called. If a deice error occurs and SCSI sense data is obtained from the deice, a subset of that sense data is also recorded. This is the default setting for tracing. 2 With tracing set to 2, lin_taped records tracing messages for each SCSI command. If a deice error occurs and SCSI sense data is obtained from the deice, all sense data is also recorded. This tracing leel should only be used when a specific problem is being diagnosed due to the potential for huge amounts of data being generated. Set the lin_tapetrace ariable in the /etc/lin_taped.conf file to 0, 1, or 2, depending on what leel of tracing you desire. If the lin_tapetrace ariable is set to an inalid number, the lin_taped daemon does not start. Tracing information is written to a file named /ar/log/lin_tape.trace, by default. Information is written into the file until it is 1 MB in size, by default. After 1 MB of information is written, the file is archied (using the Linux ar command) into file 114 IBM Tape Deice Driers Installation and User s Guide

133 Linux Deice Drier (lin_tape) lin_tape.a in the same directory. In the archie, the filename is renamed to lin_tape.trace.timestamp, where: timestamp reflects the time that the file was archied. You may change the directory to which the tracing information is written or the default maximum size of the trace file by modifying settings in the lin_taped.conf file. Refer to the instructions in the lin_taped.conf file for details. Error Logging: lin_taped records certain error messages from the lin_tape deice drier in a file named /ar/log/lin_tape.errorlog, by default. Information is written into the file until it is 1 MB in size, by default. After 1 MB of trace information is written, the file is archied (using the Linux ar command) into file lin_tape.a in the same directory. In the archie, the filename is renamed to lin_tape.errorlog.timestamp, where: timestamp reflects the time that the file was archied. You may change the directory to which the error logging information is written or the default maximum size of the error log file by modifying settings in the lin_taped.conf file. Refer to the instructions in the lin_taped.conf file for details. Wheneer the lin_taped daemon is running, error logging is enabled if tracing is enabled. Following is an example an error log record: IBMtape0---E0001 Tue Sep 10 14:04: Scsi Path : CDB Command : Status Code : Sense Data : FF 0B C Description : Hardware Error The first line indicates the tape deice special file name and the deice serial number, and the timestamp when the error message was recorded. "Scsi Path" is the SCSI path for this logical unit. It matches the order of the scsi/channel/id/ Lun information in the /proc/scsi/scsi file. "CDB Command" is the command data block of the SCSI command. "Status Code" is the returned result from the Linux SCSI middle layer deice drier (scsi_mod.o). The four bytes represent drier_byte, host_byte, msg_byte, and status_byte, respectiely. "Sense Data" is the full SCSI sense data returned from the target. "Description" is a person-readable text string obtained by parsing the sense key field of the sense data. The following circumstances are not logged in the lin_tape.errorlog file: 1. Sense key is 0, and the sense data indicates an oerlength or an underlength read, or encountering a file mark or the end of data 2. Sense key is 2, and the ASC/ASCQ indicates the deice is becoming ready 3. Sense key is 6, indicating a unit attention 4. Sense key is 8, and the ASC/ASCQ indicates the end of data Volume Logging: The lin_tape deice drier retriees the full log sense data from the tape drie wheneer the drie reaches a log threshold, or a tape is unloaded from the drie, or the drie is reset through an application. This data is stored in binary in a file named lin_tape.timestamp.log, where: lin_tapen is the deice special file (for example, lin_tape1, lin_tape2, etc.) and timestamp reflects the time the file was created. Each time log sense data is obtained, it is written to a new file. Use the appropriate tape drie hardware reference manual to decode the log sense data. Chapter 5. Linux Tape and Medium Changer Deice Drier 115

134 Linux Deice Drier (lin_tape) The olume logging data is stored in the /ar/log directory by default. You may specify another directory in the /etc/lin_taped.conf file. There are two configuration parameters in the /etc/lin_taped.conf file that you can tailor to affect the number of log sense files that are kept on your system: lin_tapemaxlogsensefiles which can hae a alue of 0 or a positie decimal number. lin_tapeautologsensefileoerwrite which can hae a alue of 0 or 1. By default, lin_tapemaxlogsensefiles is 0 and lin_tapeautologsensefileoerwrite is 1, which means that eery time log sense data is created, it is written to a new file. If lin_tapemaxlogsensefiles is 0, lin_tapeautologsensefileoerwrite is ignored, and each time log sense data is obtained, it is written to a new file. If lin_tapemaxlogsensefiles is a positie number and lin_tapeautologsensefileoerwrite is 0, each time log sense data is created, lin_taped writes that data to a file until lin_tapemaxlogsensefiles hae been created; then lin_taped stops creating new files, een if new log sense data is produced. If lin_tapemaxlogsensefiles is a positie number and lin_tapeautologsensefileoerwrite is 1, each time log sense data is created, lin_taped writes that data to a file until lin_tapemaxlogsensefiles hae been created; then when new log sense data is detected, lin_taped deletes the oldest log sense file and creates a new file with the newest log sense data; thus, only the newest data is kept. Automatically Retriee a Drie Dump: If a condition occurs in the drie such that a drie dump is created, lin_taped retriees the drie dump and saes it in a file named lin_tapex.timestamp.dmp, where lin_tapen is the deice special file (for example, lin_tape1, lin_tape2, etc.) and timestamp reflects the time the file was created. Each time a drie dump is obtained, it is written to a new file. The IBM serice organization may request that you forward drie dumps to them for analysis. The drie dumps are stored in the /ar/log directory by default. You may specify another directory in the /etc/lin_taped.conf file. There are two configuration parameters in the /etc/lin_taped.conf file that you can tailor to affect the number of drie dumps that are kept on your system: lin_tapemaxdumpfiles which can hae a alue of 0 or a positie decimal number. lin_tapeautodriedumpfileoerwrite which can hae a alue of 0 or 1. By default, lin_tapemaxdumpfiles is 0 and lin_tapeautodriedumpfileoerwrite is 1, which means that eery time a drie dump is obtained, it is written to a new file. If lin_tapemaxdumpfiles is 0, lin_tapeautodriedumpfileoerwrite is ignored, and each time a drie dump is obtained, it is written to a new file. If lin_tapemaxdumpfiles is a positie number and lin_tapeautodriedumpfileoerwrite is 0, each time a dump is obtained, lin_taped writes that data to a file until lin_tapemaxdumpfiles hae been created; then lin_taped stops creating new files, een if new drie dumps are produced. 116 IBM Tape Deice Driers Installation and User s Guide

135 Linux Deice Drier (lin_tape) If lin_tapemaxdumpfiles is a positie number and lin_tapeautodriedumpfileoerwrite is 1, each time a dump is obtained, lin_taped writes that data to a file until lin_tapemaxdumpfiles hae been created; then when a new drie dump is detected, lin_taped deletes the oldest drie dump file and creates a new file with the newest drie dump data; thus, only the newest data is kept. Automatically Retrieed SIM/MIM Data: If a condition occurs in the drie such that a drie SIM/MIM data is created, lin_taped retriees the data and sae it in a file named lin_tapex.timestamp.simmim, where lin_tapen is the deice special file (for example, lin_tape1, lin_tape2, etc.) and timestamp reflects the time the file was created. Each time SIM/MIM data is obtained, it is written to a new file. The IBM serice organization may request that you forward SIM/MIM data to them for analysis. The SIM/MIM data is stored in the /ar/log directory by default. You may specify another directory in the /etc/lin_taped.conf file. There are two configuration parameters in the /etc/lin_taped.conf file that you can tailor to affect the number of SIM/MIM files that are kept on your system: lin_tapemaxsimmimdatafiles which can hae a alue of 0 or a positie decimal number. lin_tapeautosimmimdataoerwrite which can hae a alue of 0 or 1. By default, lin_tapemaxsimmimdatafiles is 0 and lin_tapeautosimmimdataoerwrite is 1, which means that eery time SIM/MIM data is obtained, it is written to a new file. If lin_tapemaxsimmimdatafiles is 0, lin_tapeautosimmimdataoerwrite is ignored, and each time SIM/MIM data is obtained, it is written to a new file. If lin_tapemaxsimmimdatafiles is a positie number and lin_tapeautosimmimdataoerwrite is 0, each time SIM/MIM data is obtained, lin_taped writes that data to a file until lin_tapemaxsimmimdatafiles hae been created; then lin_taped stops creating new files, een if new SIM/MIM data are created. If lin_tapemaxsimmimdatafiles is a positie number and lin_tapeautosimmimdataoerwrite is 1, each time SIM/MIM data is obtained, lin_taped writes that data to a file until lin_tapemaxsimmimdatafiles hae been created; then when new SIM/MIM data is detected, lin_taped deletes the oldest SIM/MIM file and creates a new file with the newest SIM/MIM data; thus, only the newest data is kept. Selectie Tracing: lin_tape proides facilities by which you can disable and enable tracing, error logging, auto-retrieing drie dumps, and auto-retrieing SIM/MIM data. You may selectiely enable/disable them through an application program which uses the STIOC_SETP ioctl. These settings persist until the deice drier is restarted, or the host system is rebooted. The parameters and their definitions are as follows: trace This parameter is set to On by default, which enables lin_tape tracing of actiities and error logging on a particular tape drie. Set this parameter to off to stop tracing and error logging. Chapter 5. Linux Tape and Medium Changer Deice Drier 117

136 Linux Deice Drier (lin_tape) logging This parameter is set to On by default and enables logging of log sense data. Setting this flag to Off suppresses olume logging for this deice. disable_sim_logging This parameter controls the logging of SIM/MIM data for a deice. By default it is set to Off which causes SIM/MIM data to be logged. Set this flag to On to suppress the logging of SIM/MIM records. disable_auto_drie_dump This parameter controls the saing of drie dumps for a deice. By default it is set to Off which causes drie dumps to be saed. Set this flag to On to suppress the saing of drie dumps. Run lin_taped If you are running the lin_tape deice drier, ersion or higher, after installing lin_tape lin_taped starts running een if your system does not hae a tape deice attached. If you add a new tape deice into your Linux system, lin_taped automatically creates a special file under the /de directory. If you are running the lin_tape deice drier, ersion 1.3.x or less, lin_taped does not automatically start if there is no tape deice attached. After you attach a new tape deice, you'll need to start the lin_taped daemon. You can inoke lin_taped from the command line. lin_taped takes zero or more of the parameters as listed in the following: lin_taped [start stop restart status] lin_taped or lin_taped start Starts the daemon. If there is already a lin_taped running, the new one is aborted. (Use "lin_taped restart" if lin_taped is already running.) lin_taped stop Terminates the daemon and frees all the resources associated with the daemon. When the daemon is stopped, no information is saed. lin_taped restart Terminates the currently running daemon and starts a new one. The new daemon reads the /etc/lin_taped.conf file. This command should be used after modifying the /etc/lin_taped.conf file while lin_taped is running. lin_taped status Prints a message on stdout indicate whether the daemon is running or not. Note: If you run "rmmod lin_tape" command to remoe the lin_tape deice drier from the running kernel, you need to stop the lin_taped daemon first; otherwise you get a "Deice or Resource Busy" error. Reseration Conflict Logging When the deice drier receies a reseration conflict on a tape drie command it will log the conflict to the kernel debug buffer (which is typically echoed to /ar/log/messages). Prior to logging the error the deice drier will determine if a SCSI Persistent Reseration is actie on the target tape drie and, if it is, will get the resering host initiator WWPN (World Wide Port Name). If successful, the deice drier will post the message lin_tape: resere held by xxxxxxxx 118 IBM Tape Deice Driers Installation and User s Guide

137 Linux Deice Drier (lin_tape) to the debug buffer. To preent multiple identical entries in the error log, subsequent reseration conflicts from the same resering host WWPN will not be logged. Chapter 5. Linux Tape and Medium Changer Deice Drier 119

138 120 IBM Tape Deice Driers Installation and User s Guide

139 Chapter 6. Solaris Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Hardware Requirements Software Requirements Installation and Configuration Instructions Preenting Conflicts with Other Deice Driers 125 Preinstallation Considerations Installing and Updating IBMtape Configuring IBM tape deices with Fibre Channel and SAS HBAs Solaris Zones Support Configuration Parameters Remoing IBMtape Adding or Remoing Deices Deconfiguring Tape Deices Tapelist Utility Program Special Files Deice Behaiors File Naming Conentions Persistent Naming Support Control Path Failoer Support for Libraries Configuring and Deconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configuration Disable and Enable Primary and Alternate Paths 151 Data Path Failoer and Load Balancing Support for Tape Dries Configuring and Deconfiguring Path Failoer Support Primary and Alternate Paths Querying Primary and Alternate Path Configuration Disable and Enable Primary and Alternate Paths 154 System-Managed Encryption Deice Drier Configuration Querying Tape Drie Configuration Testing Data Encryption Configuration and Connectiity Field Support Information Problem Determination Functional Verification Sense Data Logging Installation Problems Tape Monitor Daemon (tmd) Tracing Facility Dynamic Tracing Utility Setting the IBM_trace Leel for Static Tracing 160 Running Diags_info Script iostat Command Reseration Conflict Logging Purpose Data Flow This chapter proides an oeriew of the IBM SCSI Tape and Medium Changer Deice Drier for Solaris, also known as IBMtape. This deice drier product proides attachment for IBM Magnetic Tape and Library System products to Sun Microsystems SPARC and x64 Serers running the Solaris operating system. It is designed specifically to take adantage of the features proided by IBM tape and library systems, including control of the random access medium changer facility (moe, element information, and inentory) present in some deices. The goal is to gie applications access to the functions required for basic operations (such as backup and restore), as well as the adanced functions needed by full tape management systems. Wheneer possible, the deice drier is designed to take adantage of the IBM tape system features transparent to the application. Both data and commands flow between the application program and the tape subsystem by way of IBMtape. Figure 12 on page 122 shows the data flow between IBMtape, the application program, the SCSI adapter deice drier, and the IBM tape system. Copyright IBM Corp. 2007,

140 Solaris Deice Drier (IBMtape) Application Program IBMtape Deice Drier SCSI or FC Host Bus Adapter Drier IBM Tape Subsystem a Figure 12. Data Flow for Solaris Deice Drier (IBMtape) Product Requirements The following hardware and software components are required and supported by IBMtape. Hardware Requirements The following hardware is required and supported by IBMtape: One of the following SCSI-2 Differential Host Bus Adapters: Sun Microsystems S-Bus Differential SCSI-2 Host Adapter Sun S-Bus Ultra Differential SCSI-2 Fast/Wide Host Adapter Sun Dual-Channel Differential Ultra SCSI Host Adapter PCI (requires FC 9799 for 3590 or FC 5099 for IBM Magstar MP 3570 or 3575) Sun Microsystems Differential Fast/Wide SCSI-2 Host Adapter (DWIS/S) Host Adapter (UDWIS/S) (P/N X1062A) One or more of the following SCSI High Voltage Differential (HVD) host bus adapters (359x only): Sun Microsystems Differential Fast/Wide SCSI-2 Host Adapter (DWIS/S) Host Adapter (UDWIS/S) (P/N X1062A) Sun Microsystems SBus Ultra Differential Fast/Wide Intelligent SCSI-2 Host Adapter (UDWIS/S) (P/N X1065A) Sun Microsystems Dual-channel Differential UltraSCSI Host Adapter, PCI (P/N X6541A) One or more of the following SCSI Low Voltage Differential (LVD) host bus adapters on Solaris Version 8, or later (Ultrium only): Sun Microsystems PCI Adapter with two fast Ethernet Interfaces and two SCSI Interfaces (P/N X2222A) Sun Microsystems Dual Fast Ethernet + Dual SCSI PCI Adapter (Dual VHDCI) Sun Microsystems PCI Dual Channel Gigabit Ethernet UTP & Dual Channel SE Ultra-2 SCSI Adapter (P/N X4422A) Sun Microsystems PCI-X Single and Dual Ultra320 SCSI Host Adapter SCSI Adapter (P/N SG-XPCI1SCSILM320-Z and SG-XPCI2SCSILM320-Z ) One or more of the following Serial Attached SCSI (SAS) host bus adapters on Solaris Version 10, or later (Ultrium only): Sun StorageTek PCI-X SAS HBA (SG-XPCI8SAS-E-Z) Sun StorageTek PCI-Express SAS HBA (SG-XPCIE8SAS-E-Z) The IBM 2108 G07 (IBM SAN Data Gateway) and IBM 2108 R03 (IBM SAN Data Gateway Router) can be used to attach SCSI models of the IBM 357x, 3590, and VTS of products with any of the supported FC AL host bus adapters. 122 IBM Tape Deice Driers Installation and User s Guide

141 Solaris Deice Drier (IBMtape) The Ultrium tape dries and Enterprise Tape dries 3590 (Model E) and 3592 with Fibre Channel Attachment are supported with the following adapters: QLogic HBA: QLA2200F, QLA2310FL, QLA2340/2340L, QLA2342/2342L, QLA2460/2462 PCI and PCI-X Fibre Channel Host Bus Adapters QLE2560/2562 PCI-E Fibre Channel Host Bus Adapters QLE2460/2462 PCI-E Fibre Channel Host Bus Adapters on x64 system only. Emulex HBA: LP8000(PCI), LP8000S(S-Bus), LP9002C(cPCI), LP9002L(PCI), LP9002S(S-Bus), LP9042DC(PCI-X), LP9802(PCI-X), LP10000(PCI-X), LP11000/11002 (PCI-X) Fibre Channel Host Bus Adapters LPe12000/12002 PCI-E Fibre Channel Host Bus Adapters LPe11000/11002 PCI-E Fibre Channel Host Bus Adapters on x64 system only AMCC HBA: FCX/2-6562(PCI-X), FCX-6562(PCI-X), FCC/2 6562(cPCI), FCC-6562(cPCI), FCE-6460(PCI) and FCE-1473(S-Bus) Fibre Channel Adapters Sun Branded HBA: Sun StorEdge 2 Gb FC PCI Single Channel network adapter (X6767A) Sun StorEdge 2 Gb FC PCI Dual Channel network adapter (X6768A) Sun StorageTek Enterprise Class 4 Gb FC PCI-X HBAs (SG-XPCI2FC-QF4 and SG-XPCI1FC-QF4) Sun StorageTek Enterprise Class 4 Gb FC PCI-E HBAs (SG-XPCIE2FC-QF4, SG-XPCIE1FC-QF4, SG-XPCIE2FC-EM4, and SG-XPCIE1FC-EM4) Sun StorageTek Enterprise Class 8 Gb FC PCI-E HBAs (SG-XPCIE1FC-EM8-Z. SG-XPCIE2FC-EM8-Z, SG-XPCIE1FC-QF8-Z, and SG-XPCIE2FC-QF8-Z) Brocade HBA: Brocade 8 GB FC PCI-E Host Bus Adapters (825, 815) Brocade 4 GB FC PCI-E Host Bus Adapters (425, 415) A known issue: Brocade HBAs do not support L-port topology. Direct attach configuration to our Tape Storage products is therefore not supported with these cards. Table 18 indicates which SCSI-attached deices are supported through the IBM 2108-G07 (IBM SAN Data Gateway) and IBM 2108-R03 (IBM SAN Data Gateway Router) with which fibre-channel host bus adapters. Table 18. SCSI Supported Deices DEVICE Magstar MP 3570 Magstar MP 3575 Enterprise 3590, models B11, B1A, E11, and E1A QLogic QLA2100 X X QLogic QLA2200F Emulex LP8000 Emulex LP8000S X X X X VTS model B18 X X X X VTS models B10, X X X B20 Chapter 6. Solaris Tape and Medium Changer Deice Drier 123

142 Solaris Deice Drier (IBMtape) IBM Enterprise Tape Drie 3590, Models B11, B1A, E11, and E1A IBM Magstar MP 3570 Tape Subsystem Model C IBM Magstar MP 3575 Tape Library Dataserer IBM TotalStorage Virtual Tape Serer (Models B10, B18, and B20) Notes: 1. Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. Tape and disk deices 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 hae been obsered. These issues are resoled by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring serer and storage configuration interoperability. It strongly recommends that your implementation plan includes proisions for separating disk and tape workloads. 2. For IBM Ultrium dries with the Fibre Channel attachment, the Sun Solaris operating system requires that the Fibre Channel addressing mode of the drie be set to hard addressing. 3. The most recent supported HBA information can be found at: Software Requirements The following software is required and supported by IBMtape: Sun Microsystems Solaris operating system Version 2.6, 7, 8, 9, or 10 on SPARC serers. For Solaris Version 2.6, Sun patch is required. Sun Microsystems Solaris operating system Version 10 on x64 serers. SCSI Host Bus Adapter (HBA) drier as supplied by the HBA manufacturer. Refer to the manufacturer s documentation for the SCSI adapter drier to determine which adapter drier is required. Installation and Configuration Instructions IBM SCSI Tape Drie and Medium Changer Deice Drier for Solaris is an installable kernel module, supplied as a standard Solaris software package. When installed, its package name is IBMtape. The following sections describe installation, remoal, configuration, and erification procedures for IBMtape. Refer to the Solaris documentation for general information about installable packages. The IBMtape package consists of the deice drier and a number of associated files and utilities. For components created during IBMtape installation, refer to Table 19. Table 19. IBMtape Components Component (Note) /etc/ibmekm.conf /etc/tmd.conf /opt/ibmtape /opt/ibmtape/diags_info /opt/ibmtape/ibmekm.conf /opt/ibmtape/tapelist Description SME configuration file, working ersion TMD configuration file, working ersion Package subdirectory Diagnostic script SME configuration file, reference ersion Utility program 124 IBM Tape Deice Driers Installation and User s Guide

143 Solaris Deice Drier (IBMtape) Table 19. IBMtape Components (continued) Component (Note) /opt/ibmtape/tmd /opt/ibmtape/tmd.conf /opt/ibmtape/ibmtape.conf /opt/ibmtape/ztapelist /opt/ibmtape/tapedtrc /usr/kernel/dr/ibmtape /usr/kernel/dr/ibmtape.conf /usr/include/sys/smc.h Description Tape Monitor Daemon (TMD) program TMD configuration file, reference ersion Configuration file, reference ersion Shell script for Solaris zones use Dynamic tracing utility program Kernel module deice drier Configuration file, working ersion Medium changer application programming interface (API) header file /usr/include/sys/st.h Tape drie API header file /usr/include/sys/sc.h Serice aid API header file /usr/include/sys/oldtape.h Compatibility API header file Note: When updating IBMtape, the working copies of IBMtape.conf, tmd.conf and ibmekm.conf are not oerwritten by the package file contents. This allows tape drie configuration options to be presered across IBMtape updates. The reference copies of IBMtape.conf, tmd.conf and ibmekm.conf are always installed in the /opt/ibmtape directory. Examples of installation commands and their results throughout this chapter use a percent sign (%) to indicate the shell prompt. Preenting Conflicts with Other Deice Driers IBMtape only attempts to claim and operate the deices described in Hardware Requirements on page 122. Howeer, the Solaris operating system includes a SCSI tape deice drier named st, which claims any SCSI-compliant tape drie that it detects, including deices that IBMtape manages. In order to aoid conflicts between IBMtape and st, you must preent st from claiming and attempting to operate IBMtape-owned deices. Likewise, other suppliers SCSI tape deice driers that you hae installed must be preented from claiming IBMtape-owned deices. Note: To preent more than one deice drier from claiming IBMtape-owned deices, IBMtape must be also configured with HBA correctly. Refer to the section of Configuring IBM tape deices with Sun FC and SAS HBAs on page 133 for the details. Attention: Failure to preent more than one deice drier from operating the same tape drie may cause system panics or data loss on the tape drie. The following installation and update steps describe how to preent conflicts between IBMtape and other SCSI tape deice driers. Preinstallation Considerations Follow these steps to install or update IBMtape. Before starting the step-by-step procedure, note the following general considerations: Differential SCSI-2 support must already exist on the machine before installing IBMtape. Install and configure one of the supported differential SCSI adapters Chapter 6. Solaris Tape and Medium Changer Deice Drier 125

144 Solaris Deice Drier (IBMtape) first, then return to this section. Refer to the differential SCSI adapter documentation for instructions on installing the adapter and adapter drier. You must hae root authority to install or remoe IBMtape. You may restart the system as part of the IBMtape installation. Take appropriate precautions that this does not adersely affect users or actie processes on the system. As a consequence of installing or reinstalling IBMtape, deice special file numbers under /de/rmt may change. These numbers are assigned by Solaris during the drier attachment process, and the sequencing cannot be specified by the deice drier or installer. Installing and Updating IBMtape There are seeral steps that must be taken prior to installing or updating IBMtape on your system to ensure proper installation and system integrity. These are: 1. Notify users that system maintenance and a restart is performed. 2. Select a time when all system actiity can be stopped to perform the installation. 3. Login to the target system as root. 4. Ensure that all user and tape drie actiity on the system is halted. 5. If tape dries not owned by IBMtape are installed on the system, list the low-density deice special files and find the SCSI addresses with which they are currently associated. % ls -l /de/rmt/*l lrwxrwxrwx 1 root root 72 Aug 26 15:47 /de/rmt/5l ->../../deices/iommu@f,e /sbus@f,e /qlgc,isp@3,10000/st@2,0:l In the preceding example, /de/rmt/5l and the related 5m, 5h, and so on, are controlled by the st deice drier and are associated with the deice at SCSI address 2, LUN 0. Record the deice type, /de/rmt special file number, owning drier, SCSI target address and LUN. This information is required later in the installation. For example, suppose an installation has two non-ibm deices owned by st at SCSI addresses 2 and 8. The low-density deices are accessed as special files /de/rmt/5l and /de/rmt/6l. For the equipment listing after recording the deice information, refer to Table 20. Table 20. IBMtape Install or Update SCSI Address/LUN DEVICE Old Special File Old Drier (Old) QIC /de/rmt/5l st 2/0 QIC /de/rmt/6l st 8/0 6. If this is an update to IBMtape, there are already IBMtape-owned deices installed. In that case, list the primary deice special files and find the SCSI addresses with which they are currently associated. % ls -l /de/rmt/*st /de/rmt/*smc lrwxrwxrwx 1 root other 46 Aug 26 16:36 /de/rmt/0st ->../../deices/pci@6,4000/scsi@3/ibmtape@b,0:st lrwxrwxrwx 1 root other 47 Aug 26 16:36 /de/rmt/1smc ->../../deices/pci@6,4000/scsi@3/ibmtape@b,1:smc 126 IBM Tape Deice Driers Installation and User s Guide

145 Solaris Deice Drier (IBMtape) Note: When the drie is configured with Sun HBA drier, een though the hardware path shows as the deice special file still indicates that the drie is configured with IBMtape drier. lrwxrwxrwx 1 root root 80 Feb 22 05:12 /de/rmt/0st ->../../deices/pci@400/pci@0/pci@d/sunw,emlxs@0/fp@0,0/st@w c9848d68,0:st The aboe deice special file is created by IBMtape. Refer to the section Special Files on page 145 for more detail. In this example, /de/rmt/0st (a SCSI tape drie) is controlled by IBMtape and is associated with the deice at SCSI address b, LUN 0. The address is reported in hexadecimal format: The file /de/rmt/1smc (a SCSI medium changer) is associated with the deice at SCSI address b, LUN 1. Record the deice type, /de/rmt special file number, owning drier, SCSI target address and LUN. This information is required later in the installation. For example, suppose an installation has only an IBMtape-owned deice installed at SCSI address 8. The deice consists of both a tape drie and SCSI medium changer. The tape drie is accessed as /de/rmt/2st, and the medium changer as /de/rmt/3smc. For a similar equipment listing after recording the deice information, refer to Table 21. Table 21. Solaris Deice Drier - IBMtape - Equipment Listing Example 1 SCSI Address/LUN DEVICE Old Special File Old Drier (Old) 3590-B11 drie /de/rmt/2st IBMtape 8/ B11 changer /de/rmt/3smc IBMtape 8/1 7. Select one of the following methods to preent conflicts between IBMtape and other SCSI tape deice driers, depending on the equipment that is attached to your system. Note: To preent more than one deice drier from claiming IBMtape-owned deices, IBMtape must be also configured with HBA correctly. Refer to the section of Configuring IBM tape deices with Sun FC and SAS HBAs on page 133 for the details. Attention: Failure to preent more than one deice drier from operating the same SCSI tape drie may cause system panics or data loss on the tape drie. a. If the system has only IBMtape-owned deices attached, follow these steps to preent st and other non-ibm SCSI tape deice driers from claiming the IBM deices. 1) Edit /kernel/dr/st.conf, and comment out all SCSI target entries by placing a pound sign (#) in the first column of each target entry. The following example shows the entries for SCSI target addresses 0 and 1 commented out. Repeat this operation for all target entries. #name="st" class="scsi" #target=0 lun=0; #name="st" class="scsi" #target=1 lun=0; 2) For other non-ibm installed SCSI tape deice driers, remoe the driers if they are not needed. If a drier is for SCSI tape deices only, it should not be needed. If a drier is for both tape and disk deices, follow the suppliers instructions to disable its access to all SCSI tape deices. Chapter 6. Solaris Tape and Medium Changer Deice Drier 127

146 Solaris Deice Drier (IBMtape) b. If the system has a mixture of IBMtape-owned deices and other tape dries, follow these steps to configure st and other non-ibm SCSI tape deice driers so that they control a range of target addresses distinct from the range that IBMtape uses. These steps leae target addresses 7 and 15 unclaimed by all target deice driers, because SCSI adapters typically use one of those two addresses. 1) Edit /kernel/dr/st.conf, and comment out SCSI target entries for addresses 7 15 by placing a pound sign (#) in the first column of each target entry. In the following example, the entries for SCSI address 7 and 8 hae been commented out. Repeat this operation for all entries in the target address range #name="st" class="scsi" #target=7 lun=0; #name="st" class="scsi" #target=8 lun=0; 2) For other non-ibm installed SCSI tape deice driers, follow the suppliers instructions to disable their access to all SCSI tape deices in the address range ) Later, after the IBMtape package has been installed, you must alter its configuration file so it does not use SCSI target addresses in the range 0 7 or address 15. Now st and other non-ibm SCSI tape deice driers hae been configured to aoid conflicting with IBMtape. 8. Remoe all special file entries under /de/rmt. This ensures that stale entries do not exist after the system is restarted. New entries are created when the system is restarted. % rm /de/rmt/* 9. Read the next section of Configuring IBM tape deices with Fibre Channel and SAS HBAs on page 132, and follow the instruction requirements for the selected HBA in the host machine before and/or after installing IBMtape. 10. If you are updating the leel of IBMtape, remoe the currently installed IBMtape package. If this is a new installation of IBMtape, skip this step. a. Use pkgrm to remoe the current leel. % /usr/sbin/pkgrm IBMtape Respond to the pkgrm prompts. b. Examine the results from pkgrm. If you see these messages, one or more IBMtape-owned tape dries or tape monitor daemon (TMD) were still in use. Identify the dries and TMD process ID (pid), and end the processes that are using them. If you cannot identify the processes, you must restart the system to free the tape drie, then continue with the installation from this point.... Deice busy Cannot unload module: IBMtape Will be unloaded upon reboot Select one of the following methods to install the IBMtape package, depending on the package distribution medium and the location of system resources. Note: If this is a new install of IBMtape, IBM deices are not yet attached to the system, pkgadd error messages similar to the following are output: 128 IBM Tape Deice Driers Installation and User s Guide

147 Solaris Deice Drier (IBMtape)... drconfig: Drier (IBMtape) failed to attach Warning: Drier (IBMtape) successfully added to system but failed to attach ## The deice drier was unable to detect any supported deices! ## Verify that the deice(s) are properly connected and powered on. ## Ensure that the SCSI adapter deice drier is installed/configured. ## Then try reinstalling the deice drier as follows: ## -enter the command: rem_dr IBMtape ## -enter the command: add_dr -m * 0666 bin bin IBMtape ## If problems persist, contact your IBM serice representatie. pkgadd: ERROR: postinstall script did not complete successfully... Later, after you hae cabled IBM dries to the system and restarted, the drier attaches normally. If the distribution medium is a package file in a Unix file system, perform the following steps. You may hae obtained a package file by downloading it from IBM s Fix Central website: For further information please see Appendix A, Accessing Documentation and Software Online, on page 317. This example presumes a package file named IBMtape located in the /tmp directory. a. If necessary, FTP the package file to the target system. Use binary transfer mode. Place the package file in the target system s /tmp directory. b. Use pkgadd to install the drier: % /usr/sbin/pkgadd -d /tmp/ibmtape If your system enironment includes a mixture of IBMtape-owned deices and deices owned by st or another third-party SCSI tape deice drier, you should hae already modified the configuration files for the non-ibm deice driers and restricted them to target addresses in the range 0 6. Edit IBMtape.conf, located in /usr/kernel/dr, and comment out entries for SCSI target addresses 0 7 and 15 by placing a pound sign (#) in the first column of each line making up the entries. In the following example, the entries for address 0, LUN 0 and address 0, LUN 1 hae been commented out. Repeat the operation for all stanzas in the address range 0 7 and address 15. Note that each SCSI target address has a stanza for both LUN 0 and LUN 1. #name="ibmtape" class="scsi" #target=0 lun=0 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0; #name="ibmtape" class="scsi" #target=0 lun=1 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0; In SAN enironment, the fibre channel HBA drier may map the SCSI target address out of the range 15 and LUN oer the number 1. You create a new entry with the mapped SCSI target in IBMtape.conf. In the following example, a IBM tape deice is mapped to the SCSI target 32 and LUN 15. name="ibmtape" class="scsi" target=32 lun=15 block_size=0 Chapter 6. Solaris Tape and Medium Changer Deice Drier 129

148 Solaris Deice Drier (IBMtape) buffering=1 immediate=0 trailer=0 sili=0; Alternatiely, you can modify the configuration file or use the utility proided by the fibre channel HBA drier to persistently bind the tape deice to the expected SCSI target address. 13. Shut down the system. One common method to perform a shutdown is shown here but use your installation s normal procedures. % /usr/sbin/shutdown -y -g0 -i0 14. Address or readdress deices as determined by your installation: a. If the system has only IBMtape-owned deices attached, you may select addresses in the range 0 6 or Leae addresses 7 and 15 unused, because these addresses are used typically by the SCSI adapter. 1) For each deice, refer to the appropriate IBM hardware reference for any special instructions about addressing. Then set the address and record the deice type, SCSI address, and LUN. For example, suppose an installation has only IBMtape-owned deices attached. An IBM deice with tape drie and medium changer is added. It is addressed at target 4 and the information is recorded. For the results, refer to Table 22 Table 22. Solaris Deice Drier - IBMtape - Equipment Listing Example 2 SCSI Address/LUN (Old) SCSI Address/LUN (New) DEVICE Old Special File Old Drier 3590-B11 drie 4/ B11 changer 4/1 b. If you are using distinct address ranges to separate tape dries that are IBMtape-owned from deices that are owned by st or another supplier s drier, readdress the tape dries now. 1) For each deice to be owned by st or another SCSI tape deice drier, refer to the manufacturer s hardware reference for any special instructions about readdressing. Then readdress each deice to an address in the range 0 6. For each tape drie that is readdressed, record the new SCSI address along side the special file number and old SCSI address that you recorded preiously. 2) Readdress all tape dries that are owned by IBMtape to addresses in the range Refer to the appropriate IBM hardware references for any special instructions about readdressing. For each tape drie that is readdressed, record the new SCSI address along side the special file number and old SCSI address, if any, that you recorded preiously. For example, suppose an installation has two non-ibm deices owned by st at SCSI addresses 9 and B (12 in decimal). An IBM deice with tape drie and medium changer is added. To preent conflicts between IBMtape and st, the non-ibm deices are all placed at addresses in the range 0 6. The new IBM deice is addressed in the range 8 14, at address 10, or X'0A'. Depending on the addresses chosen for the non-ibm deices, after readdressing and recording deice information, refer to Table 22 for the possible equipment listing. 130 IBM Tape Deice Driers Installation and User s Guide

149 Solaris Deice Drier (IBMtape) Table 23. Solaris Deice Drier - IBMtape - Equipment Listing Example 3 SCSI Address/LUN (Old) SCSI Address/LUN (New) DEVICE Old Special File Old Drier QIC /de/rmt/2l st 9/0 3/0 QIC /de/rmt/3l st b/0 5/ B11 drie a/ B11 changer a/1 Note: The SCSI target address of fibre channel tape deice may be oer Cable the tape dries to the system, if not yet done. Refer to the manufacturer s hardware references for any special instructions about cabling. Ensure that each SCSI bus is terminated properly. 16. Start the system according to your installation s normal procedures. 17. Log on as root and list the deice special files in /de/rmt as you did earlier during the install. % ls -l /de/rmt/*l % ls -l /de/rmt/*st /de/rmt/*smc Compare the SCSI addresses obtained from ls with the readdressed SCSI targets you recorded. Write the new deice special file numbers and owning drier next to the matching new SCSI addresses. For example, suppose an installation preiously had two non-ibm deices owned by st at SCSI addresses 2 and 8. An IBM deice with tape drie and medium changer is added. To preent conflicts between IBMtape and st, the non-ibm deices are all placed at addresses in the range 0 6. The new IBM deice is addressed in the range Depending on the addresses chosen, after completing installation and recording deice information, refer to Table 24 for the possible equipment listing entries. Table 24. Solaris Deice Drier - IBMtape - Equipment Listing Example 4 SCSI Address/ LUN (Old) SCSI Address/ LUN (New) DEVICE Old Special File Old Drier New Drier New Special File (Note) QIC /de/rmt/5l st 2/0 2/0 st /de/rmt/0l QIC /de/rmt/6l st 8/0 0/0 st /de/rmt/1l 3590-B11 8/0 IBMtape /de/rmt/2st drie 3590-B11 changer 8/1 IBMtape /de/rmt /3smc Note: Based on the listing, you can see that the tape drie accessed preiously as /de/rmt/5 is now accessed as /de/rmt/0, the new medium changer is accessible as /de/rmt/3smc, and so on. 18. Perform alidation of "configuration conflict" to aoid the deice being configured with more than one deice drier. a. List the deice special files in /de/rmt and check if any unexpected deice special file is created by non-ibmtape drier. b. Verify whether same SCSI address or WWNN is pointed to different deice special files owned by the different deice drier. For example, a Chapter 6. Solaris Tape and Medium Changer Deice Drier 131

150 Solaris Deice Drier (IBMtape) same tape drie is configured by st drier with the special file of /de/rmt/0 and by IBMtape drier with /de/rmt/15st at the same SCSI address (target 0 and LUN 0). lrwxrwxrwx 1 root root 49 Jul /de/rmt/0 ->../../deices/pci@81,2000/fibre-channel@1/st@0,0: lrwxrwxrwx 1 root sys 56 Jul /de/rmt/15st ->../../deices/pci@80,2000/fibre-channel@1/ibmtape@0,0:st c. Run the system command or other utility to erify if the deice can be opened using both deice special file names. Using the deice special files in aboe example, load the cartridge in the drie and run # mt -f /de/rmt/* stat command (1) IBMtape opens the drie. # mt -f /de/rmt/15stn stat IBM_ULT3580-TD5 tape drie: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 (2) st opens the drie. # mt -f /de/rmt/0n stat IBM_ULT3580-TD5 tape drie: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 (3) st fails to open the drie. # mt -f /de/rmt/0n stat /de/rmt/0n: No such file or directory 19. Verify operation of the newly installed or readdressed equipment. 20. Notify users of any changed deice special files numbers. Configuring IBM tape deices with Fibre Channel and SAS HBAs Users may experience difficulty attaching an IBM tape deice with an IBM tape drier on a fibre network. The following sections describe how to configure IBM tape deices with QLogic, Emulex, Sun, Brocade and AMCC Fibre Channel HBAs: Configuring IBM tape deices with QLogic FC HBAs Configuring IBM tape deices with Emulex FC HBAs on page 133 Configuring IBM tape deices with Sun FC and SAS HBAs on page 133 Configuring IBM tape deices with AMCC FC HBAs on page 135 Configuring IBM tape deices with Brocade FC HBAs on page 135 Configuring IBM tape deices with QLogic FC HBAs To configure an IBM tape deice with a QLogic FC HBA, complete the following steps: 1. Run the QLogic SANSurfer Control FX utility to find and record the mapped target and LUN of the tape deice. 2. Remoe the comment at the beginning of the entry for the QLogic HBA in the /usr/kernel/dr/ibmtape.conf file. For example, the following command opens the entry for QLogic QLA2462 running QLogic HBA drier qla2300: name="ibmtape" parent="qla2300" target=0; # for qla2300 only 3. Update the entry for the deice in the IBMtape.conf file, if necessary. The current entry in the IBMtape.conf file is added to target 255 with LUN 0 and 1. For instance, the following command adds an entry for a mapped deice with target 200 and LUN 3: name="ibmtape" class="scsi" target=200 LUN=3; 132 IBM Tape Deice Driers Installation and User s Guide

151 Solaris Deice Drier (IBMtape) 4. Unload and reload the IBMtape drier: # /opt/ibmtape/tmd -s # rem_dr IBMtape # add_dr -m * 0666 bin bin IBMtape # /opt/ibmtape/tmd 5. Display information on the configured deices by running /opt/ibmtape/tapelist -l. To configure an IBM tape deice with a QLogic FC HBA running with Sun branded QLogic FC HBA drier (qlc), refer to the section Configuring IBM tape deices with Sun FC and SAS HBAs. Configuring IBM tape deices with Emulex FC HBAs To configure an IBM tape deice with an Emulex FC HBA, complete the following steps: 1. Run the Emulex HBAnyware utility to find and record the mapped target and LUN of the tape deice. 2. For lpfc.6.30g or later, update the parameters setting in /kernel/dr/lpfc.conf and reboot the system. If IBMtape drier is used as a tape drier, change the parameter for IBMtape: target-tape="ibmtape If IBMtape drier is used as a changer drier, modify the setting for IBMtape: target-tapechanger="ibmtape" 3. Remoe the comment at the beginning of the entry for the Emulex HBA in /usr/kernel/dr/ibmtape.conf: name="ibmtape" parent="lpfc" target=0; If this fails to configure the changer, you may need to add the entries for LUN 0 and 1: name="ibmtape" parent="lpfc" target=x lun=0; name="ibmtape" parent="lpfc" target=x lun=1; 4. Update the entry for the deice in the IBMtape.conf file, if necessary. The current entry in IBMtape.conf adds target 255 with LUN 0 and 1. For instance, the following command adds an entry for a mapped deice with target 200 and LUN 3: name="ibmtape" class="scsi" target=200 lun=3; 5. Unload and reload the IBMtape drier: # /opt/ibmtape/tmd -s # rem_dr IBMtape # add_dr -m * 0666 bin bin IBMtape # /opt/ibmtape/tmd 6. Display information on the configured deices by running /opt/ibmtape/tapelist -l. To configure an IBM tape deice with an Emulex FC HBA running with Sun branded Emulex FC HBA (emlxs) drier, refer to the section Configuring IBM tape deices with Sun FC and SAS HBAs. Configuring IBM tape deices with Sun FC and SAS HBAs To configure an IBM tape deice with a Sun FC HBA, complete the following steps: 1. Attach the IBM tape deices on the host. 2. Install the appropriate patch for the Sun HBA drier. Chapter 6. Solaris Tape and Medium Changer Deice Drier 133

152 Solaris Deice Drier (IBMtape) 3. Run # cfgadm -al to display the configuration between the HBA and the tape deice. Run # cfgadm -al -o show_fcp_de Ap_Id to show the medium changer configuration with the FC HBA. Run # cfgadm -c configure deice to configure the tape deice with the HBA if needed. 4. Install the IBMtape tape drier by running the # pkgadd -d IBMtape command. 5. Enter the following appropriate lines in /etc/drier_aliases: IBMtape "scsiclass,01.ibm.pxxx" for tape drie. IBMtape "scsiclass,08.ibm.pxxx" for medium changer. Where: 01 and 08 stand for the type of tape drie and medium changer and XXX is the product ID string in the standard inquiry data. For example, ULT3580-TD2 is the product ID of the IBM LTO2 drie. The following entry is added in the file for the IBM LTO2 drie: IBMtape "scsiclass,01.ibm.pult3580-td2" The following is a list of the entries for the supported IBM tape deices. For the tape dries: IBMtape "scsiclass,01.ibm.pult3580-td1" IBMtape "scsiclass,01.ibm.pultrium-td1" IBMtape "scsiclass,01.ibm.pult3580-td2" IBMtape "scsiclass,01.ibm.pultrium-td2" IBMtape "scsiclass,01.ibm.pult3580-td3" IBMtape "scsiclass,01.ibm.pultrium-td3" IBMtape "scsiclass,01.ibm.pult3580-hh3" IBMtape "scsiclass,01.ibm.pultrium-hh3" IBMtape "scsiclass,01.ibm.pult3580-td4" IBMtape "scsiclass,01.ibm.pultrium-td4" IBMtape "scsiclass,01.ibm.p03592j1a" IBMtape "scsiclass,01.ibm.p03592e05" IBMtape "scsiclass,01.ibm.p03592e06" For the medium changers: IBMtape "scsiclass,08.ibm.p03584l32" IBMtape "scsiclass,08.ibm.p03584l22" IBMtape "scsiclass,08.ibm.pult3582-tl" IBMtape "scsiclass,08.ibm.pult3583-tl" IBMtape "scsiclass,08.ibm.pult3581-ta" IBMtape "scsiclass,08.ibm.pult3581-ta2" IBMtape "scsiclass,08.ibm.p3576-mtl" IBMtape "scsiclass,08.ibm.p3573-tl" IBMtape "scsiclass,08.ibm.p3577-tl" Note: The entry is also added running the # update_dr command on Solaris 8 (patch is required), Solaris 9, and later ersions of the operating system. For example: # update_dr -a -i "scsiclass,01.ibm.pult3580-td2" IBMtape 6. Reboot the system by running # reboot -- -r. 7. Run # /opt/ibmtape/tapelist -l to display the configured tape deice information. Note: All of the added entries are remoed by the operating system automatically after IBMtape is unloaded from the kernel by running the # pkgrm, rem_dr, or modunload commands. It is strongly recommended that you back up these entries in a file, and that you re-enter the entries when you upgrade the IBMtape drier before running the #pkgadd command. 134 IBM Tape Deice Driers Installation and User s Guide

153 Configuring IBM tape deices with AMCC FC HBAs To configure an IBM tape deice with an AMMC FC HBA, complete the following steps: 1. Modify and add the following parameters in /kernel/dr/jnic146x.conf: CmdTaskAttr=1; lun_throttle=1; tape-deice="ibmtape"; tape-changer="ibmtape"; 2. Update the change in jnic146x.conf. 3. Run the EZ Fibre utility to find and record the mapped target and LUN of the tape deice. 4. Remoe the comment from the beginning entry for AMCC HBA in /usr/kernel/dr/ibmtape.conf: name="ibmtape" parent="jnic146x" target=0; 5. Update the entry for the deice in IBMtape.conf if necessary. The current entry in IBMtape.conf adds target 255 with LUN 0 and 1. For instance, use the following command to add an entry for a mapped deice with a target 200 and LUN 3: name="ibmtape" class="scsi" target=200 lun=3; 6. Unload and reload the IBMtape drier: # /opt/ibmtape/tmd -s # rem_dr IBMtape # add_dr -m * 0666 bin bin IBMtape # /opt/ibmtape/tmd 7. Display information on the configured deices by running /opt/ibmtape/tapelist -l. Solaris Deice Drier (IBMtape) Configuring IBM tape deices with Brocade FC HBAs To configure an IBM tape deice with an Brocade FC HBA, complete the following steps: 1. Attach IBM tape deices on the host. 2. Install the appropriate ersion of Brocade HBA drier and its utilities. 3. Run Brocade HCM (Host Connectiity Manager) to display the configuration. 4. Install the IBMtape tape drier running # pkgadd command. 5. Enter the following appropriate lines in /etc/drier_aliases: IBMtape "scsiclass,01.ibm.pxxx" for tape drie. IBMtape "scsiclass,08.ibm.pxxx" for medium changer. Where: 01 and 08 stand for the type of tape drie and medium changer and XXX is the product ID string in the standard inquiry data. For example, ULT3580-TD2 is the product ID of the IBM LTO2 drie. The following entry is added in the file for the IBM LTO2 drie: IBMtape "scsiclass,01.ibm.pult3580-td2" The following is a list of the entries for the supported IBM tape deices. For the tape dries: IBMtape "scsiclass,01.ibm.pult3580-td1" IBMtape "scsiclass,01.ibm.pultrium-td1" IBMtape "scsiclass,01.ibm.pult3580-td2" IBMtape "scsiclass,01.ibm.pultrium-td2" IBMtape "scsiclass,01.ibm.pult3580-td3" IBMtape "scsiclass,01.ibm.pultrium-td3" IBMtape "scsiclass,01.ibm.pult3580-hh3" IBMtape "scsiclass,01.ibm.pultrium-hh3" IBMtape "scsiclass,01.ibm.pult3580-td4" Chapter 6. Solaris Tape and Medium Changer Deice Drier 135

154 Solaris Deice Drier (IBMtape) IBMtape "scsiclass,01.ibm.pultrium-td4" IBMtape "scsiclass,01.ibm.p03592j1a" IBMtape "scsiclass,01.ibm.p03592e05" IBMtape "scsiclass,01.ibm.p03592e06" For the medium changers: IBMtape "scsiclass,08.ibm.p03584l32" IBMtape "scsiclass,08.ibm.p03584l22" IBMtape "scsiclass,08.ibm.pult3582-tl" IBMtape "scsiclass,08.ibm.pult3583-tl" IBMtape "scsiclass,08.ibm.pult3581-ta" IBMtape "scsiclass,08.ibm.pult3581-ta2" IBMtape "scsiclass,08.ibm.p3576-mtl" IBMtape "scsiclass,08.ibm.p3573-tl" IBMtape "scsiclass,08.ibm.p3577-tl" Note: The entry is also added running the # update_dr command on Solaris 8 (patch is required), Solaris 9, and later ersions of the operating system. For example: # update_dr -a -i "scsiclass,01.ibm.pult3580-td2" IBMtape 6. Reboot the system by running # reboot -- -r. 7. Run # /opt/ibmtape/tapelist -l to display the configured tape deice information. Solaris Zones Support The Solaris Zones partitioning technology on Solaris 10 is used to irtualize operating system serices and proide an isolated and secure enironment for running applications. Eery Solaris system contains a global zone with ID 0, where the IBMtape drier is installed. Zones hosted by a global zone are known as non-global zones, which hae their own node name, irtual network interface, and storage assignment. The IBMtape drier supports the Solaris Zones enironment. To install IBMtape on the system with the irtualized zones, run the pkgadd system command from the global zone: #pkgadd -G -d IBMtape.x.x.x.x The IBMtape install script installs the drier in the global zone and installs some of IBMtape utilities running a non-root user in all zones. Since the tape deices in non-global zones are configured from the global zone, a script program called ztapelist was deeloped to help the user display the IBM tape deices and to dynamically assign or remoe IBM tape deices in non-global zones without the non-global zone reboot requirement. The utility (aailable in IBMtape or later) is installed on Solaris 10 and runs in the global zone only. Use the ztapelist utility on the command line as follows: Synopsis /opt/ibmtape/ztapelist [-l] [-c] [-z zonename] [-a] [-d] [-h] Options and Usage ztapelist recognizes the following options: -l Displays IBM tape deice information with the column headers for all zones 136 IBM Tape Deice Driers Installation and User s Guide

155 Solaris Deice Drier (IBMtape) -c Displays IBM tape deice information without the column headers for all zones -z zonename Shows IBM tape deices in a zone -a Dynamically adds IBM tape deices to each non-global zone without additional arguments zonename inst#_1 inst#_2 inst#_3... Dynamically sets IBM tape deices not greater than 7 in a non-global zone zonename all Dynamically sets all IBM tape deices on the system in a non-global zone -d Remoes the IBM tape deice from a non-global zone -h Displays help information The ztapelist command displays all of the IBM tape deices in the global zone and the tape deices in the non-global zones as shown in the following example. An option of ztapelist -z zonename is also proided to show all of the assigned tape deices in a particular zone. # /opt/ibmtape/ztapelist -l Running in global zone... Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/27st 03592E05(e/e) /0 1A F F /de/rmt/28smc 03584L T003904E5 2/1 805r N/A N/A 200 /de/rmt/29st ULT3580-TD4(e) /0 82F F F /de/rmt/30smc 03584L T /1 805r N/A N/A 206 /de/rmt/31st ULT3580-TD /0 73P F F /de/rmt/32smc 03584L T /1 805r N/A N/A Running in non-global zone camshaft... Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/29st ULT3580-TD4(e) /0 82F F F /de/rmt/30smc 03584L T /1 805r N/A N/A Running in non-global zone softail... Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/27st 03592E05(e/e) /0 1A F F /de/rmt/28smc 03584L T003904E5 2/1 805r N/A N/A To add the tape deices in non-global zones, run # /opt/ibmtape/ztapelist -a, as shown in the following example: Chapter 6. Solaris Tape and Medium Changer Deice Drier 137

156 Solaris Deice Drier (IBMtape) # ztapelist -a Issuing this function will assign the tape deices in non-global zone Do you wish to continue? [y/n]: y Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/27st 03592E05(e/e) /0 1A F F /de/rmt/28smc 03584L T003904E5 2/1 805r N/A N/A 200 /de/rmt/29st ULT3580-TD4(e) /0 82F F F /de/rmt/30smc 03584L T /1 805r N/A N/A 206 /de/rmt/31st ULT3580-TD /0 73P F F /de/rmt/32smc 03584L T /1 805r N/A N/A Enter Instance Number (Inst #) of a deice to be added: 200 ID NAME STATUS PATH 0 global running / 1 camshaft running /zones/zone1 2 softail running /zones/zone2 Enter the zonename where the deice will be added: camshaft Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/29st ULT3580-TD4(e) /0 82F F F009 Do you wish to continue to add the deices? [y/n]: y Enter Instance Number (Inst #) of a deice to be added: 193 Enter the zonename where the deice will be added: softail Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/27st 03592E05(e/e) /0 1A F F016 Do you wish to continue to add the deices? [y/n]: n # The ztapelist command also allows the user to remoe all or some assigned tape deices from the non-global zone, as shown in the following example: 138 IBM Tape Deice Driers Installation and User s Guide

157 Solaris Deice Drier (IBMtape) # /opt/ibmtape/ztapelist -d Issuing this function will remoe the tape deices from non-global zone Do you wish to continue? [y/n]: y Do you want to remoe the tape deices from all of non-global zones? [y/n]: n ID NAME STATUS PATH 0 global running / 1 camshaft running /zones/zone1 2 softail running /zones/zone2 Enter the zonename where the deices will be remoed: camshaft Do you want to remoe all of the tape deices from this zone? [y/n]: n Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/29st ULT3580-TD4(e) /0 82F F F /de/rmt/30smc 03584L T /1 805r N/A N/A Enter Instance Number (Inst #) of a deice to be remoed: 201 Remoing this tape deice /de/rmt/30smc for this zone camshaft... Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN /de/rmt/29st ULT3580-TD4(e) /0 82F F F009 Do you wish to continue to remoe the deices from this zone? [y/n]: n Do you wish to continue to remoe the deices from other zone? [y/n]: y ID NAME STATUS PATH 0 global running / 1 camshaft running /zones/zone1 2 softail running /zones/zone2 Enter the zonename where the deices will be remoed: softail Do you want to remoe all of the tape deices from this zone? [y/n]: y Remoing all of tape deices for this zone softail... Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN Do you wish to continue to remoe the deices from other zone? [y/n]: n Configuration Parameters When using deices controlled by IBMtape, certain deice characteristics, such as the default block size, can be controlled through the deice drier configuration file. The IBMtape configuration file is named IBMtape.conf. The working copy of this file is located in the /usr/kernel/dr directory. During installation of IBMtape, the working copy of IBMtape.conf is presered, if it exists. During remoal of IBMtape, the working copy of IBMtape.conf is not deleted. These conentions allow configuration settings to remain across updates of IBMtape. A reference copy of IBMtape.conf with factory default settings is always installed in the /opt/ibmtape directory. Note: IBM requires that the Solaris natie SCSI tape deice drier st be configured so that it does not attempt to support SCSI targets that are controlled by IBMtape. Refer to Preenting Conflicts with Other Deice Driers on page 125 for more information about multiple drier access to a deice. Attention: Failure to preent more than one deice drier from operating the same tape drie may cause system panics or data loss on the tape drie. Configuration settings are applied only at start time, or when IBMtape is unloaded manually from, then reloaded into, memory. If you change configuration settings in IBMtape.conf, you can make the changes effectie by restarting the system. As an alternatie to restarting, ensure that no IBMtape-owned deices are in use, then issue the following: Chapter 6. Solaris Tape and Medium Changer Deice Drier 139

158 Solaris Deice Drier (IBMtape) % /opt/ibmtape/tmd -s for IBMtape and later % /usr/sbin/rem_dr IBMtape % /usr/sbin/add_dr -m * 0666 bin bin IBMtape % /opt/ibmtape/tmd for IBMtape and later Default settings in IBMtape.conf can be oerridden for a particular deice (and only while the deice is kept open) using the ioctl application programming interface (API) of the deice drier. The parameter settings made through the API reert back to the default alues in IBMtape.conf the next time the deice is opened. Refer to the IBM TotalStorage and System Storage Tape Deice Driers: Programming Reference for more information about changing configuration parameters under program control. IBMtape.conf contains one stanza for each SCSI target address/lun pair owned by IBMtape. The reference IBMtape.conf file supplied with the package contains a stanza for eery possible SCSI target and LUN combination supported by IBM tape systems. The following example shows the stanza for target 0, LUN 0, with IBMtape's default configuration parameter alues. The parameter immediate is disabled, which means that SCSI commands Write FM, Locate, Load-Unload, Erase, and Rewind complete before returning status: name="ibmtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0; The following example shows the stanza for target 0, LUN 0, with IBMtape's default configuration parameter alues and the rewind immediate mode set on, which causes the SCSI rewind command to return control to the application program before the command actually completes on the tape drie: name="ibmtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 rew_immediate=1 trailer=0 sili=0; If immediate is set to 1 and rew_immediate is set to 0, the setting of rew_immediate is ignored. The name ariable identifies IBMtape as the deice drier, and class identifies the type of deice supported as SCSI. The target and the lun ariables determine the target address and LUN of IBM deices that are controlled by that stanza. On systems with multiple SCSI adapters, a single target/lun stanza controls the configuration settings for all deices addressed with that target address and LUN. Thus, two or more supported IBM deices on the system that hae the same target and LUN settings but are attached to different SCSI buses are all affected by the configuration parameters of the single stanza haing that target address and LUN. After installation of the IBMtape package is complete, you may eliminate unnecessary probing for deices by commenting out unused target/lun pairs. In 140 IBM Tape Deice Driers Installation and User s Guide

159 Solaris Deice Drier (IBMtape) this example, the stanzas for target 0, LUN 0 and target 0, LUN 1 hae been commented out. Those address/lun combinations are not probed, which saes time during a restart or manual reload of IBMtape. Howeer, if an IBM deice is addressed at target 0, LUN 0 or target 0, LUN 1, it is not detected. #name="ibmtape" class="scsi" #target=0 lun=0 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0; #name="ibmtape" #target=0 lun=1 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0; class="scsi" The remaining fie configuration parameters specifically affect the behaior of the IBM deice or deices associated with that stanza (target and LUN). All of these parameters are specific to tape drie deice operation only and hae no effect on medium changer deice behaior. The default configuration parameters are adequate for most purposes. Howeer, the alues in the configuration file can be modified to suit the specific requirements of the application or the user. Remember that modifying a alue in the configuration file determines the alue of the parameter at deice open time. When the deice is open, the alue of a parameter can be altered using an ioctl function call, but the change is effectie only while the deice remains open. Working configuration parameters reert back to the default alues (established by the configuration file) when the deice is closed and reopened. Refer to the IBM Tape Deice Driers: Programming Reference for more information about changing configuration parameters through program control. Table 25 lists and describes the set of configuration parameters recognized by the IBMtape deice drier. Table 25. Configuration Parameters Recognized by IBMtape Parameter Values Description block_size (0=ariable length) This option specifies the deice block size that is established with the SCSI Mode Select command during an open function call. Until this alue is changed, it is the working block size. Variable block size is established using a alue of zero. Any other positie alue represents a fixed block size. The maximum supported block size aries for each tape deice. Refer to the appropriate hardware reference manual for additional information. Note: IBMtape does not allow odd-byte-count fixed block reads or writes. For instance, a fixed block size of 4096 or 4098 is allowed, but 4097 is not. If you attempt to read or write using an odd-byte-count fixed block size, the read or write returns -1, with errno set to 22, inalid argument. If you must read or write odd-byte-count blocks, set block size to 0 (ariable block size), then transfer one block s worth of data per read or write. Chapter 6. Solaris Tape and Medium Changer Deice Drier 141

160 Solaris Deice Drier (IBMtape) Table 25. Configuration Parameters Recognized by IBMtape (continued) Parameter Values Description buffering (0=Off, 1=On) When a write command is processed, the data is either directly stored on the physical tape or buffered in deice hardware. Buffering can be turned On and Off with this option. If buffering is disabled, the effectie performance of the deice may be degraded seriously, because the tape deices cannot take adantage of their buffering optimization. Buffer flushing (or committing data to the tape) can be controlled by the application through the STIOC_SYNC_BUFFER ioctl function immediate (0=Off, 1=On) If immediate is set to 0, the SCSI commands Write FM, Locate, Load-Unload, Erase, and Rewind return with status when the command actually completes on the tape drie. If immediate is set to 1, these commands return with status before the command actually completes. resere_key (A string of 1-8 character ASCII alphanumeric key such as "key12345". If less than 8 characters are used, the remaining characters will be set to 0x00(NULL). resere_type (1=resere(6), 2=resere(10), 3=persist_resere) The user specifies the Persistent Reseration key that will be used by the deice drier when the Persistent Reseration is used. The resere key is assigned by the drier by default. This parameter specifies the SCSI Reseration type that will be used by the deice drier, either a SCSI Resere(6) command or a SCSI Persistent Resere command. The SCSI Resere(10) command is unsupported recently. The resere type 1 is set by default. Note: This parameter is not used if the Data Path Failoer is supported. rew_immediate (0=Off, 1=On) If rew_immediate is set to 0, the SCSI Rewind command returns with status when the command actually completes on the tape drie. If it is set to set to 1, the Rewind command returns with status before the command actually completes. If immediate is set to 1, the setting of rew_immediate is ignored. trailer (0=Off, 1=On) If a tape drie encounters logical end-of-tape (EOT) during a write operation, it returns a check condition status. The drier returns 0 bytes written to notify the application of this EOT situation. A check condition is also returned by the tape drie for eery subsequent write operation when past EOT. If trailer is enabled, writing records past EOT is allowed by the deice drier. Following the first time the write operation notifies the application of EOT, all subsequent EOT notifications are suppressed by the drier, and the actual number of bytes written is returned. When physical end of media is reached, all write operations fail with a return code of -1, regardless of the trailer setting. When trailer is enabled, managing the media past EOT is the application s responsibility. sili (0=Off, 1=On) Normally, during a read operation, if a larger block of data is requested than is actually read from the tape, the tape deice raises a check condition. The IBMtape deice drier must perform error handling procedures, which add oerhead to the read operation. The IBMtape drier does not surface this as an error condition to the application and ultimately returns the actual number of bytes read. Howeer, this drier error processing results in less than optimum read performance in some scenarios. When SILI mode is enabled, the tape deice is forced to Suppress Illegal Length Indication during read operations. This eliminates the error processing performed by the drier and results in improed read performance for some scenarios. The actual number of bytes read is still returned to the application in SILI mode. 142 IBM Tape Deice Driers Installation and User s Guide

161 Solaris Deice Drier (IBMtape) Remoing IBMtape All actie processes using IBM deices supported by the IBM SCSI Tape and Medium Changer Deice Drier for Solaris must be stopped in order for the remoal procedure to complete successfully. Use the pkgrm command to remoe the IBMtape package from the system. % /usr/sbin/pkgrm IBMtape Adding or Remoing Deices To add support for a new IBM tape system or to remoe support for a preiously attached IBM tape system, perform the following steps: 1. Edit the IBMtape.conf file in the /usr/kernel/dr directory to reflect the change in IBM deice support. Either add a new stanza to proide support for a deice that is to be added, or remoe (comment out) a stanza for a deice that is no longer supported. 2. When adding support for a new deice, ensure that the target and LUN alues in the configuration file stanza match the target and LUN settings of the IBM deice. Refer to Configuration Parameters on page 139 for more information about the IBMtape.conf configuration file. 3. Shut down and power Off the host system. 4. Plug the new deice into the SCSI bus or unplug the existing deice from the bus. Pay particular attention to proper SCSI cabling and termination. 5. Power On and start the host system. Notes: a. It is possible to reinitialize the IBMtape deice drier without restarting the system. This is done by first unloading the deice drier, then reloading the deice drier into kernel memory. b. For the ersion of IBMtape and later, the TMD daemon has to be stopped by running the /opt/ibmtape/tmd -s command to unload the IBMtape drier from the kernel. Running the /opt/ibmtape/tmd command restarts the daemon afterwards to reload the deice drier. The commands to unload the deice drier are: % /opt/ibmtape/tmd -s for IBMtape and later % /usr/sbin/rem_dr IBMtape The commands to reload the deice drier are: % /usr/sbin/add_dr -m * 0666 bin bin IBMtape % /opt/ibmtape/tmd for IBMtape and later When the IBMtape deice drier is reloaded, it reads the IBMtape.conf file and acknowledge changes made in the file. This method can be used to modify configuration parameters. Note: It is strongly suggested that the host system and all deices attached to the SCSI bus be powered Off before adding or remoing deices from the SCSI bus. Hot plugging SCSI deices can cause hardware damage and disruption of reliable system operation. Deconfiguring Tape Deices In some special situations, the user cannot modify IBMtape.conf to deconfigure some tape deices with IBMtape drier, when more than one deice is configured with the same target address, or the tape deices are attached on the FC or SAS HBA running with Sun HBA drier. Chapter 6. Solaris Tape and Medium Changer Deice Drier 143

162 Solaris Deice Drier (IBMtape) In IBMtape and later, a configuration parameter defined exclude_de_list is introduced to allow users to exclude some deices from the configuration with IBMtape. Deconfigure the tape deice using the following: 1. Add the entry of exclude_de_list in IBMtape.conf located in /usr/kernel/dr. exclude_de_list= sn1,sn2,sn3,... ; Where: sn is the serial number of the excluded deice, 10-characters long for LTO drie, 12-characters long for 359x drie and 16-characters long for changer. The serial number can be found running the following command: /opt/ibmtape/tapelist -l 2. Re-install IBMtape drier or reboot the system to allow IBMtape update the configuration. Tapelist Utility Program A Tapelist Utility Program called tapelist is installed in the /opt/ibmtape directory as part of the IBMtape package. The tapelist utility proides the user a listing of tape, medium changer and SAN data gateway deices configured with the IBMtape drier. It also displays the information of HBA with IBM tape drie attachment and the current status of load balancing. The following is an example of a Tapelist Utility Program output. # tapelist Instance : 697 Special File : /de/rmt/6st Deice : 03592E05(e/e) Serial Number : TGT/LUN : 7/0 Ucode : 04C4 World Wide NN : World Wide PN : De Phy Path : /deices/pci@1f,2000/qlgc,qla@1/ibmtape@7,0:st Path Type : N/A # tapelist -t hba_index hba_inst hba_drier reg_count usage_count HBA Path qla /deices/pci@4,2000/fibre-channel@1 1 2 lpfc 4 2 /deices/pci@6,2000/pci@1/fibre-channel@4 2 3 lpfc 1 0 /deices/pci@6,2000/pci@1/fibre-channel@5 A new feature is added in tapelist to display the drie information in the library that is running /opt/ibmtape/tapelist -L. # tapelist -L Addr Inst# Special File Deice Serial No TGT/LUN Ucode World Wide NN World Wide PN Library (/de/rmt/5smc) Info: 2894 /de/rmt/5smc 03584L T003904E5 3/1 806c N/A N/A /de/rmt/13st 03592E05(e/e) /0 1D F F /de/rmt/14st 03592E06(e/e) / F F019 Library (/de/rmt/7smc) Info: 2899 /de/rmt/7smc 03584L T /1 806c N/A N/A /de/rmt/6st ULT3580-TD4(e) /0 82F F F009 Library 3494 Info: 322 /de/rmt/10st 03592J1A / IBM Tape Deice Driers Installation and User s Guide

163 Solaris Deice Drier (IBMtape) The following is a definition of the fields and headers that appear in the preious screens: Inst # The instance number of the particular deice. Special File Deice TGT/LUN Ucode leel World Wide NN World Wide PN De Phy Path Path Type hba_index hba_inst hba_drier reg_count usage_count HBA Path Addr e/e The deice special file used to access this deice. A string indicating the deice model and encryption information (e/e: encryption capable/encryption enable). Serial No: The serial number of the deice. The SCSI target and LUN of the deice. The current microcode (firmware) loaded on the deice. A number indicating Fibre Channel World Wide Node Name of the deice. A number indicating Fibre Channel World Wide Port Name of the deice. A string indicating the deice path in the deice tree. A primary or alternate path used for failoer. The index number of the particular HBA in the HBA list. The instance number of the particular HBA assigned by the Solaris system. The HBA drier name with IBM tape drie attachment. The number of IBM tape dries attached on the HBA. The number of IBM tape dries currently using the HBA. A string indicating the HBA deice path in the deice tree. The element address where the drie is located in the library. The first and second instances of "e" stand for encryption capable and encryption enable. The usage of the tapelist program is as follows: -l Print for all of the configured deices with the column headers in long list -L Display the tape dries information in the tape library -c Don t print column headers in long list for all of the configured deices -t Display HBA information and current load balancing status -f Print the list for a particular file only -A List the tape deices by HBA -a Print out the info of all of FC HBAs -h Help menu Running tapelist without any options displays the deice information line by line for all of the configured deices. Special Files After the IBMtape drier is installed, a set of special files is aailable for performing input/output (I/O) operations to each supported deice. The deice special file names created by the IBMtape deice drier are similar to the SCSI tape special files generally used on Solaris systems. Each tape instance has a set of minor numbers that proides access to the same physical deice, but each minor number proides a different function or behaior for the tape subsystem. These minor numbers are accessed through ariations of the special file name for that deice. The special files are created in the /de/rmt directory. These special files are actually symbolic links to files created within the /deices subdirectory hierarchy. Issuing the ls -la /de/rmt command gies useful information about these deice special files. The following example shows entries returned by this command for a single IBM tape subsystem. This listing is system dependent, so entries ary slightly in format, depending on the operating system and SCSI adapter support. There may also be entries included for other deices that are not supported by the IBMtape deice drier. lrwxrwxrwx root other 79 Aug 26 18:54 0smc -> /deices/iommu@f,e /sbus@f,e /qlgc,isp@3, 10000/IBMtape@2,0:smc lrwxrwxrwx root other 78 Aug 26 18:54 0st -> Chapter 6. Solaris Tape and Medium Changer Deice Drier 145

164 Solaris Deice Drier (IBMtape) lrwxrwxrwx root other 79 Aug 26 18:54 0stb -> lrwxrwxrwx root other 80 Aug 26 18:54 0stbn -> lrwxrwxrwx root other 79 Aug 26 18:54 0stc -> lrwxrwxrwx root other 80 Aug 26 18:54 0stcb -> lrwxrwxrwx root other 81 Aug 26 18:54 0stcbn -> lrwxrwxrwx root other 80 Aug 26 18:54 0stcn -> lrwxrwxrwx root other 79 Aug 26 18:54 0stn -> These entries show the deice hierarchy established to support I/O for an IBM SCSI tape system. The attachment path of the deice special files spans from the system board, through the S-bus, to the Sun F/W SCSI adapter (supported by the QLGC, isp SCSI adapter deice drier), to the IBM deice at SCSI target 2 and LUN 0 (supported by the IBMtape deice drier). All nine of these special files are associated with the same IBM deice (deice number 0). Deice Behaiors Certain deice behaiors are determined by which special file in the set is opened for deice access. The smc special file controls only the medium changer portion of the deice and accepts only medium changer operations by way of the ioctl entry point. The smc special file does not support the read and write entry points. Only one st type special file for a particular deice may be opened at any one time. The smc special file may be opened concurrently with any one of the st special files. The IBMtape deice drier decides which types of special files to create during installation, based on the IBM deice type being configured. For the IBM 3490E Magnetic Tape Subsystem, only the eight st type special files are created. For other IBM tape dries, all nine special files shown preiously are created. For IBM tape libraries and autoloaders, only a single smc special file is created. With the information from the preious command, issuing the ls -la /deices/iommu@f,e /sbus@f,e /qlgc,isp@3,10000 command presents further information about the same special files, as shown in the following example. Again, the actual path information specified in the command aries from system to system. crw-rw-rw- 1 bin bin 109,1696 Aug 26 18:54 IBMtape@2,0:smc crw-rw-rw- 1 bin bin 109,1664 Aug 26 18:56 IBMtape@2,0:st crw-rw-rw- 1 bin bin 109,1728 Aug 26 18:54 IBMtape@2,0:stb crw-rw-rw- 1 bin bin 109,1732 Aug 26 18:54 IBMtape@2,0:stbn crw-rw-rw- 1 bin bin 109,1688 Aug 26 18:54 IBMtape@2,0:stc crw-rw-rw- 1 bin bin 109,1752 Aug 26 18:54 IBMtape@2,0:stcb crw-rw-rw- 1 bin bin 109,1756 Aug 26 18:54 IBMtape@2,0:stcbn crw-rw-rw- 1 bin bin 109,1692 Aug 26 18:54 IBMtape@2,0:stcn crw-rw-rw- 1 bin bin 109,1668 Aug 26 18:54 IBMtape@2,0:stn 146 IBM Tape Deice Driers Installation and User s Guide

165 Solaris Deice Drier (IBMtape) These entries show the major and minor numbers associated with each special file. Here, the major number is 109 and identifies to the system that the IBMtape deice drier is in support of these special files. Major numbers are assigned by the system at the time the drier is installed and ary from system to system. The nine different minor numbers are specific to the special file names and are used by the deice drier to determine which special file was used to access the deice and control the deice behaior accordingly. For example, the minor number 1696 indicates to the drier that the deice was opened by way of the smc special file. For more information on deice special files and major and minor numbers, consult the Solaris mtio man pages. Chapter 6. Solaris Tape and Medium Changer Deice Drier 147

166 Solaris Deice Drier (IBMtape) File Naming Conentions Table 26 shows the special file naming conention and the associated deice attributes recognized by the IBMtape deice drier. Table 26. IBM SCSI Tape/Medium Changer Special Files for Solaris BSD Compatibility (Note Special File Name 1) Rewind on Close (Note 2) Compression (Note 3) /de/rmt/[0 255]smc (Note 4) N/A N/A N/A /de/rmt/[0 255]stn (Note 5) No No No /de/rmt/[0 255]stcn (Note 5) No No Yes /de/rmt/[0 255]st (Note 5) No Yes No /de/rmt/[0 255]stc (Note 5) No Yes Yes /de/rmt/[0 255]stbn (Note 5) Yes No No /de/rmt/[0 255]stcbn (Note 5) Yes No Yes /de/rmt/[0 255]stb (Note 5) Yes Yes No /de/rmt/[0 255]stcb (Note 5) Yes Yes Yes Notes: 1. The BSD (b) deice special file modifies close behaior for non-rewind deices. If the deice is opened for no rewind on close in non-bsd mode, and if the last command before closing the deice was a read, then the tape is positioned after the filemark immediately following the last block read. If the deice is opened for no rewind on close in BSD mode, and if the last command before closing the deice was a read, the tape is left positioned exactly where it was following the last block read. If the deice is opened for rewind on close the BSD mode is not releant. 2. The no rewind on close (n) deice special file does not rewind the tape during a close operation. Otherwise, the tape is rewound when the deice is closed. If the last operation before closing the deice was a write or write filemark, then a sufficient number of filemarks is written so that two filemarks follow the data. For the non-rewind special files, the tapes are positioned between the trailing filemarks before closing. If the deice is then reopened and more data is written, it is separated by a single filemark from the preious data. 3. The compression (c) deice special file determines whether the tape deice uses built-in hardware compression while storing data on the tape. The compression mode of the deice can also be set to the desired state programmatically through the STIOC_SET_PARM ioctl, regardless of the default compression mode established by the special file originally used to open the deice. 4. The smc special file is created only for IBM tape systems that proide medium changer capability. For IBM tape libraries and autoloaders, the smc special file is the only file created because the IBMtape deice drier supports only the medium changer portion and does not support the tape drie portion of these deices. For the IBM 3490E Magnetic Tape System, there is no smc special file created. 5. Only one st special file may be opened at one time. The smc special file may be opened by itself or in conjunction with one of the st type files. The smc special file accepts only medium changer commands. Tape drie commands issued to the medium changer fail, with errno set to 22, inalid argument. Aside from the normal configuration with the medium changer answering as a distinct target/lun pair, some supported deices can be configured with a nonstandard integrated medium changer reporting at the same target and LUN as the tape drie. In such a case, both st and smc special files accept a limited subset of medium changer commands. If you want to use this nonstandard mode, consult the appropriate hardware reference to determine whether the drie supports such a configuration. 148 IBM Tape Deice Driers Installation and User s Guide

167 Solaris Deice Drier (IBMtape) Persistent Naming Support The deice special file names are created by the IBMtape drier in the order that the tape deices are presented by the Solaris system. Each deice special file name is maintained with the same logical name across reboots, een when an existing deice is powered off or not connected. Howeer, the logical names of deices may be changed due to the swapping of connecting cables, HBA mapping changes, tape deice drier updates, or other reasons. The user can rename the logical name by editing the /etc/delink.tab system file for the persistent name binding and reloading the IBMtape drier as follows: 1. Before the persistent name binding, make sure that the IBM tape deices are configured at the different target and LUN addresses if the deices are attached on more than one HBA. The Ultrium-3 tape drie is connected to two Emulex HBAs with the same address of target 3 and LUN 0 ia a switch in the following example. You hae to use the HBA utility, follow HBA endor instructions, or both to persistently bind the tape deices at the different mapped target and LUN. # tapelist -l Inst# Special File Deice Serial No TGT/LUN Deice Physical Path /de/rmt/2st ULT3580-TD /0 /deices/pci@6,2000/pci@1/fibre-channel@5/ibmtape@3,0 582 /de/rmt/8st ULT3580-TD /0 /deices/pci@1f,2000/pci@1/fibre-channel@5/ibmtape@3,0 The tape drie is mapped at target 3, LUN 0 on HBA 1 and target 24, LUN 0 on HBA 2 after deice persistent binding. # tapelist -l Inst# Special File Deice Serial No TGT/LUN Deice Physical Path /de/rmt/4st ULT3580-TD /0 /deices/pci@6,2000/pci@1/fibre-channel@5/ibmtape@3, /de/rmt/7st ULT3580-TD /0 /deices/pci@1f,2000/pci@1/fibre-channel@5/ibmtape@18,0 Note: Deice persistent binding is not proided on Sun HBAs, so this persistent name approach cannot be used with the same physical drie that is attached to multiple Sun HBA ports. 2. Start persistent name binding. In this example, the user renames 4st and 7st to 10st and 11st. a. Create the entry for persistent naming. Determine the target address from the Deice Physical Path in the output of tapelist -l and add the planned deice special file name in the entry. Here, 4st and 7st dries are located at 3,0 (target 3, LUN 0) and 18,0 (target 24 (0x18), LUN 0) at the deice physical paths of /deices/pci@6,2000/pci@1/fibre-channel@5/ibmtape@3,0 and /deices/pci@1f,2000/pci@1/fibre-channel@5/ibmtape@18,0. Add the address and deice file name into the entries: type=ddi_byte:tape;addr=3,0; rmt/10\m0 type=ddi_byte:tape;addr=18,0; rmt/11\m0 Notes: 1) A tab is entered between addr=3,0; and rmt/10\m0. 2) The 0 in the entry is the zero in M0. Chapter 6. Solaris Tape and Medium Changer Deice Drier 149

168 Solaris Deice Drier (IBMtape) 3) To aoid conflicts with the current deice special files assigned by the system automatically, be sure to assign a higher number for the persistent name. 4) The address is w f007,0 for the tape drie on the Sun HBA with the path of /deices/pci@1,0/pci1022,7450@1/pci1077,141@1/ fp@0,0/tape@w f007,0. b. Add the aboe entry into the /etc/delink.tab system file. c. Remoe existing links created by the IBMtape drier from /de/rmt by running the #rmcommand. d. Run the # defsadm command without any options to enable IBMtape to create the new deice special file name as defined in the entries in /etc/delink.tab. A system reboot is also required if the tape deice is attached on Sun HBA. e. Run tapelist to list the deice special files. # tapelist -l Inst# Special File Deice Serial No TGT/LUN Deice Physical Path /de/rmt/10st ULT3580-TD /0 /deices/pci@6,2000/pci@1/fibre-channel@5/ibmtape@3, /de/rmt/11st ULT3580-TD /0 /deices/pci@1f,2000/pci@1/fibre-channel@5/ibmtape@18,0 Control Path Failoer Support for Libraries Configuring and Deconfiguring Path Failoer Support Control path failoer (CPF) support is enabled automatically by default when the IBMtape deice drier is installed on Solaris system. The Solaris IBMtape deice drier proides a drier configuration parameter failoer for you to enable or disable the library control path failoer support. To enable the CPF support for all of the paths, no any action is required. To disable the CPF support for all of the paths or a particular path, use the following steps: 1. To disable CPF support for all the paths, add and set the failoer parameter to off at the beginning of IBMtape.conf file in the directory of /usr/kernel/dr. 2. To disable a particular path, add and set the failoer parameter to off in the path entry in IBMtape.conf file. For example, name="ibmtape" class="scsi" target=3 lun=1 failoer=0; 3. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel: # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 4. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd Primary and Alternate Paths When the deice drier configures a logical deice with path failoer support enabled, the first deice configured always becomes the primary path. When a second or more logical deice is configured with path failoer support enabled for the same physical deice, it configures as an alternate path. The deice drier supports up to 16 physical paths for single a deice. The primary and alternate path information can be obtained in the field of "Path Type" running the /opt/ibmtape/tapelist command output and is similar to the 150 IBM Tape Deice Driers Installation and User s Guide

169 Solaris Deice Drier (IBMtape) example in Figure 13. #tapelist -1 Inst# Special File Deice Serial No TGT/LUN Ucode WWNN WWPN Deice Physical Path Path Type /de/rmt/12smc 03584L T0039 1/1 402j N/A N/A Primary 688 /de/rmt/14smc 03584L T0039 2/1 402j N/A N/A Alt_path_1 694 /de/rmt/26smc 03584L T0039 5/1 402j N/A N/A Alt_path_2 Figure 13. Example of Control Path Failoer Support Command Output The labeling of a logical deice as either a primary or alternate path is for information only; it is used to: 1. Identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled the primary path for each physical deice. Howeer, there can be multiple logical deices labeled as an alternate path for the same deices. 2. Proide information about which logical deices configured on the system hae path failoer enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices with the tapelist utility. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Disable and Enable Primary and Alternate Paths Once you install the IBMtape deice drier, by default, all the aailable paths for a physical deice are enabled. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Data Path Failoer and Load Balancing Support for Tape Dries Note: The tape drie failoer feature code must be installed prior to enabling the DPF for IBM Ultrium tape drie in the Solaris IBMtape deice drier. Refer to Automatic Failoer on page 10 to determine which feature code is required for your machine type. Configuring and Deconfiguring Path Failoer Support Path failoer support for tape dries is enabled automatically when the deice drier with the ersion of IBMtape or later is installed, and is disabled by default at the preious ersion. When path failoer support is enabled for a logical deice, it remains set until the deice is deleted or the support is deconfigured. The path failoer setting is retained een if the system is rebooted. Path failoer Chapter 6. Solaris Tape and Medium Changer Deice Drier 151

170 Solaris Deice Drier (IBMtape) support can be enabled on all configured deices at one time, or it can be enabled or disabled selectiely by logical deice. It may be desirable at times to configure some, but not all, logical paths to a deice with the support enabled. Follow the aboe steps to enable the DPF support: 1. To enable the support globally on all currently configured deices, add an entry of dpf_support=1 at the beginning of the IBMtape.conf file, such as dpf_support=1; 2. Or, to enable a particular path, add the parameter dpf_support and turn it on in the path entry in the IBMtape.conf file. For example, name="ibmtape" class="scsi" target=3 lun=0 dpf_support=1; 3. For the IBM Ultrium tape drie, you need to enter the DPF feature key(s) in the parameter dpf_keys at the beginning of the IBMtape.conf file in the directory /usr/kernel/dr. For example: dpf_keys="a729e60f7b119411, C7A0B9ef2c1a4360, a729e60f7b118460"; Notes: a. The parameter dpf_keys is in the format key1, key2, key3,.... Each key is 16 characters long with a comma "," and a space " ". The IBMtape drier supports up to 36 dpf keys. b. DPF keys do not need to be added in IBMtape.conf if you are running the latest drie code on Ultrium-3 and Ultrium-4 dries. 4. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 5. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd This deconfigures all deices to add the parameter dpf_support=0 in the IBMtape.conf file, and reboot the system or deconfigure and reconfigure all deices. For example, 1. To disable the support globally on all currently configured deices, add the entry dpf_support=1 at the beginning of the IBMtape.conf file. # dpf_support=0; 2. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel: # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 3. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd To disable the support on a single logical deice, following these steps: 1. To enable the support globally on all currently configured deices, add an entry dpf_support=1 at the beginning of the IBMtape.conf file, such as dpf_support=1; 2. To disable a particular path, add the parameter dpf_support and turn it off in the path entry in the IBMtape.conf file. For example, name="ibmtape" class="scsi" target=3 lun=0 dpf_support=0; 3. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel: 152 IBM Tape Deice Driers Installation and User s Guide

171 Solaris Deice Drier (IBMtape) # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 4. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd Primary and Alternate Paths When the deice drier configures a logical deice with path failoer support enabled, the first deice configured always becomes the primary path. When a second logical deice is configured with path failoer support enabled for the same physical deice, it configures as an alternate path. A third logical deice is configured as the next alternate path, and so on. The deice drier supports up to 16 physical paths for a single deice. For example, if 0st (port 0 of 3592) is configured first, then 5st (port 1), 18st (port 1) and 21st (port 0) to the two HBAs through a switch (here, WWPN from port 0 and from port 1), the /opt/ibmtape/tapelist command output is similar to the example in Figure 14. #tapelist -1 Inst# Special File Deice Serial No TGT/LUN Ucode WWNN WWPN Deice Physical Path Path Type /de/rmt/0st 03592J1A /0 04CE /deices/pci@1f,2000/qlgc,qla@1/ibmtape@1,0 Primary 697 /de/rmt/5st 03592J1A /0 04CE /deices/pci@1f,2000/qlgc,qla@1/ibmtape@7,0 Alt_path_1 666 /de/rmt/18st 03592J1A /0 04CE /deices/pci@1f,4000/jni,fcr@2/ibmtape@1,0 Alt_path_2 670 /de/rmt/21st 03592J1A /0 04CE /deices/pci@1f,4000/jni,fcr@2/ibmtape@3,0 Alt_path_3 Figure 14. Example of Data Path Failoer Support Command Output The labeling of a logical deice as either a primary or alternate path is for information only, in order to: 1. Be able to identify the actual number of physical deices configured on the system and a specific logical deice associated with them. There is only one logical deice labeled the primary path for each physical deice. Howeer, there may be many (multiple) logical deices labeled as an alternate path for the same deices. 2. Proide information about which logical deices configured on the system hae path failoer support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all deices with the tapelist utility. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page 231. Chapter 6. Solaris Tape and Medium Changer Deice Drier 153

172 Solaris Deice Drier (IBMtape) Disable and Enable Primary and Alternate Paths Once you enter the parameter dpf_support in the IBMtape.conf file and install the IBMtape deice drier, all the aailable paths for a physical deice are enabled. 1. Add the parameter of dpf_support and turn it off in the path entry in IBMtape.conf file. For example: name="ibmtape" class="scsi" target=3 lun=0 dpf_support=0 2. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel: # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 3. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd To enable a path from a disabled state, you may run the following steps: 1. Add the parameter of dpf_support and turn it off in the path entry in IBMtape.conf file. For example: name="ibmtape" class="scsi" target=3 lun=0; 2. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape drier module from the current kernel: # /opt/ibmtape/tmd -s # /usr/sbin/rem_dr IBMtape 3. Reload the IBMtape drier module in the kernel and start the daemon: # /usr/sbin/add_dr -m 0666 bin bin IBMtape # /opt/ibmtape/tmd System-Managed Encryption Deice Drier Configuration System-Managed Encryption can be set on global or a specific tape drie in IBMtape.conf in /usr/kernel/dr. There are 2 new configuration parameters added for encryption: sys_encryption_proxy ON/OFF Use System Encryption FCP Proxy Manager sys_encryption_write OFF/ON/CUSTOM System Encryption for Write Commands at BOP The sys_encryption_proxy parameter enables deice drier system-managed encryption for a tape drie by setting the alue to ON (default set). The sys_encryption_write parameter controls if the deice drier can set the tape drie to encryption enabled for write commands. When set to OFF, the tape drie uses encryption for read operations; write operations do not use encryption. When set to ON, the tape drie uses encryption for both read/write operations. When set to CUSTOM, the deice drier does not modify current tape drie setting. The custom setting is intended for applications using system-managed encryption to control write encryption without deice drier interention. The parameter is set to CUSTOM by default. Note: If sys_encryption_write is set to ON, an application can not open a tape drie using the append mode. To make a global setting to enable SME in IBMtape.conf: sys_encryption_write=1; # System Encryption for Write Commands at BOP 154 IBM Tape Deice Driers Installation and User s Guide

173 Solaris System-Managed Encryption To enable SME for a particular target: name="ibmtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0 sys_encryption_write=1; To disable SME in a particular target: name="ibmtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0 sys_encryption_proxy=0; Querying Tape Drie Configuration This is a tape diagnostic and utility function, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Testing Data Encryption Configuration and Connectiity There is a data encryption test aailable to alidate the ibmekm.conf file serer entries and test tape drie to serer connectiity operations. This is a tape diagnostic and utility function, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Field Support Information When encryption failures require field support and/or deelopment analysis, run /opt/ibmtape/diags_info script to generate a file of diags.out. Tape drie dumps and EKM serer logs may be needed in addition to this information. Problem Determination The following sections describe the serice and diagnostic aids that are part of the IBM SCSI Tape and Medium Changer Deice Drier for Solaris package. Procedures for erifying correct installation of the deice, basic problem determination guidelines, and outlines of the utility program included with the IBMtape package are included. Chapter 6. Solaris Tape and Medium Changer Deice Drier 155

174 Solaris Deice Drier (IBMtape) Functional Verification If you wish to erify that the installation of the IBM SCSI Tape and Medium Changer Deice Drier for Solaris package was successful, follow these steps: 1. Enter this command to erify installation was successful /usr/bin/pkginfo IBMtape The following information should be displayed: system IBMtape IBM SCSI Tape & Medium Changer Deice Drier x.x.x.x Where: x.x.x.x is the ersion of the deice drier. 2. To erify that deice drier support for a specific IBM tape system attached to the system is functioning correctly, enter the following command: /opt/ibmtape/tapeutil -f /de/rmt/nst -o chk - substituting for n the number associated with the deice special file assigned to the IBM tape system that you want to check. Listing the contents of the /de/rmt directory (using the ls command) can be helpful in determining the proper special file name. For medium changer deices, the special file name /de/rmt/nsmc should be used. The following information should be displayed: IBM xxxxxxxx configured at /de/rmt/nst. Where: xxxxxxxx is the model number of the IBM tape system and n is the same number specified in the erify command. 3. To erify that the IBMtape deice drier is loaded in kernel memory, enter the following command: /usr/sbin/modinfo /usr/bin/grep IBMtape The following information should be displayed: 165 f5f c0s IBMtape (IBM SCSI Tape/Medium Changer DD) The first fie fields shown probably do not match your specific output. The fields indicate the ID, load address, size, major number, and reision for the IBMtape deice drier and ary from machine to machine Sense Data Logging When the tape drie responds with CHECK CONDITION status and associated sense keys of 0x1 (Recoery Error), 0x3 (Medium Error), 0x4 (Hardware Error) and 0xB (Aborted Command) for a hardware or medium error, the sense data is logged into the system log file (typically /ar/adm/messages). Installation Problems If you are experiencing problems with installation of the IBM SCSI Tape and Medium Changer Deice Drier for Solaris package, the following information may be of assistance. If you cannot sole the problems after checking the following, contact the appropriate IBM serice representatie. If you receie the following message during installation: drconfig: System call modctl_modconfig failed: No such deice or address. Warning: Drier (IBMtape) configuration failed. System could not install drier. it indicates that the IBMtape deice drier was not loaded because it did not detect the presence of any supported IBM deices on the SCSI bus. Verify that 156 IBM Tape Deice Driers Installation and User s Guide

175 Solaris Deice Drier (IBMtape) SCSI adapter deice drier support is installed and configured correctly. Verify that the IBM tape subsystem is connected properly to the SCSI bus, powered On, and online. It is not necessary for the tape drie to hae a cartridge loaded to be recognized by the IBMtape deice drier. If you cannot open an IBM deice, erify that you are using the correct special file. The IBM tape special files are of the form *st* in the /de/rmt directory. The IBM medium changer special files are of the form *smc in the /de/rmt directory. Ensure that the Sun natie tape deice drier (st) is not contending for the same IBM deice by consulting the st.conf file in the /kernel/dr directory and commenting out conflicting stanzas. Tape Monitor Daemon (tmd) The Tape Monitor Daemon is introduced in the ersion of IBMtape or later. It is designed to run concurrently with the IBMtape drier and to automatically retriee and store the IBM tape drie diagnostic information (drie dump) into the /ar/opt/ibmtape directory. The daemon is automatically started when the drier is installed, een no any tape deice is attached on the system. An entry " name="ibmtape" parent="pseudo" instance=16383; " is also entered into the configuration file of /usr/kernel/dr/ibmtape.conf automatically for the daemon during the IBMtape drier installation. The following options can be used to configure the tape monitor daemon running it on the command line. Most options can also be specified in the /etc/tmd.conf configuration file. Howeer, the command line options oerride any configuration file options. The following options can be used to configure the tape monitor daemon running it on the command line. Most options can also be specified in the /etc/tmd.conf configuration file. Howeer, the command line options oerride any configuration file options: -s Stop any currently running instance of the tape monitor daemon. -r Restart the tape monitor daemon and reload all configuration settings. -d Turn on drie error diagnostic retrieal and storage. This option is enabled by default. -D Turn off drie error diagnostic retrieal and storage. -p <directory> Specify an alternate directory for the storage of drie diagnostic information. Default directory is /ar/opt/ibmtape -l <filename> Specify a file for writing daemon related log messages. By default, the tmd only writes status information to the syslog file of /ar/adm/messages. -y Turns off writing log messages to syslog. -z Turn off compression. By default, the tmd will use a form of file compression to reduce the size of stored diagnostic information. The file name of dump presents some useful information. An example of the dump file is: IBMtape :54:14.dump.gz Here, represents the serial number of the tape deice, :54:14 is the time stamp for the dump retrieal. A message is also logged in the syslog file of /ar/adm/messages after a drie dump is retrieed by tmd. For example, Apr 9 14:54:21 Jaa tmd[3279]: Drie dump saed to /ar/opt/ibmtape IBMtape :54:14.dump. Chapter 6. Solaris Tape and Medium Changer Deice Drier 157

176 Solaris Deice Drier (IBMtape) Tracing Facility IBMtape incorporates a tracing facility that is useful for performing problem determination. The tracing facility logs diagnostic information to /ar/adm/messages based on the control ariable IBM_trace. Refer to Setting the IBM_trace Leel for Static Tracing on page 160 for instructions on how to set the trace alue. IBM_trace alues range from 0 13 and result in posted messages as shown in Table 27. Postings are cumulatie, so trace leel 3 also posts items for leels 2, 1, and 0. A trace alue of 2 or 3 is suitable for most normal production enironments, with little or no degradation of throughput. IBM_trace alues of 4 and higher increasingly degrade performance and should generally be used only when directed by IBM support personnel. Table 27. Tracing Facility Trace Leel Items Traced 0 Seere error conditions only. For installations with extremely small /ar file systems, this setting can preent filling the file system unexpectedly. Howeer, this may be at the cost of not recording messages related to serious deice or system enironment errors. 1 Deice sense data. Sense data can help in diagnosing the source of unexpected error conditions. 3 Deice opens and closes. Decoded SCSI command, sense key, ASC and ASCQ for sense data Increasingly erbose tracing information. These tracing leels are generally useful only to IBMtape deelopers. Note: IBMtape earlier than Version had only IBM_trace alues 0 4. Message content and selection differed significantly from current IBMtape ersions. By default, system error messages, including IBMtape trace messages, are placed in /ar/adm/messages. If your installation has modified /etc/syslog.conf to redirect system error messages, IBMtape tracing is handled as other kernel messages. Refer to the syslog.conf man page and the comments in syslog.conf for information about the system logging operation. Changes made to syslog.conf take effect after the next system restart. The following shows trace leel 2 output, with system date and time stamps remoed. Deice instance 390 is opened on the first line. The deice minor number is decoded and shows that the SCSI medium changer (smc) special file was opened. The second line decodes selected fields from the sense data that follows it. The decoded information shows that sense data was generated during a Moe Medium command. Looking up the decoded Sense Key /ASC/ASCQ combination in the 3590 hardware reference, we find that the command failed because the moe from location was empty. The actual sense data follows the decoded fields. Note: Solaris, rather than printing multiple sixteen byte lines of hexidecimal zeroes, prints only the first such line, followed by a repeat count. IBMtape(390) _open: 374 Inst 390, Minor (smc), Flags 0x5, TL 2/0/0, IBMtape(390) check_sense: cmd 0xa5(moe_medium), key/asc/ascq 0x5/3b/e, defer 0, retry 0, rc 22 IBMtape(390) 03590B11 SENSE DATA: IBMtape(390) b e ff IBM Tape Deice Driers Installation and User s Guide

177 Solaris Deice Drier (IBMtape) IBMtape(390) a a5 0 IBMtape(390) last message repeated 1 time IBMtape(390) IBMtape(390) IBMtape(390) _close: Inst 390, Minor (smc), Flags 0x5, exit(0) In the next example, the deice open line shows that a tape drie (dr) deice special file was opened. The sense data for deice instance 292 was generated during a space operation. The Sense Key/ASC/ASCQ shows that a filemark was encountered during the space. IBMtape(292) _open: 554 Inst 292, Minor 9412 (dr), Flags 0x5, TL 2/0/0, IBMtape(292) check_sense: cmd 0x11(space), key/asc/ascq 0x0/0/1, defer 0, retry 0, rc 5 IBMtape(292) 03570B02 SENSE DATA: IBMtape(292) f ff a IBMtape(292) c4 b IBMtape(292) IBMtape(292) 6f 28 0 ad IBMtape(292) IBMtape(292) _close: Inst 292, Minor 9412 (dr), Flags 0x5, exit(0) Finally, the sense data for deice instance 230, a tape drie, occurred during a test unit ready and indicates that no tape is loaded in the drie. IBMtape(230) _open: 728 Inst 230, Minor 7366 (dr), Flags 0x5, TL 2/0/0, IBMtape(230) check_sense: cmd 0x0(test_unit_ready), key/asc/ascq 0x2/3a/0, defer 0, retry 0, rc 5 IBMtape(230) 03570B02 SENSE DATA: IBMtape(230) a 0 ff 2 IBMtape(230) c IBMtape(230) last message repeated 1 time IBMtape(230) IBMtape(230) _close: Inst 230, Minor 7366 (dr), Flags 0x5, exit(0) You can match an instance number with its corresponding deice special file in two steps. 1. Find the instance number in /etc/path_to_inst: $ grep 292 /etc/path_to_inst "/pci@6,4000/scsi@2,1/ibmtape@2,0" 292 "IBMtape" 2. List long the contents of /de/rmt and search for the path name you found in the preious step: $ ls -l /de/rmt grep "/pci@6,4000/scsi@2,1/ibmtape@2,0" lrwxrwxrwx 1 root other 48 Aug 26 11:49 8st ->../../deices/pci@6,4000/scsi@2,1/ibmtape@2,0:st lrwxrwxrwx 1 root other 49 Aug 26 11:49 8stb ->../../deices/pci@6,4000/scsi@2,1/ibmtape@2,0:stb In this example, /de/rmt/8st, /de/rmt/8stb, and so on, are symbolic links to the deice special files that are associated with deice instance 292. Dynamic Tracing Utility A dynamic tracing utility named tapedtrc is introduced in the IBMtape or later drier to dynamically set, reset, start, stop and query IBMtape tracing at any time for debugging use. The program is located in the /opt/ibmtape directory, with the tracing leel set to 0 by default. Chapter 6. Solaris Tape and Medium Changer Deice Drier 159

178 Solaris Deice Drier (IBMtape) Use the tapedtrc program from the command line as follows: /opt/ibmtape/tapedtrc options: [set] [set] leel [get] [start] [stop] [clean] [help] [option] - Set IBMtape trace leel and/or start the tracing - Set trace to a particular trace leel - Query the current IBMtape trace leel - Start IBMtape tracing - Stop IBMtape tracing without the trace leel reset - Stop the IBMtape tracing and reset IBMtape trace leel to 0 - IBM tapedtrc help menu Setting the IBM_trace Leel for Static Tracing The user can still enable or disable static IBMtape tracing and set the IBM trace leel in /etc/system or by running the adb system command. The host is required to reboot to enable or disable the tracing when the trace leel is set in /etc/system. The IBMtape drier must be loaded in the kernel. If the tracing is enabled or disabled using the adb command, the tracing starts or stops at the next deice open. The default alue for IBM_trace is zero (0). You can define another IBM_trace alue by placing an entry in /etc/system, so that IBM_trace is set at each restart. For example, this entry in /etc/system sets IBM_trace to 2 at each restart: set IBMtape:IBM_trace = 2 When IBM_trace is set in /etc/system, it affects tracing during drier loading, initialization, and operation. You may also set or modify the IBM_trace alue manually in an adb session. Because the drier must already be loaded and initialized before using this method, the trace alue that is set is actie only during drier operation. In this sample session, ksh> is a shell prompt, and adb> is the adb session prompt. Commands that you enter are in boldface. Explanatory comments follow pound signs (#) or exclamation and pound sign pairs (!#). Text lines without a prefix are adb session responses to commands. # # Start adb session and set session prompt. ksh> adb -P "adb> " -k -w /de/ksyms /de/mem physmem 7c5e!#!# Set default for input alues to base 10. adb> a$d radix=10 base ten!#!# Display current IBM_tape alue as unsigned decimal integer. adb> IBM_trace/u IBM_trace: IBM_trace: 0!#!# Set new IBM_trace alue.!# adb will confirm the old and new alues. adb> IBM_trace/w 2 IBM_trace: 0 = 2!#!# Quit session. adb> $q # # Back to the shell. ksh> 160 IBM Tape Deice Driers Installation and User s Guide

179 Solaris Deice Drier (IBMtape) Running Diags_info Script Run the diags_info script located in the /opt/ibmtape directory. This script detects the problems on the configuration files, gathers important system HBAs and configuration information. The script should be run as root. If not run as root, the information should be labeled as such, but the alue of the information is degraded when run as a non-root user. To facilitate capture of data, the script places information in a file called diags.out in the directory locating the script. Send the output file to the location identified by your IBM serice representatie. iostat Command IBMtape drier supports the iostat system command, which reports I/O statistics for the supported tape dries in IBMtape and later ersions. Refer to man (1M) iostat for the command usage. Reseration Conflict Logging When the deice drier receies a reseration conflict during open or after the deice has been opened it will log a reseration conflict in the Solaris system log of /ar/adm/messages. Prior to logging the error the deice drier will issue a Persistent Resere In command to determine if a SCSI Persistent Reseration is actie on the resering host to get the resering host initiator WWPN (World Wide Port Name) and resere key. If successful, the deice drier will log this information in the detail data below. After initially logging the resering host WWPN, subsequent reseration conflicts from the same resering host WWPN and reseration key will not be logged to preent multiple entries in the system log until either the resering host WWPN or reseration key is different than the one initially logged or the deice drier has resered the deice and then another reseration conflict occurs. Here are the log examples: 1. The information is logged when the drie is resered with a Persistent Reseration. log_resere: Resering host key 46E48C49413E6EB1 WWPN E08B118BB1 2. The information is logged when the drie is resered with a SCSI-2 Resere. log_resere: Reseration Conflict: read full status failure (rc 16) 3. The information is logged when the drie is resered but the host reseration information isn't aailable. log_resere: Reseration Conflict: No resering host information is aailable. Chapter 6. Solaris Tape and Medium Changer Deice Drier 161

180 Solaris Deice Drier (IBMtape) 162 IBM Tape Deice Driers Installation and User s Guide

181 Chapter 7. Windows Tape and Medium Changer Deice Drier Purpose Data Flow Product Requirements Hardware Requirements Software Requirements Installation and Configuration Instructions Windows Serer 2003, and Windows Serer 2008 Instructions Persistent Naming Support on Windows Serer 2003 and Windows Serer Control Path Failoer Support for Tape Libraries 170 Configuring and Unconfiguring Control Path Failoer Support Querying Primary and Alternate Path Configuration Checking Disablement of Control Path Failoer Setting Data Path Failoer Support for Tape Dries Configuring and Unconfiguring Data Path Failoer Support Resere Type if DPF is disabled Querying Primary and Alternate Path Configuration Checking Disablement of Data Path Failoer Setting System-Managed Encryption Deice Drier Configuration Configuration File Querying Tape Drie Configuration Settings Problem Determination Windows Serer 2003 Instructions Reseration Conflict Logging This chapter describes the hardware requirements, software requirements, and installation notes for the Microsoft Windows deice driers for IBM TotalStorage and System Storage tape deices. Purpose Data Flow The Windows tape and medium changer deice drier is designed specifically to take adantage of the features proided by the IBM tape dries and medium changer deices. The goal is to gie 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 adanced functions needed by full tape management systems. Wheneer possible, the drier is designed to take adantage of the deice features transparent to the application The software described in this chapter coers the Windows deice drier and the interface between the application and the tape deice. Figure 15 illustrates a typical data flow process. Application Program Windows Tape and Medium Changer Deice Drier Host Bus Adapter Drier Tape Deice a Figure 15. Data Flow for Windows Deice Drier (IBMmag) Copyright IBM Corp. 2007,

182 Windows Deice Drier Product Requirements The most current information on supported hardware and software configurations for the Windows tape and medium changer deice drier can be found in the README files. The README files are downloaded with the latest drier which can be obtained at For further information please see Appendix A, Accessing Documentation and Software Online, on page 317. For a listing of all supported configurations, please isit: displayesssearchwithoutjs.wss?start_oer=yes. Hardware Requirements One of more of the following processors is required by the IBMtape deice drier: For the Windows Serer 2003, and Windows Serer 2008 operating systems, a 32-bit Intel compatible processor. For the Windows Serer 2003 and the Windows Serer 2008 operating systems, a 64-bit Itanium processor. For the Windows Serer 2003 and the Windows Serer 2008 operating systems, a processor that supports extended 64-bit architectures (Intel EM64T and AMD64). One or more of the following SCSI host adapters: Adaptec 2940U2W or IBM P/N 33L5000 for IBM System x (also known as xseries ) (LVD) Adaptec 2944UW (HVD) Adaptec SCSI Adapter or IBM P/N 19K4646 for IBM System x (also known as xseries) - Single Port LVD Adaptec SCSI Adapter Dual Port LVD Adaptec SCSI Card R (LVD) and 39320D-R (dual port LVD) Adaptec SCSI Card 29320ALP or IBM P/N 13N2249 (LVD) Symbios SYM bit PCI-to-Ultra-2 SCSI Dual Channel Host Adapter (LVD) from LSI Logic Corporation IBM Ultra320 SCSI Controller 2 P/N 13N2249 (SCSI LVD) IBM Ultra320 SCSI Controller 2 P/N 39R8743 (SCSI LVD) One or more of the following SAS host bus adapters: LSI Logic SAS3800X SAS Adapters IBM SAS Host Bus Adapter Controller Part Number 25R8060 One or more of the following Fibre Channel host bus adapters: IBM xseries and Netfinity FAStT Host Adapter P/N 19K1246 IBM xseries and Netfinity FAStT Host Adapter P/N 24P0960 DS4000 FC 4Gbps PCI-X Single Port HBA P/N 39M5894 DS4000 FC 4Gbps PCI-X Dual Port HBA P/N 39M5895 QLogic 4Gb FC Single-Port PCIe HBA P/N 39R6525 QLogic 4Gb FC Dual-Port PCIe HBA P/N 39R6527 Qlogic QLA2310 Qlogic QLA2340 Qlogic QLA2342 Qlogic QLA IBM Tape Deice Driers Installation and User s Guide

183 Windows Deice Drier Qlogic QLA2462 Qlogic QLE2460 (not supported for Windows 2008 SPI for IA64 serers) Qlogic QLE2462 (not supported for Windows 2008 SPI for IA64 serers) Brocade 825 Brocade 815 Brocade 425 Brocade 415 One or more of the following FC-AL host bus adapters: Qlogic QLE2460/2 4Gb PCI-E FC HBA, QLA2310FL, QLA2340, QLA2340L, QLA2342, QLA2342L, QLA2342L, QLA2460, QLA2462 Fibre Channel Adapters Emulex LPe11000/2 4Gb PCI-E FC HBA, LP1150, LP8000 and LP9002L, LP402DC, LP952L, LP9802, LP9802DC, LP10000, LP11000, LP11002 Fibre Channel Adapters 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 deices 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 hae been obsered. These issues are resoled by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring serer and storage configuration interoperability. It strongly recommends that your implementation plan includes proisions for separating disk and tape workloads. Software Requirements The software requirements are supported: SCSi or FC adapter deice drier Microsoft Windows Serer 2003 Build 3790 or later Microsoft Windows Serer 2008 SP1 Build 6001 or later Installation and Configuration Instructions This section includes instructions for installing and configuring the Windows tape and medium changer deice drier on Windows Serer 2003/Windows Serer Windows Serer 2003, and Windows Serer 2008 Instructions This section describes how to install, remoe, and uninstall the Windows tape and medium changer deice driers on Windows Serer 2003, and Windows Serer Installation Oeriew The installation process consists of the following steps: 1. Verify that the hardware and software requirements hae been met. 2. Install the host bus adapters and driers. 3. Shut down the system. 4. Connect the tape and medium changer deices to the host bus adapters. 5. Power on the tape and medium changer deices. Chapter 7. Windows Tape and Medium Changer Deice Drier 165

184 Windows Deice Drier 6. Set the tape and medium changer deice addresses. 7. Reboot the system. 8. Log on as Administrator. 9. Install and configure the deices and deice driers using the installation application. All dries accessible from a medium changer must be on the same physical SCSI bus as the changer. Installation Procedures These procedures make the following assumptions: No other drier is installed that claims the tape and medium changer deices. If you are updating the deice drier from a Microsoft certified ersion to an uncertified ersion, it is recommended that you first uninstall the certified drier by referring to the uninstall procedures in this documentation. The host bus adapter is installed, configured properly, and is running supported microcode and drier leels. Driers are identified by the following conentions, where: nnnn refers to a ersion of the drier. If there is more than one ersion, use the latest. Windows Serer 2003, 32-bit IBMTape.x86_nnnn.zip Windows Serer 2008, 32-bit IBMTape.x86_w08_nnnn.zip Windows Serer 2003 for Itanium (IA64) 64-bit architecture IBMTape.i64_nnnn.zip Windows Serer 2008 for Itanium (IA64) 64-bit architecture IBMTape.i64_w08_nnnn.zip Windows Serer 2003 for extended 64-bit architectures (Intel EM64T and AMD64) IBMTape.x64_nnnn.zip Windows Serer 2008 for extended 64-bit architectures (Intel EM64T and AMD64) IBMTape.x64_w08_nnnn.zip To install the deice driers, follow this procedure: 1. Log on as Administrator. 2. Download and install the appropriate drier. Refer to Appendix A, Accessing Documentation and Software Online, on page 317 for installation instructions. 3. Unzip the drier package to a hard drie directory of your choice, other than the root directory. 4. Ensure that the tape and medium changer deices are connected to your host bus adapter and configured properly by locating the deices in Deice Manager. 5. For drier packages prior to , double-click install.exe in the drier package. For all subsequent leels, double-click either install_exclusie.exe or install_nonexclusie.exe. 166 IBM Tape Deice Driers Installation and User s Guide

185 Windows Deice Drier With install_exclusie.exe, the drier issues automatic reseres on open and also preent multiple open handles from the host to a drie from existing at the same time, as is required by applications such as Tioli Storage Manager. With install_nonexclusie.exe, the drier permits open handles from the host to a drie to exist at the same time, as is required by applications such as Microsoft Remoable Storage Manager (RSM). The necessary.sys files for correct drier operation are installed, and all IBM deices are associated with the drier. Refer to Figure 16. a Figure 16. Installation Application in Windows Explorer Notes: a. There are additional installation features aailable through the command line interface (CLI), which include the following: Installing only the tape or medium changer deice driers ( -t or -c) Running in debug mode, which creates the file debug.txt in the drier package directory (-d) Running in silent mode, which suppresses pop-up messages requiring user interention, but only with Microsoft-certified IBM driers (-s) Disabling the Microsoft RSM serice (-r), aailable in drier packages and later Disabling DPF from installation (-f), aailable in drier packages and later Enabling Persistent Resere from installation if DPF is disabled (-p), aailable in drier packages and later. To install the deice driers using any of these features, instead of double clicking the install executable file, open a command-line window and cd to the drier package directory. For the usage information, type install_exclusie.exe -h or install_nonexclusie.exe -h at the prompt. Chapter 7. Windows Tape and Medium Changer Deice Drier 167

186 Windows Deice Drier b. If the Windows "Found New Hardware" Wizard begins during installation, cancel the wizard. The install application performs the necessary steps. 6. If you are installing a drier that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), a warning screen opens. Refer to Figure 17. If you want to continue installing the drier, select Continue Anyway. Note: All driers released by IBM hae been through a complete test to ensure that they are stable and conform to specified requirements. a Figure 17. Windows Logo Testing screen 7. If you are installing a Windows Serer 2008 drier that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), it likely has a Verisign digital signature. During installation, you may be presented with a prompt to install the software. Mark the "Always trust software from IBM Corporation" check box and click Install. You should only see this screen the first time that you install the driers, proided you click the Always trust software box. 8. To erify that the tape and medium changer deices and driers are installed correctly, follow the instructions in Appendix B, Verifying Proper Attachment of Your Deices, on page 319. Deice Remoal or Disable Procedure If you need to remoe a deice, or if you are altering the hardware configuration, you should uninstall or disable the deice first. 1. Right-click My Computer, select Manage to open the Computer Management Console, and click Deice Manager. 2. Right-click the TotalStorage or Magstar deice you wish to uninstall and select Uninstall... If you wish to disable the deice without uninstalling it, you may select Disable. 3. You are prompted to confirm the uninstallation. Click OK. 168 IBM Tape Deice Driers Installation and User s Guide

187 Windows Deice Drier 4. In Deice Manager, under System deices, right click Changer Bus Enumerator and select Uninstall. 5. In Deice Manager, under System deices, right click Tape Bus Enumerator and select Uninstall. Note: This remoal procedure remoes the deice from the deice tree, but it does not uninstall the deice drier files from your hard disk. Uninstalling the Deice Driers To uninstall the deice driers from the system, which includes deleting the system files and deallocating other system resources, complete the following: 1. Complete the steps under Deice Remoal or Disable Procedure to remoe the tape and medium changer deices. 2. Double-click uninst.exe in the drier package. Note: This remoes all the files in the system directories that were created during the installation of the deice drier. It does not delete the.zip file or the files that were extracted from the.zip file. If you desire to remoe these files, you need to delete them manually. 3. Reboot the system. Persistent Naming Support on Windows Serer 2003 and Windows Serer 2008 The Windows tape drier has an option for enabling deice object names that persist across reboots of the operating system. For example, if your tape drie has the name \.\tape and the persistent naming option is used, then \\.\tape is resered for use by that deice after an operating system reboot. Perform the following steps to enable this feature: 1. Add a DWORD alue to the registry called PersistentNaming and assign it a alue 1 at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Serices\ibmtp2kx 2. Reboot your system. On reboot, the system writes information to the registry to associate the World-Wide Node Name from Inquiry p. 0x83 with the persistent name used by the operating system. If the World-Wide Node Name is unaailable, or if the drie is a irtual (that is, emulated) drie, then the deice serial number is used rather than the World-Wide Node Name. If the PersistentNaming option is not specified in the registry, then there is no guarantee that your deices can claim the same deice name after reboot or drier initialization. You can find registry subkeys with persistent naming information at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Serices\ibmtpbs2kx Alternately, you can use the Windows Deice Manager to examine the deice number in order to determine that persistent naming is enabled on your host. Persistent names contain tape deice numbers based at (which is the decimal equialent of hexadecimal 0x49424D and ASCII "IBM"). Chapter 7. Windows Tape and Medium Changer Deice Drier 169

188 Windows Deice Drier If two physical paths exist to a drie and different Windows deice names are required (which happens, for example, when two different HBAs are connected to the drie and Data Path Failoer is disabled) the first path discoered claims the persistent deice name, and any subsequent paths that connect to the same deice receie names according to the order in which they are discoered by the Windows Deice Manager. Control Path Failoer Support for Tape Libraries To take adantage of Windows Control Path Failoer (CPF) support, the appropriate feature code must be installed. Refer to Automatic Failoer on page 10 for what feature code may be required for your machine type. Configuring and Unconfiguring Control Path Failoer Support Control Path Failoer support is enabled automatically when the deice drier is installed by default. It can be disabled from installation using -f CLI option or it may be disabled or reenabled for the entire set of attached medium changers by modifying the registry. 1. Open the reg folder of the drier package. 2. Double click DisableCPF.reg or EnableCPF.reg. 3. Reboot the system. This is necessary for any registry modification to take effect. Querying Primary and Alternate Path Configuration To check if the control path failoer has been enabled in the deice drier and display the primary and alternate paths, you may use the tape diagnostic and utility tool. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Checking Disablement of Control Path Failoer Setting If you hae disabled the control path failoer in deice drier s setting by double clicking the DisableCPF.reg file and reboot your system, you may go into the registry by issuing the Windows regedit command to confirm that CPF has been disabled. Look for a line like the following if your system is Windows Serer 2003 or Windows Serer 2008: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices\ibmcg2kx] "FailoerDisabled"=dword: This indicates that CPF has been disabled in the drier. This setting only takes effect after your system is rebooted. Data Path Failoer Support for Tape Dries To take adantage of Windows Data Path Failoer (DPF) support, the appropriate feature code must be installed. Refer to Automatic Failoer on page 10 for what feature code may be required for your machine type. 170 IBM Tape Deice Driers Installation and User s Guide

189 Windows Deice Drier Configuring and Unconfiguring Data Path Failoer Support Data Path Failoer support is enabled automatically when the deice drier is installed by default. It can be disabled from installation using -f CLI option or it may be disabled or reenabled for the entire set of attached dries or medium changers by modifying the registry. 1. Open the reg folder of the drier package. 2. Double click DisableDPF.reg or EnableDPF.reg. 3. Reboot the system. This is necessary for any registry modification to take effect. For LTO generation 3 or lower, for tape dries that require a data path license key on the host side to enable DPF, the deice drier looks for a file called %system_root%:\ibm_dpf.txt for the key, where: %system_root% is the drie letter where Windows has been installed, typically C, (for example, C:\IBM_DPF.txt). The file should contain the key on a single line, with no spaces and no other text on the line. If multiple keys are required, place each key in the file on its own line. The drier looks for this file at initialization, and if the file contains a alid DPF license key, the DPF feature is enabled and any eligible deices hae multi-path support. Note: For LTO generation 3 running the latest drie microcode, there is no longer a requirement to proide a DPF license key in IBM_DPF.txt. The microcode now handles the enablement of the DPF feature. Resere Type if DPF is disabled If DPF is disabled SCSI-2 resere is used by default to handle the reseration on tape dries. If Persistent Resere is desired rather than SCSI-2 resere ResereTypePersistent.reg will enable it (ResereTypeRegular.reg will disable it and then SCSI-2 resere will be used) or -p CLI option installation (only if -f was used to disable DPF) will enable Persistent Resere from installation. Note: If DPF is not disabled Persistent Resere will be used. Querying Primary and Alternate Path Configuration To check if the data path failoer has been enabled in the deice drier and display the primary and alternate paths you may use the tape diagnostic and utility tool. Note: Display the primary and alternate path configuration for any deice using tape diagnostic and utility functions, refer to Chapter 9, IBM Tape Diagnostic Tool (ITDT), on page Checking Disablement of Data Path Failoer Setting If you hae disabled the data path failoer in deice drier s setting by double clicking the DisableDPF.reg file and reboot your system, you may go into the registry by issuing the Windows regedit command to confirm that DPF has been disabled. Look for a line like the following if your system is Windows Serer 2003 or Windows Serer 2008: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices\ibmtp2kx] "FailoerDisabled"=dword: This indicates that DPF has been disabled in the drier. This setting only takes effect after your system is rebooted. Chapter 7. Windows Tape and Medium Changer Deice Drier 171

190 Windows Deice Drier System-Managed Encryption If you hae enabled Persistent Resere on DPF disabled look for a line like this: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices\ibmtp2kx] "ResereType"=dword: If you use ResereTypeRegular.reg then the ResereType alue will be set to 0. Deice Drier Configuration System-managed encryption parameters on Windows are placed in the registry under the key for the deice drier. The parameters are populated in user-created subkey containing the serial number of the deice. The registry keys (sys_encryption_proxy and sys_encryption_write) are used to determine SME enablement and inocation of the EKM proxy on write, respectiely. Note: Leading zeros in the serial number should be excluded. For example, if the serial number of the encryption-capable tape drie were , the user would create the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Serices\ibmtp2k3\ Under this key, the user would create DWORD alues called sys_encryption_proxy and/or sys_encryption_write, and assign them alues corresponding with the desired behaior. The deice drier SME settings can be set for all dries at once by placing the "sys_encryption_proxy" and "sys_encryption_write" registry options under the deice drier key, found at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Serices\ibmtp2k3 When this option is chosen, the settings established for all dries are oerridden by the serial-number specific settings described the preious paragraph. If no options are specified in the registry, the drier uses the default alues for the parameters. The default alue for sys_encryption_proxy is 1. This alue causes the deice drier to handle encryption key requests, if the drie is set up for system-managed encryption. This alue should not need to be changed. A alue of 0 causes the deice drier to ignore encryption key requests for system-managed encryption dries, and is not desirable. The default alue for sys_encryption_write is 2. This alue causes the deice drier to leae the encryption write-from-bop settings alone. It does not turn on or turn off encryption writing, but instead uses the settings that are already in the drie. If encryption has not been set up preiously, then the drie writes unencrypted data. A alue of 0 causes the deice drier to write unencrypted data. A alue of 1 causes the deice drier to write encrypted data. Changes to the registry require a reboot before the settings are able to be iewed; howeer, during new installations of the drier, if the old drier is not uninstalled, the old settings remain in place and no reboot is required. 172 IBM Tape Deice Driers Installation and User s Guide

191 Windows System-Managed Encryption Configuration File The file %system_root%:\ibmekm.conf is used to store the IP address of the EKM serer and other network-related parameters. The phrase %system_root% refers to the drie letter where the Windows installation is located, typically C (for example C:\IBMEKM.conf). The format for the EKM serer parameters is: Serer<tab>Timout<tab>IPAddress:Port For example, if the Windows installation is installed at c:\, the ekm serer is named ekmtest, the desired timeout is 10 seconds, and the IP address is at port Then create a line in c:\ibmekm.conf as follows: ekmtest<tab>10<tab> :4242 Querying Tape Drie Configuration Settings There is an ITDT command to query the encryption settings of a tape drie. In ITDT-SE this can be done by using either the Standard Edition - Scan Menu Commands on page 247 section or the Tapeutil menu commands using command [35] Query Encryption Status on page 267. In ITDT-GE it can be accomplished by using the Diagnostic/Maintenance tab (see Encryption on page 298) or by Query Encryption Status on page 313 using the Tapeutil tab. Problem Determination There is a debug ersion of the deice drier that can be used if you encounter problems. The debug ersion of the drier issues DbgPrint messages at arious places during deice drier execution. To capture these messages, you must start a debugger or use a tool like Debug View, aailable from: Windows Serer 2003 Instructions Using the Debug Version To install and use the debug ersion of the deice drier, perform the following steps after the drier has initially been installed: 1. Quiesce all actiity on the tape and medium changer. 2. Exit all applications that are using the tape and medium changer deices. 3. Locate the \checked folder for the deice drier leel that you are running. This folder is in the highest leel directory of the drier package, and it contains checked ersions of the tape and medium changer deice driers, ibmtpxxyyy.sys and ibmcgxxyyy.sys, where: xx = ft for the filter drier, bs for the bus drier, or blank for the base drier, and 2k3 for Windows Serer 2003, or 2k8 for Windows Serer Refer to Figure 18 on page 174. Note: The last drier leel to include support for Windows 2000 is V Subsequent leels include support for Windows Serer 2003 and Windows Serer 2008 only, and therefore only contain 2k3 and 2k8 Chapter 7. Windows Tape and Medium Changer Deice Drier 173

192 Windows System-Managed Encryption files. dd Figure 18. Checked folder 4. Copy the checked ersion of ibmtpxxyyy.sys or ibmcgxxyyy.sys to \winnt\system32\driers, oerwriting the ersion of the file already there. 5. Reboot the system. 6. Start the debugger to capture the DbgPrint messages. 7. Issue the commands to the drier. You should see debug statements printed to the debugger window. Windows 2008 Instructions 1. Quiesce all actiity on the tape and medium changer. 2. Exit all applications that are using the tape and medium changer deices. 3. If the drier is currently installed perform the Uninstall the deices procedure described in a preious section. 4. Locate the \checked folder described at step 3 from the Windows Serer 2003 instructions and additionally of the.sys files you will find.inf and.cat files. This is because Windows 2008 driers are digitally signed. 5. Copy the files from the \checked folder to the highest leel directory of the drier package oerwriting the files in there (a preious backup of this files or haing a copy of the original drier package is recommended). 6. Perform the Installation procedure. 7. Follow steps 6 and 7 from the Windows Serer Restoring the Non-Debug Version To restore the non-debug ersion of the drier, perform the following steps: 1. Quiesce all actiity on the tape and medium changer deices. 2. Exit all applications that are using the tape and medium changer deices. 174 IBM Tape Deice Driers Installation and User s Guide

193 Windows System-Managed Encryption 3. Located in the highest leel directory of the drier package, are non-debug ersions of the tape and medium changer deice driers, ibmtpxxyyy.sys and ibmcgxxyyy.sys, where: xx = ft for the filter drier, bs for the bus drier, or blank for the base drier, and yyy = 2k for Windows 2000, or 2k3 for Windows Serer 2003, or 2k8 for Windows Serer Refer to Figure 18 on page 174. Note: The last drier leel to include support for Windows 2000 is V Subsequent leels include support for Windows Serer 2003 and Windows Serer 2008 only, and only contain 2k3 files. 4. Copy the non-debug ersion of ibmtpxxyyy.sys or ibmcgxxyyy.sys to \winnt\system32\driers, oerwriting the ersion of the file already there. 5. Reboot the system. When the drier has started and commands are issued to it, the drier no longer produces debug output. Note: For Windows Serer 2008 is necessary to Uninstall the deices and then Install the non-debug ersion of the drier. Reseration Conflict Logging When the deice drier receies a reseration conflict during open or after the deice has been opened it will log a reseration conflict in the Windows eentlog. Prior to logging the error the deice drier will issue a Persistent Resere In command to determine if a SCSI Persistent Reseration is actie on the resering host to get the resering host initiator WWPN (World Wide Port Name). If successful, the deice drier will log this information as follows: Resering host key: kkkkkkkk WWPN: xxxxxxxx Where kkkkkkkk is the actual resere key and xxxxxxxx is the resering host initiator WWPN. After initially logging the resering host WWPN, subsequent reseration conflicts from the same resering host WWPN will not be logged to preent multiple entries in the error log until either the resering host WWPN is different than the one initially logged or the deice drier has resered the deice and then another reseration conflict occurs. Chapter 7. Windows Tape and Medium Changer Deice Drier 175

194 176 IBM Tape Deice Driers Installation and User s Guide

195 Chapter Enterprise Tape Library Support Purpose MTLIB Program Syntax and Examples MTEVENT Program Library Drier Information Software Interface Library Manager Eent Notification Synchronous and Asynchronous Operations Operation Complete Notification Unsolicited Notification Drier Message Queue Volume Categories IBM TotalStorage Virtual Tape Serer Subsystem Attachment Library Emulation Oeriew Emulation Design Using the 3494 API Emulation and MTLIB Program SMC Library Names Volume Categories Asynchronous Library Operations Performance Considerations AIX Data Flow Product Requirements Installation Instructions Special Files Enterprise Tape Library Attachment Test 203 Problem Determination HP-UX Data Flow Product Requirements Installation Instructions Enterprise Tape Library Attachment Test 210 Problem Determination Linux Data Flow Product Requirements Installation and Configuration Instructions Enterprise Tape Library Attachment Test 217 Problem Determination Solaris Data Flow Product Requirements Installation Instructions Enterprise Tape Library Attachment Test 223 Problem Determination Windows Data Flow Product Requirements Installation Instructions Enterprise Tape Library Attachment Test 230 Problem Determination Purpose The IBM 3494 Library deice drier is a deice drier proiding attachment for the IBM TotalStorage 3494 Enterprise Automated Tape Library and IBM TotalStorage Virtual Tape Serer (VTS) to a serer. The programs described in this chapter support the 3494 Enterprise Automated Tape Library on the following operating systems: AIX on IBM POWER-based serers HP-UX Linux Sun/Solaris Microsoft Windows NT Microsoft Windows 2000 Microsoft Windows 2003 Microsoft Windows 2008 Tru64 SGI/IRIX Copyright IBM Corp. 2007,

196 3494 Enterprise Tape Library Support MTLIB Program The mtlib program is a command-line interface used to control the 3494 Enterprise Tape Library and is installed, by default, for execution by all users on the system. This program proides the full interface (except for the MTIOCLEW library system call) as specified in the IBM Tape Deice Driers: Programming Reference, GA Refer to MTEVENT Program on page 189. The mtlib program proides an interface to the physical tape dries and olumes within a 3494 Tape Library and also to the irtual tape dries and olumes within an attached IBM TotalStorage Virtual Tape Serer (VTS). To issue commands to the physical tape dries and olumes, specify a deice special file name, such as /de/lmcp0 or the logical name of the library, such as libmgrc7. To issue commands to the irtual tape dries and olumes in an attached VTS library, specify a deice special file name or the logical name of the library with the name of the logical VTS library appended with a slash (/). For example, to issue commands to the first attached VTS library, use /de/lmcp0/ts1 or libmgrc7/ts1. The attached VTS libraries are named logically ts1, ts2, and so on and correspond to the order in which they were configured in the Tape Library. The -D flag, in conjunction with the -E flags, can be used to display the attached VTS deices and the number of the VTS library. Syntax and Examples Figure 19 shows the syntax for the mtlib program. Figure 19. Syntax Diagram for mtlib program 178 IBM Tape Deice Driers Installation and User s Guide

197 3494 Enterprise Tape Library Support The mtlib program has the following flags: Flag Description -f[filename] Deice special file for the drie, for example, /de/rmt0 (AIX), /de/rmt/0st (Sun), /de/rmt/0m (HP), /de/ibmtape0 (Linux), \\.\tape0 (Windows) -x[number] Deice number of the drie, for example, l[filename] On AIX, library special file name, for example, /de/lmcp0, /de/lmcp0/ts1. For non-aix, the logical name of the library, for example, libmgrc7. -q[type] Query the library information option: Type Description V Volume data L Library data S Statistical data I Inentory data C Category inentory data D Deice data E Expanded olume data K Inentory olume count data R Resered category list A Category attribute list M All mounted olumes -D Return an array of deices configured in the specified library -E Return (if used with the -D option) an array of expanded information for all deices configured in the specified library, including the control unit ID, deice, and VTS library number -m Mount option -d Demount option -c[requestid] Cancel the pending request option -n No wait mode -i[requestid] Query the request ID status option -C Change the category of a olume -a Audit the specified olume -k[flags] Assign a category (with one of the following flags) to a deice in the library: Type Description O Enable the category order C Clear the cartridge loader G Generate the first mount A Enable the auto mount Chapter Enterprise Tape Library Support 179

198 3494 Enterprise Tape Library Support X Remoe the deice category assignment Note: Valid combinations are OG, OA, GA, and OGA. -r Resere the category -R Release the category -S Set the category attribute Note: The categories must be resered before using this option. -s[category] Source or starting category -t[category] Target category -V[olser] Volume serial number -L[list] Filename containing a list of the olume serial numbers. Each Volume Serial should be entered as one per line in the file. -N[name] Category name to assign to the category (alid characters are uppercase A-Z, 0-9, -, *, or blank). -h[hostid] Host ID for the resere or release category or the R/A option for the query command. -u Include usage date in the expanded olume data (used in conjunction with the -qe option). The default is the ISO format with a period separator. The format can be specified with the -F option. -F[flags] Format or separator for olume usage and date with the -u option: Type Description I ISO/Japan yyyy.mm.dd E Europe dd.mm.yyyy U U.S.A. mm.dd.yyyy p Period separator mm.dd.yyyy d Dash separator mm-dd-yyyy s Slash separator mm/dd/yyyy - Verbose -#[num_categories] Number of categories to resere -A Query library addresses and status. -? Help text Note: The -l argument is required. 180 IBM Tape Deice Driers Installation and User s Guide

199 3494 Enterprise Tape Library Support The report in Figure 20 was produced by: mtlib -l /de/lmcp0 -f /de/rmt5 -qd (for AIX physical library) mtlib -l /de/lmcp0/ts1 -f /de/rmt5 -qd (for AIX VTS library 1) mtlib -1 libmgrc7 -f /de/rmt/5st -qd (for Sun) mtlib -1 libmgrc7 -f /de/rmt/5m -qd (for HP) mtlib -1 libmgrc7 -f /de/ibmtape5 -qd (for Linux) mtlib -l libmgrc7 -f \\.\tape0 -qd (for Windows) Deice Data: mounted olser...taf500 mounted category...ff00 deice category deice state...deice installed in Library. Deice aailable to Library. Volume is loaded. ACL is installed. deice class b1a extended deice status...00 Figure 20. Deice Query The report in Figure 21 was produced by: mtlib -l /de/lmcp0 -qv -VCS2000 (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qv -VCS2000 (for AIX VTS library 1) mtlib -l libmgrc7 -qv -VCS2000 (for Sun, HP, Linux, SGI, Tru64, and Windows) Volume Data: olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length olser...cs2000 category...fe00 subsystem affinity Figure 21. Volume Query Chapter Enterprise Tape Library Support 181

200 3494 Enterprise Tape Library Support The report in Figure 22 was produced by: mtlib -l /de/lmcp0 -qe -VCS2000 (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qe -VCS2000 (for AIX VTS library 1) mtlib -l libmgrc7 -qe -VCS2000 (for Sun, HP, Linux, SGI, Tru64, and Windows) Expanded Volume Data: olume status...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length olser...cs2000 deice category...ff00 Figure 22. Expanded Volume Query The report in Figure 23 was produced by: mtlib -l /de/lmcp0 -qe -u -VCS2000 (for AIX physical library) mtlib -1 libmgrc7 -qe -u -VCS2000 (for Sun, HP, Linux, SGI, Tru64, and Windows) Expanded Volume Data with Usage: olume status...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length olser...cs2000 deice category...ff00 last used (yyyy.mm.dd) Figure 23. Expanded Volume Data with Usage The report in Figure 24 was produced by: mtlib -l /de/lmcp0 -qk - (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qk - (for AIX VTS library 1) mtlib -l libmgrc7 -qk - (for Sun, HP, Linux, SGI, Tru64, and Windows) Performing Query Inentory Volume Count Data using /de/lmcp0 Inentory Volume Count Data: sequence number number of olumes category Figure 24. Inentory Count Data The report in Figure 25 was produced by: mtlib -l /de/lmcp0 -D (for AIX physical library) mtlib -l /de/lmcp0/ts1 -D (for AIX VTS library 1) mtlib -l libmgrc7 -D (for Sun, HP, Linux, SGI, Tru64, and Windows) Refer to also the tapeutil subcommand mtdeice. 182 IBM Tape Deice Driers Installation and User s Guide

201 3494 Enterprise Tape Library Support 0, C2A00 1, C2A01 Figure 25. Tape Library Deice Number The report in Figure 26 was produced by: mtlib -l /de/lmcp0 -DE (for AIX physical library) mtlib -l /de/lmcp0/ts1 -DE (for AIX VTS library 1) mtlib -1 libmgrc7 -DE (for Sun, HP, Linux, SGI, Tru64, and Windows) Refer to also the tapeutil subcommand mtdeice. Type Mod Serial # Denum Cuid Deice VTS Library B1A B1A B B B B C2A FF C2A FF C2A FF C2A FF C2A FF C2A FF C2A FF C2A FF Figure 26. Expanded Tape Library Deice List Chapter Enterprise Tape Library Support 183

202 3494 Enterprise Tape Library Support The report in Figure 27 was produced by: mtlib -l /de/lmcp0 -ql (for AIX physical library) mtlib -l /de/lmcp0/ts1 -ql (for AIX VTS library 1) mtlib -l libmgrc7 -ql (for Sun, HP, Linux, SGI, Tru64, and Windows) Library Data: Operational state...paused Operational State Interention Required functional state...00 input stations...1 output stations...1 input/output status...all input stations empty All output stations empty machine type sequence number number of cells aailable cells subsystems...6 conenience capacity...30 accessor config...01 accessor status...accessor aailable Gripper 1 aailable Gripper 2 installed Vision system operational comp aail status...primary library manager installed. Primary library manager aailable. Secondary library manager installed. Secondary library manager aailable. Primary hard drie installed. Primary hard drie aailable. Secondary hard drie installed. Secondary hard drie aailable. Conenience input station installed. Conenience input station aailable. Conenience output station installed. Conenience output station aailable. library facilities...00 bulk input capacity...0 bulk input empty cells...0 bulk output capacity...0 bulk output empty cells...0 aail 3490 cleaner cycles..0 aail 3590 cleaner cycles..91 Figure 27. Library Data 184 IBM Tape Deice Driers Installation and User s Guide

203 3494 Enterprise Tape Library Support The report in Figure 28 was produced by: mtlib -l /de/lmcp0 -qs (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qs (for AIX VTS library 1) mtlib -l libmgrc7 -qs (for Sun, HP, Linux, SGI, Tru64, and Windows) Statistical Data: hour index...10 machine type model number...l10 manufacturer...ibm plant...13 sequence number dries...6 mounted dries...1 max mounted dries...2 min mounted dries...1 ag mounted dries...1 max mounted time...22 min mounted time...16 ag mounted time...19 pending mounts...0 max pending mounts...2 min pending mounts...0 ag pending mounts...0 mounts/hour...18 index mounts/hour...0 pre-mounts/hour...0 max mount time...27 min mount time...16 ag mount time...19 pending demounts...0 max pending demounts.2 min pending demounts.0 ag pending demounts.0 demounts/hour...16 index demounts/hour..0 post-demounts/hour...0 max demount time...28 min demount time...19 ag demount time...24 pending ejects...0 max pending ejects...0 min pending ejects...0 ag pending ejects...0 ejects/hour...0 max eject time...0 min eject time...0 ag eject time...0 pending audits...0 max pending audits...0 min pending audits...0 ag pending audits...0 audits/hour...0 max audit time...0 min audit time...0 ag audit time...0 input stores/hour...0 Figure 28. Statistical Data Chapter Enterprise Tape Library Support 185

204 3494 Enterprise Tape Library Support The report in Figure 29 was produced by: mtlib -l /de/lmcp0 -qi- (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qi - (for AIX VTS library 1) mtlib -l libmgrc7 -qi - (for Sun, HP, Linux, SGI, Tru64, and Windows) Performing Query Inentory Data using /de/lmcp0 Inentory Data: sequence number number of olumes...44 inentory records record 1...category...012C olser olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 2...category alue...ff00 olser olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 3...category alue...ff00 olser...altml1 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 42...category...FF00 olser...tst039 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 43...category...FF00 olser...tst182 olume state...volume present in Library, but Inaccessible record 44...category alue...ff00 olser...xyz464 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length Note: All aailable records are produced as output per request. Fewer records are shown here for the sake of breity. Figure 29. Inentory Query 186 IBM Tape Deice Driers Installation and User s Guide

205 3494 Enterprise Tape Library Support The report in Figure 30 was produced by: mtlib -l /de/lmcp0 -qc -sff00 - (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qc -sff00 - (for AIX VTS library 1) mtlib -l libmgrc7 -qc -sff00 - (for Sun, HP, Linux, SGI, Tru64, and Windows) Performing Query Category Inentory Data using /de/lmcp0 Inentory by Category Data: sequence number number of olumes...30 category...ff00 inentory records record 1...category...FF00 olser...cs2017 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 2...category...FF00 olser...fvt896 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 3...category...FF00 olser...ihg319 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 28...category...FF00 olser...slt500 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 29...category...FF00 olser...taf195 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length record 30...category...FF00 olser...moo801 olume state...00 logical olume...no olume class /2 inch cartridge tape olume type...hpct 320m nominal length Note: All aailable records are produced as output per request. Fewer records are shown here for the sake of breity. Figure 30. Category Inentory Query Chapter Enterprise Tape Library Support 187

206 3494 Enterprise Tape Library Support The report in Figure 31 was produced by: mtlib -l /de/lmcp0 -r -#2 -h roadster (for AIX physical library) mtlib -l /de/lmcp0/ts1 -r -#2 -h roadster (for AIX VTS library 1) mtlib -l libmgrc7 -r -#2 -h roadster (for Sun, HP, Linux, SGI, Tru64, and Windows) Resered Category List: sequence number system token...roadster total number resered category category Figure 31. Resere Category Command The report in Figure 32 was produced by: mmtlib -l /de/lmcp0 -qr -h roadster (for AIX physical library) mtlib -l /de/lmcp0/ts1 -qr -h roadster (for AIX VTS library 1) mtlib -l libmgrc7 -qr -h roadster (for Sun, HP, Linux, SGI, Tru64, and Windows) Resered Category List: sequence number system token...roadster total number resered category category Figure 32. Resere Category List The report in Figure 33 was produced by: mtlib -l /de/lmcp0 -S -S101 -NSCRATCH (for AIX physical library) mtlib -l /de/lmcp0 -S -S102 -NWORKING (for AIX physical library) mtlib -l /de/lmcp0 -qa -h roadster (for AIX physical library) mtlib -l /de/lmcp0/ts1 -S -S101 -NSCRATCH (for AIX VTS library 1) mtlib -l /de/lmcp0/ts1 -S -S102 -NWORKING (for AIX VTS library 1) mtlib -l /de/lmcp0/ts1 -qa -h roadster (for AIX VTS library 1) mtlib -l libmgrc7 -S -S101 -NSCRATCH (for Sun, HP, Linux, SGI, Tru64, and Windows) mtlib -l libmgrc7 -S -S102 -NWORKING (for Sun, HP, Linux, SGI, Tru64, and Windows) mtlib -l libmgrc7 -qa -h roadster (for Sun, HP, Linux, SGI, Tru64, and Windows) Category Attribute List: sequence number system token...roadster category 0101 name: SCRATCH category 0102 name: WORKING Figure 33. Category Attribute List 188 IBM Tape Deice Driers Installation and User s Guide

207 3494 Enterprise Tape Library Support The report in Figure 34 was produced by: mtlib -l /de/lmcp0 -A (for AIX physical library) mtlib -l tire -A (for Sun, HP, Linux, SGI, Tru64, and Windows) Library Address Information: library name...tire host identification...roadster primary address primary status...online alternate address alternate status...offline Figure 34. Library Address Information MTEVENT Program Library Drier Information The mteent program is a command-line interface to the MTIOCLEW command. The mteent program has the following flags: Flag Description -l[filename] Library special file name or logical name of the library, for example, /de/lmcp0, /de/lmcp0/ts1, orlibmgrc7 -t[timeout] Number of seconds to wait for the eent to occur (0=no timeout) Notes: 1. The -l flag is required. 2. If the -t flag is not supplied, then no timeout is performed. The lmcpd communicates to the tape library through symbolic names defined in the /etc/ibmatl.conf file. One or more symbolic names can be configured for each tape library online to the system. A symbolic name is used to perform the arious library functions (such as mounting and demounting olumes). Software Interface The C object module proides three subroutines for communicating with the IBM TotalStorage 3494 Enterprise Tape Library. These subroutines are open_ibmatl, close_ibmatl, and ioctl_ibmatl. The open_ibmatl and close_ibmatl routines are used to open and close communication with the library (as the open and close system calls are used to open and close communication with a file). The ioctl_ibmatl subroutine is used to send commands to the Library Manager on the 3494 Tape Library. To send commands to the 3494 Tape Library, one symbolic name must be defined for use on the library. Library Manager Eent Notification In addition to performing library operations, the lmcpd is responsible for receiing the arious Library Manager notifications. The daemon monitors seeral types of eents. When the daemon receies an eent, it checks a list of processes waiting for an eent to determine where to delier it. If no process is waiting for the eent Chapter Enterprise Tape Library Support 189

208 3494 Enterprise Tape Library Drier that has arried, then the eent is discarded. The applications can use the Library Eent Wait call to request notification of all Library Manager eents. Refer to the IBM Tape Deice Driers: Programming Reference for more information. Synchronous and Asynchronous Operations Two types of library operations are supported: synchronous and asynchronous. The Library Manager responds to the synchronous operation immediately. These operations are completed when the library responds to the request. An example of a synchronous operation is the Library Query call. An asynchronous operation (such as a mount operation) takes longer to complete. In an asynchronous operation, the library returns an initial response when the command is accepted for execution. When the command is completed, it returns a delayed response message indicating the status of the operation. Operation Complete Notification When the Mount, Demount, Audit, or Set Volume category operation is sent to the library, a message identifier is assigned to the operation. This identifier is returned to lmcpd. When the operation is completed, an operation complete notification is sent to the daemon. The daemon makes a determination (based on the initial message identifier) as to which user process to notify that the operation is complete. The Mount, Demount, Audit, or Set Volume category operations hae an option that allows the user process to wait or not wait for the operation complete message. If the user process does not wait for the final complete, the initial message identifier is returned to the caller, and it can be used in subsequent Library Query Message ID operations to solicit the status of the asynchronous operation. Unsolicited Notification There are situations when the Library Manager has a condition to report that is not related to any I/O operation. In this case, an unsolicited notification is sent to the deice daemon. If a notification is receied, then any process waiting with the Library Eent Wait call is notified. An example of an unsolicited notification is the operational state change of the library (from the Auto mode to the Pause mode). Refer to the IBM Tape Deice Driers: Programming Reference for a list of unsolicited notifications receied by the lmcpd. Drier Message Queue The drier maintains a message queue for any process that has an open LMCP file descriptor. This queue, which has a depth of four entries, is implemented on a first-in, first-out basis. The purpose of this message is to reduce the possibility of missing a message when seeral messages occur in a short period of time. All queue entries are discarded when the LMCP file descriptor is closed. When an application issues the MTIOCLEW input/output control (ioctl) call, the drier returns the oldest entry from the message queue and deletes it. If no entries are in the queue, then the calling process is put to sleep until a message is receied. Volume Categories To facilitate the management of the tape olumes within the 3494 Tape Library, the capability to associate the tape olumes into logical groupings is proided. Each logical grouping is known as a category. For example, an installation can hae one or more scratch categories that are assigned by media type or class of user. Another potential use is managing olumes for daily, weekly, and monthly backups or olumes owned by a specific user. The lmcpd also allows a user process 190 IBM Tape Deice Driers Installation and User s Guide

209 3494 Enterprise Tape Library Drier to assign a particular category to a tape deice in the library. This process allows all the olumes associated with the category to be mounted as determined by the flags of the command on the specified deice. A category is a four digit hexadecimal number in the X'0000' X'FFFF' range. The assigned categories are: X'0000' NULL category (not usable or not assigned) X'0001' X'FEFF' General programming use X'FFFF' VOLSER specific The X'FF00' X'FFFE' categories are resered for hardware functions: X'FF00' Insert X'FF01' X'FF0F' Resered X'FF10' Eject X'FF11' Bulk eject X'FF12' X'FFF8' Resered X'FFF9' Serice olume X'FFFA' Manually ejected X'FFFB' Purge olume X'FFFE' Cleaner olume The following three categories are aailable for programming use: Insert When a tape olume is receied in the input station, the olume label is read and assigned to this category. This category cannot be assigned by a user process. Eject The olumes assigned to this category are moed from their cell into the output station. After the olume is deliered, it is remoed from the inentory. The Library Set Volume Category command is the only command that can change the category of a olume to the eject category. Bulk eject The olumes that are assigned to this category are moed from their current cell to the bulk output area in the 3494 Tape Library. Refer to the IBM TotalStorage Enterprise Automated Tape Library Operator Guide for more information about the bulk output area. The Library Set Volume Category command is the only command that can change the category of a olume to the bulk eject category. The X'FFFF' category is aailable for general programming use, except that any mount request to this category must apply to a specific olume assigned to the category (and not based on the category alone). IBM TotalStorage Virtual Tape Serer Subsystem Attachment The deice drier supports the IBM TotalStorage Virtual Tape Serer (VTS) subsystem attachment with a 3494 Enterprise Tape Library on AIX, HP-UX, Windows, and Sun/Solaris systems. An attached VTS subsystem proides irtual tape dries that are accessible with the VTS SCSI attachment feature. Volumes within the VTS subsystem are logical tape olumes. A logical tape olume appears Chapter Enterprise Tape Library Support 191

210 3494 Enterprise Tape Library Drier to the host as a normal physical tape olume, except that the VTS logical olumes are unique to the VTS subsystem and are accessible only by irtual tape dries within the VTS subsystem. Access to a VTS subsystem is specified to the deice drier as a logical library within the attached Tape Library as ts1, ts2, and so on. For example, issuing a Query Inentory command to the 3494 lib returns the physical olumes in the 3494 Tape Library, where: 3494 lib is a library configured in the /etc/ibmat1.conf file. Issuing a Query Inentory command to 3494 lib/ts1 returns the logical olumes in the first VTS subsystem attached to the 3494 Enterprise Tape Library. 192 IBM Tape Deice Driers Installation and User s Guide

211 3494 Library Emulation 3494 Library Emulation The 3494 Library Emulation support proides the ability to use applications that were written for the 3494 API on host attached SCSI Medium Changer Libraries, specifically for migration to the 3584 Ultra Scalable Library with 3592 dries. Oeriew Existing customer scripts using the mtlib program and customer or ISV applications require no or minor changes to use, depending on the 3494 functions being used. Customer and ISV applications only need to be recompiled with the new libibm.o object module in order to use the emulation support. The mtlib 3494 user command line interface program that has the same syntax and output on eery operating system and also proides a common utility for SCSI Medium Changer Libraries. Current operating system deice drier utilities ary by syntax/output, require a knowledge of SCSI Medium Changers to use, and require multiple commands to perform a single mtlib command Emulation Design The 3494 Emulation support adds a libsmc extension to the current libibm.o object module that applications compile with for existing 3494 support. The libsmc extension contains the 3494 API Emulation support, which issues SCSI Medium changer commands to the library using the operating system SCSI Medium Changer deice drier. Figure 35 and Figure 36 on page 194 show the 3494/SMC data flow between existing applications and components and the new libsmc extension. 3494/ SMC Library Data Flow Tape Deice Drier Adapter Deice Drier Library Tape Drie Application LIBIBM.O Object Module LMCPD TCP/IP 3494 Library Manager LIBSMC SMC Deice Drier Adapter Deice Drier SCSI Medium Changer a28t1001 Figure /SMC Library Data Flow Chapter Enterprise Tape Library Support 193

212 3494 Library Emulation LIBSMC and O/S Components libsmc.c 3494 API Emulation libsmc_aix.c libsmc_sun.c AIX Atape Deice Drier Solaris IBMtape Deice Drier SCSI Medium Changer Commands libsmc_hp.c HPUX atdd Deice Drier libsmc_linux.c Linux IBMtape Deice Drier Figure 36. LIBSMC and OS Components libsmc_win.c Windows IBMtape Deice Drier a28t1002 Using the 3494 API Emulation and MTLIB Program Refer to the IBM Tape Deice Driers Installation and User's Guide and the IBM Tape Deice Driers Programmer's Reference for the complete description of 3494 library support and the mtlib program and syntax. SMC Library Names The library name on the open_ibmatl ("libname") or mtlib -l libname parameter determines whether a 3494 library or an SMC library is being used. If the library name is a logical operating system SMC library name then the libsmc support is used. Otherwise, the lmcpd support is used. For example, SMC libraries on AIX are named smc0, smc1, and so on. To issue an mtlib query library command on AIX to a 3584 library named smc0: mtlib -l smc0 -ql To issue an mtlib command on Linux to a 3584 library named IBMchanger0: mtlib -l IBMchanger0 -ql Volume Categories The 3494 library supports the grouping of one or more olumes into categories that can be assigned by an application and operations that can specify a category only rather than a specific olume. SCSI Medium Changers do not proide a similar function. All olumes in an SMC library are category 0000, the NULL category. 194 IBM Tape Deice Driers Installation and User s Guide

213 3494 Library Emulation Because olume categories are not supported, the following API and mtlib command options cannot be used. Applications and mtlib scripts that use these functions might require changes. Resere category mtlib -r option Release category mtlib -R option Change a olume category mtlib -C option Set category attribute mtlib -S option Assign a category mtlib -k option Mount from a category mtlib -m -s option Asynchronous Library Operations The 3494 library performs all mount, demount, audit, and eject operations asynchronously and initially returns a request id to the host for the operation. The request id can then be queried at any time to determine if the operation is still pending, completed, or is unknown. SMC libraries perform these operations synchronously and do not support a request id. An application can select to wait for an asynchronous operation to complete by setting the API wait_flg to one or using mtlib without the -n option. The operation is synchronous on both a 3494 and SMC library and no request id is returned to the application. These applications and mtlib scripts do not require any changes. If an application selects to not wait for an asynchronous operation to complete by setting the API wait_flg to zero or using mtlib with the -n option, the operation on an SMC library is still synchronous and request id 0 is returned to the application. Most applications and scripts do not use the return request id to determine when the operation completes and use the no wait option for performance only. For example, using the no wait option on a demount operation so the application can continue while the library is demounting the olume. These applications and mtlib scripts do not require any changes but do take the same amount of time as using the wait option. Applications that use the Query Message ID or mtlib -i option to determine when the return request id operation completes may require changes, such as polling for a mount issued with the no wait option since any request id is always unknown on an SMC library because the operation has already completed. Performance Considerations The performance time of mtlib commands issued to a SCSI 3584 library ersus a 3494 ary and some performance times may be significantly higher. The mtlib commands such as -qv and -qi for example that require reading all the slot information from the library also ary in the amount of time it takes for the command to complete. The fewer the number of slots that are in the library, the shorter time it takes to complete the mtlib command and a larger number of slots in the library takes longer. Chapter Enterprise Tape Library Support 195

214 AIX 3494 Enterprise Tape Library Drier AIX The software consists of an Automated Tape Library Deice Drier (atldd), an application daemon (lmcpd) that communicates with the 3494 Library Manager (LM), and a utility program (mtlib), which proides a command-line interface to the library. Either an Ethernet or Token-Ring LAN or an RS-232 serial connection can be used for the physical connection between the host and the 3494 LM. The daemon, known to AIX specifically as the IBM Library Manager Control Point Daemon (lmcpd), communicates with tape libraries defined in a configuration file. This file, ibmatl.conf, is placed in the /etc directory when the software package is installed. Customization of this file is described in Defining Tape Libraries to the Daemon on page 198. A typical enironment for the AIX 3494 Enterprise Library Drier is an RS/6000 or System p (also known as pseries) serer on a local area network (LAN) with SCSI- or fibre-attached tape dries proiding backup and restore functions. Data Flow The software described in this chapter coers the library deice drier and the interface between the application and the library deice drier. For more information refer to Figure 37. Figure 37. Data Flow for AIX 3494 Enterprise Tape Library Drier Product Requirements The following hardware and software components are supported by IBM. 196 IBM Tape Deice Driers Installation and User s Guide

215 AIX 3494 Enterprise Tape Library Drier Hardware Requirements The library drier supports the following hardware: One of the following options, depending on the connection (RS-232 or LAN) required for the Library Manager: RS-232: One standard 25 pin null modem D-shell RS-232 cable (maximum of meters [50 feet]) LAN: - Token Ring or Ethernet Adapter support in an RS/6000 or pseries workstation attached to the Library Manager - LAN cabling (as required) IBM System Storage TS1120 Tape Drie Model EO5 IBM System Storage TS1130 Tape Drie Model E Tape Drie Model J1A Software Requirements The following software is required for the library drier: AIX 5L, Version 5.3, and later releases on IBM POWER-based serers. AIX Tape and Medium Changer Deice Drier (Atape) To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317 Installation Instructions Use the standard set of AIX methods to install and configure the LMCP deices. You must hae root authority to perform these operations. Installation Procedure Refer to Appendix A, Accessing Documentation and Software Online, on page 317 for information on obtaining the latest ersions of the deice drier and the latest documentation. Enter the following command to list the currently installed ersion of the 3494 Enterprise Library Drier: lslpp -l atldd.drier Connecting the IBM TotalStorage Enterprise Tape Library If a TTY connection is needed, use a standard 25 pin null modem D-shell RS-232 cable to connect the workstation to the 3494 Enterprise Tape Library. Place the cable on the natie serial port or on the eight port or 16 port asynchronous adapter. If a LAN connection is needed, connect the LAN cable from the Token Ring or Ethernet adapter card in the workstation to the 3494 Tape Library. Note: The cable (RS-232 or LAN) must be in place before the software is installed to ensure proper initialization of the drier. Configuring the Serial Port After the 3494 Tape Library is connected to the workstation, you must configure the serial port to which it is connected. Use smit to configure the serial port. Enter the following command: Chapter Enterprise Tape Library Support 197

216 AIX 3494 Enterprise Tape Library Drier smit tty Select the following options: 1. TTY Menu: Add a tty deice. 2. Selection Menu: Select the appropriate parent serial adapter. 3. Add TTY Menu: Enter the port number. Press F4 to generate a list of possible alues. 4. Add TTY Menu: Set baud rate to Add TTY Menu: eight data bits, one stop bit, no parity. 6. Add TTY Menu: Set Enable program to Off. Press F4 to generate a list of possible alues. 7. Add TTY Menu: Set Enable LOGIN to disable. Use the Tab key to toggle the alue. 8. Press the Return key to configure the tty deice. Repeat steps 1 through 8 for each tape library connected to the workstation. Configuring the IBM 3490E or TotalStorage 3590 Tape Drie To operate the 3494 Enterprise Tape Library successfully through the configured LMCPs, you must configure all 3490E or 3590 tape dries in the 3494 Tape Library. Refer to Configuring the Library Manager Control Point on page 199 for instructions. Defining Tape Libraries to the Daemon After the software is installed and the desired tape libraries are connected to the system, the /etc/ibmatl.conf file must be edited to define the tape libraries to the lmcpd. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each library. The symbolic names must be unique across all libraries defined in the /etc/ibmatl.conf file. Connection type is used to define the type of connection to the library (either RS-232 or TCP/IP). For RS-232 connections, this type is the deice special file name of the tty deice (for example, /de/tty0 or /de/tty1). For TCP/IP connections, this type is the IP address of the Library Manager. If the Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first IP address. Note: Ensure that duplicate IP addresses are not used in this file or unpredictable results can occur. Identifier is used to specify a name by which the Library Manager identifies the host machine. This identifier has a maximum of eight characters. The host name of the workstation is usually the best name to use (although it is not necessary). This parameter is used only to identify a particular host to the 3494 Enterprise Library Manager. Alternate LAN Connection is used to specify an alternate IP address for a 3494 High Aailability LAN attached configuration. If the High Aailability Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. 198 IBM Tape Deice Driers Installation and User s Guide

217 AIX 3494 Enterprise Tape Library Drier Note: For RS-232 attachments, the alternate LAN connection is not applicable. Failoer for RS-232 connections proceeds oer the single serial line. The following examples show how to define the library name: libmgrc7 /de/tty0 mercury This stanza defines the libmgrc7 library connected by /de/tty0 to the workstation. The library uses the mercury identifier for the host. libmgrc jupiter This stanza defines the libmgrc8 library connected through TCP/IP to the workstation. The address of the Library Manager on the 3494 Tape Library is The library uses the jupiter identifier for the host. libmgrc telos This stanza defines the libmgrc9 High Aailability library connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are and libmgrc mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The first address of the Library Manager on the 3494 Tape Library is and the second address is The library uses the mercury identifier for the host. The following stanza defines the libmgrc7 High Aailability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are and The IP addresses of the second Library Manager are and The library uses the mercury identifier for the host. libmgrc mercury Configuring the Library Manager Control Point After the drier is installed, a tape library is connected to the workstation, and the serial port is configured, you can configure the instances of the LMCP. Perform the following procedure to define and configure the LMCP: 1. Enter the following command: smit The system management interface tool (smit) main menu is displayed (refer to Figure 38). Chapter Enterprise Tape Library Support 199

218 AIX 3494 Enterprise Tape Library Drier System Management Moe cursor to desired item and press Enter. Software Installation and Maintenance Deices Physical & Logical Storage Security & Users Diskless Workstation Management & Installation Communications Applications and Serices Spooler (Print Jobs) Problem Determination Performance & Resource Scheduling System Enironments Processes & Subsystems Applications Using SMIT (information only) F1=Help F2=Refresh F3=Cancel F8=Image F9=Shell F10=Exit Enter=Do Figure 38. SMIT Main Menu 2. Select Deices (item 2) from the smit main menu. Use the up ( ) arrow and down ( ) arrow keys to moe the cursor to the desired item on the menu. Press Enter or click Do if you are processing smit in a windowed enironment. 3. Select Tape Drie from the Deices menu (refer to Figure 39). Deices Moe cursor to desired item and press Enter. Configure Deices Added after IPL Printer/Plotter TTY Asynchronous Adapters PTY Console Fixed Disk CD ROM Drie Optical Disk Drie Diskette Drie Tape Drie Figure 39. SMIT Deices Menu The Tape Drie menu is displayed (refer to Figure 40). 200 IBM Tape Deice Driers Installation and User s Guide

219 AIX 3494 Enterprise Tape Library Drier Tape Drie Moe cursor to desired item and press Enter. List All Defined Tape Dries List All Supported Tape Dries Add a Tape Drie Change / Show Characteristics of a Tape Drie Remoe a Tape Drie Configure a Defined Tape Drie Generate Error Report Trace a Tape Drie Figure 40. SMIT Tape Drie Menu 4. Select Add a Tape Drie from the Tape Drie menu (Figure 40). The Tape Drie Type menu is displayed (refer to Figure 41). 5. Select the Library Manager control point from the Tape Drie Type menu (refer to Figure 41). Tape Drie Type Moe cursor to desired item and press Enter. 8mm scsi 2.3 GB 8 mm Tape Drie 9trk scsi 1/2 Inch 9 Track Tape Drie 150mb scsi 150 MB 1/4 Inch Tape Drie ost scsi Other SCSI Tape Drie drie Tape Drie drie Tape Drie drie Tape Drie atl library LAN/TTY Library Manager Control Point Figure 41. Tape Drie Type Menu The Add an LMCP Logical Deice menu is displayed (refer to Figure 42). The Logical Name field for the Library Manager control point is optional. If the field remains blank, a unique name is assigned automatically. The assigned name is lmcpn, where: n is a number that indicates the LMCP entry and starts with zero for the first LMCP defined. The Library Name field must be one of the library names defined in the /etc/ibmatl.conf file. Refer to Defining Tape Libraries to the Daemon on page 198 for a description of this file. The Command Timeout in Minutes field is optional and is used to specify the maximum amount of time an application waits for commands to complete, including mount and demount commands. The default is to wait foreer until the command completes. Add an LMCP Logical Deice Type or select alues in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] Logical Name of LMCP (optional) [] Library Name (F4 to list library names) [libmgrc7] + Command Timeout in Minutes [] Figure 42. Add an LMCP Logical Deice Menu Chapter Enterprise Tape Library Support 201

220 AIX 3494 Enterprise Tape Library Drier 6. The COMMAND STATUS window opens with the Command: OK status. The logical name of the Library Manager control point is displayed as Defined (refer to Figure 43). COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. lmcp0 Defined Figure 43. LMCP COMMAND STATUS Window 7. Repeat steps 4 through 6 to define any additional Library Manager control points. 8. Return to the smit Tape Drie menu (refer to Figure 40). 9. Select Configure a Defined Tape Drie from the smit Tape Drie menu. A list of LMCP deices is displayed (refer to Figure 44). Tape Drie Moe cursor to desired item and press Enter. rmt0 Aailable S GB 8 mm Tape Drie rmt1 Defined IBM SSD 3490E Tape Drie lmcp0 Defined LAN/TTY Library Manager Control Point F1=Help F2=Refresh F3=Cancel F8=Image F10=Exit Enter=Do Figure 44. Configure an LMCP Selection List 10. Select a defined Library Manager control point to configure from the LMCP Selection list. The COMMAND STATUS window opens with the Command: OK status, and the Library Manager control point is shown as Aailable (refer to Figure 45). COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. lmcp0 Aailable Figure 45. Configure a Defined LMCP COMMAND STATUS Window 11. Cancel the COMMAND STATUS window by pressing F3. The LMCP Selection window opens again. 12. Continue selecting the Library Manager control points for configuration until all the deices are configured. 13. Exit from the smit menu. You hae completed the configuration of Library Manager control points to the system. Loading the Daemon The lmcpd is loaded during the system initialization. During the initial installation of the drier, you must load the daemon manually using the following command: 202 IBM Tape Deice Driers Installation and User s Guide

221 AIX 3494 Enterprise Tape Library Drier cfgmgr You can access the 3494 Enterprise Tape Library after the aboe command is executed. To erify that the daemon is loaded correctly, enter the following command: ps -efa grep lmcpd You can see multiple instances of the daemon running (which is typical), but only one instance has a parent process ID of 1. Deconfiguring the Library Manager Control Point In the following examples, replace the letter n with the appropriate number for the chosen deice. Deconfigure the LMCP deice using one of the following procedures: 1. The first method deconfigures the deice but leaes the deice defined in the configuration database. It is similar to taking the deice offline. Enter the following command to deconfigure the /de/lmcpn deice but leae it defined in the deice database: rmde -l lmcpn 2. The second method takes the deice offline and remoes the deice definition from the deice database. Enter the following command: rmde -l lmcpn -d The deice drier modules are not unloaded from the kernel until the last tape deice is deconfigured. Uninstall Procedure All deices using the atldd drier must be closed and not in use when atldd is uninstalled or the uninstall fails. You can uninstall the atldd using the smit command menu to uninstall software and selecting atldd.drier or use the following installp command: installp -u atldd.drier Special Files After the drier is installed and a Library Manager control point is configured and made aailable for use, access is proided through the special files. These special files are in the /de directory. Each instance of an LMCP has exactly one special file (for example, /de/lmcp0) associated with it Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to an AIX system. The procedure assumes that your deice is defined as /de/lmcp0. 1. Open an AIX window. 2. Enter mtlib -l /de/lmcp0-qi 3. Enter mtlib -l /de/lmcp0 -ql Problem Determination A set of tools is proided with the deice drier to determine if it is functioning correctly. The standard AIX interface is proided for problem determination. Chapter Enterprise Tape Library Support 203

222 AIX 3494 Enterprise Tape Library Drier Error Logging The drier proides logging to the system error log for arious errors. View the error log using the smit or the errpt command. The error templates follow the same form as the default AIX error log entries. AIX Deice Drier Trace Facility The AIX trace facility is supported for the deice drier. The trace eent is identified with a hookword. The hookword used by the deice drier is 426. The trace can be initiated at any time before an operation on a tape deice. Enter the following command to start the trace: trace -a -j 426 This command starts the trace in the background and collects only the trace eents with the 426 hookword. Enter the following command to stop the trace: trcstop This command stops the trace after the tape operations are performed. Enter the following command to iew the trace: trcrpt > lmcp.trace.out This command formats the trace output into a readable form and places it in a file for iewing. The /etc/lmcp.trcfmt file is installed into /etc during installation. It proides the formatting statements needed by trcrpt. Daemon Trace Facility The following trace facility is aailable for the lmcp daemon and deice drier: trcatl -[ald] Arguments: -a (trace all libraries defined in /etc/ibmatl.conf) -l <name> (name of library) -d (delete all log files; requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence oer the -l argument. 204 IBM Tape Deice Driers Installation and User s Guide

223 HP-UX 3494 Enterprise Tape Library Drier HP-UX The software consists of a daemon that communicates directly with the Library Manager of the 3494 Enterprise Tape Library through Ethernet or Token Ring LAN, a utility program that proides a command-line interface to the daemon and a C object module that can be linked with user applications to proide a communication interface with the daemon. Note: In the HP-UX operating system, this is a program that runs unattended in the background to perform a standard serice. Some daemons are triggered automatically to perform their task, others operate periodically. This software is known as a drier throughout this document because it proides the software and interface necessary to drie the 3494 Tape Library. Howeer, the product does not consist of a deice drier in the true sense of the term. That is, it is not an extension of the operating system kernel, such as a SCSI tape deice drier. A typical enironment for the HP-UX Automated Tape Library Drier is an HP workstation that acts as a data serer on a network with SCSI tape deices proiding backup or restore and data serer functions. The Library Manager control point daemon (lmcpd) is proided in the package. The lmcpd is a process that is always running on the system. It proides direct communication with the 3494 Enterprise Library Manager. An application links with the supplied C object module using the interface described in the IBM Tape Deice Driers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the arious library operations using standard UNIX namespace sockets. The lmcpd communicates with the Library Manager through TCP/IP. The /etc/ibmatl.conf configuration file is used to define the attachment for each library. Refer to Defining the Symbolic Name to the lmcpd on page 221 for more information. Data Flow The software described in this chapter coers the library drier. The interface between the application and the library drier is described in the IBM Tape Deice Driers: Programming Reference. Figure 47 on page 213 illustrates the data flow. Chapter Enterprise Tape Library Support 205

224 HP-UX 3494 Enterprise Tape Library Drier Tape Deice Drier Adapter Deice Drier Physical Tape Drie Application C Object Module LMCPD TCP/IP Library Manager a Figure 46. Data Flow for HP-UX 3494 Enterprise Tape Library Drier Product Requirements The following software and hardware are required to use this product. Hardware Requirements The following hardware is required for the library drier: 3494 Enterprise Tape Library with 3590 dries in HP-UX 11.0, 11i 1 and 2 and 3592 dries in 11.0, 11i 1, 2 and 3. IBM Virtualization Engine TS7510 and TS7520 in HP-UX 11.0, 11i 1 and 2 Enterprise Model B10, B18, and B20 Virtual Tape Serer (direct attached only) One of the following options depending on which LAN connection is used for the Enterprise Library Manager: Token-Ring Attach: Enterprise FC 5219 (Token-Ring Adapter) Token-Ring adapter card for HP workstation Token-Ring cables (as required) Ethernet Attach: Enterprise FC 5220 (Ethernet Adapter) Ethernet port or adapter for HP workstation Ethernet cables (as required) Software Requirements The following software is required for the library drier: HP-UX Version 10.20, 11.0, 11i 1, 2, and 3 IBM Tape and Medium Changer Deice Drier for HP-UX To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page IBM Tape Deice Driers Installation and User s Guide

225 HP-UX 3494 Enterprise Tape Library Drier Software Compatibility The following optional software is supported by the library drier: IBM Tioli Distributed Storage Manager for HP-UX Installation Instructions This chapter describes how to install, configure, and uninstall the HP-UX Automated Tape Library Support for the 3494 Enterprise Tape Library. The IBM Tape Library drier for HP-UX is installed using the standard swinstall process. The IBM Tape Library Drier for HP-UX is the lmcpd package. Installation Oeriew LAN support must exist on the machine before installing the IBM Tape Library drier for HP-UX. Install and configure the LAN support before proceeding with the installation of the lmcpd package. For more information, refer to the HP-UX documentation appropriate for the LAN support that you are using. 1. Copy the software from the distribution medium to the depot. 2. Check the README file and erify that your system is configured appropriately for installing the lmcpd software. 3. Install and configure the software. You must hae root authority to perform this installation procedure. The distribution diskette contains a swinstall process that includes the lmcpd daemon with other associated files and utilities. Command Sequence Information Please take note of the following facts about the command sequences described in this section: In some of the examples, filenames gien on the command line must be referenced with an absolute path. Using 'pwd'/filename to reference a file instead of filename ensures this. All the SD commands (for example, swinstall, swcopy) can be run initially with the '-p' flag to preiew the command. After obsering the preiew output, you can reissue the command without the '-p' flag to perform the actual operation. The SD commands are moderately complex scripts that usually proceed in seeral steps. The steps are typically Selection, Analysis, and Execution. Each step may produce useful information and error messages, so it is a good idea to obsere carefully the results of the installation process as it occurs. If you run into unexpected results during the installation, check the associated log file. Note: If an earlier ersion of the product is installed on the machine, execute the uninstall procedure before you enter the following commands. Refer to Uninstall Procedure on page 223 for more information. The following files are installed on the system: /etc/lmcpd (Library Manager control point daemon) /etc/ibmatl.conf (configuration file) /usr/lib/libibm.o (32 bit application interface object module) /usr/lib/libibm64.o (64 bit application interface object module) /usr/lib/libibmz.0 (32 bit application interface object module with +z option) Chapter Enterprise Tape Library Support 207

226 HP-UX 3494 Enterprise Tape Library Drier /usr/lib/libibm64z.0 (64 bit application interface object module with +Z option) /usr/lib/libibm_ia64.0 (64 bit application interface object module with +z option for Itanium system) /usr/lib/libibm_ia64z.0 (64 bit application interface object module with +Z option for Itanium system) /usr/include/sys/mtlibio.h (application interface header file) /usr/bin/mtlib (tape library drier utility program) /usr/bin/intlib64 (64 bit tape library drier utility program) /usr/bin/mteent (tape library drier utility program) /usr/bin/trcatl (tape library drier diagnostic program) /opt/lmcpd (subdirectory) /opt/lmcpd/ibmatl.conf (backup configuration file) Note: If this is an update of the lmcpd package, the existing /etc/ibmatl.conf file is presered. It is not oerwritten. A copy of ibmatl.conf is also installed in the /opt/lmcpd directory. Install the Product Manually Installing the product manually requires two steps, detailed in the following sections: 1. Copy the Software to the Software Depot on page Install the Product on page 208 Copy the Software to the Software Depot Attention: If you do not copy the lmcpd software into a depot, you cannot easily uninstall the software. Copy the appropriate drier to the Software Depot. For example: # swcopy -p -s /drier_location/lmcpd.hpux.x.x.x.x lmcpd (preiew option) # swcopy -s /drier_location/lmcpd.hpux.x.x.x.x lmcpd Use swlist to erify that the lmcpd software is in the depot: # swlist -d lmcpd Install the Product When the software is in the depot, the lmcpd software can be installed to the root file system using the HP-UX swinstall command. The following commands install lmcpd from the depot to the default root file system: # swinstall -p lmcpd (preiew option) # swinstall lmcpd Use swlist to list the software installed on the default root file system as follows: # swlist lmcpd Verify correct installation to the default root file system with the swerify command: 208 IBM Tape Deice Driers Installation and User s Guide

227 HP-UX 3494 Enterprise Tape Library Drier # swerify lmcpd Connecting the IBM TotalStorage 3494 Enterprise Automated Tape Library You can use a LAN connection (either Ethernet or Token Ring) through a TCP/IP connection. The connection must be in place before the software is installed to ensure proper initialization of the daemon. For each 3494 Enterprise Tape Library connected through TCP/IP, ensure that your machine has access to the Library Manager on the 3494 Enterprise Tape Library. Use the ping utility to erify that you hae network connectiity to the Library Manager. Consult your network administrator if you need help with this task. Defining the Library Deice to LMCPD After the software is installed and all desired tape libraries are connected to the system, the /etc/ibmatl.conf file must be edited to define the library deices to the lmcp daemon. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library. The symbolic names must be unique across all libraries defined in the ibmatl.conf file. Connection type defines the type of connection to the library. For TCP/IP connections, this type is the IP address of the 3494 Enterprise Library Manager. If the Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first IP address. Identifier is used to specify a name by which the Library Manager identifies the host machine. This identifier has a maximum length of eight characters. The symbolic network name of the host is usually the best name to use, although any name is acceptable. This parameter is used only to identify a particular host to the 3494 Library Manager. Alternate LAN Connection is used to specify an alternate IP address for an Enterprise High Aailability LAN configuration. If the High Aailability Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. The following examples show how to define the library name: 3494a jupiter This stanza defines the 3494a library connected to the host. The address of the Enterprise Library Manager is The tape library uses jupiter as the identifier for the host. libmgrc telos This stanza defines the libmgrc9 High Aailability library connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are and libmgrc mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The first address of the Library Manager on the 3494 Tape Library is and the second address is The library uses the mercury identifier for the host. The following stanza defines the libmgrc7 High Aailability library with dual LAN cards connected through TCP/IP to the workstation. The IP Chapter Enterprise Tape Library Support 209

228 HP-UX 3494 Enterprise Tape Library Drier addresses of the first Library Manager are and The IP addresses of the second Library Manager are and The library uses the mercury identifier for the host. libmgrc mercury Adding or Deleting Entries in the Library Deice You can add or delete entries in /etc/ibmatl.conf at any time. Howeer, changes do not take effect until the daemon is started again. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process, then enter the /etc/lmcpd command to start the daemon again. Ensure that the library actiity on all of the libraries is completed before starting the lmcpd again. Uninstall Procedure Attention: Do not try to uninstall the lmcpd software by deleting the files that make up the lmcpd fileset. It is best to use the swremoe command. Halt all library actiity before starting the uninstall procedure. Kill the lmcpd daemon if it is currently executing. To remoe the lmcpd software from the root file system enter: # swremoe -p lmcpd # swremoe lmcpd Other Administratie Tasks To determine what ersions of the lmcpd software are currently installed on the default root file system: # swlist -a state lmcpd To determine what ersions of the lmcpd software are stored in the default depot: # swlist -d state lmcpd To iew the set of files installed with the lmcpd software: # swlist -l file lmcpd To remoe the lmcpd software from the depot: # swremoe -d lmcpd If more than one leel of lmcpd exists in the depot, explicitly specify the leel to remoe it. For example: # swremoe -d lmcpd,r= Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to an HP-UX system. The procedure assumes that your deice is defined in /etc/ibmatl.conf as L Bring up a shell prompt. 210 IBM Tape Deice Driers Installation and User s Guide

229 HP-UX 3494 Enterprise Tape Library Drier 2. Enter mtlib -l L3494 -qi 3. Enter mtlib -l L3494 -ql Problem Determination A set of tools is proided with the software to determine if the lmcpd is functioning correctly. Error Logging The lmcpd uses the syslog facility to log the errors. Errors are logged according to the /etc/syslog.conf file. The lmcpd uses the daemon facility for logging errors. Only errors are logged with this facility. For more information about using syslog, refer to your system administration manuals. Daemon Trace Facility The following trace facility is aailable for the lmcpd daemon: trcatl -[ald] Arguments: -a (trace all libraries defined in /etc/ibmatl.conf) -l <name> (name of library) -d (delete all log files; requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence oer the -l argument. Chapter Enterprise Tape Library Support 211

230 Linux 3494 Enterprise Tape Library Drier Linux The software consists of a daemon that communicates directly with the Library Manager of the 3494 Enterprise Tape Library through Ethernet or Token Ring LAN, a utility program that proides a command-line interface to the daemon, and a C object module that can be linked with user applications to proide a communication interface with the daemon. Note: In the Linux operating system, this is a program that runs unattended, in the background, to perform a standard serice. Some daemons are triggered automatically to perform their task; others operate periodically. This software is known as a drier throughout this document because it proides the software and interface necessary to drie the 3494 Tape Library. Howeer, the product does not include a deice drier in the true sense of the term. That is, it is not an extension of the operating system kernel, such as a tape deice drier. A typical enironment for the Linux Automated Tape Library Drier is a Linux workstation that acts as a data serer on a network with tape deices proiding backup or restore and data serer functions. The Library Manager control point daemon (lmcpd) is proided in the package. The lmcpd is a process that is always running on the system. It proides direct communication with the Library Manager. An application links with the supplied C object module using the interface described in the IBM Tape Deice Driers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the arious library operations using standard UNIX namespace sockets. The lmcpd communicates with the Library Manager through TCP/IP. The /etc/ibmatl.conf configuration file is used to define the attachment for each library. Refer to Defining the Symbolic Name to the lmcpd on page 221 for more information. Data Flow The software described in this chapter coers the library drier. The interface between the application and the library drier is described in the IBM Tape Deice Driers: Programming Reference. Figure 47 on page 213 illustrates the data flow. 212 IBM Tape Deice Driers Installation and User s Guide

231 Linux 3494 Enterprise Tape Library Drier Tape Deice Drier Adapter Deice Drier Physical Tape Drie Application C Object Module LMCPD TCP/IP Library Manager a Figure 47. Data Flow for Linux 3494 Enterprise Tape Library Drier Product Requirements The following hardware and software components are required and supported by IBM. Hardware Requirements The following hardware is required for the library drier: IBM TotalStorage 3494 Enterprise Tape Library with IBM 3590 and 3592 dries with the Fibre Channel Attachment IBM System Storage TS1120 Tape Drie IBM Virtualization Engine TS7510 One of the following options, depending on which LAN connection is used for the Enterprise Library Manager: Token-Ring Attach: Enterprise FC 5219 (Token-Ring Adapter) Token-Ring adapter card for Linux workstation Token-Ring cables (as required) Ethernet Attach: Enterprise FC 5220 (Ethernet Adapter) Ethernet port or adapter for Linux workstation Ethernet cables (as required) Software Requirements The following software is supported by the library drier: For Linux distribution support, refer to 93 IBM Tape and Medium Changer Deice Drier (IBMtape) for Linux Chapter Enterprise Tape Library Support 213

232 Linux 3494 Enterprise Tape Library Drier To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Installation and Configuration Instructions The IBM Tape Library drier for Linux, (ibmatl), is supplied in an rpm package. The following sections describe installation, remoal, configuration, and erification procedures for ibmatl. Refer to any Linux distribution supporting rpm for rpm command information. You must hae root authority to proceed with the installation of the drier. In the subsequent pages, you will see file names with xxxx or x.x.x.x in them. The xxxx or x.x.x.x refer to the ersion of the drier, which will change as IBM releases new drier leels. Use the actual drier ersion numbers as you perform the procedures. Install and configure the LAN support before proceeding with installation of the ibmatl package. For more information, refer to the Linux documentation appropriate to the LAN support you are using. The following files are installed on your system: /etc/lmcpd (library manager control point daemon) /etc/ibmatl.conf (configuration file) /usr/lib/libibm.o (application interface object module) /usr/lib/libibm64.o (64-bit application interface object module for 64-bit IBM zseries system only) /usr/include/sys/mtlibio.h (application interface header file) /usr/bin/mtlib (tape library drier utility program) /usr/bin/mtlib64 (64-bit tape library drier utility program for 64-bit IBM zseries system only) /usr/bin/mteent (tape library drier utility program) /usr/bin/trcatl (tape library drier diagnostic program) On the IBM Linux for IBM S/390 and zseries systems, documentation files are installed at: /usr/share/doc/packages/ibmatl/readme (readme file) /usr/share/doc/packages/ibmatl/license (license file) On Red Hat Linux for Intel PC based systems, documentation files are installed at: /usr/share/doc/ibmatl-x.x.x.x/readme (readme file, where x.x.x.x is the ersion) /usr/share/doc/ibmatl-x.x.x.x/license (license file, where.x.x.x.x is the ersion) Note: If this is an update of the ibmatl package, the existing /etc/ibmatl.conf file is presered (it is not oerwritten). Installation Procedure If ibmatl is already installed on your system, refer to Updating Procedure on page 216. This section assumes that you are installing ibmatl on a system where it is not installed. Run the following command to install ibmatl rpm package: >rpm -i ibmatl.x.x.x.x.os.rpm Connecting the TotalStorage Enterprise 3494 Tape Library Use a LAN connection (either Ethernet or Token Ring) through TCP/IP. The connection must be in place before the software is installed to ensure proper initialization of the daemon. For each 3494 Tape Library connected through 214 IBM Tape Deice Driers Installation and User s Guide

233 Linux 3494 Enterprise Tape Library Drier TCP/IP, ensure that your machine has access to the Library Manager on the 3494 Tape Library. Use the ping utility to erify that you hae network connectiity to the Library Manager. Consult your network administrator if you need help with this task. Defining the Library Deice to the lmcpd After the software is installed and tape libraries are connected, the /etc/ibmatl.conf file must be edited to define the library deices to the lmcpd. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library. The symbolic names must be unique across all libraries defined in the ibmatl.conf file. Connection type is used to define the type of connection to the library. For TCP/IP connections, this type is the IP address of the 3494 Library Manager. If the Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first IP address. Identifier parameter is used to specify a name by which the Library Manager identifies the host machine. This identifier has a maximum length of 8 characters. The symbolic network name of the host is usually the best name to use, although any name is acceptable. This parameter is used only to identify a particular host to the 3494 Library Manager. Alternate LAN Connection is used to specify an alternate IP address for a 3494 High Aailability LAN configuration. If the High Aailability Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. The following examples show how to define the library name: 3494a jupiter This stanza defines the 3494a library that is connected to the host. The address of the 3494 Library Manager is The tape library uses jupiter as the identifier for the host. libmgrc telos This stanza defines the libmgrc9 High Aailability library that is connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are and libmgrc mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The first address of the Library Manager on the 3494 Tape Library is and the second address is The library uses the mercury identifier for the host. libmgrc mercury This stanza defines the libmgrc7 High Aailability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are and The IP addresses of the second Library Manager are and The library uses the mercury identifier for the host. Chapter Enterprise Tape Library Support 215

234 Linux 3494 Enterprise Tape Library Drier Adding or Deleting Entries in the Library Deice You can add or delete entries in /etc/ibmatl.conf at any time. Howeer, changes do not take effect until the daemon is started again. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process, and enter the /etc/lmcpd command to start the daemon again. Ensure that actiity on all libraries is completed before restarting the lmcpd. Updating Procedure If your current ibmatl was installed from an rpm package preiously, issue the following command: rpm -U ibmatl.x.x.x.x.s390.rpm --for IBM Linux on S/390 systems rpm -U ibmatl.x.x.x.x.i386.rpm --for Red Hat Intel PC based systems Querying the Installed Package The query function is supported for the ibmatl rpm package only. The installed rpm package can be queried by running the following commands to display information associated with the package. To display information about ibmatl: >rpm -qi ibmatl To display the package's file list, enter the command: > rpm -ql ibmatl To display the states of files in the package, for example, normal, not installed, or replaced: >rpm -qs ibmatl Verifying the Install/Update If the IBMtape deice drier is installed from the rpm package, issue the following command: >rpm -V ibmatl Starting ibmatl Start the daemon using the following command: /etc/lmcpd Uninstall Procedure Attention: Do not try to uninstall the ibmatl software simply by remoing the files that make up the ibmatl fileset. It is best to use the rpm -e command or the uninstall script. Note: Halt all library actiity before starting the uninstall procedure. For the rpm package, run the command rpm -e: rpm -e ibmatl 216 IBM Tape Deice Driers Installation and User s Guide

235 Linux 3494 Enterprise Tape Library Drier If more than one leel of ibmatl exists on the system, explicitly specify the leel to remoe it. rpm -e ibmatl Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Linux system. The procedure assumes that your deice is defined in /etc/ibmatl.conf as L Bring up a shell prompt. 2. Enter mtlib -l L3494 -ql 3. Enter mtlib -l L3494 -ql Problem Determination A set of tools is proided with the software to determine if the ibmatl is functioning correctly. Error Logging The ibmatl uses the syslog facility to log the errors. Errors are logged according to the /etc/syslog.conf file. The ibmatl uses the daemon facility for logging errors. Only errors are logged with this facility. For more information about using syslog, refer to your system administration manuals. Daemon Trace Facility The following trace facility is aailable for the lmcpd daemon: trcatl -[ald] Arguments: -a (trace all libraries defined in /etc/ibmatl.conf) -l <name> (name of library) -d (delete all log files; requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence oer the -l argument. Chapter Enterprise Tape Library Support 217

236 Solaris 3494 Enterprise Tape Library Drier Solaris The software consists of a daemon that communicates directly with the Library Manager of the 3494 Tape Library through RS-232 or LAN, a utility program that proides a command-line interface to the daemon, and a C object module that can be linked with user applications to proide a communication interface with the daemon. This software is known as a drier throughout this document because it proides the software and interface necessary to drie the Tape Library. Howeer, the product does not consist of a deice drier in the true sense of the term. That is, it is not an extension of the operating system kernel, such as a SCSI tape deice drier. A typical enironment for the IBM Sun Automated Tape Library Drier is a Sun workstation that acts as a data serer on a network with SCSI tape deices proiding backup or restore and data serer functions. The Library Manager control point daemon (lmcpd) is proided in the package. The lmcpd is a process that is always running on the system. It proides direct communication with the 3494 Library Manager. An application links with the supplied C object module using the interface described in the IBM Tape Deice Driers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the arious library operations using standard UNIX namespace sockets. The lmcpd communicates with the Library Manager either through a standard 25 pin null modem D-shell RS-232 cable or through TCP/IP. The /etc/ibmatl.conf configuration file is used to define the type of attachment for each library. Refer to Defining the Symbolic Name to the lmcpd on page 221 for more information. Data Flow The software described in this chapter coers the library drier. The interface between the application and the library drier is described in the IBM Tape Deice Driers: Programming Reference. Figure 48 on page 219 illustrates the data flow. 218 IBM Tape Deice Driers Installation and User s Guide

237 Solaris 3494 Enterprise Tape Library Drier Tape Deice Drier Adapter Deice Drier Physical Tape Drie Application C Object Module TCP/IP LMCPD Library Manager Natie TTY Deice Drier a Figure 48. Data Flow for Solaris 3494 Enterprise Tape Library Drier Product Requirements The following software and hardware are supported by this product. Hardware Requirements The following hardware is supported by the library drier: 3494 Enterprise Tape Library with SCSI-attached 3490E (Model C1A or C2A), 3590 and 3592 dries IBM System Storage TS1120 Tape Drie IBM Virtualization Engine TS7510 IBM TotalStorage Virtual Tape Serer (Models B10, B18, and B20) One of the following options depending on which connection (RS-232 or LAN) is required for the Enterprise Library Manager: RS-232: One standard 25 pin null modem D-shell RS-232 cable (maximum of meters [50 feet]) LAN: - Token-Ring or Ethernet adapter card in a Sun workstation attached to the 3494 Enterprise Library Manager - LAN cable Chapter Enterprise Tape Library Support 219

238 Solaris 3494 Enterprise Tape Library Drier Software Requirements The following software is required for the library drier: Sun Microsystems Solaris Version 2.6, 7, 8, 9, or 10 IBM Tape and Medium Changer Deice Drier for Solaris To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Software Compatibility The following optional software is supported by the library drier: IBM Tioli Distributed Storage Manager for Solaris Installation Instructions The IBM Tape Library drier for Solaris is installed using the standard Sun package facility. The IBM Tape Library Drier for Solaris is the lmcpd package. Preinstallation Considerations The LAN or TTY support must exist on the machine before installing the IBM Tape Library daemon for SunOS. Install and configure the LAN or TTY adapter and the associated LAN or TTY adapter deice drier before proceeding with the installation of the lmcpd package. For more information, refer to the documentation appropriate for the LAN or TTY adapter and the LAN or TTY adapter deice drier that you are using. You must hae root authority to perform this installation procedure. Note: If an earlier ersion of the product is installed on the machine, execute the uninstall procedure before you enter the following commands. Refer to Uninstall Procedure on page 223 for more information. The following files are installed on the system: /etc/lmcpd (Library Manager control point daemon) /etc/ibmatl.conf (configuration file) /usr/lib/libibm.o (application interface object module) /usr/lib/libibm64.o (64 bit application interface object module) /usr/include/sys/mtlibio.h (application interface header file) /usr/bin/mtlib (tape library drier utility program) /usr/bin/mteent (tape library drier utility program) /usr/bin/trcatl (tape library drier diagnostic program) /opt/lmcpd (subdirectory) /opt/lmcpd/ibmatl.conf (backup configuration file) Note: If this is an update of the lmcpd package, the existing /etc/ibmatl.conf file is presered. It is not oerwritten. A copy of ibmatl.conf is also installed in the /opt/lmcpd directory. Installation Procedure Use the following commands to install the lmcpd package. Substitute the deice special file name for the installation source deice that is appropriate for your system. 220 IBM Tape Deice Driers Installation and User s Guide

239 Solaris 3494 Enterprise Tape Library Drier If a preious ersion is installed on the system, uninstall the preious ersion first, enter the following command: /usr/sbin/pkgrm lmcpd To install the package from the directory that the drier is located, enter the following command: /usr/sbin/pkgadd -d lmcpd.x.x.x.x To erify that the installation was successful, enter the following command: /usr/bin/pkginfo lmcpd Connecting the 3494 Enterprise Tape Library Use one of the following methods to connect the workstation to the 3494 Tape Library: Use a standard 25 pin null modem D-shell RS-232 cable. Place the cable on the natie serial port or on the eight-port or 16 port asynchronous adapter. Use a LAN connection (either Ethernet or Token-Ring) through TCP/IP. In either case, the connection must be in place before the software is installed to ensure proper initialization of the daemon. For each 3494 Tape Library connected with an RS-232 cable, follow the directions in Configuring the Serial Port on page 221. For each 3494 Tape Library connected through TCP/IP, ensure that your machine has access to the Library Manager on the Enterprise deice. Use the ping utility to erify that you hae network connectiity to the Library Manager. Consult your network administrator if you need help with this task. Identify the hostname of your workstation to the Enterprise Library Manager by following the instructions in the IBM TotalStorage Enterprise Automated Tape Library Operator Guide, intheadd LAN Host section. Configuring the Serial Port After the 3494 Tape Library is connected to the workstation, you must configure the serial port to which it is connected. Set the following TTY port attributes: Baud rate: 9600 Data bits: 8 Stop bits: 1 Parity: None Defining the Symbolic Name to the lmcpd After the software is installed and all of the desired tape libraries are connected to the system, the /etc/ibmatl.conf file must be edited to define the tape libraries to the lmcpd. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library. The symbolic names must be unique across all libraries defined in the/etc/ibmatl.conf file. Connection type is used to define the type of connection to the library (either RS-232 or TCP/IP). For RS-232 connections, this type is the deice special file name of the tty deice (for example, /de/ttya or /de/tty1). For TCP/IP connections, this type is Chapter Enterprise Tape Library Support 221

240 Solaris 3494 Enterprise Tape Library Drier the IP address of the Library Manager. If the Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first IP address. Identifier is used to specify a name by which the Library Manager identifies the host machine. This identifier has a maximum length of eight characters. The host name of the workstation is usually the best name to use (although it is not necessary). This parameter is used only to identify a particular host to the 3494 Enterprise Library Manager. Alternate LAN Connection is used to specify an alternate IP address for an Enterprise High Aailability LAN-attached configuration. If the High Aailability Library has a dual lan card installed, the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. Note: For RS-232 attachments, the alternate LAN connection is not applicable. Failoer for RS-232 connections proceeds oer the single serial line. The following examples show how to define the library name: 3494a /de/ttya mercury This stanza defines the 3494a library that is connected by /de/ttya to the workstation. The library uses the mercury identifier for the host. 3494b jupiter This stanza defines the 3494b library that is connected through TCP/IP to the workstation. The address of the Library Manager on the Enterprise Tape Library is The library uses the jupiter identifier for the host. libmgrc telos This stanza defines the libmgrc9 High Aailability library that is connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are and libmgrc mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The first address of the Library Manager on the 3494 Tape Library is and the second address is The library uses the mercury identifier for the host. The following stanza defines the libmgrc7 High Aailability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are and The IP addresses of the second Library Manager are and The library uses the mercury identifier for the host. libmgrc mercury Adding or Deleting Entries in the Library You can add or delete entries in /etc/ibmatl.conf at any time. Howeer, changes do not take effect until the daemon is started again. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process, then enter the /etc/lmcpd command to start the daemon again. Ensure that the library actiity on all of the libraries is completed before restarting the lmcpd. 222 IBM Tape Deice Driers Installation and User s Guide

241 Solaris 3494 Enterprise Tape Library Drier Uninstall Procedure Halt all library actiity before starting the uninstall procedure. Kill the lmcpd daemon if it is currently executing. Enter the following command to uninstall the library support from your workstation: /usr/sbin/pkgrm lmcpd 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Sun Solaris system. The procedure assumes that your deice is defined in /etc/ibmatl.conf as L Bring up a shell prompt. 2. Enter mtlib -l L3494 -qi 3. Enter mtlib -l L3494 -ql Problem Determination A set of tools is proided with the software to determine if the lmcpd is functioning correctly. Error Logging The lmcpd uses the syslog facility to log the errors. Errors are logged according to the /etc/syslog.conf file. The lmcpd uses the daemon facility for logging errors. Only errors are logged with this facility. For more information about using syslog, refer to your system administration manuals. Daemon Trace Facility The following trace facility is aailable for the lmcpd daemon: trcatl -[ald] Arguments: -a (trace all libraries defined in /etc/ibmatl.conf) -l <name> (name of library) -d (delete all log files; requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence oer the -l argument. Chapter Enterprise Tape Library Support 223

242 Windows 3494 Enterprise Tape Library Drier Windows The software consists of a tape library serice that communicates directly with the Library Manager of the 3494 Enterprise Tape Library through LAN, a utility program that proides a command-line interface to the serice, and a static library and DLL that can be used to proide a communication interface with the serice. A typical enironment for the Windows Automated Tape Library Serice is a workstation running Microsoft Windows operating system that acts as a data serer on a network with SCSI tape deices proiding backup or restore and data serer functions. The IBM Automated Tape Library serice is proided in the installation package. This serice is installed with STARTUP=AUTOMATIC, which means that it is started when the Microsoft Windows operating system is started. An application program may access those functions through API calls. The interface is described in the IBM Tape Deice Driers: Programming Reference. The subroutines in this module communicate with the Enterprise Library Manager to perform the arious library operations. The serice communicates with the Library Manager through TCP/IP. The c:\winnt\ibmatl.conf configuration file is used to define the type of attachment for each library. Refer to Defining the Symbolic Name to the Serice on page 228 for more information. Data Flow The software described in this chapter coers the library drier. The interface between the application and the library drier is described in the IBM Tape Deice Driers: Programming Reference. Figure 49 on page 225 illustrates the data flow. 224 IBM Tape Deice Driers Installation and User s Guide

243 Windows 3494 Enterprise Tape Library Drier Figure 49. Data Flow for Windows 3494 Enterprise Tape Library Drier Product Requirements The following hardware and software components are required and supported by IBM. Hardware Requirements The following hardware is required for the library drier: 3494 Enterprise Tape Library with Enterprise Tape System 3590 and 3592 dries IBM System Storage TS1120 Tape Drie IBM Virtualization Engine TS7510 IBM TotalStorage Virtual Tape Serer (Models B10, B18, and B20) The following options are required for operation of the Enterprise Library Manager: Token-Ring or Ethernet adapter card in an Intel- compatible workstation running Microsoft Windows and attached to the 3494 Enterprise Tape Library LAN cable Software Requirements The following software is required for the library drier: A workstation running Microsoft Windows Serer 2003 A workstation running Microsoft Windows Serer 2008 IBM Windows Tape Deice Drier or the ADSM/TSM Deice Drier for Microsoft Windows NT if using ADSM/TSM Chapter Enterprise Tape Library Support 225

244 Windows 3494 Enterprise Tape Library Drier To obtain the most current serice and documentation for this software, refer to Appendix A, Accessing Documentation and Software Online, on page 317. Installation Instructions The IBM Tape Library serice for Microsoft Windows is installed by executing the install binary, which has the format ibmatl.x.x.x.x.x86.exe for 32-bit Windows 200x running on x86, ibmatl.x.x.x.x.i64.exe for 64-bit Windows 2003 running on IA64, and ibmatl.x.x.x.x.x64.exe for 64-bit Windows Serer 2003 and Windows Serer 2008 running on AMD64 and EM64T. Installation Procedure Use the following procedure to install the IBM Automated Tape Library Serice or to upgrade the software leel of your serice on your workstation. Follow these steps to perform the installation of the serice and its associated software: 1. Verify that the prerequisites are satisfied. Refer to Product Requirements on page Ensure that the workstation is on the LAN. 3. Log on as Administrator. 4. If the IBM Automated Tape Library Serice is currently installed, ensure that all programs and serices that use the serice are stopped, and then remoe it from the system. 5. Ensure that the IBM Automated Tape Library Serice is not running. On Windows NT, click the Start button, moe to Settings, then click Control Panel. Double-click the Serices icon. On Windows 2000 and 2003, click the Start button, moe to Settings, then click Control Panel. Double-click the Administratie Tools icon, then double-click the Serices icon. On Windows 2008, click the Start button, double-click the Administratie Tools icon, then double-click the Serices icon. The Serices window opens. Scroll through the entries until you find IBM Automated Tape Library. If you do not find the entry for IBM Automated Tape Library, the serice is not installed; click Close. If there is an entry and the status is blank, the serice is not running; click Close. If the status is Started, click IBM Automated Tape Library, then click Stop. On Windows NT, wait for the serice to stop and the Status to be set to blank, then click Close. On 32 bit Windows 200x, wait for the serice to stop and the Serice status to be set to Stopped, then close both windows. On 64 bit Windows, the serice is stopped and remoed automatically during the uninstallation. 6. Obtain ibmatl drier from the IBM storage FTP serer in binary. 7. Locate and execute ibmatl drier. 8. You see some windows displayed indicating the image is being unpacked and read and the InstallShield Wizard is being set up. After these are displayed, the screen stops on a window entitled Welcome to the IBM Automated Tape Library Setup Program. Follow the instructions on the window, then select Next. 9. The Software License Agreement window opens. Read the contents, then click Yes if you accept the terms. If you do not accept the terms, the installation script exits. 226 IBM Tape Deice Driers Installation and User s Guide

245 Windows 3494 Enterprise Library Serice 10. The Choose Destination Location window opens. You can accept the default destination folder by selecting Next >, or you can select Browse... and select another destination folder by following the prompts in the subsequent dialog. If you do not select the default destination folder, you must record your destination folder for future reference. After you select the folder, click Next >. 11. The Setup Complete window opens. You can check the Yes, I want to iew the Read Me file prompt to read the file, then click Finish, or just click Finish. The Read Me file is stored in the destination file that you indicated in step After you click Finish, if you did not select to iew the Read Me file, the installation dialog exits. If you chose to iew the Read Me, it is displayed. After you read it, exit the Notepad application. An informational message is displayed, indicating that the setup is complete. Click OK to exit the installation dialog. 13. Verify that you can use the ping utility successfully for any Tape Library you want to access from your workstation. 14. Update the c:\winnt\ibmatl.conf file, if necessary, with entries for each Tape Library you want to access from your workstation. Refer to Defining the Symbolic Name to the Serice on page 228 for details. 15. On Windows NT, start the serice by restarting the system or using the Serices option in the Control Panel window. On Windows 2000 and 2003, start the serice using the Serices icon, which is on the Administratie Tools icon in the Control Panel window. On Windows 2008, start the serice using the Serices icon, which is on the Administratie Tools icon. Note: When a firewall is enabled on Windows, you must allow the lmcpd program to access the network. Do not block the network IP port of 3494, which is used for communication between the 3494 library and lmcpd. For example, to allow lmcpd.exe access to the network on Windows 2008 serers, click on the Windows Firewall icon in the Control Panel window. Next, click on the button to allow a program or an exception, and then click the Add Program button. Select your browser and then select lmcpd.exe in /Windows/system32 for an x86 system or /Windows/SysWOW64 for i64 or x64 systems. Connecting the 3494 Enterprise Tape Library Use a LAN connection (either Ethernet or Token-Ring) through TCP/IP to connect the workstation to the 3494 Enterprise Tape Library. The connection must be in place before the serice is started to ensure proper initialization of the serice. Ensure that your machine has access to the Library Manager on the Tape Library. Use the ping utility to erify that you hae network connectiity to the Library Manager. Consult your network administrator if you need help with this task. Identify the hostname of your workstation to the Enterprise Library Manager by following the instructions in the IBM TotalStorage Enterprise Automated Tape Library Operator Guide, intheadd LAN Host section. Chapter Enterprise Tape Library Support 227

246 Windows 3494 Enterprise Library Serice Defining the Symbolic Name to the Serice After the software is installed and all of the desired tape libraries are connected to the system, the c:\winnt\ibmatl.conf file must be edited to define the tape libraries to the serice. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name identifies each tape library. The symbolic names must be unique across all libraries defined in the c:\winnt\ibmatl.conf file. Connection type is the IP address of the Library Manager. If the Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first IP address. Identifier specifies a name by which the Library Manager identifies the host machine. This identifier has a maximum length of eight characters. The host name of the workstation is usually the best name to use (although it is not necessary). This parameter only identifies a particular host to the Enterprise Library Manager. The following stanza defines the 3494b library that is connected through TCP/IP to the workstation. The address of the Library Manager on the 3494 Tape Library is The library uses the jupiter identifier for the host. 3494b jupiter The Alternate LAN Connection parameter specifies an alternate IP address for an Enterprise High Aailability LAN configuration. If the High Aailability Library has a dual LAN card installed, the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. The following stanza defines the libmgrc9 High Aailability library that is connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are and libmgrc telos The following stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The first address of the Library Manager on the 3494 Tape Library is and the second address is The library uses the mercury identifier for the host. libmgrc mercury The following stanza defines the libmgrc7 High Aailability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are and The IP addresses of the second Library Manager are and The library uses the mercury identifier for the host. libmgrc mercury Adding or Deleting Libraries to the Serice You can add or delete entries in c:\winnt\ibmatl.conf at any time. Howeer, changes do not take effect until the tape serice starts again. On Windows NT, stop and start the serice using the Serices option in the Control Panel window. On Windows 200x, stop and start the serice using the Serices icon, which is on the Administratie Tools icon in the Control Panel window. 228 IBM Tape Deice Driers Installation and User s Guide

247 Windows 3494 Enterprise Library Serice Ensure that the library actiity on all of the libraries is completed before starting the serice again. Uninstallation Procedure Use the following procedure to remoe the IBM Automated Tape Library Serice permanently from your workstation. Note: If you are upgrading the software leel of your serice, follow the steps in Installation Procedure on page 226. Follow these steps to uninstall the serice and its associated software: 1. Log on as Administrator. 2. Back up the c:\winnt\ibmatl.conf file if you want to keep a copy of this file because the uninstall procedure erases the file. 3. Ensure that all programs and serices that use the IBM Automated Tape Library Serice are stopped. 4. Ensure that the IBM Automated Tape Library Serice is not running. Click the Start button, moe to Settings, then click Control Panel. On Windows NT, double-click the Serices icon. On Windows 200x, double-click the Administratie Tools icon, then double-click the Serices icon. The Serices window opens. Scroll through the entries until you find IBM Automated Tape Library. If the status is blank, the serice is not running; click Close. If the status is Started, click IBM Automated Tape Library, then click Stop. On Windows NT, wait for the serice to stop and the Status to be set to blank, then click Close. On 32 bit Windows 200x, wait for the serice to stop and the Serice status to be set to Stopped, then close both windows. On 64 bit Windows, the serice is stopped and remoed automatically during the uninstallation. 5. Open a Command Prompt window, enter lmcpd -remoe, press Enter, then wait for the command to complete. Note: If you forget this step, the next time that the system is started, Microsoft Windows NT tries (unsuccessfully) to start the serice again. To resole this situation, you must reinstall the serice, then uninstall it. 6. Double-click Add/Remoe Programs in Windows NT/200x or Programs and Features on Windows 2008 in the Control Panel window. 7. Scroll to and select IBM Automated Tape Library. 8. For Windows NT, click Add/Remoe... For Windows 200x, click Change/Remoe. 9. A Confirm File Deletion window opens. Click Yes. 10. After arious dialogs run, a Remoe Programs from Your Computer window opens, which indicates the components that were remoed successfully. Click OK to exit the dialog. 11. For Windows NT, click Cancel on the Add/Remoe Programs Properties window. For Windows 2000 and 2003, close the Add/Remoe Programs Properties window. For Windows 2008, close the Programs and Features window. Chapter Enterprise Tape Library Support 229

248 Windows 3494 Enterprise Library Serice 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Windows system. The procedure assumes that your deice is defined in c:\winnt\ibmatl.conf as L Open a Windows command shell window. 2. Enter mtlib -l L3494 -qi 3. Enter mtlib -l L3494 -ql Problem Determination A tracing tool is proided with the software to determine if ibmatl is functioning correctly. Daemon Trace Facility The following trace facility is aailable for the ibmatl serice: trcatl -h usage: trcatl [-ald] [-l <name>] name of library [-a] all libraries defined in c:\winnt\ibmatl.conf [-d] delete all logfiles in c:\winnt\ Notes: 1. Run trcatl in the window of "Command Prompt" 2. The "-a" parameter takes precedence oer the "-l" parameter. 3. The trace.out is located under the directory where the trcalt runs Examples: trcatl -l libmgrc7 trcatl -a > trace.out 230 IBM Tape Deice Driers Installation and User s Guide

249 Chapter 9. IBM Tape Diagnostic Tool (ITDT) Purpose Accessing ITDT Supported Systems Standard Edition (ITDT-SE) Graphical Edition (ITDT-GE) Supported Equipment Standard Edition - Installation Installing ITDT-SE on Windows Operating Systems Installing ITDT-SE on i5/os Operating Systems 236 Installing ITDT-SE on Other Supported Operating Systems Standard Edition - Initial Startup Starting ITDT-SE on Solaris Operating Systems 240 Starting ITDT-SE on Windows Operating Systems Starting ITDT-SE on i5/os Operating Systems 242 Starting ITDT-SE on Other Supported Operating Systems Standard Edition - Known Issues and Limitations 243 AIX Operating Systems HP-UX Operating Systems Linux Operating Systems Solaris Operating Systems Windows Operating Systems i5/os Operating Systems All Supported Operating Systems Standard Edition - Start Menu Commands Standard Edition - Scan Menu Commands Scan Test Dump Firmware Update Encryption Full Write Tape Usage Other System Test Library Self-Test Manual Inspect Return Standard Edition - Tapeutil Menu Commands [1] Open a Deice [2] Close a Deice [3] Inquiry [4] Test Unit Ready [5] Resere Deice [6] Release Deice [7] Request Sense [8] Log Sense [9] Mode Sense [10] Query Drier Ver. (Version) [11] Display All Paths [20] Rewind [21] Forward Space File Marks [22] Backward Space File Marks [23] Forward Space Records [24] Backward Space Records [25] Space to End of Data [26] Read and Write Tests [27] Read or Write Files [28] Erase [29] Load Tape [30] Unload Tape [31] Write File Marks [32] Synchronize Buffers [33] Query/Set Parameter [34] Query/Set Tape Position [35] Query Encryption Status [36] Display Message [37] Report Density Supp (Support) [38] Test Encryp. Path (Test Encryption Key Path/Setup) [39] Config. TCP/IP Port [50] Element Information [51] Position to Element [52] Element Inentory [53] Exchange Medium [54] Moe Medium [55] Initialize Element Status [56] Preent/Allow Medium Remoal [57] Initialize Element Status Range [58] Read Deice IDs [59] Read Cartridge Location [70] Dump/Force Dump/Dump [71] Firmware Update Standard Edition - Tapeutil Scripting Commands 271 allow deinfo inquiry logpage loop modepage preent print qrypath qryersion release reqsense resere resetdrie sleep tur pd append bsf bsr density display erase fsf fsr Copyright IBM Corp. 2007,

250 IBM Tape Diagnostic Tool getparms load logsense qrypos qrytcpip read rewind rtest rwtest seod setparm setpos settcpip sync unload weof write wtest audit cartridgelocation elementinfo exchange inentory moe position dump ekmtest encryption ucode Deprecated Commands Standard Edition Scripting Commands: Known Limitations and Deiations Graphical Edition - Installation Windows Linux Graphical Edition - Known Issues and Limitations 288 Linux Windows All Supported Operating Systems Graphical Edition - User Interface Description Graphical Edition - Scan Menu Commands Scan Test Dump Firmware Update Encryption Full Write Tape Usage System Test Library Diagnostic Self-Test Manual Inspection Record Entry Graphical Edition - Tapeutil Menu Commands Open Close Inquiry Test Unit Ready Resere Deice Release Deice Request Sense Log Sense Mode Sense Query Drier Version Display All Paths Rewind Forward Space Filemarks Backward Space Filemarks Forward Space Records Backward Space Records Space to End of Data Read and Write Tests Read or Write Files Erase Load Tape Unload Tape Write Filemarks Synchronize Buffers Query/Set Parameter Query/Set Position Query Encryption Status Display Message Report Density Support Test Encryption Path Element Information Position to Element Element Inentory Exchange Medium Moe Medium Initialize Element Status Preent/Allow Medium Remoal Initialize Element Status Range Read Deice IDs Read Cartridge Location Dump/Force Dump/Dump Firmware Update This chapter describes the IBM Tape Diagnostic Tool. Purpose The IBM Tape Diagnostic Tool (ITDT) is aailable in two ersions: Standard Edition (ITDT-SE) - This is a command line ersion. Graphical Edition (ITDT-GE) - This is a GUI ersion for the following: Microsoft Windows operating systems Linux operating systems 232 IBM Tape Deice Driers Installation and User s Guide

251 IBM Tape Diagnostic Tool Both ersions proided the user with a single diagnostic program for tapeutil applications. Both SE and GE contained tapeutil functionality with SE also proiding scripting capability. Note: The term tapeutil is a synonym for the tool that was deliered with the deice drier. For example, this tool was named tapeutil on Unix operating systems; it was named ntutil on Microsoft Windows operating systems. The aailable adanced operations proided by the IBM Tape Diagnostic Tool was performed on Tape Dries and Tape Libraries. By using this functionality, the customer performed maintenance tasks and ran diagnostic tasks to determine tape drie issues. This significantly reduced product downtime and increased productiity. The IBM Tape Diagnostic Tool is designed to: Run quick or extended diagnostics on tape dries Inoke tape library self-test operations Retriee dumps from tape dries and libraries Perform a firmware update on tape dries or libraries Test the performance of the enironment by completely writing a cartridge and measuring performance Verify tape drie compression Measure system performance Retriee and display cartridge usage information Verify the encryption enironment This test is used to erify if data on the cartridge was actually written encrypted. Scan the system to discoer all supported tape and library deices. Perform a connection test This test is used to erify that all deices are attached properly Perform a sequence of sub-tests to check if the tape deice is defectie and output a pass/fail result Note: When this test is performed, all data on the cartridge is oerwritten. Perform a full write function This function writes the entire cartridge, oerwriting all preious data with a selectable block size containing either compressible or incompressible data and then outputs performance data. Note: When this test is performed, all data on the cartridge is oerwritten. Perform a system test Write different block sizes with compressible and incompressible data and then outputs performance data. Note: When this test is performed, all data on the cartridge is oerwritten. Perform a tape usage function to retriee statistical data and error counters Perform a manual inspect function for deices not recognized. The ITDT-SE proides the most important functions of the preious tapeutil tools. As an extension of the current tapeutil ariants, the set of operations and functions Chapter 9. IBM Tape Diagnostic Tool (ITDT) 233

252 IBM Tape Diagnostic Tool Accessing ITDT aailable with ITDT-SE is identical across all supported operating systems (unless a particular function is not aailable on a particular system). Dedicated deice driers for tapes and libraries may be installed on the target system and there is usually an application installed that uses the tape/library deices. When this configuration exists, ITDT-SE can coexist with the application so that when the application disables the deice internally, ITDT-SE can perform the diagnostics on that deice. One option to access ITDT is through Appendix A, Accessing Documentation and Software Online, on page 317. When downloading an IBM drier there is a corequisite to download ITDT so that you will hae this tool aailable for your use if it is needed. Supported Systems You can also naigate to the ITDT Web page: 1. Go to the Tape Support page: tape. 2. Under Product: select your product. 3. On the right side, click Download. 4. In the Tool/Utility section, click Software, then choose the latest ersion of ITDT for your product. ITDT is supported on the following systems. Standard Edition (ITDT-SE) The Standard Edition (ITDT-SE) is supported on the following: AIX operating systems (64-bit pseries/system p) AIX 5L 5.3 AIX 6.1 HP-UX operating systems HP-UX Version 11i 1, 2 and 3 (64-bit PA-Risc and Itanium) Linux operating systems Linux systems with Kernel 2.6, glibc and later (32-bit x86) Linux systems with Kernel 2.6, glibc and later (64-bit x64) Linux systems with Kernel 2.6, glibc and later (64-bit IA-64) Linux systems with Kernel 2.6, glibc and later (64-bit pseries/system p) Linux systems with Kernel 2.6, glibc and later (64-bit zseries/system z) Macintosh OS X Mac OS X and later (Leopard) (Intel, 32-bit) Mac OS X Serer and later (Intel, 32-bit) Mac OS X 10.6 (Snow Leopard) and later (Intel, 32 and 64-bit) Mac OS X Serer 10.6 and later (Intel, 32 and 64-bit) Solaris operating systems Solaris Version 9 and 10 (64-bit SPARC and 64-bit x64) Windows operating systems 234 IBM Tape Deice Driers Installation and User s Guide

253 IBM Tape Diagnostic Tool Microsoft Windows Serer 2003, Microsoft Windows Serer 2008 (32-bit x86) Microsoft Windows Serer 2003, Microsoft Windows Serer 2008 (64-bit x64) Microsoft Windows Serer 2003, Microsoft Windows Serer 2008 (64-bit i64) i5/os V5R3, V5R4 and IBM i 6.1 (iseries/system i) Graphical Edition (ITDT-GE) The Graphical Edition (ITDT-GE) is supported on the following: Supported Equipment Windows operating systems Microsoft Windows Serer 2003/2008 (32-bit x86) Microsoft Windows Serer 2003/2008 (64-bit x64) [with a 32-bit JVM]. Linux operating systems Linux Distributions with Kernel 2.6, glibc and later (x86) The following equipment is supported for both the Standard Edition (ITDT-SE) and the Graphical Edition (ITDT-GE): IBM Ultrium 3580 Tape Drie (Generation 3, 4 and 5) IBM Ultrium Tape Dries T800/F, T800V, T1600/F, T3000V/P IBM System Storage 3588/TS1030 model F3A and F3B Tape Drie IBM System Storage 3588/TS1040 model F4A Tape Drie IBM System Storage 3588/TS1050 model F5A Tape Drie IBM System Storage 3580 Half Height/TS2230 and TS2240 Tape Drie Express IBM System Storage TS2250 Tape Drie IBM System Storage TS2340 Tape Drie Express IBM System Storage TS2350 Tape Drie IBM System Storage 3592/TS1120/TS1130 Enterprise Tape System IBM System Storage 3572/TS2900 Tape Library Express IBM System Storage 3573/TS3100 and TS3200 Tape Library Express IBM System Storage 3576/TS3310 Tape Library IBM System Storage 3577/TS3400 Tape Library IBM System Storage 3584/TS3500 Tape Library The following equipment are supported System x LTO Tape dries. These dries are not tested by the IBM System Storage Test Lab. They are also not supported by IBM System Storage support. All queries are to be addressed to IBM System x support. IBM Full High LTO Gen 1, p/n 00N8016, replacement p/n 37L5799 IBM Full High LTO Gen 2, p/n 59P6744, replacement p/n 71P9141 IBM Full High LTO Gen 3, p/n 25R0012 and 39M5657, replacement p/n 25R0003 and 23R4808 IBM Half High LTO Gen 3, p/n 43W8478, replacement p/n 23R7036 IBM Half High LTO Gen 4, p/n 44E8895, replacement p/n 45E1125 IBM Half High LTO Gen XXX Library and Autoloader IBM Full High LTO Gen 1, p/n 09N4048* 4560-SLX IBM Full High LTO Gen 2, p/n 71P9146* LX IBM Full High LTO Gen 2 Chapter 9. IBM Tape Diagnostic Tool (ITDT) 235

254 IBM Tape Diagnostic Tool LX IBM Full High LTO Gen 3 SCSI (p/n 42C3942 and 40K2573) and Fibre (p/n 40K2575)* LX IBM Full High LTO Gen 3 SCSI (p/n 40K2596) and Fibre (p/n 42D8769)* Note: *Please refer to Retain tip H External document link: docdisplay?lndocid=migr &brandind= All other System x LTO tape dries are not supported by ITDT. Note: Replacement part numbers are only gien for the stand alone IBM LTO tape dries. For i5/os operating systems, see i5/os Operating Systems on page 245 for product support limitations. Standard Edition - Installation This section describes the installation procedures for the Standard Edition of ITDT in arious operating systems. Attention: Before using the IBM Tape Diagnostic Tool Standard Edition (ITDT-SE) with the IBM Tape Deice Drier, we recommend upgrading to the latest aailable IBM Tape Deice Drier leel. The [U] Tapeutil option will only work if the IBM Tape Deice Drier is installed. The -force-generic-dd startup option to bypass the IBM Tape Deice Drier has no effect on the [U] Tapeutil option commands; they will still use the IBM Tape Deice Drier if it is installed. In a System Managed Encryption setup, the [E] Encryption test will always exit with NO DRIVER SPECIAL FILE when ITDT-SE is started with -force-generic-dd. Installing ITDT-SE on Windows Operating Systems To install ITDT-SE on Windows operating systems, perform the following steps: Note: ITDT-SE can only be used by a user with Administrator rights. 1. Download itdtinst<ersion>windows<arch>.exe where <arch> can be: AMD64 (64-bit Intel EM64T or AMD serers) IA64 (64-bit Itanium serer) X86 (32-bit Intel-compatible serers) to a directory of your choice. 2. Execute the following command: itdtinst<ersion>windows<arch>.exe Installing ITDT-SE on i5/os Operating Systems ITDT-SE for i5/os or IBM i will be installed using a graphical installer based on the InstallAnywhere installation software that needs to be executed on a Microsoft Windows system and will install the software onto the remote i5/os system. The installer will generate installation information on the local Microsoft Windows 236 IBM Tape Deice Driers Installation and User s Guide

255 IBM Tape Diagnostic Tool system so that the program can be remoed from the remote i5/os system by running the uninstaller on the local Microsoft Windows system. To install ITDT-SE on i5/os operating systems, perform the following steps: Note: ITDT-SE on i5/os requires a Microsoft Windows PC with a Jaa runtime or higher. 1. Start the installer itdtinst<ersion>i5os.exe. 2. Read through the welcome and license screens. a Figure 50. Welcome/Startup screen 3. Accept the License Agreement, then click the Next button. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 237

256 IBM Tape Diagnostic Tool a Figure 51. License screen 4. Enter your i5/os system hostname or IP address and administrator credentials. Start the installation by pressing the Install button. Click the Done button when the installation is complete. Note: The user name should be QSECOFR. a Figure 52. Machine credentials screen 238 IBM Tape Deice Driers Installation and User s Guide

257 IBM Tape Diagnostic Tool a Figure 53. Installation progress screen a Figure 54. Installation complete screen Installing ITDT-SE on Other Supported Operating Systems To install ITDT-SE on other supported operating systems, perform the following steps: Chapter 9. IBM Tape Diagnostic Tool (ITDT) 239

258 IBM Tape Diagnostic Tool Note: ITDT-SE can only be used by a user with root access rights, except for the Mac OS which requires the user to hae the minimum of read/write access to the deice file. 1. Download itdtinst<ersion><os> to a directory of your choice. itdtinst<ersion>aix is for AIX operating systems itdtinst<ersion>linuxx86 is for Linux operating systems on Intel hardware itdtinst<ersion>linuxppc is for Linux operating systems on pseries itdtinst<ersion>linuxs390x is for Linux operating systems on zseries itdtinst<ersion>hpux is for HP-UX operating systems. itdtinst<ersion>macos is for Mac OS operating systems. itdtinst<ersion>solaris is for Solaris operating systems. 2. Perform the following command to make itdtinst<ersion><os> executable: chmod 700 itdtinst<ersion><os> 3. Execute the following command: itdtinst<ersion><os> or./itdtinst<ersion><os> depending on your operating system. Standard Edition - Initial Startup This section describes the startup procedures for the Standard Edition of ITDT in arious operating systems. Starting ITDT-SE on Solaris Operating Systems 1. If the IBM Tape Deice Drier is not used, if it is not installed, or you want to be able to run -force-generic-dd, then configure the sgen drier. A script sgen_solaris_conf.sh is included in the ITDT-SE package. This script allows the user to configure the sgen generic SCSI drier that is shipped with Sun Solaris. ITDT-SE requires that the sgen deice drier is configured so that the deices you want to work with can be found. Note: For system security reasons, always reset the sgen deice drier settings after you finish working with ITDT-SE, using the sgen_solaris_conf.sh script. To configure the sgen drier, start the sgen_solaris_conf.sh script with root access. The following command line options are aailable on the SGEN drier configuration screen: 240 IBM Tape Deice Driers Installation and User s Guide 1) Check drier: This option checks if the drier /kernel/dr/sgen is aailable. 2) List drier settings: This option shows the current actiated deices. 3) New drier configuration: This option displays the screen that is used to create a new drier configuration (see Step 2 on page 241). 4) Stop sgen drier: This option stops the drier (that is, rem_dr sgen). 5) Start sgen drier: This option stops and starts the sgen drier. 6) Exit program: This option closes the shell script.

259 IBM Tape Diagnostic Tool 2. Enter option 3) to create a new drier configuration: The following command line options are aailable on the New Configuration screen. Use these options to configure the sgen drier: 1) List targets: This option shows the targets in current configuration. 2) Define deice types: This option defines drie and changer types. 3) or 5) Add target(s): This option adds targets to the list. Note: Option 3 allows for the addition of indiidual deices one at a time, Option 5 allows for the addition of a range of deices, eliminating the need to add a large number of deices one by one. 4) or 6) Remoe target(s): This option remoes targets from the list. Note: Option 4 allows for the remoal of indiidual deices one at a time, Option 6 allows for the remoal of a range of deices, eliminating the need to remoe a large number of deices one by one. 7) Sae configuration: This option saes the modifications. 8) Back to Main Menu: This option returns to the main menu. 3. After the sgen drier is configured, enter command line option 8 to go back to the main menu. 4. On the SGEN drier configuration screen enter command line option 5). This option starts the sgen drier, new deices are found using the definitions performed in Step After the new deices are found, enter option 6) to exit the sgen_solaris_conf.sh script. Note: For Fibre Channel Host Bus Adapters (HBAs), special handling is required. Attached deices need to be configured with their WWPN in the sgen.conf file. This task needs to be done manually, it is not performed by using the sgen_solaris_conf.sh script. The following is an example how to add those deices: Run the command "cfgadm -al" to get the WWPN number(s).... c4 fc-priate connected configured c4:: tape connected configured... Add the WW-PN number(s) into the sgen.conf file. name="sgen" parent="fp" target=0 lun=0 fc-port-wwn=" "; name="sgen" parent="fp" target=0 lun=1 fc-port-wwn=" "; If you hae finished the editing, the sgen drier has to be restarted. Please enter "update_dr sgen". To start ITDT-SE execute the following command:./itdt At first start, read the User License Agreement: Press Enter to scroll the license screens forward or b followed by Enter to go back. Type i if you agree to the terms of license or q followed by Enter to quit the application. During the initial program startup, the input and output directories are created: Input directory: default directory for firmware files during Firmware Update Chapter 9. IBM Tape Diagnostic Tool (ITDT) 241

260 IBM Tape Diagnostic Tool Output directory: directory containing the result files, dump files and log files after running tests ITDT-SE does not make changes outside the installation directory. Starting ITDT-SE on Windows Operating Systems Start ITDT by executing the following command: itdt.exe At first start, read the User License Agreement: Press Enter to scroll the license screens forward or b followed by Enter to go back. Type i if you agree to the terms of license or q followed by Enter to quit the application. At first program startup, the license text will be displayed and the input and output directories will be created. ITDT-SE does not create any registry entries or make changes outside the installation directory. Input directory: default directory for firmware files during Firmware Update Output directory: directory containing the result files, dump files and log files after running tests Starting ITDT-SE on i5/os Operating Systems To use ITDT-SE to update firmware or pull dumps from a Tape Drie inside a Tape Library, make sure the dries are aried online in STANDALONE MODE by performing the following steps: 1. Issue the command WRKMLBSTS. Identify the Library and dries you want to work with. Note their names (for example, TAPMLB01, TAP01, TAP02,... and so on). 2. Deallocate the corresponding dries using option Vary OFF the TAPMLB using option Enter the following command: WRKCFGSTS *DEV TAP* Identify the dries which were noted in Step 1, (for example, TAPMLB01, TAP01, TAP02) and ary them ON using option Launch the iseries Q-Shell enironment with the following command: QSH 6. Change to the folder /home/itdt with the following command: cd /home/itdt 7. Start ITDT with the following command:./itdt 8. Update Firmware and pull dumps. See Firmware Update on page 253 and Dump on page When firmware updates and dumps are complete, enter the following command: WRKCFGSTS *DEV TAP* 10. Vary off the TAPs that you worked with using option Issue the command WRKMLBSTS. Identify the Library and Dries you worked with. 12. Vary on the TAPMLB using option IBM Tape Deice Driers Installation and User s Guide

261 IBM Tape Diagnostic Tool 13. Press F5 to refresh the screen; the TAPs belonging to the TAPMLB should show up. 14. Allocate the TAPs back to the TAPMLB using option 4 or 5. Starting ITDT-SE on Other Supported Operating Systems To start ITDT-SE execute the following command:./itdt At first start, read the User License Agreement: Press Enter to scroll the license screens forward or b followed by Enter to go back. Type i if you agree to the terms of license or q followed by Enter to quit the application. During the initial program startup, the input and output directories are created: Input directory: default directory for firmware files during Firmware Update Output directory: directory containing the result files, dump files and log files after running tests ITDT-SE does not make changes outside the installation directory. Standard Edition - Known Issues and Limitations This section describes the known issues and limitations of the ITDT-SE program. AIX Operating Systems The following are the known scan limitations: Only deices that hae the deice state "aailable". For FC and SAS deices, ID and LUN greater than 999 won't be displayed, they will be masked by ###. When logged in ia telnet, backspace may not be working - an escape sequence is inserted and the input is ignored after Enter is pressed. HP-UX Operating Systems Verify that the following patches are installed before starting ITDT-SE: PA-Risc: At least these patches: ld and linker tools cumulatie patch libc cumulatie patch Itanium/IA-64: All regular patches and the following patches: VxVM 3.5~IA.014 Command Patch VxVM 3.5~IA.014 Kernel Cumulatie Patch Aries cumulatie patch linker + fdp cumulatie patch Note: ITDT-SE is emulated by Aries (a binary emulator that transparently emulates 32-bit and 64-bit HP-UX PA-RISC applications on HP-UX IA-64 machines). On HP-UX11.iV3 systems, tape libraries operated through the drie's control path (no control path failoer) may disappear from the Deice List after a [F] Firmware Chapter 9. IBM Tape Diagnostic Tool (ITDT) 243

262 IBM Tape Diagnostic Tool Update on the controlling drie. We recommend to perform repeated [S] Scan operations to make the library reappear in the deice list. Linux Operating Systems ITDT-SE on Linux requires glibc or later. Note: On a SLES9 s390x (64bit) configuration, you may experience a SCSI CMD TIMEOUT when running the [T] option while using the IBM Tape Deice Drier. For SUSE SLES9 on zseries please ensure that the kernel update SUSE-SA:2007:035 is installed. Solaris Operating Systems Rescan may take 6-8 minutes, depending on the numbers of host adapters and deices attached. The known scan limitations: SCSI ID 0-255, LUN 0-10 If the IBM Tape Deice Drier is not installed on Solaris 10, tape deices may not be found during scan although they are configured in sgen.conf. When this eent occurs, perform the following steps to configure the deices: 1. Check the current drier bindings for IBM Tape dries and changers by entering the following commands: # egrep "scsiclass,01" /etc/drier_aliases (for dries) # egrep "scsiclass,08" /etc/drier_aliases (for changers) 2. Modify the /etc/drier_alias file to comment all lines not starting with sgen and containing identification of your dries and changers. Examples: #st "scsiclass,01" (all tape dries) #st "scsiclass,01.ibm.pult3580-td4" (IBM tape drie model ULT3580-TD4) #st "scsiclass,08" (all changers) #st "scsiclass,08.ibm.p3573-tl" (IBM changer model 3573-TL) 3. Check that the configured dries are not configured for st drier by entering the following command: # cfgadm -al If the tape drie is claimed by st deice drier, an entry with cxx:rmt/y, is displayed, for example: c11::rmt/0 tape connected configured unknown 4. Add sgen drier aliases with one of the following commands: # update_dr -a -i "scsiclass,01.ibm.pult3580-hh4" sgen (adds sgen alias for IBM drie, model ULT3580-HH4) # update_dr -a -i "scsiclass,01" sgen (adds sgen alias for all dries attached to the system) # update_dr -a -i "scsiclass,08.ibm.pult3581-ta2" sgen (adds sgen alias for IBM changer, model ULT3581-TA2) # update_dr -a -i "scsiclass,08" sgen (adds sgen alias for all changers attached to the system) 5. Check that the dries and changers are now configured with the following command: # cfgadm -al 6. If the dries or changers are not listed in the output of cfgadm -al, reboot the system and erify the list of configured deices with the command: 244 IBM Tape Deice Driers Installation and User s Guide

263 IBM Tape Diagnostic Tool # cfgadm -al Windows Operating Systems After a firmware update, deices may disappear. This is a known Windows problem. See the Article ID: at: Repeated Scan operations may help to rediscoer the deice. When switching applications on Windows while ITDT-SE is running, an extra ESC character may appear on the input line, when this occurs, the input is ignored after pressing the Enter key. If you are using Adaptec SCSI Host Bus Adapters, ensure that you are using the latest Adaptec Host Bus Adapter Driers instead of the driers shipped with the Windows operating system. On Microsoft Windows systems where the maximum transfer size is limited to less than 64kB, the Dump and Firmware update operations will not work. i5/os Operating Systems ITDT-SE on i5/os supports only tape dries; it does not support autoloaders and libraries. Media changers and media changer operations are not supported with this release of ITDT-SE. To test a tape drie inside a library, the cartridge must be imported manually before starting the Deice Test. The Tape Drie must be aried online. If the Tape Drie is operated through a Tape Library, the Library must be aried offline. See Starting ITDT-SE on i5/os Operating Systems on page 242 for details. As the Library is aried offline, the Encryption Test does not delier decrypted data in a Library Managed Encryption enironment. ITDT-SE on i5/os V5R4 requires the following PTF installed: PTF: SI25023 Release: 540 Abstract: OSP-MEDIA-TAPE-THREADS-MSGCEE0200- T/QTAHRMGR QTARDCAP FAILS The [U] Tapeutil option is not aailable for i5/os with this release as all the underlying operations require the IBM Tape Deice Drier to be installed. FC 5912 SAS HBA support is only for Power6 and V6R1 configurations attached to LTO Gen 4 HH tape dries (No support for LTO 3 HH SAS). All Supported Operating Systems This section describes the known issues and limitations of the ITDT-SE program on all other supported operating systems. Preent/Allow Medium Remoal is missing as a Tape Drie option, but can still be performed by using the [56] Preent/Allow Medium Remoal option for Tape Libraries while the tape deice is opened. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 245

264 IBM Tape Diagnostic Tool User Interface Issues If you press the arrow keys on most Unix operating system consoles, the input is ignored after pressing the Enter key. When the Tab key is pressed as an input string for field data, the user interface is corrupted. Make sure that field input does not start with a number followed by space and additional text as this is interpreted as an entry to a specific row in the field. To aoid this, use an underscore character (_) instead of the space character. Command Timeout There is no instant operation termination upon SCSI command timeout; for example, when the SCSI cable is unplugged after starting POST A. When a command timeout condition occurs, ITDT may still continue to perform more operations (like unmounting the cartridge) instead of instantly terminating with a timeout condition. 3576/TS3310 Tape Library Library Firmware Update using ITDT-SE is not supported with the 3576/TS3310. Update the Firmware using the 3576/TS3310 Web User Interface Tape Library Dries in a 3494 tape library or an STK silo library are supported, only the [T] Test option won t work due to deice-specific restrictions for handling cartridges. Standard Edition - Start Menu Commands After program startup, ITDT-SE displays the start screen menu. a Figure 55. Start Screen Menu The following commands are aailable on the start screen menu: S - Scan for tape dries Opens the screen for the Scan function (refer to Standard Edition - Scan Menu Commands on page 247). U - Tapeutil 246 IBM Tape Deice Driers Installation and User s Guide

265 IBM Tape Diagnostic Tool Opens the screen for the Tapeutil operation commands. These commands are the standardized tapeutil functions with most of the options aailable that were aailable with the preious tapeutil functions (refer to Standard Edition - Tapeutil Menu Commands on page 263). H - Help Help starts and displays the aailable online help. Q - Quit Quits the function. Standard Edition - Scan Menu Commands When using ITDT-SE, after entering S on the start screen, the Scan function starts and displays the first deice list screen. This screen contains the S, T, D, F, E, W, U, and O commands. Entering the O command displays the second deice list screen. The second screen contains the Y, L, I, and R commands. a Figure 56. Scan Menu The following commands are described in this section: S - Scan on page 248 T - Test on page 250 D - Dump on page 252 F - Firmware Update on page 253 E - Encryption on page 256 W - Full Write on page 258 U - Tape Usage on page 259 O - Other on page 260 Chapter 9. IBM Tape Diagnostic Tool (ITDT) 247

266 IBM Tape Diagnostic Tool a Figure 57. More Scan Options Y - System Test on page 260 L - Library Self-Test on page 262 I - Manual Inspect on page 262 R - Return on page 263 Scan The Scan function [S] is used to discoer all supported tape and library deices that are attached to the computer system so that they can be selected for the subsequent ITDT-SE operations. The scan function also seres as a connection test that can be used to erify proper attachment of the deices. Before continuing, make sure no other program is accessing the deices used by ITDT-SE. For example, stop the backup jobs that are accessing the deices when using ITDT-SE, or if not sure, stop the entire backup application. After starting ITDT-SE, type the S key followed by the Enter key to actiate the scan function. Depending on the operating system and the number of attached dries, the scan can take seeral minutes. See Standard Edition - Known Issues and Limitations on page 243 for more details. During the scan operation, a bar in the lower left edge of the screen shows that the scan operation is still in progress. Once the scan is finished, the first deice list screen is displayed. 248 IBM Tape Deice Driers Installation and User s Guide

267 IBM Tape Diagnostic Tool Name of current screen Deice number Selected deice Command Command prompt a Figure 58. Deice List Screen The first deice list screen shows all detected deices and the connection information (host adapter number, bus number, SCSI/FCP ID and LUN) along with product data (Model name, Unit Serial number, Microcode reision). For dries that are attached to a library, the Changer column shows the serial number of the changer the drie is attached to. Scrollable data is indicated by "VVVVVVVVV" at the bottom of the screen. To scroll down to access non-displayed entries, type + and press the Enter key. Note: For fast down scrolling, type + followed by a space and the number of lines to scroll down then press the Enter key. To scroll back, use - instead of +. Note: For fast up (backward) scrolling, type - followed by a space and the number of lines to scroll up then press the Enter key. If no deices appear or if deices are missing in the list, make sure that: ITDT-SE is running with administrator/root rights. The deices are properly attached and powered on. Linux: The deices must be attached at boot time. i5/os: Only tape dries will be detected. Solaris, when no IBM tape deice drier is in use: Ensure that sgen is correctly configured: file /kernel/dr/sgen.conf is correctly configured (see Starting ITDT-SE on Solaris Operating Systems on page 240). Solaris 10, see (see Standard Edition - Known Issues and Limitations on page 243) More than 12 deices displayed - scroll down the Deice List. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 249

268 IBM Tape Diagnostic Tool ITDT-SE uses the IBM Tape Deice Drier for its operations. If no IBM Tape Deice Drier is installed, the generic deice drier for the operating system is used instead. On Microsoft Windows, any Tape Deice Drier that is installed is used. If you need to bypass the IBM Tape Deice Drier for diagnostic purposes, start ITDT-SE with the following command: itdt -force-generic-dd Note: For operating system specific information on how to use this command, please isit the corresponding Initial Startup sections. Test Once the desired deice is displayed, select the deice for test. Only one deice can be selected. The Test function [T] checks if the tape deice is defectie and outputs a pass/fail result. Attention: the test. The test functionality erases user data on the cartridge that is used for For the library or autoloader test, the [L] library test should be selected. Notes: 1. The test can take from 15 minutes up to 2 hours. 2. The test runs only on tape dries, not on autoloaders or libraries. To perform the test function, it is recommended that a new or rarely used cartridge is used. Scaled (capacity-reduced) cartridges should not be used to test the deice. To test tape dries within a library, the library must be in online mode. 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. Select the deice you want to test by entering its number and press the Enter key. 2. Type T followed by the Enter key to actiate the test. If no cartridge is inserted, ITDT-SE prompts to insert a cartridge. Either insert a cartridge and press the Enter key or stop the test by entering C followed by the Enter key. Note: If ITDT-SE detects data on the cartridge, the Deice Test screen displays a message (as shown in Figure 59 on page 251). 250 IBM Tape Deice Driers Installation and User s Guide

269 IBM Tape Diagnostic Tool a Figure 59. Data Delete Question Type Y followed by the Enter key to continue the test if you are absolutely sure that data on the cartridge can be oerwritten. If you are unsure, type N followed by the Enter key to stop the test. During the test, the program shows a progress indicator in form of a bar of hash marks (#) ( 1 ) that shows the progress of a single sub-test as well as a description of that sub-test. The user may stop the test by selecting the abort option (exceptions: POST A, POST B see below). During the test, a progress indicator will be shown on the test screen. Messages from the test steps will be shown in the status field. 1 2 a Figure 60. Test Running The test sequence contains the following steps: 1. Mount Medium 2. [Medium Qualification] only if the preious step indicated this requirement 3. Load/Write/Unload/Read/Verify 4. POST A 5. Performance Test (run 2 times if first run failed with performance failure) 6. POST B Chapter 9. IBM Tape Diagnostic Tool (ITDT) 251

270 IBM Tape Diagnostic Tool 7. Unmount Medium 8. Get FSC 9. Get Logs The test can be stopped by typing A followed by the Enter key at any time except during the POST tests, which are not interruptible. Note: It may take some time until the test actually stops. a Figure 61. Test Results When all sub-tests are finished, ITDT-SE shows a screen that displays the attachment and deice information as in the first deice list screen, together with the test result and failure information in the code field. The screen also shows the output files that were generated during the test run. The files may be requested by the IBM Support Center. If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the first deice list screen; otherwise, type Q followed by the Enter key to exit the program. Dump Perform the following to start the Dump [D] process: 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. 2. Select the deice you want to retriee a dump from by entering its number and press the Enter key. 3. Type D and press the Enter key to start the dump retrieal for the selected deice. The ongoing dump process is performed (it takes less than 1 minute). 252 IBM Tape Deice Driers Installation and User s Guide

271 IBM Tape Diagnostic Tool Dump Filenames Log Filenames a Figure 62. Dump When the dump process is performed on a tape library or autoloader other than the 3584/TS3500, the Dump function stores one log file in the output folder of the program (*.blz). For the 3584/TS3500, a dump file (*.a.gz) will be stored in the output folder. Note: When the Dump function is performed for tape libraries or autoloaders other than the 3584/TS3500, the Log file only contains Log Sense and Mode Sense pages, while a Drie or 3584/TS3500 Dump contains much more diagnostic information. Retriee the files from the ITDT-SE output subdirectory that was created during the installation. The following are examples of the directory: Example output directory (Windows): c:\itdt\output Example output directory (Unix): /home/user/itdt/output Example output directory (i5/os): /home/itdt/output (On the IFS) use FTP or the i-series Naigator to transfer the file If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the deice list; otherwise, type Q followed by the Enter key to exit the program. Firmware Update The Firmware Update [U] upgrades the firmware of tape dries and tape libraries. See Supported Equipment on page 235 for a list of supported products. Note: See 3576/TS3310 Tape Library on page 246 for more information on how to update the firmware on a 3576/TS3310 Tape Library. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 253

272 IBM Tape Diagnostic Tool a Figure 63. Firmware Update screen The following site is aailable for the latest firmware files: Download the files to the ITDT-SE input subdirectory that was created during the installation. The following are examples of the directory: Example input directory (Windows): c:\itdt\input Example input directory (Unix): /home/user/itdt/input Example input directory (i5/os): /home/itdt/input (on the IFS) use FTP or the i-series Naigator to transfer the file To do a Firmware Update perform the following steps: 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. 2. Select the deice you want to update by typing the number of the deice and pressing the Enter key. 3. Type F and press the Enter key to display the Firmware Update screen. 4. To select the needed firmware update perform one of the following: If the firmware file you downloaded is listed in the Content field of the Firmware Update screen, type the corresponding line number and press the Enter key. If the firmware file is stored in a directory other than the one displayed in FW Dir, then type F followed by a space and the fully qualified path to the directory containing the firmware file, then press the Enter key. For example, enter the following to change the firmware directory (Unix): f /home/user/firmware If no files are displayed in the Content field, check the Dir OK field on the right side of the screen. It indicates true if the directory exists, false otherwise. If the content of the displayed FW Dir has changed, type D and press the Enter key to refresh the directory content. 254 IBM Tape Deice Driers Installation and User s Guide

273 IBM Tape Diagnostic Tool Note: The selected filename is reset to the first item (#0) after using the Refresh function. If the displayed directory contains more files than those shown, type + and press the Enter key to scroll down the list. For fast down scrolling type + followed by a space and the number of lines to scroll down then press the Enter key. To scroll back, use - instead of +. Scrollable data is indicated by "VVVVVVVVVVVVVVVVV". VVVVV = More data a Figure 64. Scrollable Data screen 5. After selecting the firmware file, type C and press the Enter key to continue. 6. Before starting the firmware update, make sure the file displayed in the FW File field is the correct file. If the correct file is displayed, proceed to the next step. If the correct file is not displayed, type C and press the Enter key to change the selected firmware file. Go to Step 4 on page 254. Note: The selected filename is reset to the first item in the list when returning to that dialog from the Start Update dialog. 7. If you decide to run the firmware update, type S and press the Enter key to start the firmware update. During the firmware update, a firmware update progress screen is displayed. Attention: Once started, do not interrupt the firmware update. The firmware update usually takes 3-5 minutes, but it can take up to 45 minutes for libraries. If you decide not to run the firmware update, type R and press the Enter key to return to the Deice List. Note: If ITDT-SE detects a FIPS-certified drie firmware, it displays a warning dialog. Before continuing, ensure that you use a FIPS-certified firmware to update the drie. 8. After completion, the Status field on the bottom right side indicates PASSED if the firmware was updated successfully and FAILED otherwise. Type R and press the Enter key to return to the Deice List. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 255

274 IBM Tape Diagnostic Tool Encryption The Encryption [E] function is used to erify if data on the cartridge was actually written encrypted. It reads both decrypted and raw data from the cartridge into two separate files on disk. The user can then erify that the data differs to ensure that encryption worked. The Encryption function does not proide a Write - Read test. The Encryption function is only supported on encryption enabled dries and requires an encryption infrastructure including the Encryption Key Manager (EKM) to be properly set up. An encrypted data cartridge must be used. The Encryption function is supported for the following encryption enironments: System Managed: IBM tape deice drier must be installed and in use by ITDT to read decrypted data Library Managed Application Managed: Only raw encrypted data will be read (result file *.ENC) Note: On i5/os, media changers and media changer operations are not supported with this release of ITDT-SE. To test a tape drie inside a library, the Tape Drie must be aried online and the Tape Library must be aried offline (see Starting ITDT-SE on i5/os Operating Systems on page 242 for details). As the Library is aried offline, the Encryption function does not delier decrypted data in a Library Managed Encryption enironment. 1. After starting ITDT-SE, type S followed by the Enter key to actiate the deice scan. 2. Select the deice you want to test by entering its number and press the Enter key. Type E and press the Enter key to start the encryption test. 3. ITDT-SE then switches to the Encryption Verification screen. On this screen, the system requires the entry of the number of the start record and the amount of data (in KB) to be read. 4. Type S followed by a space and the start record number, then press the Enter key to enter the start record number. Type L followed by a blank and the data length, then press the Enter key to enter the data length, maximum KB. 256 IBM Tape Deice Driers Installation and User s Guide

275 IBM Tape Diagnostic Tool a Figure 65. Encryption Start screen 5. If you entered the alues correctly, press the Enter key to start the encryption. During the encryption, the program shows a progress indicator in form of a bar of hash marks (#) that shows the progress of a single sub-test as well as information about that sub-test. The Encryption function can be stopped by typing A followed by the Enter key at any time. Note: It may take some time until the Encryption function actually stops. If all encryption operations are finished, ITDT-SE shows a screen that displays the Status field on the bottom left side that indicates PASSED if the encrypted test completed successfully and ABORTED otherwise. The screen also shows the output files that were generated during the Encryption function: file serial#.n.enc contains the raw encrypted data file serial#.n.dec contains the decrypted data Table 28 defines the abort codes. Table 28. Definitions of Abort Codes ABORT CODE LOCATE FAILED MEDIUM NOT ENCRYPTED NO DRIVER SPECIAL FILE DRIVE ENCRYPTION DISABLED ROOT CAUSE Start position as requested by the user could not be reached ITDT detected medium as non-encrypted System-Managed enironment, but generic deice file is used instead of IBM deice drier special file Mode Sense detected disabled drie encryption UNEXPECTED DATA Set Raw read mode failed END OF MEDIUM One of the commands failed End of medium encountered before the gien amount of data could be read Chapter 9. IBM Tape Diagnostic Tool (ITDT) 257

276 IBM Tape Diagnostic Tool Table 28. Definitions of Abort Codes (continued) ABORT CODE ROOT CAUSE END OF DATA End of data encountered before the gien amount of data could be read READ FAILED ENCRYPTION ERROR INVALID PARAMETER User entered data length of 0kB If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the deice list; otherwise, type Q followed by the Enter key to exit the program. Full Write The Full Write [F] function writes the entire cartridge with a gien block size either with compressible or incompressible data and output performance data. Attention: The Full Write function erases data on the cartridge that is used for the test. Notes: 1. The Full Write function takes approximately 2 hours when writing incompressible data, less time for compressible data. 2. The Full Write function runs only on tape dries, not on autoloaders or libraries. The Full Write test can be used to: Demonstrate that the drie is capable of writing the full amount of data on a cartridge. Identify system issues with compression. Drie data compression is always switched on during the full write. When run with compressible data, the output shows the compression rate. If the compression rate is higher than 1.0 but the system does not appear to be able to compress data on the cartridge, then check the deice drier and software settings to see if they disable compression. 1. After starting ITDT-SE, type S followed by the Enter key to actiate the deice scan. 2. Select the deice you want to write to by entering its number and press the Enter key. Type W and press the Enter key to start the full write. ITDT-SE then switches to the Full Write screen. If no cartridge is inserted, ITDT-SE prompts to insert a cartridge. Either insert a cartridge and press the Enter key or stop the test by typing C followed by the Enter key. Note: If ITDT-SE detects data on the cartridge, it shows the Full Write screen, and displays the following message: Cartridge not empty! Oerwrite data? Type Y followed by the Enter key to continue the test if you are absolutely sure that data on the cartridge can be oerwritten. If you are unsure, type N followed by the Enter key to stop the test. 258 IBM Tape Deice Driers Installation and User s Guide

277 IBM Tape Diagnostic Tool 3. The system prompts for entry of a transfer size between 16 KB and the maximum block size supported by the system (maximum possible alue is 512 KB). This is a check for the type of supported block size is performed. Enter the appropriate alues for your system. 4. Select the type of data to write, either: [C] Compressible or [I] Incompressible. During the full write, the program shows a progress indicator in form of a bar of hash marks (#) that shows the progress of the full write. The full write can be stopped by typing A followed by the Enter key at any time. Note: It may take some time until the full write actually stops. If all write operations are finished, ITDT-SE shows a screen that displays the compression ratio ( 1 ) and the write performance (shown in 2 as the Data Rate) for the selected block size. If an error occurred during the full write, data is only written partially. "Compressible = Yes" means that the data written was just zeroes, so that the data could be compressed by the drie with a maximum compression ratio. "Compressible = No" means that a data pattern was written that the drie could almost not compress at all. If the compression ratio is 1, the drie was not able to compress the data (equialent to 1:1 compression ratio). If the compression ratio is 94.0, the drie was able to do 94:1 compression meaning that 94 bytes in the original data could be compressed to 1 byte on the medium means 100 bytes could be compressed down to 1 byte on the medium. If you want to use other ITDT-SE functions, type R followed by the Enter key to return to option 4 the deice list; otherwise, type Q followed by the Enter key to exit the program. 2 1 a Figure 66. Full Write Results Tape Usage The Tape Usage [U] function retriees statistical data and error counters from a cartridge. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 259

278 IBM Tape Diagnostic Tool a Figure 67. Tape Usage Screen 1. After starting ITDT-SE, type S followed by the Enter key to actiate the deice scan. 2. Select the deice you want to test by entering its number and press the Enter key. 3. Type U followed by the Enter key to start the tape usage log retrieal. ITDT-SE then switches to the tape usage screen. If no cartridge is inserted, ITDT-SE prompts to insert a cartridge. Either insert a cartridge and press the Enter key or stop the test by entering C followed by the Enter key. During the get logs operation, the program shows a progress indicator in form of a bar of hash marks (#) that shows the progress of a single sub-operation as well as a description of that operation. If all sub-operations are finished, ITDT-SE shows a Tape Usage completion screen. The Status field on the bottom right side indicates PASSED if the log retrieal completed successfully and ABORTED otherwise. Other Other [O] - type O followed by the Enter key to display a screen with the following commands: System Test Library Self-Test on page 262 Manual Inspect on page 262 Return on page 263 System Test The System Test [Y] is a short test that performs the following: Reeals system performance bottlenecks. Compressible data throughput alues can reeal bandwidth limitations caused by the system or cabling or HBA. Measures performance ariations across the different block sizes to find the ideal block size for the system configuration. The System Test only runs on tape dries, not on autoloaders or libraries. To perform a System Test on tape dries within a library, the library must be in online mode. 260 IBM Tape Deice Driers Installation and User s Guide

279 IBM Tape Diagnostic Tool 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. 2. Type O and press the Enter key to display the second deice list screen. 3. On the second deice list screen, type Y and press the Enter key to start the System Test. ITDT-SE then switches to the System Test screen. If no cartridge is inserted, ITDT-SE prompts to insert a cartridge. Either insert a cartridge and press the Enter key or stop the test by typing C followed by the Enter key. Note: If ITDT-SE detects data on the cartridge, it shows the System Test screen, and displays the following message: Cartridge not empty! Oerwrite data? Type Y followed by the Enter key to continue the test if you are absolutely sure that data on the cartridge can be oerwritten. If you are unsure, type N followed by the Enter key to stop the test. The System Test is performed as follows: a. System Test determines the amount of data to write for each supported blocksize (a percentage of the cartridge is written for each blocksize). b. System Test writes the amount of data with all supported block sizes in powers of two down to 16kB (at maximum 512, 256, 128, 64, 32, 16), first with incompressible, then with compressible data, and then displays performance data and progress screen. c. At the end of the test, a summary screen is displayed. a Figure 68. System Test Results Compressible = Yes" means that the data written was just zeroes, so that the data could be compressed by the drie with a maximum compression ratio. "Compressible = No" means that a data pattern was written that the drie could almost not compress at all. If the compression ratio is 1, the drie was not able to compress the data (equialent to 1:1 compression ratio). If the compression ratio is 94.0, the drie was able to do 94:1 compression meaning Chapter 9. IBM Tape Diagnostic Tool (ITDT) 261

280 IBM Tape Diagnostic Tool that 94 bytes in the original data could be compressed to 1 byte on the medium means 100 bytes could be compressed down to 1 byte on the medium. The System Test can be stopped by typing A followed by the Enter key at any time. Note: It may take some time until the System Test actually stops. If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the deice list; otherwise press Q followed by the Enter key to exit the program. Library Self-Test The Library Self-Test [L] starts and monitors the library-internal self-test. This test only runs on libraries and autoloaders, not on tape dries. 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. 2. Type O and press the Enter key to display the second deice list screen. 3. On the second deice list screen, type L and press the Enter key to start the Library Self-Test. A Deice Test screen is displayed and a functionality test on the tape library is performed. At the end of the test, a results screen is displayed. The Library Self-Test can be stopped by typing A followed by the Enter key at any time. Note: It may take some time until the Library Self-Test actually stops. If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the deice list; otherwise press Q followed by the Enter key to exit the program. Manual Inspect Manual Inspect [I] creates a manual inspection record if a deice does not appear in the deice list. This test is intended for deices that are not recognized or hae a technical problem which can not be determined by ITDT-SE. If a tape drie cannot be identified using a deice scan, the user can manually create a test record for the drie. The system prompts for the user to run the SCSI/FC Wrap test for the drie (see the serice manual for the drie). The results of the wrap test can be entered along with some additional inspection information. The result are saed into binary and text output files that hae the same format as the output files generated by the test. 1. Start ITDT-SE, then type S and press the Enter key to scan for the deices. 2. Type O and press the Enter key to display the second deice list screen. 3. On the second deice list screen, type I and press the Enter key to open the Manual Inspection screen. 4. On the next screen, type M followed by a space and the model name and press the Enter key. For example: M ULT3580-TD1 5. Enter the required information to complete the items in the screen: a. Type N followed by a space and the serial number and press the Enter key. 262 IBM Tape Deice Driers Installation and User s Guide

281 IBM Tape Diagnostic Tool b. Type T followed by a space and the content of the Message Display and press the Enter key. c. Optionally, type A followed by a space and additional information text and press the Enter key. 6. After all information has been entered, type S and press the Enter key to sae the data. The information is stored in a binary file (which can be used for further analysis), and in a human-readable text file. Both files are stored in the ITDT-SE output folder. If you want to use other ITDT-SE functions, type R followed by the Enter key to return to the first deice list screen; otherwise press Q followed by the Enter key to exit the program. Return Return [R] - type R followed by the Enter key to go back to the first deice list screen. Standard Edition - Tapeutil Menu Commands When the user executes the U command on the ITDT-SE start screen, the Tapeutil operation screen is displayed. Note: On any screen, to execute a command, press the shortkey displayed in brackets [ ], followed by the Enter key. The following commands are described in this section: [1] Open a Deice on page 264 [2] Close a Deice on page 264 [3] Inquiry on page 264) [4] Test Unit Ready on page 264 [5] Resere Deice on page 265 [6] Release Deice on page 265 [7] Request Sense on page 265 [8] Log Sense on page 265 [9] Mode Sense on page 265 [10] Query Drier Ver. (Version) on page 265 [11] Display All Paths on page 265 [20] Rewind on page 265) [21] Forward Space File Marks on page 265 [24] Backward Space Records on page 266 [23] Forward Space Records on page 266 [22] Backward Space File Marks on page 266 [25] Space to End of Data on page 266 [26] Read and Write Tests on page 266 [27] Read or Write Files on page 266 [28] Erase on page 267 [29] Load Tape on page 267 [30] Unload Tape on page 267 Chapter 9. IBM Tape Diagnostic Tool (ITDT) 263

282 IBM Tape Diagnostic Tool [31] Write File Marks on page 267 [32] Synchronize Buffers on page 267 [33] Query/Set Parameter on page 267 [34] Query/Set Tape Position on page 267 [35] Query Encryption Status on page 267 [36] Display Message on page 268 [37] Report Density Supp (Support) on page 268 [38] Test Encryp. Path (Test Encryption Key Path/Setup) on page 268 [39] Config. TCP/IP Port on page 269 [50] Element Information on page 269 [51] Position to Element on page 269 [52] Element Inentory on page 270 [53] Exchange Medium on page 270 [54] Moe Medium on page 270 [55] Initialize Element Status on page 270 [56] Preent/Allow Medium Remoal on page 270 [57] Initialize Element Status Range on page 270 [58] Read Deice IDs on page 270 [59] Read Cartridge Location on page 270 [70] Dump/Force Dump/Dump on page 271 [71] Firmware Update on page 271 [1] Open a Deice When you select the Open a Deice command [1]: 1. ITDT checks if a deice is already opened. 2. You are prompted for a deice special file name. 3. You are prompted for an open mode (rw, ro, wo, append). 4. ITDT opens the deice you selected. [2] Close a Deice When you select the Close a Deice command [2]: 1. ITDT checks if the deice is already closed. 2. ITDT closes the deice. [3] Inquiry When you select the Inquiry command [3]: 1. You are prompted for page code. 2. ITDT then displays a decoded format of a hexadecimal dump and prints a hexadecimal dump of the inquiry data. [4] Test Unit Ready When you select the Test Unit Ready (TUR) command [4], ITDT issues the Test Unit Ready ioctl command. 264 IBM Tape Deice Driers Installation and User s Guide

283 IBM Tape Diagnostic Tool [5] Resere Deice When you select the Resere Deice command [5], ITDT issues a resere command for the deice. [6] Release Deice When you select the Release Deice command [6], ITDT issues a release command for the deice. [7] Request Sense When you select the Request Sense command [7]: 1. ITDT issues a Request Sense command. 2. ITDT then displays a decoded format of hexadecimal dump sense data and prints hexadecimal dump sense data. [8] Log Sense When you select the Log Sense command [8]: 1. You are prompted for Log Sense Page. 2. ITDT issues a mode sense command. 3. ITDT performs a hexadecimal dump page. [9] Mode Sense When you select the Mode Sense command [9]: 1. You are prompted for Mode Sense Page. 2. ITDT issues mode sense command. 3. ITDT performs a hexadecimal dump page. [10] Query Drier Ver. (Version) When you select the Query Drier Version command [10]: 1. ITDT issues the required command to get drier ersion. 2. ITDT prints drier ersion. [11] Display All Paths When you select the Display All Paths command [11]: 1. ITDT issues an ioctl command. 2. ITDT outputs decoded path information for all paths. [20] Rewind When you select the Rewind command [20], ITDT issues the ioctl rewind command for the deice. [21] Forward Space File Marks When you select the Forward Space File Marks command [21]: 1. You are prompted for the number of file marks to space forward. 2. ITDT issues (extrinsic) ioctl command. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 265

284 IBM Tape Diagnostic Tool [22] Backward Space File Marks When you select the Backward Space File Marks command [22]: 1. You are prompted for the number of file marks. 2. ITDT issues (extrinsic) ioctl command. [23] Forward Space Records When you select the Forward Space Records command [23]: 1. You are prompted for the number of records to space forward. 2. ITDT issues (extrinsic) ioctl command. [24] Backward Space Records When you select the Backward Space Records command [24]: 1. You are prompted for the number of records to space backward. 2. ITDT issues (extrinsic) ioctl command. [25] Space to End of Data When you select the Space to End of Data (EOD) command [25], ITDT issues the (extrinsic) ioctl command. [26] Read and Write Tests When you select the Read and Write Tests command [26]: You are prompted for block size (If you just press Enter, the default block size is 10240). You are prompted for the number of blocks per read/write (If you just press Enter, the default number of blocks is 20). You are prompted for the number of repetitions (If you just press Enter, the default number of repetitions is 1). You can then select one of the following options: Read data from tape (to run Read only test) Write data to tape (to run Write only test) Write/Read/Verify (to run Read and Write test) ITDT performs the selected test and displays the transfer size and block size used for this test, the number of records read/written, and the total bytes transferred. [27] Read or Write Files When you select the Read or Write Files command [27]: You are prompted to specify the filename of the source file (for Write test) or the destination file (for Read test). You are prompted for the number of records to be read. You can then select one of the following options: Read File from Tape: ITDT reads a file from tape and stores data into a file with the gien filename. Write File to Tape: ITDT reads data from file with the gien filename and writes data to tape. 266 IBM Tape Deice Driers Installation and User s Guide

285 IBM Tape Diagnostic Tool ITDT displays the number of records read/written, the transfer size and the total bytes transferred. [28] Erase When you select the Erase command [28], ITDT issues the (extrinsic) ioctl command. [29] Load Tape When you select the Load Tape command [29], ITDT issues the load tape command. [30] Unload Tape When you select the Unload Tape command [30], ITDT issues the unload tape command. [31] Write File Marks When you select the Write File Marks command [31]: 1. You are prompted for the number of file marks to write. 2. ITDT issues the (extrinsic) ioctl command. [32] Synchronize Buffers When you select the Synchronize Buffers command [32], ITDT issues the ioctl command. [33] Query/Set Parameter When you select the Query/Set Parameter command [33]: 1. ITDT displays non-changeable parameters. Note: The list of non-changeable parameters is operating system specific. 2. ITDT displays changeable parameters. Note: The list of changeable parameters is operating system specific. 3. You are prompted for parameter to change. 4. ITDT requests prompt for parameter alue (if required). 5. ITDT requests safety prompt (if required). 6. ITDT issues the ioctl command. [34] Query/Set Tape Position When you select the Query/Set Tape Position command [34]: 1. ITDT displays the current position 2. You are prompted for a new position to set. 3. ITDT issues the Set Position ioctl command. [35] Query Encryption Status When you select the Query Encryption Status command [35]: 1. ITDT issues Get Encryption State ioctl command. 2. ITDT displays encryption settings (Encryption capability, Encryption Method, Encryption state). Chapter 9. IBM Tape Diagnostic Tool (ITDT) 267

286 IBM Tape Diagnostic Tool [36] Display Message When you select the Display Message command [36]: 1. You are prompted for the text of message 0 (8 characters or less). 2. You are prompted for the text of message 1 (8 characters or less) 3. You are prompted for message type (msg0, msg1, flash0, flash1, alt). 4. ITDT issues the Display Message ioctl command. Not all dries hae a display. The 3592 drie is the only one at this time that has display message capability since it is the only one with a display that is more than 1 character long. Eight is the limit of the characters on a display screen. [37] Report Density Supp (Support) When you select the Report Density Support command [37]: 1. ITDT prints report status text for all supported media. 2. ITDT issues Report Density Support ioctl command to retriee all supported media. 3. ITDT prints all requested reports. Data is printed in a decoded way. Scroll the screen to print each one of the following: Density name Assigning organization Description Primary density code Secondary density code Write OK Duplicate Default Bits per MM Media Width Tracks Capacity (megabytes). 4. ITDT prints report status text for current media 5. ITDT issues Report Density Support ioctl command to retriee current media 6. ITDT prints report data in a decoded way. [38] Test Encryp. Path (Test Encryption Key Path/Setup) When you select the Test Encryption Key Path/Setup command [38]: Note: Not supported for the HP-UX operating system. 1. ITDT prints status message that serer configuration and connections are tested 2. ITDT issues the Encryption Diagnostics ioctl command, Ping Diag 3. ITDT prints number of serers aailable or error message 4. ITDT issues the Encryption Diagnostics ioctl command, Basic Encryption Diag 5. ITDT prints completion code or error message 6. ITDT issues the Encryption Diagnostics ioctl command, Full Encryption Diag 7. ITDT prints completion code or error message. 268 IBM Tape Deice Driers Installation and User s Guide

287 IBM Tape Diagnostic Tool [39] Config. TCP/IP Port Drie Ethernet port configuration, only aailable for LTO-5 dries. First, the current Ethernet settings will be read and displayed, then the user will get prompted for eery parameter to be changed: ITDT- Set TCP/IP Port Address IPV Port V Subnet Mask Length <Specify Address IPV4 [enter] for > Pressing the Enter key will step to the next parameter without changing the current one. Once all parameters are changed, the configuration will be written to the drie and a screen similar to the following will appear: IBM Tape Diagnostic Tool Standard Edition - Deice Test Host Bus ID LUN Model Serial Ucode Deice ## 636 ULT3580-TD A1W Setting TCP/TP Configuration... Reading current TCP/TP Configuration... Number of Port Descriptors 1 Port Descriptor for Port 1 Number of Socket Descriptors 2 Get Adapter:1 IPV :5050/24 Wed Feb 03 02:55: Result: PASSED Code: OK <[Q] Quit [N] Next [P] Preious + - [Enter] Return> [50] Element Information When you select the Element Information command [50]: 1. ITDT issues the ioctl command 2. ITDT displays number of robots, first robot address, number of slots, first slot address, number of i/e elements, first element address, number of dries, first drie address. [51] Position to Element When you select the Position to Element command [51]: 1. You are prompted for destination address 2. ITDT issues the ioctl command. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 269

288 IBM Tape Diagnostic Tool [52] Element Inentory When you select the Element Inentory command [52]: 1. ITDT issues the Element Info ioctl command. 2. ITDT issues the Element Inentory ioctl command. 3. ITDT displays decoded element inentory info, type n followed by return to show next page of information. [53] Exchange Medium When you select the Exchange Medium command [53]: 1. You are prompted for source address. 2. You are prompted for first destination address. 3. You are prompted for second destination address. 4. ITDT issues the ioctl command. [54] Moe Medium When you select the Moe Medium command [54]: 1. You are prompted for source address. 2. You are prompted for destination address. 3. ITDT issues the ioctl command. [55] Initialize Element Status When you select the Initialize Element Status command [55]: 1. ITDT prints command summary. 2. ITDT issues the ioctl command. [56] Preent/Allow Medium Remoal When you select the Preent/Allow Medium Remoal command [56]: 1. You are prompted to select (1) for Preent Remoal, or (0) for Allow Remoal. [57] Initialize Element Status Range When you select the Initialize Element Status Range command [57]: 1. You are prompted for the first slot address. 2. You are prompted for the number of slots. 3. ITDT issues the ioctl command. [58] Read Deice IDs When you select the Read Deice IDs command [58], ITDT retriees the deice ID information for all aailable dries and displays the information. Type n followed by Enter to show the next page. [59] Read Cartridge Location When you select the Read Cartridge Location command [59]: 1. You are prompted for the address of the first slot. 2. You are prompted for number of elements. 3. ITDT erifies that the gien address range is alid, otherwise prints error message and exit. 4. ITDT issues the READ_CARTRIDGE_LOCATION ioctl command. 270 IBM Tape Deice Driers Installation and User s Guide

289 IBM Tape Diagnostic Tool 5. ITDT issues the Element Info ioctl command. 6. ITDT erifies that the address range is alid; otherwise print error message and exit. 7. If no slots are found in Element Info data, print error message and exit. 8. ITDT issues the READ_CARTRIDGE_LOCATION ioctl command. 9. ITDT prints decoded storage element information, Type n followed by Enter to show next page. [70] Dump/Force Dump/Dump When you select the Dump/Force Dump/Dump command [70]: ITDT retriees dump. ITDT issues Force Dump command. ITDT retriees second dump. ITDT displays name of stored dump files and the output directory where they are stored. The dump filenames start with the serial number of the deice. [71] Firmware Update When you select the Firmware Update command [71]: 1. ITDT displays the default input directory where the firmware files should be stored. The following are examples of the directory: Example input directory (Windows): c:\itdt\input Example input directory (Unix): /home/user/itdt/input 2. You are prompted to specify a different input directory if required, or to press Enter to keep the standard ITDT directory. 3. You are prompted to specify the firmware file name and press Enter to start. 4. ITDT performs firmware update and displays progress status and result. Note: See 3576/TS3310 Tape Library on page 246 for more information on how to update the firmware on a 3576/TS3310 Tape Library. The following site is aailable for the latest firmware files: Standard Edition - Tapeutil Scripting Commands Scripting has been enabled with the 4.0 release of ITDT SE. ITDT-SE proides backward compatibility for existing tapeutil scripts. While some legacy commands exists they will not be documented in their entirety as they will be phased out oer time. New scripts should always use those listed in this guide, the Common Command set (CS), and existing scripts need to be modified for forward compatibility with ITDT. Following you will find a list of commands, on each command you will find the command, a description, parameter list, and which platforms are supported. Some commands will hae numbers after them, this means there is a corresponding menu command in Standard Edition - Tapeutil Menu Commands on page 263. The following are the generic inocation parameters as in use by the legacy command sets: -f filename Chapter 9. IBM Tape Diagnostic Tool (ITDT) 271

290 IBM Tape Diagnostic Tool Note: "filename" is a deice special file for the drie/changer, for example: /de/rmt0 (AIX), /de/rmt/0st (Sun), /de/rmt/0m (HP), /de/ibmtape0 (Linux), \\.\tape0 (Windows) For a complete list of the filename syntax, please refer the section "Special Files" on each platform. The calling conention for the Common Command set will be: itdt -f filename [Open Mode] Subcommand [Subcommand...] The Open Mode flag is supported on all platforms. If the flag is not set, the deice will be opened in read/write mode. Additional parameters that may be required for opening the deice will be automatically detected and set. Valid Open Modes are -w 0 for Read/Write -w 1 for Write Only -w 2 for Read Only -w 3 for Append only Note that the new command set will enable legacy commands on eery platform, een if that wasn't supported by Tapeutil before. The output will follow current Tapeutil conentions, but if there is different output for a single command on arious platforms, the output will be implemented according to the AIX output as the primary scripting platform. Note that Tapeutil allowed undocumented abbreiations for some of the commands, for example it was possible to shorten inquiry to inq or inqu or inqui and so on. The following command abbreiations will be supported with ITDT-SE too: inq(uiry), req(sense), pos(ition), ele(mentinfo), in(entory), deid(s), cartridge(location). A list of Deprecated Commands are below at Deprecated Commands on page 285. Also there is a list of unsupported commands and known exceptions at the end of this section in Standard Edition Scripting Commands: Known Limitations and Deiations on page 286. The following commands are described in these sections: The General commands are: allow on page 274 deinfo on page 274 inquiry on page 274 logpage on page 274 loop on page 274 modepage on page 274 preent on page 275 print on page 275 qrypath on page 275 qryersion on page 275 release on page 275 reqsense on page 276 resere on page 276 resetdrie on page 276 sleep on page IBM Tape Deice Driers Installation and User s Guide

291 IBM Tape Diagnostic Tool tur on page 276 pd on page 276 The Tape commands are: append on page 277 bsf on page 277 bsr on page 277 density on page 277 display on page 277 erase on page 278 fsf on page 278) fsr on page 278 getparms on page 278 load on page 278 logsense on page 278 qrypos on page 279 qrytcpip on page 279 read on page 279 rewind on page 279 rtest on page 279 rwtest on page 280 seod on page 280 setparm on page 280 setpos on page 281 settcpip on page 281 sync on page 282 unload on page 282 weof on page 282 write on page 282 wtest on page 282 The Medium Changer Subcommands are: audit on page 283 cartridgelocation on page 283 elementinfo on page 283 exchange on page 283 inentory on page 283 moe on page 284 position on page 284 The Serice Aid commands are: dump on page 284 ekmtest on page 284 encryption on page 284 ucode on page 285 Chapter 9. IBM Tape Diagnostic Tool (ITDT) 273

292 IBM Tape Diagnostic Tool allow (Deprecated: unlock, -o rem) Allow medium remoal for tape or changer deices (unlock door). The counter command for this is preent. Parameters: None Supported platforms: All deinfo (Deprecated: -o gdi) Show deice information (deice type, sub type and block size) Parameters: None Supported platforms: AIX, Solaris, HP-UX inquiry (Deprecated: -o inq) Issue an Inquiry command and dump the bytes in Hex. Parameters: inquiry [Page code in Hex, 00-FF without leading x] Note: ITDT will print a hex dump of the inquiry data on all platforms. Supported platforms: All logpage (Deprecated: -o log) This subcommand issues the SCSI Log Sense command to the deice for the specified page and displays the log sense data. Parameters: logpage Page (page in hex without the leading x) Supported platforms: All loop This subcommand loops all subsequent subcommands continuously or a number of times if the Count parameter is specified. Also refer to the sleep subcommand. Parameters: loop [Count] Supported platforms: All modepage (Deprecated: -o mod) This subcommand issues the SCSI Mode Sense command to the deice for the specified page and displays the mode sense data. Parameters: modepage Page (page in hex without leading x) 274 IBM Tape Deice Driers Installation and User s Guide

293 IBM Tape Diagnostic Tool Supported platforms: All preent (Deprecated: -o lck, lock) Preent medium remoal for tape or changer deices (lock door). The counter command for this is allow. Parameters: None Supported platforms: All print This subcommand prints the associated text to standard output. It can be used at any time to display the progress of the subcommands. Parameters: print Text Supported platforms: All qrypath (Deprecated: -o phs, path, checkpath) This subcommand displays information about the deice and SCSI paths, such as logical parent, SCSI IDs, and the status of the SCSI paths for the primary path and all alternate paths that are configured. Parameters: None Note: ITDT will show the entire path information for all the commands. Supported platforms: All qryersion (Deprecated: -o dr) This subcommand prints out the current ersion of the IBM deice drier. Parameters: None Supported platforms: All release (Deprecated: -o rel) This subcommand explicitly releases a deice and makes it aailable for other hosts by issuing the SCSI Release command. Parameters: None Supported platforms: All Chapter 9. IBM Tape Diagnostic Tool (ITDT) 275

294 IBM Tape Diagnostic Tool reqsense (Deprecated: -o req) This subcommand issues the SCSI Request Sense command to the deice and displays the sense data in hex format. Parameters: None Supported platforms: All resere (Deprecated: -o res) This subcommand explicitly reseres a deice by issuing the SCSI Resere command. Parameters: None Supported platforms: All resetdrie This subcommand issues a Send Diagnostic command (Reset Drie subcommand) to reset the deice. Parameters: None Supported platforms: AIX, Linux sleep Sleep for the specified number of seconds before executing the next subcommand. Parameters: sleep [Seconds] Supported platforms: All tur (Deprecated: -o tur) This subcommand issues the SCSI Test Unit Ready command to the deice. Parameters: None Supported platforms: All pd This subcommand displays Vital Product Data (VPD) that are part of the Inquiry command data and outputs Manufacturer, Product Identification and Reision Leel. Parameters: None 276 IBM Tape Deice Driers Installation and User s Guide

295 IBM Tape Diagnostic Tool Supported platforms: All append Opens the deice in append mode. The file access permission is Write Only. Parameters: None Supported platforms: All, but on Windows this open mode is not supported by the IBM Tape Deice Drier. On HP-UX this open mode is re-mapped to r/w by the IBM Tape Deice Drier. bsf (Deprecated: -o bsf) This subcommand backward spaces Count filemarks. The tape is positioned on the beginning of the last block of the preious file. An optional Count can be specified. The default is 1. Parameters: bsf [Count] Supported platforms: All bsr (Deprecated: -o bsr) This subcommand backward spaces Count records. An optional count can be specified. The default is 1. Parameters: bsr [Count] Supported platforms: All density (Deprecated: -o gdn / -o rds) This subcommand issues the SCSI Report Density Support command for all supported media and for the current media loaded in the drie, and displays the results. If the drie is not loaded, the current media density is not reported. Parameters: None Note: ITDT-SE will output detailed information on all platforms. Supported platforms: All display (Deprecated: -o msg) This subcommand displays a message on the display panel of the tape deice. Up to 16 characters can be used for the message. If the message is longer than eight characters, the display alternates between the first eight characters and the remainder of the message. Parameters: display message1 message2 Chapter 9. IBM Tape Diagnostic Tool (ITDT) 277

296 IBM Tape Diagnostic Tool Supported platforms: All erase (Deprecated: -o era) This subcommand erases the tape. Parameters: None Supported platforms: All fsf (Deprecated: -o fsf) This subcommand forward spaces count filemarks. The tape is positioned on the first block of the next file. An optional count can be specified. The default is 1. Parameters: fsf [Count] Supported platforms: All fsr (Deprecated: -o fsr) This subcommand forward spaces count records. An optional count can be specified. The default is 1. Parameters: fsr [Count] Supported platforms: All getparms (Deprecated: -o parms / status / -o gpa) Get and show drie, media and drier parameters. Parameters: None Supported platforms: All load (Deprecated: -o lod) This subcommand issues a SCSI Load command to load a tape. subcommand loops all subsequent subcommands continuously or a number of times if the Count parameter is specified. Also refer to the sleep subcommand. Parameters: None Supported platforms: All logsense Retriee all Log Sense pages and output them as hex. Parameters: 278 IBM Tape Deice Driers Installation and User s Guide

297 IBM Tape Diagnostic Tool None Supported platforms: All qrypos (Deprecated: -o gpo) This subcommand displays the current tape position. Parameters: None Supported platforms: All qrytcpip Output the current drie TCP/IP configuration. Only supported with LTO-5. Will output adapter and TCP/IP address information for IP4 with address, port and subnet mask example: itdt -f \\.\tape0 qrytcpip Adapter:1 IPV :7070/112 Exit with code: 0 Parameters: None Supported platforms: All read This subcommand reads a file, or a specified number of records, from the tape to the destination file name specified with the -d flag. If the optional count parameter is used, only the number of records specified with the -c flag are read unless a filemark is encountered before the number of specified records. If the count parameter is not used, all records up to the next filemark on tape are read. Parameters: read -d Dest [-c Count] Supported platforms: All rewind (Deprecated: -o rew) Rewind the tape. Parameters: None Supported platforms: All rtest (Deprecated: -o rea) This subcommand performs a read test by reading a random data pattern from the tape and erifying that it matches the written data. The rtest subcommand can be used after the wtest subcommand to erify the data. An optional block size, count, and repetition can be specified with the -b, -c, and -r flags, respectiely. If the block size is fixed, then the count specifies the number of blocks to read on each repetition. If the block size is zero (ariable), then the count Chapter 9. IBM Tape Diagnostic Tool (ITDT) 279

298 IBM Tape Diagnostic Tool rwtest specifies the number of bytes to read on each repetition. The default is a block size of 10240, a count of 20 blocks, and a repetition of 1. Parameters: read [-b Blocksize] [-c Count] [-r Repetition] Supported platforms: All This subcommand performs a read and write test by writing a random data pattern on the tape, reading it, and erifying that it matches the written data. An optional block size, count, and repetition can be specified with the -b, -c, and -r flags, respectiely. If the block size is fixed, then the count specifies the number of blocks to write on each repetition. If the block size is zero (ariable), then the count specifies the number of bytes to write on each repetition. The default is a block size of 10240, a count of 20 blocks, and a repetition of 1. Parameters: rwtest [-b Blocksize] [-c Count] [-r Repetition] Supported platforms: All seod (Deprecated: -o eod) Spaces to end of data on the tape. Parameters: None Supported platforms: All setparm (Deprecated: -o spa / olid / compress / nocompress / sili / nosili / autoload / noautoload / retain / noretain) ITDT-SE will use the new setparm option that corresponds to the current interactie mode options. Parameters: The Value will be for the blocksize parameter for the capacity parameter (=percentage) 1 (SCSI) and 2 (AIX) for recordspacemode the Volume Id string for the olid parameter NONEASSOPERSWORM for the writeprotect parameter 0 for off/no and 1 for on/yes for setparm autoload, autodump, buffering, compression, immediate, readpastfilemark, sili, simmim, trace, trailer, olumelogging Supported platforms: All, but only a subset of the parameters is supported by the platform's deice driers: 280 IBM Tape Deice Driers Installation and User s Guide

299 IBM Tape Diagnostic Tool Table 29. Supported Platforms Linux Windows AIX Solaris HP-UX setparm autoload X setparm autodump X setparm blocksize X X X X X setparm buffering X X X X setparm capacity X X X X setparm compression X X X X X setparm immediate X X X X setparm readpastfilemark X setparm recordspacemode X setparm sili X X X setparm simmim X setparm trace X setparm trailer X X X X setparm olid X setparm olumelogging X X setparm writeprotect X X X X setpos (Deprecated: -o spo / asf) This subcommand issues the SCSI Locate command to the deice to set the tape position. If the optional Blockid parameter is specified, the tape position is set to the Blockid. Otherwise, if the Blockid parameter is omitted, the tape position is set to the last position saed using the qrypos subcommand. Parameters: setpos [Blockid] Supported platforms: All settcpip Sets the drie Ethernet port TCP/IP settings for LTO-5 dries. If the optional parameters port and subnet_mask_length are not specified, the current settings for these parameters are not changed. IP4 addresses are entered in the syntax a.b.c.d:port/subnet_mask_length where a,b,c,d are alues with 1 to 3 digits. itdt -f \\.\tape0 settcpip :0/24 Setting TCP/TP Configuration... Adapter:1 IPV :7070/112 Adapter:1 IPV6 [0001:0016:0021:01BC:15B3:1A0A:1E61:22B8]:7070/112 Exit with code: 0 Parameters: address[:port[/subnet_mask_length]] Supported platforms: All Chapter 9. IBM Tape Diagnostic Tool (ITDT) 281

300 IBM Tape Diagnostic Tool sync (Deprecated: -o syn) This subcommand will synchronize buffers/flush the tape buffers to tape. Parameters: None Supported platforms: All unload (Deprecated: -o off / offline / rewoffl) This subcommand rewinds and unloads the tape. Parameters: None Supported platforms: All weof (Deprecated: -o eof / eof) These subcommands write count filemarks. An optional count can be specified. The default is 1. Parameters: weof [Count] Note: The weof parameter [count] is optional, if it is not supplied, 1 filemark will be written. Supported platforms: All write This subcommand writes the source file specified with the -s flag on the tape. Parameters: write -s Source Supported platforms: All wtest (Deprecated: -o wri) This subcommand performs a write test by writing a random data pattern on the tape. The rtest subcommand can be used after the wtest subcommand to erify the data that was written. An optional block size, count, and repetition can be specified with the -b, -c, and -r flags, respectiely. If the block size is fixed, the count specifies the number of blocks to write on each repetition. If the block size is zero (ariable), the count specifies the number of bytes to write on each repetition. The default is a block size of 10240, a count of 20 blocks, and a repetition of 1. Parameters: wtest [-b Blocksize] [-c Count] [-r Repetition] Supported platforms: All 282 IBM Tape Deice Driers Installation and User s Guide

301 IBM Tape Diagnostic Tool audit (Deprecated: -o aud / -o ier) This subcommand with no parameters issues the SCSI Initialize Element Status command to the deice. Using the optional parameters Address and Count issues the SCSI Initialize Element Status With Range command to the deice. The Address parameter specifies the starting element address and the Count parameter, if used, specifies the number of elements to initialize. If Count is omitted, it defaults to 1. Parameters: audit [[Address] [Count]] Supported platforms: All cartridgelocation This subcommand with no parameters issues the SCSI Read Element Status command to the deice to report all slots with the cartridge location information. Using the optional parameters Slot and Count issues the SCSI Read Element Status to the deice for a specific starting Slot address and optionally the Count specifies the number of slots to return. If Count is omitted, it defaults to 1. Parameters: cartridgelocation [Slot [Count]] Supported platforms: All elementinfo (Deprecated: -o ele) This subcommand displays element information (number and address) of each element type. Parameters: None Supported platforms: All exchange (Deprecated: -o exh) This subcommand issues the SCSI Exchange Medium command to the deice using the Source, Dest1, and Dest2 addresses specified. This command performs the equialent function of two Moe Medium commands. The first moes the cartridge from the element address specified by the Dest1 parameter to the element address specified by the Dest2 parameter. The second moes the cartridge from the element address specified by the source parameter to the element address specified by the Dest1 parameter. Parameters: exchange Source Dest1 Dest2 Supported platforms: All inentory (Deprecated: -o in) This subcommand with no parameters issues the SCSI Read Element Status command for each element type and displays the element status information. If the optional -i parameter is used, then only the import/export Chapter 9. IBM Tape Diagnostic Tool (ITDT) 283

302 IBM Tape Diagnostic Tool element status information is returned. If the optional - parameter is used, then only the element status information for the specified Volid if found is returned. Parameters: inentory [-i - Volid] Note: ITDT will support the optional parameters on all platforms. Supported platforms: All moe (Deprecated: -o mo) This subcommand issues the SCSI Moe Medium command using the source and destination addresses specified. The element addresses can be obtained using the elementinfo subcommand. Parameters: moe Source Dest Supported platforms: All position (Deprecated: -o pos) This subcommand issues the SCSI Position to Element command using the destination specified. Parameters: position Dest Supported platforms: All dump (Deprecated: -o sdp) Forces a dump of the tape drie and stores the dumps before and after the force dump in the ITDT-SE output folder with the ITDT-SE naming conention (serialnumber.a.gz and serialnumber.b.gz). Parameters: None Supported platforms: All ekmtest Test encryption key path/setup. Parameters: None Supported platforms: AIX, Linux, Solaris, Windows encryption Query tape drie encryption settings and display the encryption state. Parameters: None 284 IBM Tape Deice Driers Installation and User s Guide

303 IBM Tape Diagnostic Tool ucode Supported platforms: All (Deprecated: -o dmc) This subcommand downloads microcode to the deice. The Filename is a file that contains the ucode. Parameters: ucode Filename Supported platforms: All Deprecated Commands The following is a list of commands that are currently aailable in this ersion of ITDT, howeer in a future release the following commands and some alternate calls of the Common Command Scripting set will no longer be aailable and the scripts containing these commands will need to be changed. The scripts using the deprecated commands should be changed for future editions. The General commands are: disablepath / -o dis enablepath / -o ena fuser kill passthru resetpath The Tape commands are: bsfm chgpart -o chk fsfm getrecsize / -o grs idp list mediainfo / -o gmi qryinquiry qrypart qrysense retension / -o ret sdp setblk status / -o gds The Medium Changer subcommands are: deids / -o dc mount unmount / demount The Serice Aid commands are: Chapter 9. IBM Tape Diagnostic Tool (ITDT) 285

304 IBM Tape Diagnostic Tool fmrtape forcedump / -o fdp reset ucodeleel / -o qmc Standard Edition Scripting Commands: Known Limitations and Deiations The scripting commands idp, sdp, chgpart and qrypart are currently not supported with LTO5 dries. They are currently kept for legacy reasons as-is, but will be promoted to first-class commands for LTO5 dries with a later release. When scripting, one should be aware of the following general deiations to the legacy tapeutil scripting command set. The Verbose Mode parameter is ignored for the ITDT-SE implementation; instead always the full information is printed out. For some operations, the sense data length is limited to 32 bytes this is required by the ITDT test sequences. The list command will not work on Linux ariants where the reported maximum SCSI transfer size is larger than the size the system can actually transfer. Due to the fact that ITDT-SE opens the deice read/write by default in scripting mode, the WORM mode can not be deactiated in scripting mode. Use the Tapeutil interactie mode instead to deactiate the WORM mode. Scripting mode command deiations to legacy tapeutil (tapeutil will not be changed): 1. The erg (Erase Gap) command will not be supported. 2. The mtdeice command will not be supported. 3. The tell command will not be supported. 4. The seek command will not be supported. 5. The format command will not be supported. 6. The -o qsn command will not be supported. 7. path/querypath/path / qrypath / checkpath /-ophs-output: always show all paths. 8. deinfo - different output (decoded on all platforms) 9. inquiry - different output on Linux (like AIX in hex) 10. pd - different behaior on Solaris (like AIX) 11. modepage - HP-UX and Solaris output deiations (like AIX) 12. inentory - additional parameters on AIX aailable on all platforms 13. cartridgelocation - AIX parameter deiation aailable on all platforms 14. mediainfo - different output -> decode on all platforms 15. setpos - logical s. physical position, only set logical position as on AIX 16. HPUX: -o gpo -t 12 --> parameter -t12 (logical, physical) is not supported. 17. density - output all information on all platforms 18. setparm (new) - work around the inability to set all parameters on all platforms except the undocumented HP-UX release 286 IBM Tape Deice Driers Installation and User s Guide

305 IBM Tape Diagnostic Tool 19. getparms (new) - retriee all parameters on all platforms, independent of flag set 20. qryinquiry - output the same as on AIX 21. logsense - does not output header with deice/serial/olid, example: Graphical Edition - Installation 05/12/09 15:10:44 Deice: ULT3580- S/N: Volid: UNKNOWN Windows To install ITDT-GE on Windows, download the executable file install_itdt_ge_<ersion>.exe on a directory of your choice. Double-click the downloaded file to launch the installer application. ITDT-GE installer automatically uninstalls any preious ersion before installing the current one. ITDT-GE requires a 32-bit Jaa Runtime Enironment (JRE) to be installed. Install one of the following: Jaa SR11 by IBM Corporation or higher Jaa 1.4.2_17 by Sun Microsystems or higher Note: If IBM Jaa 1.5 on a Microsoft Windows system is used, ensure that it is Jaa 1.5 SR6 or higher. For the graphical user interface (GUI) a minimum screen resolution of 1024*768 pixels is required. The supported Windows operating systems for ITDT-GE are: Microsoft Windows XP Microsoft Windows Serer 2003 Microsoft Windows Serer 2008 (x86, 32-bit) 64-bit Windows x64 is supported for ITDT-GE, but 32-bit JVM must be used. Linux To install ITDT-GE on Linux, download the executable file install_itdt_ge_<ersion>.bin to a directory of your choice. install_itdt_ge_<ersion>.bin needs to be run by a user with root access rights. ITDT-GE requires a 32-bit Jaa Runtime Enironment (JRE) to be installed. Note: The JRE deliered with Red Hat Enterprise Linux 4 and 5 (RHEL4, RHEL5) is not supported. Install one of the following supported JREs before launching the ITDT Installer: Jaa SR11 by IBM Corporation or higher Jaa 1.4.2_17 by Sun Microsystems or higher On RHEL4, RHEL5 and other Linux systems where none of the supported JREs is aailable in the path do the following: Chapter 9. IBM Tape Diagnostic Tool (ITDT) 287

306 IBM Tape Diagnostic Tool 1. Add your Jaa directory to the path before starting the installer: The following are examples of how to extend the search path (replace <ersion> with the ersion that is in use). For IBM Jaa Runtime Enironment: $ export PATH=/opt/IBMJaa2-142/jre/bin:$PATH $./install_itdt_ge_<ersion>.bin For Sun Microsystems Jaa Runtime Enironment: $ export PATH=/usr/jaa/j2re1.4.2_09/bin:$PATH $./install_itdt_ge_<ersion>.bin Note: In the aboe examples, replace the directory names with your JRE directories. 2. Create a symbolic link to the JRE to ensure that ITDT finds the right JRE before starting ITDT-GE. For IBM Jaa Runtime Enironment: $ ln -sf /opt/ibmjaa2-142/jre /opt/ibm/itdt-ge/jre For Sun Microsystems Jaa Runtime Enironment: $ ln -sf /usr/jaa/j2re1.4.2_09 /opt/ibm/itdt-ge/jre Note: In the aboe examples, replace the directory names with your JRE directories. The ITDT-GE installer automatically uninstalls any preious ersion before installing the current one. For the graphical user interface (GUI) a minimum screen resolution of 1024*768 pixels is required. The supported Linux operating systems for ITDT-GE are: Linux Distributions with glibc and higher (x86, 32-bit) Graphical Edition - Known Issues and Limitations This section describes the known issues and limitations of ITDT-GE. Linux It is strongly recommended to not operate Security Enhanced Linux (SELinux) in enforcing mode while running ITDT-GE. On RedHat Enterprise Linux 4 and 5 and SuSE Enterprise Linux 10 inoking the online help may cause an error message "Problems opening link / Unable to open web browser on {0}" to appear. Workarounds are to issue the commands: a) ln -s /usr/bin/firefox /usr/local/bin/mozilla or b) export MOZILLA_FIVE_HOME=/usr/lib/firefox<ersion> Replace with the appropriate path to your installed Firefox ersion before starting ITDT-GE. Gnome Desktop If you are using the Gnome desktop, please be sure to log into the desktop session as root to use ITDT-GE to preent deice access issues. 288 IBM Tape Deice Driers Installation and User s Guide

307 IBM Tape Diagnostic Tool Windows On Microsoft Windows systems where the maximum transfer size is limited to less than 64kB, the Dump and Firmware update operations will not work. Performance Issues If you are using Adaptec SCSI Host Bus Adapters, ensure that you are using the latest Adaptec Host Bus Adapter Driers instead of the driers shipped with the Windows operating system. Deices Disappear After Firmware Update After a firmware update, deices may disappear. This is a known Windows problem. See the Article ID: at: Repeated Scan operations may help to rediscoer the deice. All Supported Operating Systems Command Timeout There is no instant operation termination upon SCSI command timeout; for example, when the SCSI cable is unplugged after starting POST A. When a command timeout condition occurs, ITDT may still continue to perform more operations (like unmounting the cartridge) instead of instantly terminating with a timeout condition. 3576/TS3310 Tape Library Library Firmware Update using ITDT-GE is not supported with the 3576/TS3310 tape library. Update the Firmware using the 3576/TS3310 Web User Interface Tape Library Dries in a 3494 tape library or an STK silo library are supported, only the Test option won t work due to deice-specific restrictions for handling cartridges. Graphical Edition - User Interface Description a Figure 69. Graphical Edition User Interface To start ITDT-GE on Windows click the shortcut created by the installation process. On Linux, no start menu entry is generated. Start ITDT-GE by opening a Terminal window, then switch to root user: $sufinally start ITDT-GE with $ /opt/ibm/itdt-ge/itdt-ge Chapter 9. IBM Tape Diagnostic Tool (ITDT) 289

308 IBM Tape Diagnostic Tool The User Settings dialog appears the first time the program is run, allowing the entry of user specifications: user name, company name, output path and log leel. The Output Path defines the location where the test reports and dumps are saed. The Windows default output path is C:\Documents and Settings\<username>\.itdt-ge\output where <username> is the Windows user login name. The Linux default output path is /root/.itdt-ge/output The Log Leel should not be changed unless requested to do so by the IBM Support Center. It is strongly recommended that this information be proided to allow for further analysis of test results. The interface of the GE edition is as follows: The main menu in the upper left The graphical buttons to select either the Diagnostic or the Tapeutil perspectie The Control Center with the toolbar that contains the main actions as well as adanced actions that can be reached by drop-down arrows The test tab area on the right that contains all output of the running as well as preiously finished tests The Status Information area on the bottom that summarizes the results of preiously run tests or notifies when a test tab requires user input a Figure 70. Graphical Edition Preferences It is strongly recommend that this information be proided to allow for further analysis of test results. Click OK to sae the settings and close the dialog. 290 IBM Tape Deice Driers Installation and User s Guide

309 IBM Tape Diagnostic Tool The ITDT-GE interface contains the following: a Figure 71. Graphical Edition Interface Main Menu ( 1 on Figure 71)- Located in upper left (File, Window, Help) The following main program menu items are aailable: a Figure 72. Main Program Menu Items Control Center ( 2 on Figure 71) - Located on left side (Deice operations - Scan, Test, Dump, and Update) Additional deice operations are aailable using drop-down arrows. Test Lab ( 3 on Figure 71) - Located from center to right side (Contains running and preiously run tests) Status Information ( 4 on Figure 71) - Located below the Test Lab (Contains summary results of tests) The Control Center is the primary section the ITDT-GE operations. The following toolbar buttons for the deice operations are aailable: Chapter 9. IBM Tape Diagnostic Tool (ITDT) 291

310 IBM Tape Diagnostic Tool a Figure 73. Toolbar Buttons Click the Scan menu item in the Control Center to display the list of tape deices found. When the scan is complete, select one deice in the Test Lab by clicking the corresponding checkbox. Test Click the arrow next to the Test menu item to select an extended test. Dump Click the arrow next to the Dump menu item to select additional log options. Update Click the Update menu item to start the firmware update. For each deice on which the operation has been started, a tab appears on the right panel (Test Lab area). The tab contains the operation information and status. Only one operation can be run at a time with ITDT-GE. The benefit in using tabs een for the single operation mode is that you get a history of operations as for each consecutie operation, a separate tab is opened. Graphical Edition - Scan Menu Commands The following commands are described in this section: Scan on page 293 Test on page 294 Dump on page 296 Firmware Update on page 297 Encryption on page 298 Full Write on page 299 Tape Usage on page 301 System Test on page 301 Library Diagnostic Self-Test on page IBM Tape Deice Driers Installation and User s Guide

311 IBM Tape Diagnostic Tool Scan a Figure 74. Scan Function The scan function is used to discoer all supported tape and library deices that are attached to the computer system so that they can be selected for the subsequent ITDT-GE operations. The scan function also seres as a connection test that can be used to erify proper attachment of the deices. Note: When pressing the Scan button for the first time, a dialog box is displayed, that warns the user to stop all backup jobs. Once the scan is finished, the deice list is displayed, in the Control Center area. A scroll bar is aailable to display all the deices. Once the desired deice is displayed, select the deice for test. Only one deice can be selected. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 293

312 IBM Tape Diagnostic Tool Test a Figure 75. Test Menu The test function checks if the tape deice is defectie and outputs a pass/fail result. Attention: The test functionality erases user data on the cartridge that is used for the test. Notes: 1. The test can take from 15 minutes up to 2 hours. 2. The test runs only on tape dries, not on autoloaders or libraries. To perform the Test function, it is recommended that a new or rarely used cartridge is used. Scaled (capacity-reduced) cartridges should not be used to test the deice. To test tape dries within a library, the library must be in online mode. After selecting the deice you want to test, start the Test function selecting the Test menu item. The Test function can be stopped by clicking the Abort button. Note: It may take some time until the Test function actually stops. 294 IBM Tape Deice Driers Installation and User s Guide

313 IBM Tape Diagnostic Tool 1 a Figure 76. Test Results Note: Information can be found in the.txt/.blz files. See the log file section ( 1 ). The test sequence contains the following steps: 1. Mount Medium 2. [Medium Qualification] only if the preious step indicated this requirement 3. Load/Write/Unload/Read/Verify 4. POST A 5. Performance Test (run 2 times if first run failed with performance failure) 6. POST B 7. Unmount Medium 8. Get FSC 9. Get Logs Chapter 9. IBM Tape Diagnostic Tool (ITDT) 295

314 IBM Tape Diagnostic Tool Dump a Figure 77. Dump Menu After selecting the deice you want to dump, start the Dump function by selecting Dump -> Dump from the actions toolbar. When the dump process is performed on a tape library or autoloader other than the 3584/TS3500, the Dump function stores one log file in the output folder of the program (*.blz). For the 3584/TS3500, a dump file (*.a.gz) will be stored in the output folder. Both files start with the serial number of the deice ( 1 ). 296 IBM Tape Deice Driers Installation and User s Guide

315 IBM Tape Diagnostic Tool 1 2 a Figure 78. Dump Results Note: When the Dump function is performed for tape libraries or autoloaders other than the 3584/TS3500, the Log file only contains Log Sense and Mode Sense pages, while a Drie or 3584/TS3500 Dump contains much more diagnostic information. ( 2 ) Firmware Update The Firmware Update upgrades the firmware of tape dries and tape libraries. See Supported Equipment on page 235 for a list of supported products. Note: See 3576/TS3310 Tape Library on page 246 for more information on how to update the firmware on a 3576/TS3310 Tape Library. The following site is aailable for the latest firmware files: To do a Firmware Update perform the following steps: 1. Select the deice you want to update. 2. Select the Update menu item. 3. A standard file dialog opens to select the path of where the firmware update is located. The path is either the default input path or the location of the last successfully opened firmware file. Press OK button on this file dialog to start the update on the selected deice. During the firmware update, a firmware update progress screen is displayed, indicating the progress of the update. Attention: Once started, do not interrupt the firmware update. The firmware update usually takes 3-5 minutes, but it can take up to 45 minutes for libraries. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 297

316 IBM Tape Diagnostic Tool Encryption Note: If ITDT-GE detects a FIPS-certified drie firmware, it displays a warning dialog. Before continuing, ensure that you use a FIPS-certified firmware to update the drie. a Figure 79. Encryption Function Note: Note that the test shown on the graphic aboe was run on a non-encrypted deice and is showing a failure. The Encryption function is used to erify if data on the cartridge was actually written encrypted. It reads both decrypted and raw data from the cartridge into two separate files on disk. The user can then erify that the data differs to ensure that encryption worked. The Encryption function is only supported on encryption enabled dries and requires an encryption infrastructure including the Encryption Key Manager (EKM) to be properly set up. 1. After selecting the deice you want to test, start the encryption function by selecting Test -> Encryption Verification from the actions toolbar. 2. ITDT-GE then displays the Encryption Verification screen. On this screen, the system requires the entry of the number of the start record and the amount of data (in KB) to be read. 3. Enter the required alues and click OK to start the encryption. The Encryption function can be stopped by clicking the Abort button. Note: It may take some time until the Encryption function actually stops. Table 28 on page 257 defines the abort codes. 298 IBM Tape Deice Driers Installation and User s Guide

317 IBM Tape Diagnostic Tool Full Write The Full Write function writes the entire cartridge with a gien block size either with compressible or incompressible data and output performance data. Attention: The Full Write function erases data on the cartridge that is used for the test. Notes: 1. The Full Write function takes approximately 2 hours when writing incompressible data, less time for compressible data. 2. The Full Write function runs only on tape dries, not on autoloaders or libraries. The Full Write test can be used to: Demonstrate that the drie is capable of writing the full amount of data on a cartridge. Reeal system performance bottlenecks. Full Write firsts runs the test with incompressible data first, then runs the test with compressible data. If no difference in oerall performance is obsered, then probably there is a bandwidth limitation caused by the system or cabling or HBA. Identify system issues with compression. Compression is always switched on during the full write. When run with compressible data, the output shows the compression rate. If that is higher than 1.0 but your system does not appear to be able to compress data on the cartridge, check your deice drier and software settings to see if they disable compression. To perform a full write on tape dries within a library, the library must be in online mode. 1. After selecting the deice you want to write to, start the Full Write function by selecting Test -> Full Write from the actions toolbar. 2. Click OK to start the full write. ITDT-GE then displays the Full Write screen. If no cartridge is inserted, ITDT-GE prompts to insert a cartridge. Either insert a cartridge and click OK or stop by clicking the Abort button. Note: If ITDT-GE detects data on the cartridge, it displays the following message (Figure 80 on page 300): Chapter 9. IBM Tape Diagnostic Tool (ITDT) 299

318 IBM Tape Diagnostic Tool a Figure 80. Oerwrite Data Click Yes to continue the test if you are absolutely sure that data on the cartridge can be oerwritten. If you are unsure, click No to stop the test. 3. The system prompts for entry of a transfer size between 16 KB and the maximum block size supported by the system (maximum possible alue is 512 KB). Select the appropriate alue for your system. a Figure 81. Transfer Size 4. Select the type of data to write, either: [C] Compressible or [I] Incompressible. The full write can be stopped by clicking the Abort button. Note: It may take some time until the full write actually stops. "Compressible = Yes" means that the data written was just zeroes, so that the data could be compressed by the drie with a maximum compression ratio. "Compressible = No" means that a data pattern was written that the drie could almost not compress at all. If the compression ratio is 1, the drie was not able to compress the data (equialent to 1:1 compression ratio). If the compression ratio is 94.0, the drie was able to do 94:1 compression meaning 300 IBM Tape Deice Driers Installation and User s Guide

319 IBM Tape Diagnostic Tool that 94 bytes in the original data could be compressed to 1 byte on the medium means 100 bytes could be compressed down to 1 byte on the medium. If all write operations are finished, ITDT-GE displays the performance statistics for the selected block size written on the cartridge, in the Status Information area. If an error occurred during the full write, data is only written partially. Tape Usage a Figure 82. Tape Usage The Tape Usage function retriees statistical data and error counters from a cartridge. 1. After selecting the deice you want to test, start the Tape Usage function by selecting Dump -> Tape Usage Log from the actions toolbar. 2. ITDT-GE then displays the tape usage screen. If no cartridge is inserted, ITDT-GE prompts to insert a cartridge. Either insert a cartridge and click OK or stop by clicking the Abort button. System Test The System Test is a short test that performs the following: Reeals system performance bottlenecks. Compressible data throughput alues can reeal bandwidth limitations caused by the system or cabling or HBA. Measures performance ariations across the different block sizes to find the ideal block size for the system configuration. The System Test only runs on tape dries, not on autoloaders or libraries. To perform a System Test on tape dries within a library, the library must be in online mode. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 301

320 IBM Tape Diagnostic Tool After selecting the deice you want to test, start the System Test function by selecting Test -> System Test from the actions toolbar. ITDT-GE then displays the System Test screen. If no cartridge is inserted, ITDT-GE prompts to insert a cartridge. Either insert a cartridge and click OK or stop by clicking the Abort button. Note: If ITDT-GE detects data on the cartridge, it displays the following message: Cartridge not empty! Oerwrite data? Click Yes to continue the test if you are absolutely sure that data on the cartridge can be oerwritten. If you are unsure, click No to stop the test. a Figure 83. System Test The System Test is performed as follows: 1. System Test determines the amount of data to write for each supported blocksize (a percentage of the cartridge is written for each blocksize). 2. System Test writes the amount of data with all supported block sizes in powers of two down to 16kB (at maximum 512, 256, 128, 64, 32, 16), first with incompressible, then with compressible data, and then displays performance data and progress screen. 3. At the end of the test, a summary information is displayed. Library Diagnostic Self-Test The Library Self-Test starts and monitors the library-internal self-test. This test only runs on libraries and autoloaders, not on tape dries. After selecting the deice you want to test, start the Library Self-Test function by selecting Test -> Library Diagnostic Self-Test from the actions toolbar. 302 IBM Tape Deice Driers Installation and User s Guide

321 IBM Tape Diagnostic Tool At the end of the test, the results are displayed in the Status Information area. Manual Inspection Record Entry A manual inspection record can be generated if the deice does not appear in the deice list. This test is intended for deices that are not recognized or hae a technical problem which can not be determined by ITDT-GE. If a tape drie cannot be identified using a deice scan, the user can manually create a test record for the drie. The system prompts for the user to run the SCSI/FC Wrap test for the drie (see the serice manual for the drie). The results of the wrap test can be entered along with some additional inspection information. The result are saed into binary and text output files that hae the same format as the output files generated by the test. 1. From the Main program menu, select File -> Manual Record 2. Enter the required information to complete the items in the screen: a. Enter the deice serial number. b. Enter the content of the Message Display. c. Optionally, enter any additional information text. 3. After all information has been entered, click OK. The information is stored in a binary file (which can be used for further analysis), and in a human-readable text file. Both files are stored in the ITDT-GE output folder. Graphical Edition - Tapeutil Menu Commands After the initial startup, 4.0 will show two figures under the top menu. The Graphical ersion now offers the same commands that are found in the SE Tapeutil section along with the Diagnostic commands. After selecting the Tapeutil option the following page will appear. Chapter 9. IBM Tape Diagnostic Tool (ITDT) 303

322 IBM Tape Diagnostic Tool a Figure 84. Tapeutil Control Center The left drop-down box within the Tapeutil Control Center is used to select between Tape Drie Commands and Tape Library Commands. The commands from the General Commands and Serice Aid Commands ITDT-SE categories are duplicated into the two sections to make the GUI naigation easier. After the command category is selected, a drop-down box appears that allows the selection of a command: 304 IBM Tape Deice Driers Installation and User s Guide

323 IBM Tape Diagnostic Tool a Figure 85. Tape Drie Commands After the command is selected, an area appears where command parameters can be entered: a Figure 86. Command Parameters When the user presses the Execute button, the Results output is placed below the Parameter section: Chapter 9. IBM Tape Diagnostic Tool (ITDT) 305

324 IBM Tape Diagnostic Tool a Figure 87. Command Parameter Results This screen layout will stay within the Tapeutil perspectie until the program is closed. Outputs of subsequent operations are added to the Results field. Commands that fail are indicated with a red cross in the Status area, commands that succeed with a green check mark. The status area can be cleared by pressing the Clear button. The general commands that are aailable under both menus are: Open on page 307 Close on page 307 Inquiry on page 308 Test Unit Ready on page 308 Resere Deice on page 308 Release Deice on page 308 Request Sense on page 308 Log Sense on page 308 Mode Sense on page 308 Query Drier Version on page 308 Display All Paths on page 308 The tape drie specific commands are: Rewind on page 309 Forward Space Filemarks on page 309 Backward Space Filemarks on page 309 Forward Space Records on page 309 Backward Space Records on page 309 Space to End of Data on page 309 Read and Write Tests on page IBM Tape Deice Driers Installation and User s Guide