IBM Tape Device DriversInstallation and User’s Guide GC27-2130-07 IBM Tape Device Drivers Installation and User’s Guide GC27-2130-07 Note! Before using this information and the product that it supports, be sure to read the general information under “Notices” on page 387. Eighth Edition (February 2009) This eighth edition of the IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-07, replaces and makes obsolete the following manuals: v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-06 v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-05 v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-04 v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-03 v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-02 v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-01. v IBM Tape Device Drivers Installation and User’s Guide, GC27-2130-00. v IBM TotalStorage and System Storage Tape Device Drivers Installation and User’s Guide, GC35-0154-17. v IBM Ultrium Device Drivers Installation and User’s Guide, GC32-0430-13 © Copyright International Business Machines Corporation 2007, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii Preface . . . . . . . . . . . . . . . ix Related Information . . . . . . . . . . . . ix How to Send Your Comments . . . . . . . . xiv Special Printing Instructions . . . . . . . . . xv Data Flow . . . . . . . . . . . . . . . 91 Product Requirements . . . . . . . . . . . 92 Installation and Configuration Instructions . . . . 94 Tape Drive, Media, and Device Driver Parameters 100 Special Files . . . . . . . . . . . . . . 105 Control Path Failover Support for Tape Libraries 106 Data Path Failover and Load Balancing Support for Tape Drives . . . . . . . . . . . . . . 108 Open Source Device Driver - lin_tape . . . . . 110 System-Managed Encryption . . . . . . . . 111 Problem Determination . . . . . . . . . . 114 Chapter 1. Introduction . . . . . . . . 1 Purpose . . . . . IBM Tape Products . . . . . . . . . . . . . . . . . . . . . . 1 . 1 Chapter 2. Common Extended Features Purpose . . . . . . . . . Supported Hardware . . . . Path Failover and Load Balancing Data Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 . 9 . 9 . 13 . 15 Chapter 6. Solaris Tape and Medium Changer Device Driver . . . . . . . 121 Purpose . . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . . Product Requirements . . . . . . . . . . Installation and Configuration Instructions . . . Special Files . . . . . . . . . . . . . . Persistent Naming Support . . . . . . . . . Control Path Failover Support for Libraries . . . Data Path Failover and Load Balancing Support for Tape Drives . . . . . . . . . . . . . . System-Managed Encryption . . . . . . . . Problem Determination . . . . . . . . . . 121 121 122 124 142 145 146 147 150 152 Chapter 3. AIX Tape and Medium Changer Device Driver . . . . . . . . 21 Purpose . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . . Product Requirements . . . . . . . . . . Installation and Configuration Instructions . . . Tape Drive, Media, and Device Driver Parameters Special Files . . . . . . . . . . . . . Persistent Naming Support . . . . . . . . Control Path Failover Support for Tape Libraries . Data Path Failover and Load Balancing Support for Tape Drives . . . . . . . . . . . . . System-Managed Encryption . . . . . . . Problem Determination . . . . . . . . . Tape Drive Service Aids . . . . . . . . . Performance Considerations . . . . . . . . . . . . 21 22 22 24 26 . 32 . 34 . 35 37 39 41 46 49 Chapter 7. Windows Tape and Medium Changer Device Driver . . . . . . . 159 Purpose . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . Product Requirements . . . . . . . . . Installation and Configuration Instructions . . Persistent Naming Support on Windows Server 2003 and Windows Server 2008 . . . . . . Control Path Failover Support for Tape Libraries Data Path Failover Support for Tape Drives . . System-Managed Encryption . . . . . . . Problem Determination . . . . . . . . . . . . . 159 159 160 161 . . . . . Chapter 4. HP-UX Tape and Medium Changer Device Driver . . . . . . . . 53 Purpose . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . . Product Requirements . . . . . . . . . . Installation and Configuration Instructions . . . Supported Configuration Parameters . . . . . Special Files . . . . . . . . . . . . . Persistent Naming Support . . . . . . . . Control Path Failover Support for Tape Libraries . Data Path Failover and Load Balancing Support for Tape Drives . . . . . . . . . . . . . Problem Determination . . . . . . . . . . . . . . . . . 53 53 54 56 73 76 78 78 . 177 178 . 179 . 180 . 181 Chapter 8. Tru64 Device Driver . . . . 185 Purpose . . . . . Product Requirements . . . . . . . . . . . . . . . . . . . 185 . 185 Chapter 9. 3494 Enterprise Tape Library Support . . . . . . . . . . 189 Purpose . . . . . . . MTLIB Program . . . . MTEVENT Program . . . Library Driver Information . 3494 Library Emulation . . AIX . . . . . . . . HP-UX . . . . . . . Linux . . . . . . . . Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 190 201 201 205 208 217 224 230 . 80 . 83 Chapter 5. Linux Tape and Medium Changer Device Driver . . . . . . . . 91 Purpose . . . . . . . . . . . . . . . 91 © Copyright IBM Corp. 2007, 2009 iii Windows . TRU64. . SGI IRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 . 243 . 249 Solaris System . . Microsoft Windows Tru64 System . . SGI/IRIX System . . . . System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 312 314 316 Chapter 10. IBM Tape Diagnostic Tool (ITDT). . . . . . . . . . . . . . . 255 Purpose . . . . . . . . . . . . . . Accessing ITDT . . . . . . . . . . . Supported Systems . . . . . . . . . . Supported Equipment . . . . . . . . . Standard Edition - Installation and Initial Startup Standard Edition - Known Issues and Limitations Standard Edition - Start Menu Commands . . Standard Edition - Scan Menu Commands. . . Standard Edition - Tapeutil Menu Commands . Graphical Edition - Installation . . . . . . Graphical Edition - Known Issues and Limitations Graphical Edition - User Interface Description . Graphical Edition - Scan Menu Commands . . . . . . 256 257 257 258 259 262 265 266 279 287 288 289 291 Appendix C. Managing the Microcode on the IBM Tape Drive . . . . . . . 317 AIX System . . . HP-UX System . . Linux System . . Solaris System . . Microsoft Windows Tru64 System . . . . . . . . . . . . . . System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 318 318 318 318 319 . . . . . . Appendix D. Tape Utility Programs 321 322 335 345 357 366 385 Appendix A. Accessing Documentation and Software Online . 301 Appendix B. Verifying Proper Attachment of Your Devices . . . . . 303 AIX System . . HP-UX System . Linux System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 . 306 . 308 AIX System - Tape Utility Program (tapeutil) . . . HP-UX System - Tape Utility Program (tapeutil) Linux System - Tape Utility Program (IBMtapeutil) Solaris System - Tape Utility Program (tapeutil) Microsoft Windows System - Utility Program (ntutil). . . . . . . . . . . . . . . . Tru64 System - RAS Utility Program (IBMrasutil) Notices . . . . . . . . . . . . . . 387 Trademarks . . . . . . . . . . . . . . 387 Index . . . . . . . . . . . . . . . 389 iv IBM Tape Device Drivers Installation and User’s Guide Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. Current Attachment Array . . . . . . . . 2 Example of an IBM Tape Environment . . . . 3 Sample Encryption Configuration File. . . . 18 Data Flow for AIX Device Driver (Atape) 22 Data Path for AIX Device Driver (Atape) 50 Data Flow for HP-UX Device Driver (ATDD) 54 Example of atdd_d.log Output . . . . . . 86 Data Flow for Linux Device Driver (lin_tape) 92 Data Flow for Solaris Device Driver (IBMtape) . . . . . . . . . . . . . 122 Example of Control Path Failover Support Command Output . . . . . . . . . . 147 Example of Data Path Failover Support Command Output . . . . . . . . . . 149 Data Flow for Windows Device Driver (IBMmag) . . . . . . . . . . . . . 159 Select Components Menu (using IBMUltrium.WinNT.exe) . . . . . . . . 163 Start Menu . . . . . . . . . . . . 164 Creating Driver List . . . . . . . . . 164 Rescanning for Tape Device . . . . . . . 164 Install Driver Menu - Select Cancel . . . . 165 Tape Devices Menu . . . . . . . . . 166 Have Disk Menu . . . . . . . . . . 167 Install Driver Menu . . . . . . . . . 168 Windows NT Statement . . . . . . . . 168 Tape Devices and Remove Driver Menu 169 Control Panel Selection . . . . . . . . 170 Add/Remove Programs Properties . . . . 171 Drive Removal Menu . . . . . . . . . 172 Manual Starting and Stopping Menu 173 Installation Application in Windows Explorer 175 Windows Logo Testing screen . . . . . . 176 Checked folder . . . . . . . . . . . 183 Example Output for Tru64 Device Driver and IBM 3590 Tape Drive . . . . . . . . . 187 Syntax Diagram for mtlib program . . . . 190 Device Query . . . . . . . . . . . 193 Volume Query . . . . . . . . . . . 193 Expanded Volume Query . . . . . . . 194 Expanded Volume Data with Usage . . . . 194 Inventory Count Data. . . . . . . . . 194 Tape Library Device Number . . . . . . 195 Expanded Tape Library Device List . . . . 195 Library Data . . . . . . . . . . . . 196 Statistical Data . . . . . . . . . . . 197 Inventory Query . . . . . . . . . . 198 Category Inventory Query . . . . . . . 199 Reserve Category Command . . . . . . 200 Reserve Category List . . . . . . . . . 200 Category Attribute List . . . . . . . . 200 Library Address Information . . . . . . 201 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 3494/SMC Library Data Flow . . . . . . LIBSMC and OS Components . . . . . . Data Flow for AIX 3494 Enterprise Tape Library Driver . . . . . . . . . . . SMIT Main Menu . . . . . . . . . . SMIT Devices Menu . . . . . . . . . SMIT Tape Drive Menu . . . . . . . . Tape Drive Type Menu . . . . . . . . Add an LMCP Logical Device 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 Driver . . . . . . . . . . . Data Flow for Linux 3494 Enterprise Tape Library Driver . . . . . . . . . . . Data Flow for Solaris 3494 Enterprise Tape Library Driver . . . . . . . . . . . Data Flow for Windows 3494 Enterprise Tape Library Driver . . . . . . . . . . . Data Flow for TRU 64 3494 Enterprise Tape Library Driver . . . . . . . . . . . Data Flow for SGI IRIX 3494 Enterprise Tape Library Driver . . . . . . . . . . . Start Screen Menu . . . . . . . . . . Scan Menu . . . . . . . . . . . . More Scan Options. . . . . . . . . . Device List Screen . . . . . . . . . . Data Delete Question . . . . . . . . . Test Running. . . . . . . . . . . . Test Results . . . . . . . . . . . . Dump . . . . . . . . . . . . . . Full Write Results . . . . . . . . . . Tape Usage Screen . . . . . . . . . . System Test Results . . . . . . . . . Graphical Edition User Interface . . . . . Graphical Edition Pre-scan Interface . . . . Scan Function . . . . . . . . . . . Test Menu . . . . . . . . . . . . Test Results . . . . . . . . . . . . Dump Menu . . . . . . . . . . . . Dump Results . . . . . . . . . . . Encryption Function . . . . . . . . . Overwrite Data . . . . . . . . . . . Transfer Size . . . . . . . . . . . . Tape Usage . . . . . . . . . . . . System Test . . . . . . . . . . . . Linux Command Line Help Display . . . . Example of Base Mode . . . . . . . . Example of Library Mode . . . . . . . Symbolic Values . . . . . . . . . . 205 206 208 212 212 213 213 213 214 214 214 218 225 231 237 244 250 265 266 267 268 269 270 270 271 276 276 278 289 290 291 292 293 294 294 296 298 298 299 300 346 368 369 383 © Copyright IBM Corp. 2007, 2009 v vi IBM Tape Device Drivers Installation and User’s Guide . 7. . 29. 2. 8. . 126 . . . .Equipment Listing Example 2 . 17. . 95 Special Files for IBM TotalStorage Tape Devices . . .IBMtape . 2007. . 26. . . 130 . . . . . . . . 77 Trace Flags . . . . . . Configuration Parameters Recognized by IBMtape . . Ultrium Product Comparison . . . . . . 24. 31.Tables 1. .IBMtape . . . . . . . . 105 19. 87 Troubleshooting (Problems and Solutions) 88 Components Created During lin_tape Installation . . . . 4. . IBMtape Install or Update . . 138 . . . Definitions of Abort Codes . . . . . 19 Feature Codes (Encryption) . Tape Utility Program Documentation . . 75 Special Files . Solaris Device Driver . . IBM SCSI Tape/Medium Changer Special Files for Solaris . . . . . . . . . . . . . 21. and Solutions . . . . Solaris Device Driver . . . . 22. 3. . . Driver Descriptions . . . . . 2009 vii . . . . .IBMtape . . . 18. 6. . 23. . . 9. . . . 84 Problems. . . . . 13. . . . . . . . . IBMtape Components . 16. . . 95 Components Created During IBMtapeutil Installation . . . . . . . . . 77 New Special Files in HP-UX 11i v3 . . . 20 Special Files for Tape Devices . . . . . . 11. . . . . . . 30. . . . . . . . . . . . 27. . . . Tracing Facility . . . . . . .Equipment Listing Example 1 . 33 Special Files for Medium Changer Devices 33 Error Description . . . . Reasons. . . . . . . . 32. 6 Supported Hardware by Operating System 9 Supported Devices and Feature Codes . . . . . . . . . . . . . . . . . 5. . . . . . 20. . . . . . . . . . 129 . . . . . . 12. . . . .IBMtape . 50 Device-Specific Parameter Definitions . . . . 14.Equipment Listing Example 4 . 110 123 124 126 . 25. . 15. . 74 Driver-Specific Parameters (Global) . IBMtape and lin_tape Comparison . . Solaris Device Driver . . Solaris Device Driver . . 144 154 274 302 321 © Copyright IBM Corp. . . 15 Interoperability between IPv4 and IPv6 Clients and Servers . SCSI Supported Devices . . . . . . 10. . . 130 . . . . 28.Equipment Listing Example 3 . viii IBM Tape Device Drivers Installation and User’s Guide . 2007. medium changer.Preface These publications and URLs provide user information and installation assistance for IBM® tape drive. GA32-0558 v IBM System Storage 3953 Tape System Introduction and Planning Guide. GA32-0556 v IBM System Storage TS3500 Tape Library Operator Guide. GA32-0557 IBM Ultrium Tape Drive Models T800 and T800F The following publications relate to the IBM Ultrium Tape Drive Models T800 and T800F: v IBM Ultrium Tape Drive Models T800 and T800F Setup.software. and Service Guide. including the Adobe® PDF version of this publication. GA32-0555 v IBM System Storage TS1120 Tape Drive and Controller Operator Guide. and User’s Guide. is available at the following ftp site: ftp://ftp. Operator. 2009 ix . and library device drivers.ibm. GA32-0566 Current® Products IBM TotalStorage Enterprise Tape System 3592 Publications The following publications relate to the IBM TotalStorage® Enterprise Tape System 3592: v IBM TotalStorage Enterprise Tape System 3592 Operator Guide. GA32-0463 v IBM TotalStorage Enterprise Tape System 3592 Hardware Reference. Related Information Reference material. GA32-0465 v IBM TotalStorage Enterprise Tape System 3592 Introduction and Planning Guide. SC23-5231 IBM System Storage TS2230 Tape Drive The following publications relate to the IBM System Storage TS2230 Tape Drive: © Copyright IBM Corp. GA32-0464 v IBM TotalStorage Silo Compatible Tape Frame 3592 Introduction. GA32-0560 v IBM System Storage TS3500 Tape Library Introduction and Planning Guide. GC26-7697 IBM LTO Ultrium 3-H Tape Drive The following publications relate to the IBM LTO Ultrium 3-H Tape Drive: v IBM LTO Ultrium 3-H Tape Drive Setup. and Service Guide. GA32-0466 IBM System Storage TS1120 Tape Drive The following publications relate to the IBM System Storage™ TS1120 Tape Drive: v IBM System Storage TS1120 Tape Drive and Controller Introduction and Planning Guide.com/storage/devdrvr/Doc A companion publication covering programming aspects for the device drivers is: IBM Tape Device Drivers: Programming Reference. Operator. GA32-0559 v IBM System Storage 3953 Library Manager Model L05 Operator Guide. Planning. 19P2440 IBM Virtualization Engine TS7520 The following publications relate to the IBM Virtualization Engine™ TS7520: v IBM Virtualization Engine TS7520 Hardware.v IBM System Storage TS2230 Tape Drive Setup. GA32-0454 v IBM System Storage TS3100 Tape Library and TS3200 Tape Library Installation Quick Reference. Operator. GA32-0572 IBM System Storage TS3310 Tape Library The following publications relate to the IBM System Storage TS3310 Tape Library: v IBM System Storage TS3310 Tape Library Setup and Operator Guide. Operator. and Service Guide. and Service Guide. GA32-047 x IBM Tape Device Drivers Installation and User’s Guide . GA32-0477 v IBM System Storage TS3310 Tape Library Maintenance Information. GA32-0476 IBM System Storage TS3100 Tape Library The following publications relate to the IBM System Storage TS3100 Tape Library: v IBM System Storage TS3100 Tape Library and TS3200 Tape Library Setup. GA32-0478 v IBM System Storage TS3310 Tape Library SCSI Reference. GC26-7708 v IBM TotalStorage 3580 Tape Drive Models L33/L3H Quick Reference. GC26-7766-01 v IBM Virtualization Engine TS7520 Introduction and Planning Guide. GC27-2107 Storage TS3400 Tape Library Maintenance Information. and Service Guide. GC27-2100 IBM TotalStorage 3580 Tape Drive Models L33/L3H The following publications relate to the IBM TotalStorage 3580 Tape Drive Models L33/L3H: v IBM TotalStorage 3580 Tape Drive Models L33/L3H Setup. GC27-2104 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: v IBM System Storage TS3500 Tape Library Planning and Operator Guide. GC27-2103 v IBM System Storage TS2340 Tape Drive Models L43/S43 Quick Reference Card. GC27-2099 v IBM System Storage TS2230 Tape Drive Installation Quick Reference. GA32-0573 Storage TS3400 Tape Library Planning and Operator Guide. GC27-2068-00 IBM System Storage TS3400 Tape Library The following v IBM System v IBM System v IBM System publications relate to the IBM System Storage TS3400 Tape Library: Storage TS3400 Tape Library Installation Quick Reference. and Service Guide. Operator. Setup. GA32-0408 v IBM System Storage TS3500 Tape Library Maintenance Information. GA32-0456 v IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference. and Problem Determination Guide. GC27-2067-00 v IBM Virtualization Engine TS7500 User Guide. Operator. GC26-7709 IBM System Storage TS2340 Tape Drive The following publications relate to the IBM System Storage TS2340 Tape Drive [also known as IBM LTO4 (TS2340)]: v IBM System Storage TS2340 Tape Drive Models L43/S43 Setup. Installation. and Service Guide.com Microsoft Windows The following URL relates to Microsoft® Windows® systems: http://www.redhat.com Solaris The following URL relates to Sun Solaris systems: http://www. GA32-0415 IBM TotalStorage Ultrium Tape Autoloader 3581 The following publication relates to the IBM TotalStorage Ultrium Tape Autoloader 3581: v IBM 3581 Ultrium Tape Autoloader Setup. Operator.sun.com Legacy Products IBM TotalStorage Ultrium External Tape Drive 3580 The following publications relate to the IBM TotalStorage Ultrium External Tape Drive 3580: v IBM 3580 Ultrium Tape Drive Setup.IBM System Storage TS3200 Tape Library The following publications relate to the IBM System Storage TS3200 Tape Library: v IBM System Storage TS3100 Tape Library and TS3200 Tape Library Setup. GA32-047 AIX The following URL points to information about IBM System p® (also known asERserver pSeries®) servers: http://www-1. GA32-0412 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: v IBM 3581 Tape Autoloader Models L28/L38/L3H and F28/F38/F3H Setup. and Service Guide.com Linux The following URLs relate to Linux® distributions: http://www. and Service Guide.suse.ibm. Operator.com http://www. Operator. GA32-0454 v IBM System Storage TS3100 Tape Library and TS3200 Tape Library Installation Quick Reference.hp. GA32-0456 v IBM System Storage TS3100 Tape Library and TS3200 Tape Library SCSI Reference. GA32-0470 Preface xi .com/servers/eserver/pseries HP-UX The following URL relates to HP HP-UX systems: http://www. Operator.microsoft. and Service Guide. Models F01. and C2A Maintenance Information. GA32-0458 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: v IBM 3583 Tape Library Setup and Operator Guide. and C2A Hardware Reference. C1A. GA32-0345 Introduction and Planning Guide. Operator. and Service Guide. and FC0. GA32-0365 Hardware Reference C-Series Models. and Operator’s Guide. GC26-7769 IBM TotalStorage Enterprise Automated Tape Library 3494 The following publications relate to the IBM TotalStorage Enterprise Automated Tape Library (3494): v IBM TotalStorage Enterprise Automated Tape Library (3494) Introduction and Planning Guide. F11. GA32-0425 v IBM Storage Area Network Data Gateway Module Setup. Installation. Setup. and Service Guide. GA32-0448 v IBM TotalStorage Enterprise Automated Tape Library (3494) Operator Guide. GA32-0411 v IBM 3583 Tape Library Service Guide. GA32-0219 v IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models E01 and E11 User’s Guide. Installation.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: v IBM TotalStorage 3582 Tape Library Setup. C22. C1A. C11. SA37-0407 IBM 3490E Tape Subsystem The following publications relate to the IBM 3490E Tape Subsystem: v IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models C10. GA32-0436 IBM Virtualization Engine TS7510 The following publications relate to the IBM Virtualization Engine TS7510: v IBM Virtualization Engine TS7510 Hardware. Operator. and Problem Determination Guide. Planning. F1. C22. GA32-0449 v IBM TotalStorage 3494 Tape Library Maintenance Information. GC26-7766 v IBM Virtualization Engine TS7510 Introduction and Planning Guide. GA32-0378 IBM Magstar MP 3570 Tape Subsystem The following publications relate to the IBM Magstar® MP 3570 Tape Subsystem: v v v v IBM Magstar IBM Magstar IBM Magstar IBM Magstar GA32-0394 MP MP MP MP 3570 3570 3570 3570 Tape Tape Tape Tape Subsystem Subsystem Subsystem Subsystem Operator’s Guide. IBM Magstar MP 3575 Tape Subsystem The following publications relate to the IBM Magstar MP 3575 Tape Subsystem: xii IBM Tape Device Drivers Installation and User’s Guide . GA32-0298 v IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models C10. SA37-0299 v IBM 3490E Tape Subsystem. C11. GC26-7767 v IBM Virtualization Engine TS7510 User Guide. GA32-0348 Hardware Reference. SA26-2009 v 7334 Model 410 8mm Tape Library Service Guide. SY32-0408 IBM 7334 8mm Tape Library The following publications relate to the IBM 7334 8mm Tape Library: v 7334 Model 410 8mm Tape Library Setup and Operator Guide. GA32-0354 IBM 7331 8mm Tape Library The following publications relate to the IBM 7331 8mm Tape Library: v IBM 7331 8mm Tape Library Installation Guide. GA32-0399 v 3447 and 7337 Digital Linear Tape Library Service Guide. GA32-0331 v IBM TotalStorage Enterprise Tape System 3590 Operator’s Quick Guide. SA26-7111 IBM 7332 4mm DDS-2 Tape Cartridge Autoloader The following publications relate to the IBM 7332 4mm DDS-2 Tape Cartridge Autoloader: v IBM 7332 4mm DDS-2 Tape Cartridge Autoloader Model 005 Installation Guide. SA26-7138 v IBM 7332 4mm DDS-2 Tape Cartridge Autoloader Model 005 Operator Guide. GA32-0330 v IBM TotalStorage Enterprise Tape System 3590 Hardware Reference. SA26-7140 IBM 7332 Model 220 External 4mm Tape Autoloader The following publications relate to the IBM 7332 Model 220 External 4mm Tape Autoloader: v 7332 Model 220 4mm Tape Autoloader. SA41-0051 Preface xiii . SA26-2005 v 7332 Model 220 4mm Tape Autoloader Service Guide. SA26-7110 v IBM 7331 8mm Tape Library Operator Guide. Setup and Operator Guide. GA32-0380 v IBM Magstar MP 3575 Tape Library Dataserver Operator Guide. SY32-0412 IBM 7336 4mm Tape Library The following publication relates to the IBM 7336 4mm Tape Library: v IBM 7336 4mm Tape Library Model 205 Operator and Setup Guide. SA37-0309 IBM 3447 and 7337 Digital Linear Tape Library The following publications relate to the IBM 3490E Tape Subsystem: v 3447 and 7337 Digital Linear Tape Library Setup and Operator Guide. GA32-0382 IBM TotalStorage Enterprise Tape System 3590 The following publications relate to the IBM TotalStorage Enterprise Tape System 3590: v IBM TotalStorage Enterprise Tape System 3590 Introduction and Planning Guide. GA32-0400 v 7337 Model 360 Digital Linear Tape Library Setup and Operator Guide. GA32-0329 v IBM TotalStorage Enterprise Tape System 3590 Operator Guide.v IBM Magstar MP 3575 Tape Library Dataserver Introduction and Planning Guide. SA26-7139 v IBM 7332 4mm DDS-2 Tape Cartridge Autoloader Model 005 Service Guide. GA32-0381 v IBM Magstar MP 3575 Tape Library Dataserver Hardware Reference. com SGI The following URL relates to SGI systems: http://www.S.S.A.131-199X Revision 10H. and other countries: 520-799-2906 xiv IBM Tape Device Drivers Installation and User’s Guide .sgi.com Other Publications IBM Storage Area Network Data Gateway Installation and User’s Guide. you can send us comments electronically by using these addresses: v Internet:
[email protected] The following URL points to information about Tru64 systems: http://www. SC26-7304 Additional Information The following publication contains additional information related to the IBM tape drive.com v IBMLink™ from U. X3. If you have comments or suggestions for improving this publication. Canada.: STARPUBS at SJEVM5 v IBMLink from Canada: STARPUBS at TORIBM v IBM Mail Exchange: USIB3VVD at IBMMAIL v Fax from U. X3B5/91-305.A.180.9/91-11 Revision 1 How to Send Your Comments Your feedback is important in helping us provide the most accurate and best quality information. X3B5/91-173C.. medium changer.2/86-109 X3. and library device drivers: v American National Standards Institute Small Computer System Interface X3T9. and X3T9.ibm. and a separate section on these operating systems for the 3494 Enterprise Tape Library. you must repeat the process above. Navigate to the last page in the section and note that page number. Preface xv . Sun Solaris. Important printer note This area indicates the pages that will actually print in your specified range of pages. respectively. follow these steps: 1. HP-UX. then choose ″Pages″ and enter the page range for the section. Windows. 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 one or more separate sections of the manual. Only the page range entered prints. 4. 3. entering the page range for the Table of Contents and the Index page range. Navigate to the beginning of the section and note the page number. Select File —> Print. Note: When selecting the page range for the section you wish to print. 2. Ignore the page number appearing on the page itself when entering page ranges for your printer. for example. Linux. Tru64.Special Printing Instructions This Tape Device Drivers Installation and User’s Guide contains different sections for each type of operating system/platform. not the page printed on the actual document. note that the print page range is based on the page controls for Adobe Acrobat. Enter the Adobe page numbers to print. AIX®. If you wish to print those items. xvi IBM Tape Device Drivers Installation and User’s Guide . Purpose The IBM tape and medium changer device drivers are designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. IBM Tape Products The IBM Tape product family provides an excellent solution for customers with small to large storage and performance requirements. Current Products Figure 1 on page 2 illustrates the attachment of various current products to an open systems server. Whenever possible. Solaris. Windows and Tru64 operating systems. the driver is designed to take advantage of the device features transparent to the application. The goal is to give 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).Chapter 1. Please note that some independent software vendor (ISV) applications have certain device driver requirements. Refer to the specific operating system chapters for details on device support. 2009 1 . as well as to the advanced functions needed by full tape management systems. 2007. Not all devices are supported on all operating systems. Introduction This publication describes the IBM Tape and Medium Changer Device Drivers for AIX. HP-UX. Before you install the device drivers. please refer to the ISV web site or their support to find out what device drivers should be used for the ISV. © Copyright IBM Corp. Linux. Introduction 2 3 4 11 System Storage 5 1 10 8 9 7 6 SystemSto rage Figure 1. Current Attachment Array 1 Open Systems Server 2 IBM Virtualization Engine TS7520/TS7530 3 IBM Virtualization Engine TS7650 4 IBM TS2230/TS2240 Ultrium 3/4 Half-High Tape Drive 5 IBM TS2340 (or 3580) Ultrium 3/4 Full-High Tape Drive 6 IBM TS1120/TS1130 Tape Drive [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 environment that could include an IBM 3583 Tape Library and an IBM TS3500 Tape Library. 2 IBM Tape Device Drivers Installation and User’s Guide dd000004 . The drive has a native storage capacity of 400 GB per cartridge (800 GB at 2:1 compression) on the Ultrium 3 data cartridge. featuring HyperFactor technology. IBM System Storage TS2230/TS2240 Tape Drive The IBM System Storage TS2230 Tape Drive Model H3L (Machine Type 3580. This model incorporates the Linear Tape Open (LTO) IBM Ultrium 3 Half-High Tape Drive. high-capacity data-storage device that is designed to backup and restore open systems applications. able to process up to 900 megabytes per second in a clustered configuration. tiered storage hierarchy of disk and tape. ProtecTIER. The result is superior inline performance.6 TB (with 2:1 compression) in conjunction with the IBM System Storage LTO Ultrium 800 GB data cartridge. and simply increasing disk capacity year after year is a no-win strategy. SAP part number 3580L3E) is a high-performance. 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. IBM Virtualization Engine TS7650 Disk storage can be expensive. Model H3L. It is available with a Small Computer Systems Interface (SCSI) or with a Serial Attached SCSI (SAS) interface. The IBM System Storage TS2240 Tape Drive is an excellent tape storage solution for businesses requiring backup or low-cost. de-duplicating data in real time as it is written to your back-up device. The TS2240. offers the same high capacity of full-high LTO 4 tape drives. with a half-high form factor. The native data transfer performance of the TS2240 Tape Drive has increased over the previous LTO half-high generation to up to 120 MB/sec. unmatched scalability and enterprise data integrity. the benefits of both technologies can be leveraged to help enhance performance and provide the capacity needed for today’s tape processing requirements. which provides up to double the capacity of Ultrium 3 cartridges. uses powerful algorithms to filter out duplicate data so that only new data items are stored. The TS2240 Tape Drive continues to provide an excellent alternative to Chapter 1. Example of an IBM Tape Environment IBM Virtualization Engine TS7520 The IBM Virtualization Engine TS7520 product is a virtual-tape solution designed to help optimize tape processing. Deploying this innovative offering can help reduce batch processing time and management overhead. and it’s done in-line. ProtecTIER employs blazing fast performance. real-time archival storage of their data. Introduction 3 . The TS2240 has a physical storage capacity of up to 1.Introduction Open Systems Server IBM Tape Drive Medium Changer Robot Tape Cartridges a250116 IBM Tape Drive IBM Tape Device Driver IBM Tape Library Figure 2. Through the implementation of an integrated. This model incorporates the Linear Tape Open (LTO) IBM TotalStorage Ultrium Tape Drive (Generation 3). The IBM LTO Ultrium 4 Half-High Tape Drive has a native storage capacity of 800 GB per cartridge (1600 GB at 2:1 compression). The TS3200 Tape Library is an external 4U standalone or rack-mountable unit that incorporates up to two IBM TotalStorage Ultrium 3 Tape Drives. such as a desktop unit. and has a native data rate of up to 80 Mbps per drive. the Ultrium 4 Tape Drive doubles the tape cartridge capacity up to 800 GB native physical capacity (1600 GB with 2:1 compression). high-capacity data-storage device for the midrange open systems environment. which more than doubles maximum tape drive performance over the Generation 2 LTO Ultrium Tape Drive (Ultrium 2). The Ultrium 4 SAS Tape Drive is encryption-capable and designed to support Application Managed Encryption. long-term retention and data governance and regulatory compliance. Fibre Channel attachment. and cartridge capacity than the IBM TotalStorage Tape System 3590 and the 3592 tape drive. The TS2240 provides added security features by supporting encryption of data with 3 Gbps SAS connectivity. high-capacity data-storage devices in a half-height form factor that are designed to backup and restore open systems applications. The IBM LTO Ultrium 3-H Tape Drive and IBM LTO Ultrium 4 Half-High Tape Drive are high-performance. with the use of the new IBM LTO Ultrium 800 GB Data Cartridge. The TS1130 tape drive offers high-performance flexible data storage with support for data encryption. It is designed to increase maximum tape drive throughput native data rate performance up to 120 MB/sec compared to the IBM LTO generation 3 Tape Drive (Ultrium 3) at 80 MB/sec native data transfer rate.Introduction slower and smaller capacity 1/4-inch. 4 mm and 8 mm DLT/SDLT tape drives. IBM System Storage TS1120/TS1130 Tape Drive (Enterprise) The IBM System Storage TS1120 Tape Drive is the second generation of the 3592 tape drive. 4 IBM Tape Device Drivers Installation and User’s Guide . In addition. It is available with Small Computer System Interface (SCSI) or Serial Attached SCSI (SAS) interface. better security. and a new high-technology design that increases the native data rate to 100 MB/sec. IBM TotalStorage 3580 (Ultrium) Tape Drive (Models L33 and L3H) The IBM TotalStorage 3580 Tape Drive Model L33/L3H offers high-capacity. The IBM LTO Ultrium 3-H Tape Drive has a native storage capacity of 400 GB per cartridge (800 GB at 2:1 compression). The TS1120 tape drive has a dual-ported 4-Gbps Fibre Channel interface. for connection to a wide spectrum of open system servers. This tape drive comes with a SCSI Ultra160 LVD attachment. reliability. performance. tape autoloader. The IBM System Storage TS1130 Tape Drive features storage capability to help you establish easy access to data. It provides higher levels of performance. and technology designed for the midrange open systems environment. They are available with a Small Computer Systems Interface (SCSI) or with a Serial Attached SCSI (SAS) interface. or tape library. 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 environments. Both drives can be integrated into an enclosure. IBM System Storage TS2340 Tape Drive The IBM System Storage TS2340 Tape Drive [also known as IBM LTO4] is a high-performance. the E9U has space for up to two (one redundant) power supply modules (At least one power supply module must be installed if a drive is present in the E9U). This unique design houses up to 22 tape cartridges in a compact 2U form factor with easy access to tape cartridges via two removable magazines and an Input/Output (I/O) Station. and redundant power supplies. automated tape library combining IBM automation technology for midrange to enterprise open systems environments. The base library module. the TS3500 tape library can have an expanded available storage capacity of over 5000 TB (with 3:1 compression) using TotalStorage Enterprise 3592 Tape Drives. low-cost solution for simple. Model E05). which houses up to 36 cartridges (30 storage slots and 6 Input/Output slots) and two LTO generation 3 tape drives. It comes with 4 Gbps dual-ported switched fabric Fibre Channel attachment. With scalability of one to sixteen frames and up to 192 tape drives.Introduction 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. which are ordered separately. per drive. IBM System Storage TS3310 Tape Library The IBM System Storage TS3310 Tape Library is a modular. The TS3400 Tape Library is an external 5U stand-alone or rack-mountable unit that incorporates up to two IBM System Storage TS1120 Tape Drives Model 3592-E05 (Machine Type 3592. Additionally. The IBM TotalStorage Ultrium Scalable Tape Library 3583 can be used for save. The TS3310 model L5B can be expanded with the addition of expansion units. The TS1120 Tape Drive has a native data transfer rate of up to 100 MB/ sec. Introduction 5 . drives. IBM System Storage TS3400 Tape Library The IBM System Storage TS3400 TAPE LIBRARY is designed to offer high performance drive technology and automation for the open systems environment. The TS3500 Tape Library supports logical partitioning and can house both IBM LTO Ultrium and IBM TotalStorage Enterprise 3592 Tape Drives (in separate frames). model L5B. scalable tape library designed to scale vertically with expansion for Linear Tape Open (LTO) tape cartridges. high-capacity. The TS3400 Tape Library is an addition to the family of IBM System Storage tape library offerings. 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 Chapter 1. restore and mass storage archives where multi-terabyte capacities are required. IBM System Storage TS3100 Tape Library The IBM System Storage TS3100 (Machine Type 3573) Tape Library provides a compact. Each model E9U contains 92 physical LTO cartridge storage cells and space for up to four LTO generation 3 tape drives. is the entry point for the product family. Three different library models are available with storage capacities of 18 through 72 slots and one to six Ultrium tape drives. 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 drives in either a stand alone or optional rack mount configuration. It contains all of the necessary robotics and intelligence to manage the 5U high library system. the model E9U. unattended data backup. Table 1. the documentation pertaining to the IBM branded family of products should be used.400 GB of uncompressed data storage. IBM TotalStorage Ultrium External Tape Drive 3580 The IBM TotalStorage Ultrium External Tape Drive 3580 is a stand alone. IBM TotalStorage Ultrium Tape Autoloader 3581 The IBM TotalStorage Ultrium Tape Autoloader 3581 is an external. Ultrium Product Comparison StorageSmart by IBM Ultrium StorageSmart by IBM Ultrium External Tape Drive TX200 StorageSmart by Ultrium Tape Autoloader SL7 StorageSmart by Ultrium Scalable Tape Library SL72 No equivalent in the IBM Ultrium product set IBM Version of Ultrium IBM TotalStorage Ultrium External Tape Drive 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. StorageSmart by IBM Ultrium Products The StorageSmart™ by IBM Ultrium family of products is compatible with the IBM branded versions of the Ultrium family products. The autoloader can be used with compatible software applications to automate backup/recovery or other data storage activities. With both Low Voltage Differential (LVD) Ultra-2 SCSI and High Voltage Differential (HVD) Ultra SCSI attachments.8 TB uncompressed native storage. restore. Table 1 cross references the StorageSmart by IBM Ultrium product set to the IBM Ultrium product set. The Model L28 comes with a LVD Ultra160 SCSI attachment. The autoloader has seven storage slots giving the autoloader up to 1. and archiving requirements for PC and Open Systems operating systems. providing an automated tape solution to a variety of system 6 IBM Tape Device Drivers Installation and User’s Guide . or rack-mounted tape autoloader that incorporates one IBM Ultrium Tape Drive. It can accommodate one or two Ultrium generation 2 Tape Drives and comes standard with a one-cartridge I/O station and 23 data cartridge slots giving a native library capacity of 4. In this manual. 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 drive.Introduction Drives for the midrange open systems environment. large capacity. while the Model F28 comes with a Native Switched Fabric Fibre Channel attachment. stand-alone. high performance tape drive that adheres to the Linear Tape Open (LTO) specifications and supports the IBM Ultrium format tape. this device is suitable for a variety of save. The Ultrium Tape 2U Autoloader 3581 capacity is eight tape cartridges. for connection to a wide spectrum of open systems servers. The drive supports native tape capacities of up to 200 GB with uncompressed data transfer rates of up to 35 MB per second. providing a media capacity of up to 1. where there is no specific mention of the StorageSmart by IBM Ultrium branded set of products.2 TB with 2:1 compression) data storage per unit.6 TB (3. The ACL or CSL can load the next tape from the cartridge stack into the tape drive either automatically when a tape is unloaded. you must use the hard addressing mode. IBM TotalStorage Enterprise Tape System 3590 The IBM TotalStorage Enterprise Tape System 3590 consists of a tape drive combined with an automatic cartridge facility (ACF). Note: The 3590 drive has two Fibre Channel addressing modes. To the host software. IBM Virtualization Engine TS7510 The IBM Virtualization Engine TS7510 product delivers and increased level of storage capability to the traditional storage product hierarchy. IBM Magstar MP 3570 Tape Subsystem The IBM Magstar MP 3570 Tape Subsystem consists of one or two tape drives (depending on the model) integrated with a full capability medium changer robotic facility. IBM 3490E Magnetic Tape Subsystem The IBM 3490E Magnetic Tape Subsystem consists of one or two tape drives (depending on the model) combined with an automatic cartridge loader (ACL) or cartridge stack loader (CSL).Introduction environments. migration of data between direct access storage devices (DASD) and tape. The IBM device drivers control both the Magstar MP tape drives and the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. which provides random access of cartridges in the storage cells under program control. IBM TotalStorage Virtual Tape Server (Models B10. the IBM Virtualization Engine TS7510 looks like a 3584 library with associated tape drives. IBM 7332 4mm Tape Cartridge Autoloader The IBM Magstar MP 3575 Tape Library Dataserver is a scalable family of high-performance tape libraries that use the IBM Magstar MP tape drives. the ACF on the Enterprise Tape System 3590 can operate as an integrated medium changer device to provide random access of cartridges in the magazine cells under program control. Chapter 1. use lower addresses for hosts and higher addresses for drives. It provides a solution for automating tape operations such as save/restore. and other mass data applications. B18. or when the tape drive is under program control. When attaching a 3590 drive directly to a host (without a switch). and B20) The IBM TotalStorage Virtual Tape Server (VTS) product delivers an increased level of storage capability to the traditional storage product hierarchy. a VTS subsystem looks like a 3490E Enhanced Capability Tape Subsystem with associated Cartridge System Tape or Enhanced Capacity Cartridge System Tape. The IBM device drivers control both the Magstar MP tape drives and the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. To the host software. IBM Magstar MP 3575 Tape Library Dataserver The IBM Magstar MP 3575 Tape Library Dataserver is a scalable family of high-performance tape libraries that use the IBM Magstar MP tape drives. In addition to the functions that the ACL or CSL provide for the IBM 3490E Magnetic Tape Subsystem. Introduction 7 . When attaching an open systems server to a 3590 Fibre Channel drive. The IBM 7336 product is a 4mm Tape Medium Changer Library device. Access to the tape drives within these libraries is through the native operating system AIX Tape Device Driver.Introduction IBM 7331. 8 IBM Tape Device Drivers Installation and User’s Guide . The AIX Enhanced Device Driver controls the robotic cartridge handling mechanism in these tape libraries that instructs the robot to mount and demount the cartridges. 7334. or 7337 Tape Medium Changer The IBM 7331 and 7334 products are 8mm Tape Medium Changer Library devices. 7336. The IBM 7337 product is a DLT Tape Medium Changer Library device. . . 2009 9 . . . Supported Hardware Table 2 lists the IBM device drivers that are supported. . 20 Purpose This chapter provides general information about the IBM Device Drivers. . Path Failover and Load Balancing . 15 Tape and Library Requirements. 2007. To obtain the most current service and documentation for this software. . . .Chapter 2. . . . . . .” on page 301. For detailed requirements for each operating system. . . Supported Hardware by Operating System Linux DEVICE AIX HP-UX Intel and AMD System Opteron p Processors Models X X ® Windows System z® Models X Solaris Tru64 2000 X X (not LTO4) X (only LTO1) Server 2003 X NT X (LTO1 and LTO2 only) X Server 2008 IBM LTO Ultrium Tape Drive X X (not LTO4 on HP-UX 11. . . . “Accessing Documentation and Software Online. . . . . . . . . . . . refer to the appropriate chapter. . 9 . . . . . . 14 . . . . Supported Devices and Feature Codes Data Encryption . . . . . . . . 13 . . . . . 16 Planning for System-Managed Tape Encryption 17 Planning for Library-Managed Tape Encryption 19 Feature Codes (Encryption) . Automatic Failover . . . . . . 13 . . . 15 Planning for Application-Managed Tape Encryption . Table 2. 9 . . . . . . . Common Extended Features Purpose . . Dynamic Load Balancing . . Supported Hardware . . 14 . . . . . . refer to Appendix A. . . . . . . . Refer to the specific operating system chapters for details on device support. . . .0) X IBM System Storage TS1120/ TS1130 Tape Drive Model E05/E06 IBM System Storage TS2230 Tape Drive IBM System Storage TS2240 Tape Drive X X X X X X X X X (only SCSI LVD) X X X X X X X X X X X © Copyright IBM Corp. . . Supported Hardware by Operating System (continued) Linux DEVICE AIX HP-UX Intel and AMD System Opteron p Processors Models X X ® Windows System z® Models Solaris Tru64 2000 X Server 2003 X NT Server 2008 X IBM System Storage TS2340 Tape Drive IBM System Storage TS3100 Tape Library IBM System Storage TS3200 Tape Library IBM System Storage TS3310 Tape Library IBM System Storage TS3400 Tape Library IBM System Storage TS3500 Tape Library IBM System Storage Virtualization Engine TS7520 IBM System Storage Virtualization Engine TS7650 IBM System Storage TS2240 Tape Drive IBM System Storage TS2340 Tape Drive IBM System Storage TS3100 Tape Library X X (not HP-UX 11.0) X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X (not HP-UX 11.0.Device Driver Features Table 2. 11i v3) X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 10 IBM Tape Device Drivers Installation and User’s Guide . Models B11. B1A IBM TotalStorage Enterprise Tape System 3590. Model J1A IBM Virtualization Engine TS7510 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Chapter 2. Common Extended Features 11 .Device Driver Features Table 2. E1A.0) X IBM System Storage TS3310 Tape Library IBM System Storage TS3400 Tape Library IBM System Storage TS3500 Tape Library IBM System Storage Virtualization Engine TS7520 IBM TotalStorage UltraScalable Tape Library 3584 IBM TotalStorage Enterprise Tape System 3590. H11. Models E11. Supported Hardware by Operating System (continued) Linux DEVICE AIX HP-UX Intel and AMD System Opteron p Processors Models X X ® Windows System z® Models Solaris Tru64 2000 X X (only LTO1) X (not LTO4) Server 2003 X NT X (LTO1 and LTO2 only) X Server 2008 X IBM System Storage TS3200 Tape Library X X (not LTO4 on HP-UX 11. H1A IBM TotalStorage Enterprise Tape System 3592. Supported Hardware by Operating System (continued) Linux DEVICE AIX HP-UX Intel and AMD System Opteron p Processors Models ® Windows System z® Models Solaris Tru64 2000 X X Server 2003 X NT X Server 2008 IBM TotalStorage Virtual Tape Server. 220 IBM 7334 8mm Tape Library Model 410 IBM 7336 4mm Tape Library Model 205 or 305 (support for autochanger only) X X X X X X X X X X X X X X X X X X X X X X 12 IBM Tape Device Drivers Installation and User’s Guide . C01. L24. L12. B12. C02.Device Driver Features Table 2. L32 IBM 7331 8mm Tape Library Model 205 or 305 (support for autochanger only) IBM 7332 4mm Tape Cartridge Autoloader Model 005. C11. L18. B20 IBM Magstar MP 3570 Tape Subsystem Model B00. B11. C12. Models B10. B18. 110. B1A IBM Magstar MP 3570 Tape Subsystem Model C00. C1A IBM Magstar MP 3570 Tape Subsystem Model L06. B01. B02. the system detects two logical devices of the tape drive. Refer to “Supported Devices and Feature Codes” on page 14 for a list of supported devices and what path failover feature code may be required for your machine type. This is transparent to the running application. 2. Sometimes manual failover may require operator intervention to reset the drive because a SCSI Reservation could still exist on the failing HBA path. For example.Device Driver Features Table 2.com/storage/devdrvr Some devices require a path failover feature code to be installed prior to enabling the path failover support in the device driver. Supported Hardware by Operating System (continued) Linux DEVICE AIX HP-UX Intel and AMD System Opteron p Processors Models ® Windows System z® Models Solaris Tru64 2000 Server 2003 NT Server 2008 IBM 7337 DLT Tape Library (support for autochanger only) X Path Failover and Load Balancing Device driver path failover support configures multiple physical paths to the same device within the device driver and provides two basic functions: 1. if a permanent path error occurs (because of an HBA or cable failure. Common Extended Features 13 . This connection provides two physical paths to same tape drive for redundancy if one path from an HBA to the drive fails. Without path failover support. Automatic Failover The automatic failover support provides error recovery on an alternate path when a permanent error occurs on one path. It is possible to initiate manual failover by restarting the application on the alternate logical device. but the application has to be restarted from the beginning. Path Failover is supported on certain tape products with the latest IBM device drivers available on the following ftp download site: ftp://ftp. The first HBA is connected to port 0 of the drive. Chapter 2. A backup and restore application can open and use only one logical device at a time because they represent the same physical device. Automatic failover to an alternate physical path when a permanent error occurs on one path.ibm. the application fails. At startup or configuration. Dynamic load balancing for tape devices using multiple Host Bus Adapters (HBA). for example).software. Each logical device is a physical path to the same tape drive. A long backup or restore operation may have been in progress when the path error occurred. and the second HBA is connected to port 1 of the drive. consider a simple multipath connection that consists of two Host Bus Adapters (HBA) connected through a switch to the tape drive. consider a machine with two Host Bus Adapters. the device driver assigns the application to use HBA1. The dynamic load balancing support is independent from the automatic failover support. HBA1 and HBA2. When the next application opens a tape drive. The device driver updates the usage on the HBA assigned to the application when the device is closed. it would be assigned to HBA1. the device driver determines which path has the HBA with the lowest usage. the automatic failover support attempts recovery on the next available path. and assigns that path to the application. For example. some devices require feature codes as listed in Table 3 on page 15. Regardless of the path assigned initially for load balancing. if that path fails. When the first application opens a tape drive for use. the current operation continues on the alternate path without interrupting the application. The failover error recovery first restores the previous device state. Dynamic load balancing uses all Host Bus Adapters whenever possible and balance the load between them to optimize the resources in the machine. HBA2 would have one application using it and the next application that opens a tape drive would be assigned to HBA2. with multiple tape drives attached. If the first application finishes and closes the device. When another application opens a different device with multiple HBA paths. 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 successful. the device driver configures them internally as a single device with multiple paths. Path failover includes Control Path Failover (CPF) for tape libraries and Data Path Failover (DPF) for tape drives. Likewise. Each tape drive is connected to both HBA1 and HBA2. Supported Devices and Feature Codes Path failover is supported only for the devices listed in Table 3 on page 15. and tape position. The application can still open and use only one logical device at a time. so again there would be two applications using HBA1 and two applications using HBA2. When a second application opens a tape drive for use. there would now be one application using HBA1 and two applications using HBA2. Initially. the device driver assigns the second application to use HBA2. if the second application finishes and closes the device. When an application opens a device that has multiple HBA paths configured. 14 IBM Tape Device Drivers Installation and User’s Guide . In order to use path failover support. then retries the failing operation. the device driver again determines the path with the lowest HBA usage and assigns that path to the second application. SCSI Reservation.Path Failover When the path failover support is enabled on both logical devices. the device driver initiates failover error recovery automatically on the alternate path. If an application opens the primary device and a permanent path error occurs. there are no tape drives currently in use. Dynamic Load Balancing The dynamic load balancing support optimizes resources for tape devices that have physical connections to multiple Host Bus Adapters (HBA) in the same machine. and is transparent to the system and library layers. there are three methods of encryption management to choose from. Path Failover is only supported on SAS devices attached to Windows and Linux for Intel/AMD processor based servers. Supported Devices and Feature Codes Supported Tape Library TS1120 TS1130 3592 TS3500 TS3400 TS3310 TS3200 TS7520 TS7650 3583 3582 Feature Code (FC). no FC required (DPF only) FC 1682 (CPF and DPF) Standard. In the open system environment. If system-managed or library-managed encryption is used. and library layer. Application-managed encryption does not require this feature code for any of encryption-capable tape drives. Path failover is not supported on parallel SCSI (except for some parallel SCSI drives on AIX operating systems). no FC required (DPF only) Standard. system layer. the Transparent LTO Encryption feature code is required for the library with Ultrium LTO4 tape drives. 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 drive. Application-Managed Tape Encryption This method is best where operating environments run an application already capable of generating and managing encryption policies and keys. Common Extended Features 15 . no FC required (CPF and DPF) FC 1682 (CPF and DPF) FC 1682 (CPF and DPF) FC 1682 (CPF and DPF) Standard. no FC required (DPF only) FC 1680 (CPF). with the result that key management and the encryption policy engine may be located in any one of the three environmental layers: application layer. Refer to “Feature Codes (Encryption)” on page 20 for the feature code numbers. no FC required (DPF only) Standard. such as Tivoli® Storage Manager (TSM). This feature code is not required for TS1120 tape drives. Your operating environment determines which is the best for you. FC 1681 (DPF) Notes: 1. 2. Chapter 2. if required Standard. Path failover is not supported on Virtual Tape Libraries (except for those listed in Table 3) that emulate IBM tape devices.Path Failover Table 3. Data Encryption Tape and Library Requirements Encryption support is available in the IBM encryption-capable TS1120 and Ultrium LTO4 (Fibre Channel or SAS) tape drives that support encryption. FC 1681 (DPF) FC 1680 (CPF). These methods differ in where you choose to locate your Encryption Key Manager (EKM) application. Policies specifying when encryption is to be used are defined through the application interface. Data Encryption Application-managed encryption is supported on AIX.ibm.com/storage/devdrvr/ Refer to your software vendor for support details. Policy control and keys pass through the library-to-drive interface. the following is required: v Encryption-capable tape drive(s) v Encryption configuration features: – Library code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 drives 16 IBM Tape Device Drivers Installation and User’s Guide .ibm. Solaris. and HP-UX. Library-managed encryption is supported on AIX.boulder. Library-Managed Tape Encryption This method is best for encryption-capable tape drives 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. Windows Server 2003. Policy controls and keys pass through the data path between the system layer (device drivers) and the encryption-capable tape drives. Key generation and management is performed by the EKM.ibm. For details on setting up system-managed encryption in different operating system environment.jsp System-Managed Tape Encryption In this method. and HP-UX. please refer to the IBM System Storage Tape Library Operator’s Guide for your library. therefore encryption is transparent to the applications. For details on setting up application-managed tape encryption refer to the Tivoli Storage Manager documentation or for more information. Windows Server 2003. Planning for Application-Managed Tape Encryption Note: Please contact your IBM Representative for additional information about encryption on the IBM encryption-capable tape drive. Please refer to “Planning for Application-Managed Tape Encryption” for details on the hardware and software requirements for application-managed encryption. Linux.com/infocenter/tivihelp/v1r1/index. a Java™ application running on the host. In order to perform encryption on the encryption-capable tape drive. key generation and management is performed by the EKM.software. a Java application running on a host.com/storage/devdrvr/ Refer to “Planning for System-Managed Tape Encryption” on page 17 for details on the hardware and software requirements for system-managed encryption. Windows Server 2008. Encryption is transparent to the applications. Windows 2000. For details on setting up library-managed encryption on encryption-capable tape drives. Policies are based on cartridge volume serial numbers. It is required to use the latest device drivers available on the following ftp down load site: ftp://ftp. Windows Server 2008. Please refer to “Planning for Library-Managed Tape Encryption” on page 19 for details on the hardware and software requirements for library-managed encryption. refer to the applicable chapter for each operating system. It is required to use the latest device drivers available on the ftp down load site: ftp://ftp. visit the following site: http://publib. Solaris.software. Linux. verify. Planning. and User Guide) v Encryption configuration features: – Encryption Key Manager (EKM) – Tape drive code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 drives – Tape system library code updates Setup Tasks for System-Managed Tape Encryption on Open Systems Operating System Any task not identified as an IBM service task is the responsibility of the customer. and configure encryption-capable tape drive (refer your IBM System Storage Tape Drive or Library Operator’s Guide). 4. Chapter 2. Common Extended Features 17 . Install and enable appropriate Device Driver Level (refer to the appropriate operating system chapter in this document for more details) Edit /etc/ibmekm. 4. Refer to the appropriate TSM documentation. cable. Verify encryption of the test volume by Autonomic Management Engine (AME): issue QUERY VOLUME FORMAT=DETAILED Verify that Drive Encryption Key Manager is set to Tivoli Storage Manager. 1. 2. Perform write/read operation to test encryption. the following is required: v Encryption-capable tape drive(s) v Keystore (refer to the IBM System Storage Encryption Key Manager Introduction. 3. Planning for System-Managed Tape Encryption Note: Please contact your IBM Representative for additional information about encryption on the IBM encryption-capable tape drive. cable. for example). Keystore b. and configure the encryption-capable tape drive (refer your IBM System Storage Tape Drive or Library Operator’s Guide ) 2. Install. Planning. 1. Install.) Install. 5. and User Guide for more information on both. In order to perform encryption on the encryption-capable tape drive. Set up encryption policies. System-Managed Encryption Configuration Note: The tape drive must be set to system-managed encryption from the drive panel or library user interface before using device driver system-managed encryption. and configure: a. 3. EKM (Refer to the IBM System Storage Encryption Key Manager Introduction.conf file.Data Encryption – Tape drive code updates Application-Managed Tape Encryption Setup Tasks Any task not identified as an IBM service task is the responsibility of the customer. Use tapeutil EKM test functions to verify. Install appropriate IBM tape device driver level (Atape. 5. The IPv4 address # entered as x. # ekmtest 10 fe80::207:30ee:edcb:d05d 8050 # # The Encryption Key Server address and port can be a local loop back # address 127. # Up to 16 server address and port entries are supported if there are multiple # TCP/IP connections to the same server and/or multiple servers. # ekmtest 10 9. # # Interoperability between IPv4 and IPv6 versions running on dual-stack hosts: # IPv4 Client <--> IPv4/IPv6 Server using IPv4 address for EKM server # IPv6 Client <--> IPv4 Server using IPv4 address for EKM server # IPv6 Client <--> IPv6 Server using IPv6 address for EKM server # # Sample entry for a local server with a 10 second timeout using port 8050 # in IPv4 format # ekmtest 10 127. duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp.12. # The server is for information only and is not used. 2006 # All Rights Reserved # Licensed Materials .x. then Encryption Key Manager needs to be configured.0.0. Figure 3 is an example of the sample configuration file installed.x. 18 IBM Tape Device Drivers Installation and User’s Guide . The servers are configured in a text file ibmekm.123. use Table 4 on page 19 to choose an appropriate IP address type and then add the IP address in the entry of the encryption configuration file. # # This file contains the TCP/IP address(s) and port(s) for the Encryption Key # Server with a configuration entry in the following formats.conf configuration file: v IPv4 format: “EKMserver timeout IPv4_address Port_number” v IPv6 format: “EKMserver timeout IPv6_address Port_number” To set up an IP address for an EKM server. # # The format for IPv4 address: # server timeout address:port # for example. # IBM Encryption Key Manager Configuration File # # (C) COPYRIGHT International Business Machines Corp.1:port in IPv4 format or ::1 port in IPv6 format if the server # is on the same host or a network address and port if external to the host.0.Data Encryption After installing the device driver. Sample Encryption Configuration File The following shows the different entry formats for IPv4 and IPv6 addresses in the ibmekm.x:port.Property of IBM # # US Government Users Restricted Rights .Use. The IPv6 address entered as x:x:x:x:x:x:x:x port.1234:8050 # # The format for IPv6 address: # server timeout address port # for example.1:8050 # # in IPv6 format # ekmtest 10 ::1 8050 Figure 3.0. The timeout value is # specified in seconds.conf that is installed in the /etc directory by the device driver if a current configuration file does not already exist. and User Guide) v Encryption configuration features: – Encryption Key Manager (EKM) – Tape system library code updates and Transparent LTO Encryption feature code for libraries with Ultrium LTO4 drives. 1. EKM (Refer to the IBM System Storage Encryption Key Manager Introduction. and User Guide for more information on both. verify. After configuring servers in the ibmekm. Install. Planning.conf file then specific tape drives need to be configured to the device driver for system-managed encryption. – Tape drive code updates Library-Managed Tape Encryption Tasks Any task not identified as an IBM service task is the responsibility of the customer. and configure a. Interoperability between IPv4 and IPv6 Clients and Servers IPv4 EKM IPv6 EKM IPv4 EKM server IPv4-only server IPv6-only server host host dual-stack host IPv4 IPv4 Client/IPv4-only host IPv6 (no) Client/IPv6-only host IPv4 Client dual-stack host IPv6 Client dual-stack host IPv4 IPv4 (no) IPv4 IPv6 EKM server Dual-stack host IPv4 IPv6 (no) IPv6 (no) IPv6 IPv4 (no) IPv4 IPv6 The timeout value in seconds is used when a request is sent to the server and the time for the server to respond in case no response is received. The device driver default does not enable encryption. the following is required: v Encryption-capable tape drive(s) v Keystore (refer to the IBM System Storage Encryption Key Manager Introduction. Planning. the operation is retried on the next configured server. In order to perform encryption on the encryption-capable tape drive. Chapter 2. Install and cable the encryption-capable tape drive (IBM service task for TS1120 Tape Drive). Refer to the following sections for specific information depending on the operating system. When a connection can not be made or is lost on the current server being used. A maximum of 16 server connections can be configured for failover. Common Extended Features 19 . Planning for Library-Managed Tape Encryption Note: Please contact your IBM Representative for additional information about encryption on the IBM encryption-capable tape drive. Keystore b. 2.Data Encryption Table 4. a sample script (rekey_unix. In addition. Both of these sample programs must be used in conjunction with both the IBM tape and changer drivers. Use library diagnostic functions to verify. If the drives in use are TS1120 Tape Drives. Use IBM System Storage Tape Library Specialist to enable the tape drive for library-managed tape encryption (refer to your IBM System Storage Tape Drive or Library Operator’s Guide). 4. not in I/O station cells or tape drives.ibm. Windows). Linux. Bulk Rekey For customers using Library-Managed Encryption with 3592 Enterprise Tape Drives and IBM tape and changer drivers running on open systems operating system (AIX. If you are using application-managed encryption. For Unix operating systems. the Transparent LTO Encryption feature codes listed in Table 5 are required for the associated IBM tape libraries with Ultrium LTO4 tape drives.Data Encryption 3. no feature code is required on any encryption-capable tape drives.com/storage/devdrvr/sample_code.c) is provided. and are provided to give customers guidance on bulk rekey operations. For more information and to download the sample code packages. Feature Codes (Encryption) Tape Library TS3500 TS3400 TS3310 TS3100/3200 FC 1604 Standard Feature FC 5900 FC 5900 Feature Code 20 IBM Tape Device Drivers Installation and User’s Guide . For Windows operating systems.sh) is provided and must be used in conjunction with the tapeutil version bundled in the same package. a sample c program (rekey_win. The sample code packages are provided ″as-is″ with limited testing. Feature Codes (Encryption) In order to use system-managed and library-managed encryption. Table 5. see ftp://ftp.software. sample code for performing bulk rekey operations is available. data cartridges must be located in storage cells. Solaris. this feature code is not required for system-managed or library-managed encryption. HP-UX. . . . . . Error Logging . . 21 22 22 22 24 24 25 25 26 26 26 26 27 31 32 32 32 33 34 34 35 35 36 36 37 37 37 38 Primary and Alternate Paths. . . . AIX iostat Utility for Tape Performance . . . . . Using the Dump Support . . . . . . . . . Configuring Tape and Medium Changer Devices Deconfiguring Tape Devices . . . . . . . . . 2007. . . . . . . . © Copyright IBM Corp. . . .Tape Utility Program (tapeutil)” on page 322. . . . . . . . . . . . . . . . . . Data Path Failover and Load Balancing Support for Tape Drives . . . . . Error Log Templates . . . . . Control Path Failover Support for Tape Libraries . . . . . 2009 21 . . . . Special Files for Tape Devices . . . 39 . . . . . . Tape Drive Service Aids . Performance Considerations . . . . . . . . . . . . . . Before installing the device drivers. . . . . . . . . . . . . . Querying Tape Drive Configuration . . . . . . Atape Component Trace (ACTRC) Utility . . . . . Configuring and Unconfiguring Primary and Alternate Devices . . . . . . . Reservation Conflict Logging . . . . . . please refer to the ISV web site or their support to find out what device drivers should be used for the ISV. . and Device Driver Parameters Configuration Parameters. . . . . . . . . . . . . . “IBM Tape Diagnostic Tool (ITDT). . . . Special Files for Medium Changer Devices . . . . . . Special Files . . . . . Automatic Cartridge Facility Mode . . . . Software Requirements . . . . . Configuring and Unconfiguring Path Failover Support . . . Component Tracing. . . . . . Trace Facility . . Problem Determination . Media Parameters . Automatic Dump Facility . . . . . . Data Path . . . . . Persistent Naming Support . . . . . . . . . . . . . . .” on page 255 or “AIX System . . . . . . as well as to the advanced functions needed by full tape management systems. . . . . AIX Tape and Medium Changer Device Driver Purpose . . . . . Whenever possible. . . . . . . . Log File . . . . . . . . . . . . 39 39 39 40 40 40 40 41 41 41 42 42 42 43 43 45 45 46 46 46 46 47 49 49 50 50 50 This chapter describes the IBM AIX Enhanced Tape and Medium Changer Device Driver (Atape) for IBM tape devices. . . . . . . . . . . . . . . . . . . Uninstalling . . . . . . . Product Requirements . . . . . . . . . . . . . . . . Querying Primary and Alternate Path Configurations . . . . . . . . . . . . . . . . Tape Log Utility . . Data Flow . . . . . . 38 . . . Installation Procedure . . . . . . . . Error Logging . . . . . . Device and Volume Information Logging . . . . . . . . . . . . . . . Media. . . . . . . . . . . . . . Atape System Trace (ATRC) Utility . . . . . . . . . . . . . . . . Configuring and Unconfiguring Path Failover Support . . Configuring and Unconfiguring Primary and Alternate Devices . For tape diagnostic and utility functions refer to Chapter 10. . . Common AIX Utilities . . . . . . Purpose The IBM AIX Enhanced Tape and Medium Changer Device Driver is designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. . . The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges). . . . . . . . Device Driver Configuration. . . System-Managed Encryption . . . . Details of Tape Service Aids . . Querying Primary and Alternate Path Configuration . . Primary and Alternate Paths. . Hardware Requirements . . . . . . . . Testing Data Encryption Configuration and Connectivity . . . . . Tape Drive. Field Support Information . . . . . . . . . . . . . . . . . . . . . .Chapter 3. . . Before Calling Support . . . Installation and Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Data Path Failover License Key . Please note that some independent software vendor (ISV) applications have certain device driver requirements. . . . . . . . Deconfiguring Medium Changer Devices . . . . . . . . . . Changing the Logical Name After Initial Boot . the driver is designed to take advantage of the device features transparent to the application. . . . . . . . 7044 .H80.7025 . Data Flow for AIX Device Driver (Atape) Product Requirements The following hardware and software components are supported by IBM.System p (also known as pSeries) 620 (7025 .System p (also known as pSeries) 660 (7026 .System p (also known as pSeries) 655 (7039 .AIX Device Driver (Atape) Data Flow The software described in this chapter covers the AIX Enhanced Device Driver (Atape device driver) and the interface between the application and the tape device.F80 . For data flow.System p (also known as pSeries) 610 (7028 .170.7026 .651) .System p (also known as pSeries) 640 (7026 . Hardware Requirements The following hardware is supported by the Atape device driver: v 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 drives: – – – – – 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 Universal Differential Ultra SCSI Adapter (HVD) (FC 6204) Integrated Ultra2 SCSI Adapter for LVD attachment (with a VHDCI connector): .6H0.6C1. 6H1.9112 .6F0. 270 Integrated Ultra3 SCSI Adapter for LVD attachment (with a VHDCI connector): .6C4. Figure 4. M80 – . 6F1) . 6E4 .6M2) .System p (also known as pSeries) 650 (7038 . 6E1) .265 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) v One or more of the following IBM RS/6000 or System p (also known as pSeries) FC-AL host bus adapters for TS1120 tape drives 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 Device Drivers Installation and User’s Guide .B80) .System p (also known as pSeries) 630 (7028 . 6M1) . refer to Figure 4. TS3500 (3584) Library – TS1120 (3592 E05) Enterprise Drive .RS/6000 or System p (also known as pSeries) FC 6207 PCI Differential Ultra SCSI Adapter . one of the following RS/6000 or System p (also known as pSeries) host adapters: – Micro Channel® SCSI Adapters . Models B11. refer to the specific product document for hardware attachment requirements. is supported with the System p (also known as pSeries) FC 6227 or FC 6228 Gigabit Fibre Channel Adapters and FC6239 2 Gigabit Fibre Channel PCI-X Adapters.RS/6000 or System p (also known as pSeries) FC 6204 PCI Universal Differential Ultra SCSI Adapter v For 733x devices.RS/6000 or System p (also known as pSeries) FC 2412 Enhanced SCSI-2 Differential Fast/Wide Adapter/A .TS3400 (3577) Library Chapter 3. and B20) IBM Magstar MP 3570 Tape Subsystem Model C IBM Magstar MP 3575 Tape Library Dataserver v The IBM TotalStorage Enterprise Tape System 3592 Model J is supported with FC6239 2 Gigabit Fibre Channel PCI-X Adapters. E1A.RS/6000 or System p (also known as pSeries) FC 2420 SCSI-2 Differential High Performance External I/O Controller (limited to seven SCSI IDs) – PCI SCSI Adapters . – TS1130 (3592 E06) Enterprise Drive . v The IBM TotalStorage Enterprise Tape System 3590 Model E and Model H Tape Drives with Fibre Channel Attachment.TS3400 (3577) Library .RS/6000 or System p (also known as pSeries) FC 6209 PCI SCSI-2 Differential Fast/Wide Adapter . E11.RS/6000 or System p (also known as pSeries) FC 2409 PCI SCSI-2 Differential Fast/Wide Adapter . and H1A IBM TotalStorage Virtual Tape Server (Models B10. H11.3494 IBM Enterprise Tape Library .3494 IBM Enterprise Tape Library . AIX Tape and Medium Changer Device Driver 23 . B1A. Four Gigabit Fibre Channel Adapter (PCI-E) (FC 5773 and FC 5774) v The 8 Gigabyte Fibre Channel Adapter (FC 5735) is supported on pSeries for the following tape drives and libraries. v The following SCSI-attached devices are supported through the IBM 2108-G07 (SAN Data Gateway) attached to the FC 6227 or FC 6228 Gigabit Fibre Channel Adapters and FC6239 2 Gigabit Fibre Channel PCI-X Adapters: IBM TotalStorage Enterprise Tape System 3590. B18.AIX Device Driver (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) v For the 3490E and Magstar devices.RS/6000 or System p (also known as pSeries) FC 2416 SCSI-2 Differential Fast/Wide Adapter/A . Attention: At the end of the installation procedure. If the installation summary shows that the Atape driver was installed successfully.TS3100 (3573-L2U) Library . 24 IBM Tape Device Drivers Installation and User’s Guide . disk.2 and later releases on IBM POWER-based AIX servers. the following messages are displayed: 0503-292 This update does not fully take effect until after a system reboot. Instructions for uninstalling the device driver are outlined below in “Uninstalling” on page 26. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. or both) where disk and tape subsystems share a common HBA. IBM is focused on assuring server/storage configuration interoperability. you should reboot the machine and attempt to install the Atape driver a second time. When the bosboot command completes.TS3500 (3584) Library Note: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is generally not recommended. the installp facility automatically runs the AIX bosboot command to update the boot record with the newly installed Atape files. We strongly recommend that your overall implementation plan includes provisions for separating disk and tape workloads.TS3500 (3584) Library – Ultrium TD3 LTO drives . it is not necessary to reboot the machine at this time.TS3100 (3573-L2U) Library . This message is referring to the updates to the boot record only.TS3200 (3573-L4U) Library . installp: bosboot process completed.TS3500 (3584) Library – Ultrium TD4 LTO drives . “Accessing Documentation and Software Online. Software Requirements The AIX Enhanced Device Driver (Atape device driver) supports AIX 5L™ Version 5.AIX Device Driver (Atape) . refer to Appendix A.” on page 301. If the installation summary shows that the install failed.TS3200 (3573-L4U) Library . Tape and disk devices require incompatible HBA settings for reliable operation and optimal performance characteristics. Installation and Configuration Instructions The recommended procedure for installing a new version of the device driver is to uninstall the previous version. stability problems have been observed. Under stress conditions (high I/O rates for either tape. To obtain the most current service and documentation for this software. Configuring Tape and Medium Changer Devices After the driver software is installed and a tape device is connected to the adapter.” on page 301. Note: If the tape device was configured previously by another SCSI device driver.:$PATH 5. and is powered up.driver version: lslpp -l Atape. The following command is an example: rmdev -l ost1 -d Installation Procedure Enter the following command to list the currently installed Atape. If you are attaching an IBM TotalStorage Enterprise Tape System 3590 Model E or Model H Tape Drive with the Fibre Channel Attachment. remove any existing device definitions for it. Chapter 3. make sure it is defined with the hard addressing option. Make sure the current path is defined in the command shell PATH variable. 3. Access to the device is not provided until the device is configured. You have a command shell window open on the server to perform the installation procedure.AIX Device Driver (Atape) Installation Procedure For information on obtaining the latest version of device drivers and the latest documentation.x. 4. properly attached to the server.x. You have logged onto the server on an account which has root authority. “Accessing Documentation and Software Online.driver This installs and commits the Atape driver on the system.x. The tape device is properly functioning. or v Power Off your subsystem and reboot the system to configure it automatically and make available any new tape or medium changer devices on the system. issue the following command to remove the device definition before performing the following steps: rmdev -l [device] Configure a tape device using one of the following procedures: v Enter the following command with no parameters: cfgmgr The command configures all devices automatically (including any new tape or medium changer devices). Preinstallation Considerations Before proceeding with the installation. 2. This can be accomplished in the korn shell using the following command: EXPORT PATH=. refer to Appendix A. AIX Tape and Medium Changer Device Driver 25 . verify the following items: 1.driver Enter the following command to install the Atape driver in the current directory for example installp -acXd Atape. If the tape device was configured previously by another device driver (not Atape). the device can be configured and made available for use.x Atape. such as OST (Other SCSI Tape). The first method leaves the tape device defined in the configuration database. It is similar to bringing the device offline (not in use). It is similar to bringing the device offline.driver or using the following installp command: installp -u Atape. but leave it defined in the device database: rmdev -l rmtn 2. Deconfigure the medium changer device using one of the following procedures: 1. replace the letter n with the appropriate number for the chosen device. Media. but leave it defined in the device database: rmdev -l smcn 2. replace the letter n with the appropriate number for the chosen device. The second method brings the medium changer device offline and removes its definition from the device database. Enter the following command to bring the /dev/rmtn tape device offline. Deconfigure the tape device using one of the following procedures: 1. You can uninstall the Atape device driver using the smit command menu to uninstall software and selecting Atape. The second method brings the tape device offline and removes its definition from the device database. and Device Driver Parameters This chapter describes the parameters that control the operating modes of the AIX Enhanced Tape and Medium Changer Device Driver. Enter the following command: rmdev -l rmtn -d The device driver is not unloaded from the kernel until the last device is deconfigured. 26 IBM Tape Device Drivers Installation and User’s Guide . Enter the following command to bring the /dev/smcn medium changer device offline.driver Tape Drive. Enter the following command: rmdev -l smcn -d The device driver is not unloaded from the kernel until the last device is deconfigured. Uninstalling Attention: All devices that use the Atape driver must be closed and cannot be in use when Atape is uninstalled or the uninstall fails. The first method leaves the device defined in the configuration database. Deconfiguring Medium Changer Devices Note: In the following examples.AIX Device Driver (Atape) Deconfiguring Tape Devices Note: In the following examples. The configuration parameters are: v Alternate Pathing v Autoloading v Emulate autoloader (359x devices only) v Block size v Buffered mode (359x devices only) v Compression v v v v v Fail degraded media (359x devices only) Logging Maximum size of the log file New logical name Read error recovery time (359x devices only) v Record space mode v Rewind immediate v Trailer labels Alternate Pathing This parameter enables or disables the path failover support when a device is configured. and F11 IBM TotalStorage Enterprise Tape System 3590. F01. but they are always restored to the configuration values when a device is closed. ACL. ACF. and C11 IBM Magstar MP 3570 Models B02. and C12 (configured in split mode only) v IBM 7332 (all models) Chapter 3. E01. E11. or CSL installed on the tape device. The installation defaults are provided for all parameters initially. The AIX smit command is used to set these parameters when configuring a device or to change these parameters. B11. and H11 IBM Magstar MP 3570 Models B01. Some parameters can be temporarily changed during the open subroutine by an application. C01. Autoloading This parameter enables the autoloading feature of the device driver. C02. AIX Tape and Medium Changer Device Driver 27 . E11. Models B11.AIX Device Driver (Atape) Configuration Parameters The operating parameters for the tape drive and device driver are set and changed by configuration parameters. Note: The autoloading feature is supported only on the following device types and configurations: v v v v IBM 3490E Models C11. The configuration parameters are used to set the operating mode of the tape drive and device driver when a device is opened. The installation default is Off (path failover is not enabled). “Data Path Failover and Load Balancing Support for Tape Drives” on page 37 for a description of the path failover and failover support. 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 Drive installed. It is used with the autoloading capability of the autoloader. These parameters are queried by an application. The AIX chdev command is used to change the configuration parameters. B12. C22. A value of zero is the variable block size. The installation default is Off (do not emulate autoloader). the tape is unloaded. 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 installation default is Off (no autoloading). If this parameter is set to Off. or the IBM 3490 Model F autoloader is set to Random mode. the device driver automatically rewinds and unloads the tape. This feature allows multivolume backups (with commands such as tar) without prompting for a volume change. or on other UNIX® operating systems. the device driver emulates an autoloading tape drive. v The device is installed in a 3494 Enterprise Tape Library. This eliminates the need to re-configure the autoloader of the device Random or Automatic operation. When an unload command is sent to the device driver to unload a tape. 28 IBM Tape Device Drivers Installation and User’s Guide . v The device is used by an application with stack loader support. If this parameter is set to On and the ACF is in Random mode. or the IBM 3490E Model Fxx is set to Random mode. or forward space file operation. v The ACF. or on device types/models that are different from the backup device type/model. If the parameter is set to on. or Random mode. this feature is supported only when the two drives are configured in Split mode. Emulate Autoloader This parameter controls how the device driver operates when the ACF on the IBM TotalStorage Enterprise Tape System 3590. C02. returned to the magazine. Note: On IBM Magstar MP 3570 Models B02. loads the next tape. Tapes created with AUTOLOAD=YES may not be readable in configurations without Atape autoload enabled. or CSL must be set to Automatic. The following conditions are required to use this feature: v The autoloading parameter must be set to On. System. the IBM Magstar MP tape device. the IBM Magstar MP 3570. ACL. then continues reading or writing the next tape. Block Size This parameter specifies the block size used for read and write operations. When the end of tape is reached. and the tape remains in the drive. v The cartridge stacker must be loaded with one or more tapes. During a read. and the next tape in the magazine is loaded automatically into the tape drive. then the tape stacker acts as one large virtual tape. v The tapes being read were not written using the autoloading feature. the normal unload operation occurs. v The application is MKSYSB. no end of tape is detected by the application.AIX Device Driver (Atape) Do not enable autoloading if one of the following conditions is true: v The device is used by an application that provides library medium changer support for the IBM 3581 or IBM 3583. and C12. or in Base mode with only one drive configured and available to AIX. write. This feature does not work in Base mode if both drives are in the available state to AIX. Any other value is a fixed block size. For more information. If compression is enabled. Each time a new entry is made. the information is not saved. The installation default is 500. Fail Degraded Media This parameter controls whether the device driver fails a tape operation when degraded media is detected by the IBM TotalStorage Enterprise Tape System 3590. the data is either stored directly on the physical tape or buffered in the tape device. Buffered Mode When a write command is processed. Degraded media is a correctable condition that prevents the IBM TotalStorage Enterprise Tape System 3590 from performing high speed Locate operations. for which the default is a fixed block size of 1024 bytes. the statistical information about the device and media is saved in a log file when a tape is unloaded. the device fails the command and returns a media error to the application. Maximum Size of the Log File This parameter specifies the number of entries made before the log file starts to wrap. The installation default is On (use Buffered mode). Compression Hardware compression is implemented in the device hardware. The installation default is Off (no logging). Buffering can increase the device performance. Chapter 3. the oldest entry is overlaid. the device driver is notified when the first command is sent to the tape drive. This parameter is intended for use by real time applications that cannot tolerate long Locate commands. Each entry is approximately 2 KB (2048 bytes). The installation default is On (use compression). If this parameter is set to Off. If logging is set to On. After the log file starts to wrap. A Locate command can take over 20 minutes. the number of entries stays constant. If this parameter is set to On. then the effective performance can increase based on the compressibility of the data.AIX Device Driver (Atape) The installation default is zero (use variable length) except for the IBM 7332 4mm Tape Cartridge Autoloader. Logging This parameter turns the volume information logging on and off. This parameter turns the compression feature On and Off. This parameter has no effect on error logging because error logging is always enabled. For more information. refer to “Device and Volume Information Logging” on page 41. AIX Tape and Medium Changer Device Driver 29 . refer to “Device and Volume Information Logging” on page 41. If a tape is loaded and the IBM 3590 cannot read the positioning information from the tape. If logging is set to Off. the device driver does not fail the command. The installation default is Off (do not fail the tape operation if degraded media is detected). depending on the desired position and the amount of data on the tape. There is no installation default value for this parameter. This parameter can also be selected using one of three device special files that allow trailer-label processing. This parameter is intended for use by real-time applications that cannot tolerate long delays when reading data from the tape.AIX Device Driver (Atape) New Logical Name Setting this parameter changes the logical name of the device to a new name as specified. where x is the name of the device (for example. the recovery time for read errors is limited to a maximum of 5 seconds. If this parameter is set to Off. Setting this parameter reduces the amount of time that it takes to close a device for a Rewind on Close special file. but the next command takes a long time to finish unless the rewind operation is physically complete. The first write operation to detect EOM fails. 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 installation default is SCSI mode. and rmtx. Trailer Labels If this parameter is set to On. No data is written during the operation. full recovery is used by the device and can take up to 10 minutes. The installation default is Off (do not limit the read error recovery time).41.60.40). then writing a record past the early warning mark on the tape is allowed. the device driver returns -1 and the errno variable is set to input/output error (EIO). Read Error Recovery Time This parameter controls the read error recovery time for the IBM TotalStorage Enterprise Tape System 3590. The special files are rmtx.40. When a forward or backward space record operation is issued to the driver and a filemark is encountered. If it is set to On. rmtx. All subsequent write operations are allowed to continue until the physical end of the volume is reached and EIO is returned. Record Space Mode This parameter specifies how the device driver operates when a forward or backward space record operation encounters a filemark. The installation default is Off (no rewind immediate) except for the IBM 7332 4mm Tape Cartridge Autoloader. The two modes of operation are SCSI and AIX. 30 IBM Tape Device Drivers Installation and User’s Guide . then the rewind tape operation executes faster. for which the default is On (rewind immediate). If this parameter is set to On. After the logical name is changed. Rewind Immediate This parameter turns the immediate bit On and Off in rewind commands. the new logical name parameter is cleared. rmt0. and the errno variable is set to ENOSPC. The SCSI mode is the default mode of operation. The AIX mode returns the same EIO errno value 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). but (unlike persistent protect) it cannot be reset on the tape. It is reset when the tape is unloaded or the tape drive is reset. Changing this parameter destroys any existing data on the tape. Capacity scaling remains with the tape across mounts until it is changed. “IBM Tape Diagnostic Tool (ITDT). The media parameters are: v Capacity scaling v Logical write protect v 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. Media Parameters The ability to set or change media parameters is a tape diagnostic and utility function. Capacity scaling can be set at 100% for the entire tape (which is the default) or set at 75%.” on page 255 or “AIX System . Logical Write Protect This parameter sets or resets the logical write protect of the current tape on IBM TotalStorage Enterprise Tape System 3590. 60 GB media for the IBM 3592 cannot be capacity scaled and is always 100%.Tape Utility Program (tapeutil)” on page 322.AIX Device Driver (Atape) The installation default is Off (no trailer labels). Notes: 1. The tape position must be at the start of the tape to change this parameter from its current value. 3. For example. 50%. and write-once read-many (WORM) protect. After a tape is WORM protected. WORM protect also remains with the tape across mounts. to change capacity scaling from a 300 GB format tape (100%) to a 60 GB format tape. Persistent protect remains or persists with the tape across mounts until it is reset. or 25% of the tape or any device specific hexadecimal value. IBM TotalStorage Enterprise Tape System 3592. Attempting to set capacity scaling that is not supported by a device or the current media loaded always returns 100% and cannot be changed. select the capacity scaling option. or Magstar MP tape subsystems. it can never be written on again. 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 tape drive can access data faster at the expense of data capacity. The three types of logical write protect are: associated protect. or Magstar MP tape subsystems. IBM TotalStorage Enterprise Tape System 3592. persistent protect. AIX Tape and Medium Changer Device Driver 31 . For example on IBM 3592. By reducing the capacity of the tape. 2. refer to Chapter 10. then select the option to enter a hexadecimal value and enter 35. Associated protect remains only while the current tape is mounted or associated with the tape drive. Chapter 3. Volume ID for Logging This parameter is the volume ID of the current loaded tape.AIX Device Driver (Atape) Notes: 1. As shown in Table 6. Automatic Cartridge Facility Mode If the IBM TotalStorage Enterprise Tape System 3590 or Magstar MP tape subsystem has an ACF installed.smc special file does not support the following operations: v Read v Write v Open in Diagnostic mode v Commands designed for a tape drive If a tape drive has a SCSI medium changer device attached. When this special file is opened. then the ACF mode can be queried by the tapeutil application using the Query/Set Parameters option in the window. See “AIX System . Special Files Once the driver is installed and a tape device is configured and available for use. 32 IBM Tape Device Drivers Installation and User’s Guide . Note: The asterisk (*) represents a number assigned to a particular device (such as rmt0). 2. Note: ITDT does not support the IBM TotalStorage Enterprise Tape System 3590. These special files. Both this special file and the rmt* special file can be opened at the same time. in addition to the tape special files. For detailed information. The tape position must be at the start of the tape to change this parameter from its current value. the application can view the medium changer as a separate SCSI device.smc special file provides a separate path for issuing commands to the medium changer. a special file is provided for tape devices that allows access to the medium changer as a separate device. then all operations (including the medium changer operations) are supported through the interface to the rmt* special file. The file descriptor that results from opening the rmt*. access is provided through the special files. For tape drives with attached SCSI medium changer devices. It is used in the log file entry (if volume logging is active) to identify the entry with a particular volume. are in the /dev directory. which consist of the standard AIX special files for tape devices (with other files unique to the Atape driver).Tape Utility Program (tapeutil)” on page 322 for information on the tapeutil application. Attempting to set logical write protect that is not supported by a device or the current media loaded always returns ″No″ and cannot be changed. the rmt*. refer to Table 6 on page 33. Special Files for Tape Devices Each tape device has a set of special files that provides access to the same physical drive but to different types of functions. The device driver sets the volume ID to UNKNOWN initially and when the tape is unloaded. The Bytes per Inch options are ignored for the tape devices supported by this driver.null file is a pseudo device similar to the /dev/null AIX special file. For more information. 3.4 /dev/rmt*. AIX Tape and Medium Changer Device Driver 33 . The rmt*.20 /dev/rmt*. Special Files for Tape Devices Special File Name /dev/rmt* /dev/rmt*.10 file bypasses normal close processing . Rewind on Close (Note 1) Yes No Yes No Yes No Yes No No Yes Yes No Yes Yes N/A Retension on Open (Note 2) No No Yes Yes No No Yes Yes No No No No No No N/A Bytes per Inch (Note 3) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Trailer Label No No No No No No No No No No Yes Yes Yes No N/A Unload on Close No No No No No No No No No Yes No No Yes No N/A Special Files for Medium Changer Devices After the driver is installed and a medium changer device is configured and made available for use. The smc* special file provides a path for issuing commands to control the medium changer robotic device.10 (Note 4) /dev/rmt*. The input/output control (ioctl) calls can be issued to this file without a real device attached to it. The rmt*.null Description Access to the medium changer robotic device Pseudo medium changer device Chapter 3.3 /dev/rmt*.smc file can be opened independently of the other tape special files. Read and write system calls return the requested number of bytes. Special Files for Medium Changer Devices Special File Name /dev/smc* /dev/smc*.1 /dev/rmt*. access to the robotic device is provided through the smc* special file in the /dev directory. Table 7 shows the attributes of the special file. 4.60 /dev/rmt*. refer to Table 7.41 /dev/rmt*.AIX Device Driver (Atape) Table 6. and the tape is left at the current position. The density selection is automatic.smc (Note 6) Notes: 1. Retensioning is not performed because these tape products perform the retension operation automatically when needed. The Retension on Open special files rewind the tape on open only.5 /dev/rmt*.7 /dev/rmt*. and the device driver returns a successful completion. The asterisk (*) represents a number assigned to a particular device (such as smc0).2 /dev/rmt*. 5.40 /dev/rmt*.6 /dev/rmt*. Table 7.null (Note 5) /dev/rmt*. This file can be used for application development or debugging problems. The Rewind on Close special files write filemarks under certain conditions before rewinding. The term smc is used for a SCSI medium changer device. 6. 2. The rmt*. if the existing rmt1 target 1 device is powered off or not connected.null file is a pseudo device similar to the /dev/null AIX special file. and host bus adapter (HBA). For applications that need a consistent naming convention for all attached devices. 1.AIX Device Driver (Atape) Table 7. and HBA that the device is connected to. if there are three tape drives attached to a parallel SCSI adapter. For example. lun 0 target 2. and 2 respectively. and the device driver returns a successful completion. lun 0 Available Available If the previous rmt1 target 1 device is powered on after reboot and the cfgmgr command is run. Special Files for Medium Changer Devices (continued) Special File Name Description Note: The smc*. even when the system is rebooted. but there are other cases where the logical names of devices could change when the system is rebooted. LUN ID. 34 IBM Tape Device Drivers Installation and User’s Guide . lun 0 Available Available Available On the next reboot. lun 0 target 2. for example. lun 0 Available This is one example. the HBA would initially configure them as Available with the following logical names: rmt0 rmt1 rmt2 target 0. LUN ID. the HBA performs a device discovery and assigns a default logical name to each device found in a sequential order. the HBA configures the device as rmt2 instead of rmt1: rmt2 target 1. The commands can be issued to this file without a real device attached to it. each with a LUN ID of 0 and a target address of 0. This file can be used for application development or debugging problems. lun 0 target 1. When the AIX operating system is booted. Changing the Logical Name After Initial Boot The logical name of a device can be changed after an initial boot and configured. This can be done using the SMIT menu or the chdev command from a script or command line. 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. the HBA would initially configure two devices as Available with the following logical names: rmt0 rmt1 target 0. The file descriptor that results from opening the smc special file does not support the following operations: v Read v Write v Commands designed for a tape device Persistent Naming Support Persistent naming support is used to ensure that attached devices are always configured with the same logical name based on the SCSI ID. it remains set until the device is deleted or the support is unconfigured. it remains in the defined state and is not configured for use. rmt-1. 4. Control Path Failover Support for Tape Libraries Note: The library control path failover feature code must be installed prior to enabling the path failover support in the Atape device driver. In this example. lun 0 target 1. AIX Tape and Medium Changer Device Driver 35 . run: chdev –l rmt0 –a new_name=rmt-0 The output of this command displays rmt0 changed. enter a non-AIX default logical name. the HBA detects that there are unique names predefined for the attached devices. Run SMIT from a command line and select Devices. It must be configured initially on each logical device after installation. Configuring and Unconfiguring Path Failover Support Path failover support is not enabled automatically when the device driver is installed. Note: When path failover is enabled. the devices would configure as follows: rmt-0 rmt-1 rmt-2 target 0. 6. This is transparent to the running application. 3. In this case. if the three tape drives are changed to rmt-0. In the New Logical Name field. 5. Refer to “Supported Devices and Feature Codes” on page 14 for what feature codes may be required for your machine type. When path failover support is enabled for a logical device. Chapter 3. Select the logical device to be changed from the list displayed. Select Tape Drive. tape0. For example. or any descriptive name desired. changing the logical name for either a primary or alternate device only changes that individual device name. 2. but the next rmt-2 tape drive configures as the same name at the same location after reboot.AIX Device Driver (Atape) For example. Using SMIT to Change the Logical Name To change the logical name using SMIT. Using chdev Command to Change the Logical Name The logical name of a device can be changed using the chdev command. The Atape device driver path failover support configures multiple physical control paths to the same logical library within the device driver and provides automatic failover to an alternate control path when a permanent error occurs on one path. and rmt-2 respectively. to change the logical name of the device rmt0 to rmt-0. lun 0 target 2. lun 0 Available Defined Available Since rmt-1 is not detected by the HBA but has been predefined at the SCSI ID and LUN ID. perform the following steps: 1. a default rmt0 logical name for a tape drive could be changed to rmt-0. Press Enter to process the change. and the system is then rebooted with rmt-1 powered off. The alternate path failover setting is retained even if the system is rebooted. Select Change/Show Characteristics of a Tape Drive. and the HBA uses those names. When a second logical device is configured with path failover support enabled for the same physical device.Tape Utility Program (tapeutil)” on page 322. Querying Primary and Alternate Path Configurations You can display the primary and alternate path configuration for all devices with the lsdev command. The labeling of a logical device as either a primary or alternate path is for information only. A third logical device is also configured as an alternate path with either -A or -ALT appended. refer to Chapter 10.AIX Device Driver (Atape) To enable or disable the support on a single logical device. The support can also be enabled or disabled using the chdev command. it configures as an alternate path.” on page 255 or “AIX System . you can easily determine how many physical devices are configured with path failover support. for example: chdev chdev chdev chdev -l -l -l -l smc0 smc1 smc0 smc1 -aalt_pathing=yes -aalt_pathing=yes -aalt_pathing=no -aalt_pathing=no Primary and Alternate Paths When the device driver configures a logical device with path failover support enabled. there can be many (multiple) logical devices labeled as an alternate path for the same devices. but the first device configured is labeled the primary device. 2. All other logical devices configured after the first device are labeled as alternate devices. The device driver supports up to 16 physical paths for a single device. Run the following command: lsdev -Cc tape | grep P For example. Provide information about which logical devices configured on the system have path failover support enabled. Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. To see this. On SCSI attached devices. and so on. -ALT is appended to the location field of the device. There can be two or more logical devices configured for a single physical device. -PRI is appended to the location field of the device. “IBM Tape Diagnostic Tool (ITDT). then select Yes or No for Enable Path Failover Support. -P is appended to the location field. On Fibre attached devices. Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. On SCSI attached devices. -A is appended to the location field. On Fibre attached devices. However. in order to: 1. 36 IBM Tape Device Drivers Installation and User’s Guide . smc1. run the lsdev -Cc tape command and look at the location field in the data. the first device configured always becomes the primary path. select the logical device to change such as smc0. There is only one logical device labeled as the primary path for each physical device. and so on. use the smit menu to Change/Show Characteristics of a Tape Drive. removes the -A or -ALT appended to the location field. or delete license keys for this feature before enabling the path failover feature as described below. Unconfiguring an alternate path device removes that device from the primary device path list. Data Path Failover and Load Balancing Support for Tape Drives Notes: 1. and switch number/port. which also applies to the Path Failover and Failover Support. Installing Data Path Failover License Key Use the following command line script to query. if applicable) and in the Available state. All alternate devices that were unconfigured are reconfigured. 3. the operation is different for a primary device. changing the physical device address/connection without either rebooting or unconfiguring and reconfiguring the devices has unpredictable results and is not supported. DPF keys do not need to be added if you are running the latest drive code on Ultrium-3 and Ultrium-4 drives. 5. 2. host bus adapter. 4. and makes the device available. All remaining alternate devices are reconfigured as alternate paths. 1234567890abcdef. and changes the device to the Defined state. Logical devices that are configured as primary paths can also be unconfigured and reconfigured at any time after initial configuration is run. All key values “A-F” should be entered in lowercase letters as “a-f. The first device that is reconfigured becomes the new primary device. add. The key is a 16-digit hexadecimal value. All alternate devices are unconfigured as described previously. the following events occur: 1. 4. The primary device is unconfigured.AIX Device Driver (Atape) Configuring and Unconfiguring Primary and Alternate Devices Logical devices configured as alternate paths can be unconfigured and reconfigured at any time after the initial configuration is run. 3. When devices are initially configured at a specific SCSI ID and physical connection (drive port. However. This function is not supported for devices that are attached through an IBM San Data Gateway or on the IBM Virtualization Engine TS7510. The -P or -PRI appended to the location field is removed. Likewise. Some devices require a path failover feature code installed prior to enabling the path failover support in the Atape device driver. The AIX operating system only supports a static configuration of devices. AIX Tape and Medium Changer Device Driver 37 . These methods provide the ability to unconfigure and reconfigure physical devices on the system when device connections or addressing changes are made. configuring a new alternate path device or reconfiguring an existing one in the Defined state adds that device to the primary device path list. The device is changed to the Defined state. The primary and any other alternate devices are still available. 2. for example. appends -A or -ALT to the location field. Refer to “Supported Devices and Feature Codes” on page 14 for what feature code may be required for your machine type. When a primary device is unconfigured.” v Query installed keys: dpf_keys Chapter 3. When path failover support is enabled for a logical device. or it can be enabled or disabled selectively by logical device. For example. but not all. Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. setting path failover to Yes. There is only one 38 IBM Tape Device Drivers Installation and User’s Guide . To enable the support globally on all currently configured devices. it remains set until the device is deleted or the support is unconfigured. the first device configured always becomes the primary path and PRI is appended to the location field of the device. It may be desirable at times to configure some. then rmt1. A third logical device is configured as the next alternate path with ALT appended. the lsdev -Cc tape command output is similar to the following: rmt0 Available 20-60-01-PRI IBM 3590 Tape Drive and Medium Changer (FCP) rmt1 Available 30-68-01-ALT IBM 3590 Tape Drive and Medium Changer (FCP) If rmt1 is configured first.AIX Device Driver (Atape) v Install a license key: dpf_keys -a key v Delete a license key: dpf_keys -d key Configuring and Unconfiguring Path Failover Support Path failover support is not enabled automatically when the device driver is installed. then select Yes or No for Enable Path Failover Support. use the smit menu to Change/Show Characteristics of a Tape Drive. it configures as an alternate path and ALT is appended to the location field. It must be configured initially on each logical device after installation. and reconfigures all devices. if rmt0 is configured first. When a second logical device is configured with path failover support enabled for the same physical device. Path failover support can be enabled on all configured devices at one time. run the command: /usr/lpp/Atape/instAtape -a This unconfigures all devices that have path failover set to No. in order to: 1. The support can also be enabled or disabled using the chdev command. The device driver supports up to 16 physical paths for a single device. the command output is similar to the following: rmt0 Available 20-60-01-ALT IBM 3590 Tape Drive and Medium Changer (FCP) rmt1 Available 30-68-01-PRI IBM 3590 Tape Drive and Medium Changer (FCP) The labeling of a logical device as either a primary or alternate path is for information only. for example: chdev -l rmt0 -aalt_pathing=yes chdev -l rmt0 -aalt_pathing=no Primary and Alternate Paths When the device driver configures a logical device with path failover support enabled. logical paths to a device with the support enabled. then rmt0. To enable or disable the support on a single logical device. and so on. The path failover setting is retained even if the system is rebooted. All remaining alternate devices are reconfigured as alternate paths. for example. Logical devices that are configured as primary paths can also be unconfigured and reconfigured at any time after initial configuration is run. All other logical devices configured after the first device are labeled as alternate devices. and changes the device to the Defined state. Configuring and Unconfiguring Primary and Alternate Devices Logical devices configured as alternate paths can be unconfigured and reconfigured at any time after the initial configuration is run. Likewise. Provide information about which logical devices configured on the system have path failover support enabled. The primary device is unconfigured. run the lsdev -Cc tape command and look at the location field in the data. AIX Tape and Medium Changer Device Driver 39 . and makes the device available. 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 Chapter 3. These methods provide the ability to unconfigure and reconfigure physical devices on the system when device connections or addressing changes are made. However. configuring a new alternate path device or reconfiguring an existing one in the Defined state adds that device to the primary device path list. but the first device configured is labeled the primary device. the operation is different for a primary device. The primary and any other alternate devices are still available. The device is changed to the Defined state. you can easily determine how many physical devices on the RS/6000 or System p (also known as pSeries) server are configured with path failover support. All alternate devices are unconfigured as described previously. 3. 2. appends ALT to the location field. Unconfiguring an alternate path device removes that device from the primary device path list. 5. There may be two or more logical devices configured for a single physical device. 4. To see this. The PRI appended to the location field is removed. All alternate devices that were unconfigured are reconfigured. 2. When a primary device is unconfigured. there may be many (multiple) logical devices labeled as an alternate path for the same devices. System-Managed Encryption Device Driver Configuration System-Managed Encryption can be set on a specific tape drive using the standard SMIT panels to Change/Show Characteristics of a tape device or the command line chdev command.AIX Device Driver (Atape) logical device labeled the primary path for each physical device. The first device that is reconfigured becomes the new primary device. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices with the lsdev command. However. By running lsdev -Cc tape | grep PRI. removes the ALT appended to the location field. the following events occur: 1. the device driver does not modify current tape drive setting.Tape Utility Program (tapeutil)” on page 322.Tape Utility Program (tapeutil)” on page 322. refer to Chapter 10. an application can not open a tape drive using the append mode. errpt –a > errpt. When set to off.conf file server entries and test tape drive to server connectivity operations. the tape drive uses encryption for both read/write operations.rmt1 All Atape files in /var/adm/ras/Atape* 40 IBM Tape Device Drivers Installation and User’s Guide . An encryption failure is indicated when the asc/ascq in the sense data is EFxx or EExx. “IBM Tape Diagnostic Tool (ITDT). Refer to the tape drive hardware reference for specific information on the asc/ascq being reported. The wrt_encryption attribute controls whether the device driver can set the tape drive to encryption enabled for write commands. The asc/ascq can be found in the first column of the second row in detail sense data. When set to on. “IBM Tape Diagnostic Tool (ITDT).” on page 255 or “AIX System .” on page 255 or “AIX System . This is a tape diagnostic and utility function. Testing Data Encryption Configuration and Connectivity There is a data encryption test available to validate the ibmekm.AIX System-Managed Encryption The sys_encryption attribute enables device driver system-managed encryption for a tape drive by setting the value to yes. For example: Detail Data SENSE DATA 0A00 0000 5A08 EF11 FF02 D105 0000 0000 0000 2020 2000 0041 0000 0000 0000 25FF 0000 FFFF 4A00 0000 0000 0009 FF00 0000 0000 00FF 0191 0000 0000 0000 FF00 0002 FFF0 0000 0000 0000 0000 B7E3 0000 0000 0000 0000 0001 0000 0000 0000 0A00 2127 0000 0000 F000 0000 0000 0000 0000 0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 1458 0000 0000 0000 0000 0000 0000 3930 0000 0000 0000 3220 0000 Field Support Information When encryption failures require field support and/or development analysis the following data should be provided for a problem on a specific tape drive from the machine (rmt1 for example) for the device driver.rmt1 lsattr –El rmt1 > lsattr. the tape drive uses encryption for read operations. Querying Tape Drive Configuration This is a tape diagnostic and utility function. Tape drive dumps and EKM server logs may be needed in addition to this information. Note: If wrt_encryption is set to on. The custom setting is intended for applications using system-managed encryption to control write encryption without device driver intervention. 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. When set to custom. refer to Chapter 10. write operations do not use encryption.rmt1 tapeutil –f /dev/rmt1 encryption > encryption. Error logging is routed to the system error log. enter the following command: sysdumpdev -l To establish the rmt1 tape device as a secondary dump device. the logging facility gathers all available information through the SCSI Log Sense command. Dump Device Commands To list the current dump devices. For example: dd if=/dev/rmt1 of=tapedump1 ibs=4096 obs=512 crash tapedump1 Note: The ibs value is the input block size. use the sysdumpstart command. Use the sync command to ensure that the cache is flushed before issuing the sysdumpstart -s command. If the block size of the tape device is larger than the block size sent during the dump process.AIX Device Driver (Atape) Problem Determination A set of tools is provided with the device driver to determine if the device driver and the tape device are functioning correctly. The information is extensive for some devices and limited for other devices. enter the following command: sysdumpdev -z After the dump data is placed on the tape. This process is a separate facility from error logging. Using the Dump Support Dump support is provided through the dump entry point in the driver. The standard AIX interface is provided for problem determination. To send the dump data to the secondary dump device. AIX Tape and Medium Changer Device Driver 41 . If set to On. To list the last dump data. copy it to a file on the disk before using the crash command to process it. Device information logging is sent to a separate file. Refer to appropriate AIX manuals for a description of how to use the dump devices and how to read the dump data. Set the block size to zero on the tape device and experiment with the ibs value for the dd command. enter the following command: sysdumpdev -s /dev/rmt1 To perform a dump operation. Device and Volume Information Logging An optional logging utility is provided to log the information about the device and the media. The following parameters control this utility: v Logging v Maximum size of the log file v Volume ID for logging Chapter 3. enter the following command: sysdumpstart -s Note: This command stops the system. the dump operation fails. The C source code (tapelog. the device driver will log this information as follows: Reserving host key xxxxxxxx WWPN xxxxxxxx Where the first xxxxxxxx is the actual reserve key and the second xxxxxxxx is the reserving host initiator WWPN. The syntax for the tape log utility is: tapelog -l Name [-d] or tapelog -f File [-d] Notes: 1. and Device Driver Parameters” on page 26 for a description of these parameters. contains all pages the device supports. File is the name of a log file (such as Atape. The log pages are displayed as hexadecimal values in dump format. Each entry has a header followed by the raw Log Sense pages as defined for a particular device. 3. Each time the rewind and unload sequence occurs or the STIOC_LOG_SENSE ioctl command is issued. The first log page is always page 0x00.c) for the program is in the /usr/lpp/Atape/samples directory. The -d parameter. the values in the device log buffers are reset with the Log Sense command. Page 0x00 is followed by all pages specified in page 0x00.rmt0.log The files are in binary format. For example: tapelog -l rmt0 > rmt0. an entry is added to the log. 2.log Reservation Conflict Logging When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the AIX error log. Tape Log Utility A tape log utility is installed with the tapelog device driver that displays the contents of the log file in ASCII text. therefore. The contents of the log file are displayed as standard output.rmt1. The format of each following page is defined in the SCSI specification and the device manual. The file name is dependent on each device. Log File The data is logged in the /usr/adm/ras directory.log). An example of the rmt1 device file is: /usr/adm/ras/Atape. deletes the log file for the specified device. This page. Name is the logical name of the device (such as rmt0). Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name) and reserve key. Each time a new cartridge is loaded. if used. each device has a separate log.AIX Device Driver (Atape) Refer to “Tape Drive. as defined in the SCSI-2 ANSI specification. 42 IBM Tape Device Drivers Installation and User’s Guide . If successful. To save the log in a file. The log data is gathered on a per-volume basis. The program contains a sample of the interface to the log file and the structure used to read the file. Media. use the AIX redirection function. subsequent reservation conflicts from the same reserving host WWPN will not be logged to prevent multiple entries in the error log until either the reserving host WWPN is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs. Error Labels Errors are logged with an associated error label and error ID. media. errno x The possible errno values are: v ENOMEM . Refer to “Error Log Analysis” on page 48. The error label indicates the basic type of error: v TAPE_ERR1 Tape media error v TAPE_ERR2 Tape hardware error v TAPE_ERR4 SCSI Adapter detected error v TAPE_ERR5 Unknown error v RECOVERED_ERROR Temporary tape hardware or media error v SIM_MIM_RECORD_3590 3590 Service/Media Information Message (Log Page X'31') v TAPE_SIM_MIM_RECORD Tape drive Service/Media Information Message (Log Page X'31') v DEV_DUMP RETRIEVED Device dump retrieved Chapter 3. The error log can also be viewed using the smit or the errpt command. AIX Tape and Medium Changer Device Driver 43 . and SCSI adapter related errors in the AIX system error log.Device has a Persistent Reservation but does not support the Persistent Reserve In service action v EBUSY . The following items describe the error labels and detail data for the templates used for logging tape device.Unknown I/O failure occurred Error Logging The device driver provides logging to the AIX system error log for various errors. If the Persistent Reserve In command fails then the detail data will contain the following entry with the errno from the failing Persistent Reserve In command: Unable to obtain reserving host information. The error log can be viewed for specific devices using the Error Log Analysis utility provided with the tape drive service aids. Each error log entry is identified by an error label and contains detail data associated with the type of error.AIX Device Driver (Atape) After initially logging the reserving host WWPN. Error Log Templates The error log templates the device driver uses follow the same format as the default AIX tape error log entries.Device has failed the command with reservation conflict and has a SCSI-2 Reserve active v EIO .Device driver cannot obtain memory to perform the command v EINVAL . Target is reserved to another initiator.Blown terminator fuse or bad termination. 08 NO DEVICE RESPONSE . 04 COMMAND TIMEOUT .Adapter indicated a hardware failure..Adapter indicated SCSI bus has been reset. v 40 FUSE OR TERMINAL PWR ..Adapter indicated a microcode failure.AIX Device Driver (Atape) v TAPE_DRIVE_CLEANING Tape drive needs cleaning v RESERVE_CONFLICT Reservation conflict Detail Data Detail data is logged with the associated error that identifies the cause of the error. v 18 RESERVATION CONFLICT . v 80 SCSI BUS RESET .Host I/O bus error during data transfer. Detail data for the SIM_MIM_RECORD_3590 or TAPE_SIM_MIM_RECORD entries contain the raw data from Log Sense Page X'31'. then an adapter error was reported. 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 .Command timed out before completion. 44 IBM Tape Device Drivers Installation and User’s Guide . 10 ADAPTER HARDWARE FAILURE . v 08 BUSY STATUS . then a SCSI error was reported. v 22 COMMAND TERMINATED . For parallel SCSI adapters. this is the general_card status code as defined in /usr/include/sys/scsi.Device command queue is full.Target did not respond to selection phase. hh This byte indicates the type of adapter error that occurred. v 28 QUEUE FULL . 02 SCSI BUS FAULT .. If this field is 02.SCSI bus protocol or hardware error.Device terminated the command.h: v v v v v 01 HOST IO BUS ERROR .Device reported a check condition.Target is busy. and byte gg indicates the type of error. This byte indicates the type of SCSI error that occurred: v 02 CHECK CONDITION . If this field is 01. cc is the operation code (byte 0) Logical unit (byte 1) in the CDB Bytes 2 through 12 in the CDB Status validity field. Refer to the hardware reference manual for the format of this entry. gg v 20 ADAPTER SOFTWARE FAILURE . Where: aa bb xx cc dd ee ff Length of the command descriptor block (CDB) SCSI target address Unused or reserved Start of CDB. and byte hh indicates the type of error. Whenever a check condition occurs and the sense data indicates that a dump is available. rmt0.Blown terminator fuse or bad termination. Enter the following AIX command to stop the trace: trcstop Chapter 3. The trace event is identified with a hookword. 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 events with the 326 hookword (Atape device driver).dump3 Note: X is the device number.Adapter detected a new worldwide name for the device.Command timed out before completion.h: 01 HOST IO BUS ERROR .Host I/O bus error during data transfer.dump1 Atape. 03 COMMAND TIMEOUT .rmtx.rmtx. this is the adapter_status code as defined in /usr/include/sys/scsi_buf. 09 TRANSPORT RESET .rmtx. 0A TRANSPORT BUSY . for example.The transport layer is currently inoperative. 0B TRANSPORT DEAD . A maximum of three dumps for each device are stored in this directory as: Atape. The hookword used by the device driver is 326.The transport layer is busy. If more than three dumps occur.Failure in the transport layer. 08 FUSE OR TERMINAL PWR .Adapter indicated a hardware failure. When the device is first configured. the ss byte is the sense data from the device. AIX Tape and Medium Changer Device Driver 45 . Trace Facility The AIX trace facility is supported for the device driver. the dump name is set to dump1. the driver starts over at dump1. Refer to the appropriate device reference manual for the specific format and content of these bytes. Automatic Dump Facility The device driver provides an automatic dump facility for devices that support reading a dump and indicating when a dump is available in device sense data. 06 ADAPTER SOFTWARE FAILURE . therefore the last three dumps are always kept. 02 TRANSPORT FAULT . The trace can be initiated at any time before an operation on a tape device.AIX Device Driver (Atape) For FCP or SAS adapters.Adapter indicated a microcode failure. the device driver reads the dump from the device and stores it in the /var/adm/ras directory.Adapter detected an external SCSI bus reset. ss If byte gg indicates a check condition. 04 NO DEVICE RESPONSE .dump2 Atape. 07 WW NAME CHANGE .Target did not respond to attempts to select it. 05 ADAPTER HARDWARE FAILURE . enter the atrc command. 2. Enter the following AIX command to view the trace: trcrpt > trace.BZ) to a file (for example. Atape System Trace (ATRC) Utility The atrc trace utility is also installed with the device driver to start. The AIX system dump is normally stored in the /var/adm/ras directory as a vmcore. and format a device driver trace.1. run the following commands: ctctrl -D -c Atape trcrpt -l Atape -o actrc. 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.1 trcrpt -l Atape -o actrc.out The Atape component trace can also be retrieved from a system dump.dump Atape Component Trace (ACTRC) Utility The actrc component trace utility is also installed with the device driver to dump and format the current Atape component trace. where x is a dump number 1. stop. To stop and format the trace.BZ file.out This command formats the trace output into a readable form and places it into a file for viewing.3 and above support component tracing. Refer to the AIX ctctrl man page for a complete description of the ctctrl command and parameters.1. run the following commands: dmpuncompress /var/adm/ras/vmcore. To start the trace. actrc. vmcore. actrc.AIX Device Driver (Atape) This command stops the trace after the tape operations are performed.out AIX file in the current directory.BZ trcdead -c /var/adm/ras/vmcore. You must have root authority to run this command. Unlike system tracing that needs to be started and stopped. 46 IBM Tape Device Drivers Installation and User’s Guide . The trace is formatted to an atrc. The trace is formatted to an actrc. component tracing by default is on all the time and runs continually. To determine if component tracing is available run the command ctctrl -q to display a list of supported components with their default settings. To retrieve and format the Atape component trace from a dump file (for example.x. and so on.out file in the current directory.dump) into the current directory. enter the atrc command again.out) into the current directory. To dump and format the component trace. run the command actrc. Component Tracing Later releases of AIX 5. To dump and format the current component trace to a file (for example. Tape Drive Service Aids The service aids provided with the device driver can be called using the interactive interface of the tape utility program and selecting Tape Drive Service Aids under General Commands or using the Service Aid Subcommands in the command-line interface of the tape utility program. Select the device from the IBM Tape Drive Selection window. Select the device from the IBM Tape Drive Selection window. The Read Dump operation starts. Select Read Dump from the IBM Tape Drive Service Aids window. Details of Tape Service Aids The following service aid utilities are installed with the device driver: v Force Microcode Dump v Read Dump v Microcode Load v Error Log Analysis v Reset Drive v Create an FMR Tape Force Microcode Dump This utility forces a dump operation on the tape drive. To access this utility: 1. After the dump operation is performed. then press Enter. The Force Microcode Dump operation starts. 3. Enter the destination file name or device in the Prompting for Destination window. it may be necessary to press the Esc key and the number 7 key instead of F7.AIX Device Driver (Atape) The service aids described in the following sections are accessible through the AIX diagnostic subsystem using the AIX diag command. or a tape cartridge. and a window opens when the operation is completed. Open the Service Aids window. “IBM Tape Diagnostic Tool (ITDT). Note: On certain terminal types. 2. Open the Service Aids window. To access this utility: 1.” on page 255 or “AIX System . enter the device name of the tape drive (for example. Refer to “Details of Tape Service Aids” and “Service Aid Subcommands” on page 330. then press Enter. then press Enter. Select Force Microcode Dump from the IBM Tape Drive Service Aids window. /dev/rmt0). 3. or the interactive and command-line interfaces of the tapeutil program installed with the device driver. To transfer the dump data to a file. enter the file name. the dump data can be transferred from the tape drive using the Read Dump utility. AIX Tape and Medium Changer Device Driver 47 . then press Enter. Press F7 to commit. For tape diagnostic and utility functions refer to Chapter 10.Tape Utility Program (tapeutil)” on page 322. a diskette. To transfer the dump data to a tape cartridge. and a window opens when the operation is completed. The default destination is the /dev/rfd0 diskette drive. 4. Read Dump This utility transfers the dump data from the device to a file. Chapter 3. 2. AIX Device Driver (Atape) Microcode Load This utility downloads microcode to the device 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 drive. To access this utility: 1. Open the Service Aids window. 2. Select Microcode Load from the IBM Tape Drive Service Aids window, then press Enter. 3. Select the device from the IBM IBMTape Drive Selection window, then press Enter. 4. Enter the source file name or device on the Prompting for Source File window. The default source is the /dev/rfd0 diskette drive. 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 drive is Federal Information Processing Standard (FIPS) code, then a window opens and displays the following: Warning: The drive is currently using FIPS code. Press Enter to continue with downloading new drive 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. 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 drive 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 Service Aids window. 2. Select Error Log Analysis from the IBM Tape Drive Service Aids window, then press Enter. 3. Select the device from the IBM Tape Drive Selection window, then press Enter. 4. If entries are listed in the error log for the selected device, 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. 48 IBM Tape Device Drivers Installation and User’s Guide AIX Device Driver (Atape) Reset Drive This utility resets the tape drive. To access this utility: 1. Open the Service Aids window. 2. Select Reset Drive from the IBM Tape Drive Service Aids window, then press Enter. 3. Select the device from the IBM IBMTape Drive Selection window, then press Enter. The Reset Drive 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 drive. To access this utility: 1. Open the Service Aids window. 2. Select Create an FMR Tape from the IBM Tape Drive Service Aids window, then press Enter. 3. Select the device from the IBMTape Drive Selection window, then press Enter. The Create an FMR Tape operation starts, and a window opens when the operation is completed. Performance Considerations This chapter describes the parameters and issues that may affect the perceived performance of the tape drive. In general, AIX applications that operate at a file level to move data between disk storage devices and tape do not exploit the full capabilities of a high end tape device. The goal of this discussion is to give an overview of the data path components involved in moving data between disk storage devices and tape. The following chapter describes basic techniques and common utilities in a specific environment that can be used to understand how a device is performing. Performance issues encountered by advanced application developers are beyond the scope of this document. v Refer to the hardware reference for the specific device for performance specifications. v Refer to the application documentation for information on device-specific application configuration. v Refer to the operating system documentation for information on disk storage device striping and other techniques for improving file system performance. Data Path The simplified model in Figure 5 shows the components involved in the data path for moving data at a file level between disk storage devices 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 adversely. Chapter 3. AIX Tape and Medium Changer Device Driver 49 AIX Device Driver (Atape) Figure 5. Data Path for AIX Device Driver (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 device. Note: The device 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 device is uncompressed. 2. The block_size parameter should be set to variable (block_size=0) and command or application parameters specified to a block size appropriate for the device. 3. Block sizes of 128 KB or greater should be used to improve 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 devices (such as disk). To determine if the iostat utility supports the configured tape drives, run the command iostat -p. If the configured tape drives are supported, a list of configured tape drives are displayed with the statistics listed for each drive. Refer to the AIX iostat man page for a complete description of the iostat command and parameters. When using the Data Path Failover feature, only the primary path for the tape drive 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 8 before contacting support. Table 8. Error Description Information Configuration Device parameters Error log. Call hardware support if errors are found for TAPE_ERR* or SCSI* error labels. Driver version Command lscfg -v lsattr -E -l rmtN errpt -a lslpp -l Atape.driver 50 IBM Tape Device Drivers Installation and User’s Guide AIX Device Driver (Atape) Table 8. Error Description (continued) Information Command Device microcode level (may not apply to all tapeutil -f /dev/rmtN reqsense devices) Trace of failing command Refer to “Trace Facility” on page 45 Chapter 3. AIX Tape and Medium Changer Device Driver 51 AIX Device Driver (Atape) 52 IBM Tape Device Drivers Installation and User’s Guide Chapter 4. HP-UX Tape and Medium Changer Device Driver Purpose . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . . Product Requirements . . . . . . . . . . ATDD Implementation . . . . . . . . Hardware Requirements . . . . . . . . Software Requirements . . . . . . . . Software Interface to the Device Driver . . . Installation and Configuration Instructions . . . Installation and Configuration for PCI Drivers. Installation and Configuration of Precision Bus Drivers . . . . . . . . . . . . . . Supported Configuration Parameters . . . . . Configuration Parameter Definitions . . . . Special Files . . . . . . . . . . . . . Persistent Naming Support . . . . . . . . Control Path Failover Support for Tape Libraries . Configuring and Unconfiguring Path Failover Support . . . . . . . . . . . . . Primary and Alternate Paths. . . . . . . . . . . . . . . . . . . . . . 53 53 54 54 54 55 56 56 56 64 73 73 76 78 78 Querying Primary and Alternate Path Configurations . . . . . . . . . . . Disable and Enable Primary and Alternate Paths Data Path Failover and Load Balancing Support for Tape Drives . . . . . . . . . . . . . Configuring and Unconfiguring Path Failover Support . . . . . . . . . . . . . Primary and Alternate Paths. . . . . . . Querying Primary and Alternate Path Configuration . . . . . . . . . . . Disable and Enable Primary and Alternate Paths Problem Determination . . . . . . . . . Error Logging . . . . . . . . . . . Reservation Conflict Logging . . . . . . Sense Data Logging . . . . . . . . . Support_info Script . . . . . . . . . . Tracing Facility . . . . . . . . . . . Atdd_d Log Daemon . . . . . . . . . Problems and Solutions . . . . . . . . . 80 80 . 80 . 81 . 82 . 83 83 . 83 . 83 . 83 . 84 . 84 . 84 . 85 . 87 . 79 . 79 This chapter provides an overview of the IBM Tape and Medium Changer Device Driver for HP-UX that provides support for IBM tape drives and medium changer devices. For tape diagnostic and utility functions refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 255 or “HP-UX System - Tape Utility Program (tapeutil)” on page 335. Purpose This device driver product provides SCSI-3 attachment for the IBM tape devices to selected Hewlett-Packard Precision Bus and PCI-based operating systems running HP-UX 10.20, 11.0, 11i v1, 11i v2, and 11i v3. The HP-UX installed name of this device driver is Advanced Tape Device Driver (ATDD). ATDD is used throughout this section to identify this driver. ATDD is designed specifically to take advantage of the features provided by the IBM tape devices (refer to “Supported Hardware” on page 9. The goal is to give applications access to the functions required for basic operations (such as backup and restore) and the advanced functions needed by full tape management systems. Whenever possible, the device driver is designed to take advantage 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 Device Driver for HP-UX (ATDD). Figure 6 on page 54 shows the relationships between the IBM Tape and Medium Changer Device Driver for HP-UX, the application program, the SCSI or Fibre Channel adapter device driver, and the IBM tape subsystem. © Copyright IBM Corp. 2007, 2009 53 HP-UX Device Driver (ATDD) Figure 6. Data Flow for HP-UX Device Driver (ATDD) Product Requirements The following hardware and software components are required and supported by the IBM Tape and Medium Changer Device Driver for HP-UX (ATDD). ATDD Implementation ATDD is actually a set of device driver implementations for operation in the following HP-UX operating system environments: v HP Precision Bus - HP-UX 10.20 (32 bit) - versions of this driver are identified by levels ATDD 2.9.x.x. v HP Precision Bus - HP-UX 11.00 (32 bit) - versions of this driver are identified by levels ATDD 4.9.x.x. v HP PCI Bus - HP-UX 11.00 (64 bit) - versions of this driver are identified by levels ATDD 1.x.x.x. v HP PCI Bus - HP-UX 11i v1 (64 bit) - versions of this driver are identified by levels ATDD 3.x.x.x. v HP PCI Bus - HP-UX 11i v2 (64-bit for Itanium® 2) - versions of this driver are identified by levels ATDD 5.5.x.x. v HP PCI Bus - HP-UX 11i v2 (64-bit for PA-RISC) - versions of this driver are identified by levels ATDD 5.6.x.x. v HP PCI Bus - HP-UX 11i v3 (64-bit for Itanium 2) - versions of this driver are identified by levels ATDD IA.6.x.x.x. v HP PCI Bus - HP-UX 11i v3 (64-bit for PA-RISC) - versions of this driver are identified by levels ATDD PA.6.x.x.x. Hardware Requirements ATDD supports the following HP SCSI host bus adapters: v v v v v v v v v v 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 revision 3543 or later (ATDD Precision Bus drivers) 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 v3 only) HP PCI 1000Base-T and 1000Base-SX Adapter (HP A6794A, LVD) (11i v3 only) 54 IBM Tape Device Drivers Installation and User’s Guide a250104 Application Program ATDD Device Driver SCSI or Fibre Channel Adapter Device Driver IBM Tape Subsystem HP-UX Device Driver (ATDD) v HP PCIe SC44Ge SAS Host Bus Adapter (HP AH303A, SAS) (11i v3 only) ATDD supports the following HP Fibre Channel adapter: v v v v 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 devices that are attached to HSC/GSC bus architectures. 2. For attachment of Enterprise Tape System 3590 and IBM Magstar MP devices 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 available as FC 9798 for Enterprise Tape System 3590 and FC 5098 for the 3575 Tape Library Dataserver 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 device on the bus as usual. 3. The low level 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 version (FCP-2), dated 17 November 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 devices require incompatible HBA settings for reliable operation and optimal performance characteristics. Under stress conditions (high I/O rates for tape, disk, or both) where disk and tape subsystems share a common HBA, stability problems have been observed. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. IBM is focused on assuring server and storage configuration interoperability. It strongly recommends that your implementation plan includes provisions for separating disk and tape workloads. 5. The HP A6826A HBAs need the Qlogic firmware level B.11.11.02 or later. If the adapter is directly connected to a 3592 without a switch, then the topology on the drive port needs to be set to L-port. The most recent supported HBA information can be found at the following site: http://www-01.ibm.com/servers/storage/support/config/ess/index.jsp Software Requirements The following software is required and supported by ATDD: v HP-UX operating system version 10.20, 11.0, 11i v1, 11i v2, and 11i v3. v 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. The latest driver information can be found at the following site: ftp://ftp.software.ibm.com/storage/devdrvr/HPUX Chapter 4. HP-UX Tape and Medium Changer Device Driver 55 This entry point is driven by the input/output control (ioctl) system function call. By default. ACDD. refer to the atdd. ACDD. ATDD automatically configures all supported IBM tape drives that are attached and powered On when the system starts. 11i v1 and v2. selected IBM Medium Changer devices can be configured by running the swinstall command with the -x ask=true command option. Installation and Configuration for PCI Drivers This chapter describes how to install. 11i v1 and v2. Additionally. the ATDD package consists of five modules in the kernel: v v v v v atdd . or by running /opt/atdd/bin/atdd_claim –c c in 11. the changer part of ATDD.static tape driver kernel module acdd . The installation process depends on whether all IBM tape drives are to be configured by ATDD or only selected 56 IBM Tape Device Drivers Installation and User’s Guide .com/storage/devdrvr/HPUX/11i_PCI/ Software Interface to the Device Driver The IBM Tape and Medium Changer Device Driver for HP-UX provides the following standard HP-UX entry points for IBM tape systems: Open Write Read Close IOCTL This entry point is driven by the open system function call.HP-UX Device Driver (ATDD) Attention: To install ATDD in HP-UX 11i v3. Installation and Configuration Instructions The following sections describe the installation and configuration for three types of HP-UX devices. does not configure IBM Medium Changer devices by default because many applications use either their own changer drivers or the native schgr or sctl drivers. In HP-UX 11. GA32-0566.static legacy changer driver kernel module atdd_core . the changer part of ATDD.0. and SCSI specific operations.static legacy tape driver kernel module acdd_leg . and uninstall the IBM Tape and Medium Changer Device Driver for HP-UX (ATDD) for PCI-based systems. medium changer device.Readme file at the following site: ftp://ftp. refer to the IBM Tape Device Drivers Programming Reference.software. This entry point is driven explicitly by the close system function call and implicitly by the operating system at program termination.ibm. configure. It provides a set of tape device. For the detailed information. some HP-UX patches must be applied first on the system. For programming information.DLKM core kernel module Overview of the Installation Process During and after the ATDD is installed. This entry point is driven by the read system function call. can be set to configure (CLAIM) all attached IBM Medium Changer devices. This entry point is driven by the write system function call. the ATDD package includes with atdd tape driver and acdd changer driver dynamic loadable kernel modules (DLKM). It allows HP-UX applications to access and control the features and attributes of IBM SCSI tape subsystems programmatically.0. In HP-UX 11i v3.static changer driver kernel module atdd_leg . This error can be overridden using ’-x’ to set the mount_all_filesystems option to FALSE. Follow these steps to perform the install: 1. This ensures that all listed file systems are mounted before proceeding. When this option is used. Additionally. Analysis. Many commands (for example. you must create a configuration file that directs the device driver on how to customize driver behavior for particular IBM TotalStorage and System Storage devices. If you encounter unexpected results during the installation. swinstall and swremove) attempt to mount all file systems in the /etc/fstab file at the start of the analysis phase. the command finishes with a warning that indicates no attempt is made to mount all file systems. Copy the software from the distribution medium to the depot. 3. or NOT configured at all. 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. (Optional) If you are not using the standard device driver defaults. selectively configured. swinstall or swcopy) can be run first with the -p flag to preview the command. you can reissue the command without the -p flag to perform the actual operation.HP-UX Device Driver (ATDD) ones. If all Chapter 4. Check the README file and verify that your system is configured appropriately for installing ATDD. and Execution. While using the software distributor commands. HP-UX Tape and Medium Changer Device Driver 57 . After observing the preview output. filenames given on the command-line must be referenced with an absolute path. v The software distributor commands are moderately complex scripts that frequently require several steps. Each step may produce useful information and error messages. but it often causes an error with NFS mounted file systems. Using ’pwd’/filename to reference a file instead of filename ensures this. for IBM Medium Changers. so it is a good idea to carefully observe the results of the installation process as it occurs. Preinstallation Considerations Make sure your system is ready to install ATDD before you begin. installation selection or post-installation configuration can determine whether all IBM Medium Changers should be configured. v All the software distributor commands (for example. 2. The steps are typically Selection. The following describes facts about the command sequences: v In some of the examples. Create the Drive Configuration File. Ensure that the tape drives to be managed by ATDD are powered on. This also helps ensure that files are not loaded into a directory that may be below a future mount point. 4. and whether configured tape drives exhibit default behavior or require specific configuration settings. Install and configure the software. check the associated log file. 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. Create an entry in the /etc/rc.e. v No trailing comments may appear on a variable definition line.0 Create the Hardware Path Entry: You must tell the driver which hardware path you want to attach to if you are not using the installation defaults for driver behavior.9. If you do need to create a Drive Configuration File. perform the following steps: 1.HP-UX Device Driver (ATDD) configured devices are to use the device driver configuration defaults.0 58 IBM Tape Device Drivers Installation and User’s Guide .1.1.. v You do not use the device driver configuration defaults.7. the Fibre Channel) the tape drive is connected to. Record the hardware path entry of the adapter: For example: 0/10/0/0 3. The configuration file is named sbin/init. Determine the SCSI target address of the tape drive. Run ioscan to determine the hardware path (i. The Drive Configuration File is required if: v You are running a level of ATDD before level 1.6.255. perform the following steps: 1. skip to the instructions in “Power Off the Tape Drives” on page 59.8.0 on HP-UX 11.0.drivetargetaddress.d/atdd and has the following syntax: ATDD_global_parameter=value ATDD_device_parameter[index]=value Note: v Blank lines and lines starting with # are ignored.0 (tape drive) For a tape drive at SCSI target address 3.3.14. # ioscan -f -C tape 2. the SCSI adapter) the tape drive is connected to.8.config. v No spaces may appear within each entry.255.e.0 To determine the device hardware path for IBM tape drives with the Fibre Channel attachment.0.6. If you do not need to create a Drive Configuration File.0 ATDD_HWPATH[2]=0/5/0/0. Determine the Device Hardware Path for IBM Tape Drives: To determine the device hardware path for IBM tape drives with a SCSI attachment. the device hardware path is: 0/10/0/0. it is not necessary to create a configuration file before installing the driver for ATDD. For example: ATDD_HWPATH[0]=0/10/0/0. HWPATH = adapterpath.. consult the following instructions.0.0 ATDD_HWPATH[1]=0/10/0/0. Run ioscan to determine the hardware path (i.d/atdd configuration file for each device you want the driver to attach. Record the hardware path entry of the Fibre Channel: For example: HWPATH = 0/5/0/0.7. # ioscan -f -C ext_bus 2. HP-UX Tape and Medium Changer Device Driver 59 . If you have four tape devices attached. check the /etc/rc. four ATDD_HWPATH entries are required in the configuration file. Each device may have a different value for each configuration variable.log for errors and correct the problem. it attaches itself to all tape drives that are in the CLAIMED state as shown by entering the command: # ioscan -fk -C tape Before you continue. The index number associated with the configuration variable associates the parameter setting with the device at the hardware path with the same index.1. If you have a single 3590 device operating in one LUN mode. power Off the tape drive and run ioscan without the ’-k’ argument as follows: # ioscan -f -C tape Chapter 4.0 (based on the hardware path entry in “Create the Hardware Path Entry” on page 58).0. Refer to Table 9 on page 74 and Table 10 on page 75 for a description of all configuration parameters.HP-UX Device Driver (ATDD) Note: This example shows that three devices are CLAIMED by the ATDD. you can also enter: # ioscan -funNC tape To remove a tape drive from the CLAIMED state so it is not configured by this driver. Example 1: ATDD_IMMEDIATE[0]=1 This parameter allows application control to return from the device before the rewind completes for the device at hardware path 0/10/0/0.6. Power Off the Tape Drives When the ATDD software is initially installed. To change these settings. enter: # ioscan -funC tape In HP-UX 11i v3. an entry is made in the configuration file assigning an appropriate value to the desired configuration variable. Create the Device Specific Configuration Entries (Optional): The ATDD is shipped with default settings for all configuration parameters. Example 2: ATDD_TRAILER[1]=1 This parameter allows write operations after an early end-of-tape warning for the device at hardware path 0/10/0/0. To list device file names in the /dev directory and its subdirectories. then you would have only a single ATDD_HWPATH entry. make sure all devices CLAIMED with the preceding command are devices you want this device driver to manage. Note: If you experience difficulties with your tape device. 1. Enter ″Y″ to allow the ATDD to configure all attached IBM Medium Changer devices. It copies the latest version of the driver to the software depot and installs the latest driver version.HP-UX Device Driver (ATDD) Install the Driver Using the ATDD Installation Script An installation script (InstallAtdd) is provided to automate driver installation and perform some checking functions. then run the install script. uninstall it before attempting to install the latest version. the ATDD software is configured automatically upon installation. Refer to “Uninstalling the software” on page 64. uninstall it before attempting to install the latest version.x atdd (preview option) # swcopy -s /driver_location/atdd.x.x.x. 2. Refer to “Uninstalling the software” on page 64. then the ATDD software is not configured automatically.x atdd Use swlist to verify 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 drives are powered on.” Install Drivers Manually Installing the drivers manually requires the steps detailed in the following sections. 3.x.x. 60 IBM Tape Device Drivers Installation and User’s Guide . For example: # swcopy -p -s /driver_location/atdd. or answer ″N″ to allow the HP native changer driver to configure these Medium Changer devices. the customer is prompted with the question. Copy the Software to the Software Depot: Attention: If you do not copy the ATDD software into a depot. the ATDD software can be installed to the root file system using the HP-UX swinstall command. “Install the ATDD Software” on page 60. The system reboot is required to install ATDD in HP-UX 11i v3. download the install script from the ftp site. If the target root file system is the primary. To install ATDD with the script. To install ATDD manually. Copy the appropriate driver to the Software Depot. If a previous version of ATDD is installed on your system. follow the steps in “Install Drivers Manually. 2.x. If the target is an alternate root file system. Notes: 1. If a previous version of ATDD is installed on your system. “Copy the Software to the Software Depot” on page 60. ″Would you like to activate the Medium Changer support by ATDD (Y/N)?″. you will not be able to uninstall the product readily. When the installation script runs. run the ioscan command to list the tape drives found: # ioscan -fknC tape Class I H/W Path Driver S/W State H/W Type Description ============================================================================================ tape 0 0/3/0/0.1 acdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/2chng autoch 4 0/5/0/0.0 atdd CLAIMED DEVICE IBM 03590B11 /dev/rmt/1m /dev/rmt/1mn /dev/rmt/c4t6d0BEST /dev/rmt/c4t6d0BESTn /dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c4t6d0BESTb /dev/rmt/c4t6d0BESTnb tape 4 0/5/0/0. 11i v1.23.0. Run #ioscan -funC tape or autoch to show the tape devices bound with the legacy atdd_leg and acdd_leg drivers. run the following ioscan command to view the medium changers found: # ioscan -fnkC autoch Class I H/W Path Driver S/W State H/W Type Description ======================================================================= autoch 0 0/3/0/0.232. This is true even if the version already installed is more recent than the version being installed.232. Chapter 4. Enter ″Y″ to allow the ATDD to configure all attached IBM Medium Changer devices.23.0. or answer ″N″ to allow the HP native changer driver to configure these Medium Changer devices.1.2 atdd CLAIMED DEVICE IBM ULT3580-TD1 /dev/rmt/4m /dev/rmt/4mn /dev/rmt/c6t0d2BEST /dev/rmt/c6t0d2BESTn /dev/rmt/4mb /dev/rmt/4mnb /dev/rmt/c6t0d2BESTb /dev/rmt/c6t0d2BES If you have enabled ACDD.0. the existing version is replaced. HP-UX Tape and Medium Changer Device Driver 61 . You can use swlist to list the software installed on the default root file system as follows: # swlist atdd You can verify correct installation to the default root file system with the swverify command as follows: # swverify atdd After the installation is completed. 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 (preview option) # swinstall -x ask=true atdd in HP-UX 11.1 acdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/0chng autoch 2 0/6/0/0. ″Would you like to activate the Medium Changer support by ATDD (Y/N)?″. and v2 # swinstall -x autoreboot=true -x ask=true atdd in HP-UX 11i v3 Running the swinstall command with the ask option set to TRUE prompts the customer.5.10.0.5.0.0 atdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/0m /dev/rmt/0mn /dev/rmt/c4t5d0BEST /dev/rmt/c4t5d0BESTn /dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c4t5d0BESTb /dev/rmt/c4t5d0BESTnb tape 1 0/3/0/0.6.255.1.1.HP-UX Device Driver (ATDD) Note: If an earlier version of the product is already installed on the target root file system. run # ioscan -funNC tape or autoch to display the tape devices configured with ATDD and ACDD drivers.17.1 acdd CLAIMED DEVICE IBM ULT3583-TL /dev/rmt/4chng In HP-UX 11i v3.5. 5. run the command: # /opt/atdd/bin/atdd_claim -u v In HP-UX 11i v3. 1.0.d/atdd. To determine the HW path: # ioscan -fnk|grep IBM autoch 0 0/3/0/0.d/atdd: v For tape drives: /opt/atdd/bin/atdd_claim -t v For medium changers: /opt/atdd/bin/atdd_claim -c 3. ATDD automatically configures all supported IBM tape drives that are attached and powered on when the ATDD package is installed. The ACDD driver does not configure IBM Medium Changer devices by default. edit the ″Claiming Device″ section in the file of /sbin/init. Reboot the system to unconfigure the changer devices: # shutdown -ry now Configure Selected IBM Tape Devices with ATDD/ACDD in HP-UX 11.HP-UX Device Driver (ATDD) Configure all IBM Tape Drives/Media Changers with ATDD/ACDD: By default.0. 11i v1 and v2: Attaching Selected IBM Tape Devices to ATDD/ACDD During Auto Booting: To claim a specific tape device with atdd/acdd during reboot. 11i v1 and v2. Add a command line in the ″Configuring Device″ section in /sbin/init.1 schgr CLAIMED DEVICE IBM 03590E11 2.5. For example. To configure all IBM Medium Changer devices 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 devices. run the command: # /opt/atdd/bin/atdd_claim -c v In HP-UX 11i v3. To determine the HW path of the device: 62 IBM Tape Device Drivers Installation and User’s Guide . To configure all IBM Medium Changer devices on the system after the install of the ATDD package: v In HP-UX 11. Bind each changer device with the ACDD driver: # ioscan -b -M acdd -H hw_path 2. 11i v1 and v2. Reboot the system to configure the changer devices: # shutdown -ry now To remove the claim with ACDD after the next reboot: v In HP-UX 11. Bind each changer device with a changer driver: # ioscan -b -M acdd -H hw_path 2. do the following: 1. Comment out the command line(s) in the init script of /sbin/init.d/atdd: /opt/atdd/bin/atdd_claim -H 0/3/0/0. to attach IBM 3590E11 medium changer with acdd driver: 1.1 Attaching Selected IBM Tape Devices to ATDD/ACDD Dynamically: To dynamically attach selected IBM tape device after the ATDD installation.0. do the following: 1. run the following commands. and then reboot the system. For example.1 Note: The dynamic attachment may be lost after the system reboots. All of IBM medium changers are claimed if you use acdd and acdd_leg as the changer drivers during ATDD are installed.30. Reboot the system: Chapter 4.1 insf -H 0/3/0/0.5.1 # rmsf -H 0/3/0/0.1 schgr CLAIMED DEVICE IBM 03590E11 2.d/atdd file. # Configuring Device Section: # add specific device claim here. Create the device special files: # insf -H 0/3/0/0.0 autoch 0 0/3/0/0.5. perform these steps: 1.5. run the system ioscan command to force a non-ATDD/ACDD driver to bind an IBM tape device. To attach a selected IBM tape device with a particular driver. atdd driver automatically configures all supported IBM tape drives that are attached and powered on when the ATDD package is installed. Attaching Selected IBM Tape Device with a Particular Driver: Use the system ioscan and rmsf commands to force a non-atdd/acdd driver to bind an IBM tape device.5. To keep the binding to a selected device with a particular driver after a reboot.5.1. The acdd driver does not configure IBM medium changer devices by default. force bind the IBM 3590E media changer with the HP native changer driver schgr with these steps: 1. Verify the force binding: # ioscan -fnk |grep IBM tape 0 0/3/0/0.HP-UX Device Driver (ATDD) # ioscan -fnk|grep IBM autoch 0 0/3/0/0.5. for example # /opt/atdd/bin/atdd_claim -H 0/3/0/0. HP-UX Tape and Medium Changer Device Driver 63 .1 4.5.5.1 atdd schgr CLAIMED CLAIMED DEVICE DEVICE IBM IBM 03590E11 03590E11 Note: The force binding is lost after the system reboots.5. Determine the HW path of the device: # ioscan -fnk |grep IBM tape 0 0/3/0/0. add these command-lines in steps 2–4 in ″Claiming Device″ section in /sbin/init.5.1 atdd acdd CLAIMED CLAIMED DEVICE DEVICE IBM IBM 03590E11 03590E11 2.1 rmsf -H 0/3/0/0.5.1 ioscan -M schgr -H 0/3/0/0.0 autoch 0 0/3/0/0.0.1 # /opt/atdd/bin/atdd_claim -H 0/6/0/0.1 5. For example. To claim the device with ATDD/ACDD: # /opt/atdd/bin/atdd_claim -H 0/3/0/0.0. Force binding: # ioscan -M schgr -H 0/3/0/0.5.5.255.1 Configure Selected IBM Tape Devices with ATDD/ACDD in HP-UX 11i v3: By default. For example. Determine the HW path of the device: # ioscan -fNk | grep IBM tape 1 64000/0xfa00/0x7 atdd CLAIMED DEVICE IBM 03592E05 2. to force bind the IBM 3592E05 tape drive with the HP native tape driver estape. Force the binding: # ioscan -b -M estape -H 64000/0xfa00/0x7 3. Remove the I/O configuration from the system: 3. Preinstallation Considerations Make sure your system is ready to install ATDD before you begin. run kmadmin. Create the device special files if it does not exist after the system bootup: # insf -H 64000/0xfa00/0x7 5.0 To view the fileset of ATDD installed on the system: # swlist -l file atdd To display and manage ATDD kernel modules and kernel-tunable parameters. To uninstall ATDD (from the root file system): # swremove atdd in HP-UX 11. kctune commands in HP-UX 11i v2 and v3. Verify the force binding: # ioscan -fNk | grep IBM tape 1 64000/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. and uninstall the IBM Tape and Medium Changer Device Driver for HP-UX (ATDD) for HP Precision Bus (HP-PB) systems.HP-UX Device Driver (ATDD) # shutdown -ry now 4.0. kmsystem. 64 IBM Tape Device Drivers Installation and User’s Guide . kmtute and kmadmin commands in HP-UX 11. For example: # swremove -d atdd.5. print out the ATDD driver module status entering the command: # kcmodule -d atdd Module State Cause atdd static explicit Description Advanced Tape Device Driver Installation and Configuration of Precision Bus Drivers This chapter describes how to install. configure. 11i v1 and v2 # swremove -x autoreboot=true atdd in HP-UX 11i v3 Other Administrative Tasks: To determine whether the current version of ATDD is installed or configured on the default root file system: # swlist -a state atdd To determine the versions of ATDD stored in the default depot: # swlist -d atdd To remove ATDD from the depot: # swremove -d atdd If more than one level of ATDD exists in the depot. Follow these steps to perform the install: 1. Copy the software from the distribution medium to the depot. Refer to the system manual for more detail.r=3. It is best to use the swremove command. For an example. explicitly specify the level to remove it. or go to the “Kernel Configuration” in sam utility.0.0 and 11i v1 and kcmodule. 3. v No spaces can appear within each entry. Ensure that the tape drives to be managed by ATDD are powered on. It is a good idea to observe carefully the results of the installation process as it occurs. Create the Configuration File A configuration file must be created that tells the device driver how to customize your configuration. The file is named etc/rc. Install and configure the software. 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. Note the following facts about the command sequences described in this section: v In some of the examples. swinstall or swcopy) can first be run with the -p flag to preview the command. the command finishes with a warning indicating that no attempt is made to mount all file systems. If you encounter unexpected results during the installation. v The software distributor commands are moderately complex scripts that frequently require several steps. Determine the Device Hardware Path for Enterprise Tape System 3590: To determine the device hardware path. swinstall and swremove) attempt to mount all file systems in the /etc/fstab file at the start of the analysis phase.d/atdd. This ensures that all listed file systems are mounted before proceeding. While using the software distributor commands. follow these steps: Chapter 4. When this option is used. The steps are typically Selection. This error can be overridden using ’-x’ to set the mount_all_filesystems option to FALSE. Check the README file and verify that your system is configured appropriately for installing ATDD. check the associated log file. but it often causes an error with NFS mounted file systems. 4. Analysis.cfg and has the following syntax: ATDD_global_parameter=value ATDD_device_parameter[index]=value Note: v Blank lines and lines that start with # are ignored. Each step may produce useful information and error messages. you can reissue the command without the -p flag to perform the actual operation. This also helps ensure that files are not loaded into a directory that may be below a future mount point. Using ’pwd’/filename to reference a file instead of filename ensures this. and Execution. v No trailing comments can appear on a variable definition line. Many commands (for example.HP-UX Device Driver (ATDD) 2. v All the software distributor commands (for example. HP-UX Tape and Medium Changer Device Driver 65 . filenames given on the command-line must be referenced with an absolute path.config. After observing the preview output. 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. the device hardware paths are: 56/40. C11.3. HWPATH = adapterpath.3. To control the operation of the library mechanism. Run ioscan to determine which SCSI adapter the Magstar MP library drive is connected to. C02. The hardware path definitions present in the atdd. C02.drivetargetaddress. a definition for LUN 1 for each drive must be present in the atdd. Models B02. B12. The panel on the front of the Magstar MP library displays the selected target addresses. In this case.0 (3590 one LUN mode) or HWPATH = adapterpath.drivetargetaddress. Record the hardware path entry of the adapter: for example. Base configuration is intended for attachment of one or two drive libraries on a single SCSI bus. the device hardware paths are: 66 IBM Tape Device Drivers Installation and User’s Guide . C01.1 (3590 random 2 LUN mode) For a 3590 at SCSI target address 3 in random 2 LUN mode. Determine the SCSI target address of the 3590 drive.1 Determine the Device Hardware Path for Magstar MP 3570 Tape Subsystem: The Magstar MP 3570 product family consists of stand alone tape drives (Models B00 and C00) and library models with one or two tape drives.drivetargetaddress.0 (Magstar MP drive) HWPATH = adapterpath. 56/40 3. Run ioscan to determine which SCSI adapter the 3590 drive is connected to.cfg file must include a definition for drive 1 LUN 1 for operation of the library mechanism.drivetargetaddress. and C12 can operate in a split configuration where each drive and a subset of the cartridge slots are viewed as an independent library.HP-UX Device Driver (ATDD) 1. SCSI Medium Changer commands are issued to LUN 1 of one or both of the drive ports depending on the library configuration. Models B01.0 56/40. B12. random access cartridge loader and are known as library units. To determine the device hardware path.1 (Magstar MP library changer) For a Magstar MP library with a single drive at target address 3 in base configuration. follow these steps: 1. # ioscan -f -C ext_bus 2. Typically.drivetargetaddress. The panel on the front of the 3590 drive displays the selected target address. Determine the SCSI target addresses of the Magstar MP drives. independent SCSI buses are used for operation of each logical library. Control of the library is accomplished by sending Medium Changer commands to LUN 1 of drive 1 (the drive on the left as viewed from the rear of the library). # ioscan -f -C ext_bus 2. B11. HWPATH = adapterpath.cfg file to control each logical library independently.0 HWPATH = adapterpath. B02. and C12 support a 20 cartridge. Record the hardware path entry of the adapter: for example. 56/40 3. The 3575 deviates from the SCSI-3 specification in that device and element reservations issued on one port apply only to those hosts that access that port.0 56/40.1 (3575 library control path) For a 3575 library with two drives in one logical library (drive 1 at SCSI target 3 and drive 2 at SCSI target 4).0 56/40.4. LUN 1 for the first drive in each logical library is mandatory and is enabled automatically by the library firmware. The panel on the front of the 3575 library displays the selected target addresses. the automation conforms to the SCSI-3 Primary Commands standard for multiple port behavior (except for the handling of reservations).drivetargetaddress1.0 (Magstar MP drive) HWPATH = adapterpath. HWPATH = adapterpath. first-served basis for hosts accessing the same logical library on different ports. Run ioscan to determine which SCSI adapter the Magstar MP library drive is connected to. Access to a logical library is on a first-come.1 Determine the Device Hardware Path for Magstar MP 3575 Tape Libraries: Each drive 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 drive port. LUN 1 could be configured for two drives in the same logical library.3. HP-UX Tape and Medium Changer Device Driver 67 . In that case. drive 3 for logical library 2.3.3.drivetargetaddress1. Each port can accept commands while the library is in use by another host by way of another port. # ioscan -f -C ext_bus 2.cfg file. and L32) can support two or three logical libraries depending on the specific model. and drive 5 for logical library 3). Target device LUN 1 also needs to be enabled at the library operator panel for drives other than the first drive in each logical library if they are used to accept automation commands. The 3575 Model L06 supports one logical library. L24. but this is unnecessary in most instances. To determine the device hardware path.1 Chapter 4. The other 3575 tape libraries (Models L12. Determine the SCSI target addresses of the Magstar MP drives.drivetargetaddress2. Other drives may have LUN 1 configured. Special files for operation of the 3575 automation are based on the hardware path definitions present in the atdd.0 56/40. the device hardware paths are: 56/40. LUN 1 control of the library mechanism can be configured for any drive by way of the front panel on the library. Record the hardware path entry of the adapter: For example.0 (Magstar MP drive) HWPATH = adapterpath. Conceivably.HP-UX Device Driver (ATDD) 56/40. but this is optional. The first drive in each logical library must have LUN 1 configured to operate the automation for that logical library (drive 1 for logical library 1. Initiators connected to the same logical library through an alternate port are not subject to those reservations. 56/40 3.3. L18. follow these steps: 1. For example.drivetargetaddress.0.0 (drive 1) HWPATH=adapterpath. 3. IBM Ultrium Tape Libraries with Fibre Channel Attachment: To determine the hardware path for the 3580 tape drive and the 3582.HP-UX Device Driver (ATDD) Determine the Drive Hardware Path for IBM 3580 Ultrium Tape Drive. follow this procedure: 1.0. for example. Record the hardware path entry of the adapter.2 0/8/0/0.3.0 1/8/0/0. HWPATH=adapterpath.0 Determine the Drive Hardware Paths for IBM 3580 Ultrium Tape Drive. and 3584 Tape Libraries with SCSI attachment.drivetargetaddress.0.5. and 3584 tape library with fibre channel attachment. 0/5/0/0.drivetargetaddress.0 (drive n) The drive hardware paths for an IBM Ultrium 3583 Tape Library with a drive at SCSI ID 3 and SCSI ID 5 are: 1/8/0/0.3. Determine the SCSI target addresses of the IBM Ultrium drives in the Tape Library. 0/4/0/0. The switch on the rear of the IBM 3580 Ultrium Tape Drive displays the selected SCSI target address.8.255.0. Run ioscan to determine which hardware path the IBM Ultrium drive is connected to: # ioscan -f -C tape 2.0.0 (3580 drive) or HWPATH=adapterpath.7.0. Record the hardware path entry of the IBM Ultrium Fibre Channel drive. HWPATH=adapterpath. follow this procedure: 1.0 0/8/0/0. 3583.8. Record the hardware path entry of the adapter. 3581 Tape Autoloader with SCSI Attachment: To determine the hardware path for the 3580 Tape Drive and the 3581 Tape Autoloader with SCSI attachment.drivetargetaddress.8. the drive device hardware path is: 0/4/0/0.0. Run ioscan to determine which SCSI adapter the IBM Ultrium drive or autoloader is connected to: # ioscan -f -C ext_bus 2. The LCD panel on the front of the unit can display the drive (and medium changer SCSI address) for the IBM 3581 Ultrium Tape Autoloader.3 (3580 stand alone tape drive) (3583 drive 1) (3583 drive 2) 68 IBM Tape Device Drivers Installation and User’s Guide . follow this procedure: 1. 3583.0. The LCD panel on the front of the unit can display the drive (and medium changer) SCSI addresses.0 Determine the Drive Hardware Paths for IBM Ultrium Tape Libraries with SCSI Attachment: To determine the hardware path for the 3582.9.0. Run ioscan to determine which SCSI adapter the IBM Ultrium Tape Library is connected to: # ioscan -f -C ext_bus 2. for example: 1/8/0/0 3. Determine the SCSI target address of the IBM Ultrium drive (3580) or the drive in the IBM 3581 Ultrium Tape Autoloader.0 (3581 drive) For an IBM 3581 Ultrium Tape Autoloader at SCSI target address 3. HP-UX Device Driver (ATDD) Create the Hardware Path Entry for Ultrium Tape Drives: If devices are to be configured with settings other than the defaults. has index=0.0. three ATDD_HWPATH entries are required in the configuration file. Each device may have a different value for each configuration variable. LUN 0.0.d/atdd configuration file.2 (3583 SCSI drive 1 with SDG) ATDD_HWPATH[5]=0/8/0/0. The index number associated with the configuration variable associates the parameter setting with the device at the hardware path with the same index.config. then you would have only a single ATDD_HWPATH entry. The third device.1.0 (3580 stand alone SCSI drive) ATDD_HWPATH[1]=1/10/0/0.0 (based on the hardware path entry in “Create the Hardware Path Entry” on page 69).8.d/atdd. Create an entry for each device that requires further configuration settings. For 3590 devices configured in random 2 LUN mode.0 ATDD_HWPATH[1]=56/40.7. To change these settings. HP-UX Tape and Medium Changer Device Driver 69 .0. two hardware path entries are required.0. LUN 0. For example ATDD_HWPATH[0]=56/40.cfg configuration file for each device you want the driver to attach. At least one hardware path entry is required in the configuration file.6. 3581 with two 3580 SCSI Tape Drives inside at SCSI target addresses 5 and 6. The index is used to identify the device for control of the configuration settings in the next section.1. One is needed for the drive (LUN 0). Create the Device Specific Configuration Entries (Optional): The ATDD is shipped with default settings for all configuration parameters.255. Create the Hardware Path Entry: You must tell the driver which hardware path you want to attach to.5.0 (3580 stand alone FC drive) ATDD_HWPATH[4]=0/8/0/0.0.0 (3581 SCSI drive 2) ATDD_HWPATH[3]=0/5/0/0. has index=3. The second device. an entry is made in the configuration file assigning an appropriate value to the desired configuration variable.6.9. If you have three tape devices attached. and one is needed for the ACF (LUN 1).0.3 (3583 SCSI drive 2 with SDG) This example shows that four devices are CLAIMED by the ATDD.config. Example 2: Chapter 4. 3580 Stand Alone FC Tape Drive at target 9. The format for the entries is HW_PATH[index]=DeviceHardwarePath.0 (3581 SCSI drive 1) ATDD_HWPATH[2]=1/10/0/0. entries defining the hardware device paths must be placed in the /etc/rc. Create an entry in the /etc/rc. has index=1 and 2 . The last one is 3583 with SAN Data Gateway (SDG) Module and two 3580 SCSI Tape Drives at target 0. LUN 2 and 3 (index=4 and 5). Example 1: ATDD_IMMEDIATE[0]=1 This allows application control back from the device before rewind is complete for the device at hardware path 56 / 40.0. If you have a single 3590 device operating in one LUN mode. The first device.0.0.0. 3580 Stand Alone SCSI Tape Drive at SCSI target address 1. LUN 0.1. For example: ATDD_HWPATH[0]=0/4/0/0.0 Note: This example shows that two devices are CLAIMED by ATDD.8. x. make sure all devices that report CLAIMED with the preceding command are devices you want this device driver to manage. Copy the Software to the Software Depot Attention: If you do not copy the ATDD software into a depot.x. or answer "N" to allow the HP native changer driver to configure these Medium Changer devices.x atdd (preview option) # swcopy -s /driver_location/atdd. It copies the latest version of the driver to the software depot and installs the latest driver version. To install ATDD manually. Power Off the Tape Drives When the ATDD software is initially installed . "would you like to activate the Medium Changer support by ATDD (Y/N)?" Enter "Y" to allow the ATDD to configure all attached IBM Medium Changer devices. then run the install script. Note: If you experience difficulties with your tape device. follow the steps in “Install Drivers Manually” on page 60.log for errors and correct the problem. Refer to Table 9 on page 74 and Table 10 on page 75 for a description of all configuration parameters. Note: If a previous version of ATDD is installed on your system.0.6. uninstall it before attempting to install the latest version. power Off the tape drive and run ioscan without the ’-k’ argument as follows: # ioscan -f -C tape Install the Drive Using the ATDD Installation Script An installation script (Install Atdd) is provided to automate driver installation and perform some checking functions. # swcopy -p -s /driver_location/atdd. check the /etc/rc. it attaches itself to all tape drives that are in the CLAIMED state as shown by entering the command: # ioscan -fk -C tape Before you continue. you will not be able to uninstall the product readily. To install ATDD with the script.x atdd 70 IBM Tape Device Drivers Installation and User’s Guide . To list device file names in the /dev directory and its subdirectories.x. download the install script from the ftp site. When the installation script runs.x.x.HP-UX Device Driver (ATDD) ATDD_TRAILER[1]=1 This allows write operations after an early end-of-tape warning for the device at hardware path 56 / 40. enter: # ioscan -funC tape To remove a tape drive from the CLAIMED state so it is not be configured by this driver.x. the customer is prompted with the question. including required system software patches and required tape related firmware versions. Configuration requires restarting the system and rebuilding the kernel. reissue the swinstall command with the autoreboot option set as follows: # swinstall -p -x autoreboot=true atdd (preview 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 verify correct installation to the default root file system with the swverify command as follows: # swverify atdd Chapter 4. The file also documents any changes in the installation. If the target is an alternate root file system. This is true even if the version already installed is more recent than the version being installed. use the swlist command to view the README file under the directory /opt/OMImag/Readme. Note: If an earlier version of the product is already installed on the target root file system. This requires you to issue the swinstall command with the -x autoreboot option set to TRUE. the ATDD software is not configured automatically. It is therefore very important that you review it before proceeding with the software installation. HP-UX Tape and Medium Changer Device Driver 71 .HP-UX Device Driver (ATDD) Use swlist to verify that the ATDD software is in the depot: # swlist -d atdd Review the ATDD README File After copying the ATDD software to the depot. If the target root file system is the primary. and administration of the software that occurred after this documentation was completed. Install the ATDD Software When the software is in the depot and only the appropriate drives are powered on. the ATDD software can be installed to the root file system using the HP-UX swinstall command. The following commands install ATDD from the depot to the default root file system: # swinstall -p atdd (preview option) # swinstall atdd If you get an error message stating that this product needs to restart the system. the existing version is replaced. the ATDD software is configured automatically upon installation. use. # swlist -d -a readme atdd The README file lists the system configuration requirements. as described below. Modify the /stand/system file. adding a stanza in the form of: driver 56/48. To create the special files.1.3.5.0 Where: # denotes the next instance and the adapter/drive path for your device.config. run the ioscan command to list the tape drives found: # ioscan -fknC tape Class I H/W Path Driver S/W State H/W Type Description ============================================================================================ tape 0 0/3/0/0. 3.0.HP-UX Device Driver (ATDD) After the installation is completed. Restart the system: # shutdown -ry now or # reboot 5. adding the hardware path and instance: ATDD_HWPATH[#]=56/48.3.232. This manual process requires having the right 72 IBM Tape Device Drivers Installation and User’s Guide . run the following ioscan command to view the medium changers found: # ioscan -fnkC autoch Class I H/W Path Driver S/W State H/W Type Description ======================================================================= autoch 0 0/3/0/0.2 atdd CLAIMED DEVICE IBM ULT3580-TD1 /dev/rmt/4m /dev/rmt/4mn /dev/rmt/c6t0d2BEST /dev/rmt/c6t0d2BESTn /dev/rmt/4mb /dev/rmt/4mnb /dev/rmt/c6t0d2BESTb /dev/rmt/c6t0d2BESTnb If you have enabled ACDD.d/atdd.1 acdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/2chng autoch 4 0/5/0/0. the spt for the other ext_bus). This command echoes to console but does NOT create special files.255. Build the kernel as root: # mk_kernel -o /stand/vmunix -s/stand/system 4.1 acdd CLAIMED DEVICE IBM ULT3583-TL /dev/rmt/4chng Adding an IBM Tape Device Using the Currently Installed ATDD To add an IBM tape device using the currently installed ATDD.cfg.0 atdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/0m /dev/rmt/0mn /dev/rmt/c4t5d0BEST /dev/rmt/c4t5d0BESTn /dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c4t5d0BESTb /dev/rmt/c4t5d0BESTnb tape 1 0/3/0/0.10.0.1 acdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/0chng autoch 2 0/6/0/0.5.1.0. 2.23.0 atdd with the adapter/drive path for your device.232.6. After the system is up.1.23.5.17.0 atdd CLAIMED DEVICE IBM 03590B11 /dev/rmt/1m /dev/rmt/1mn /dev/rmt/c4t6d0BEST /dev/rmt/c4t6d0BESTn /dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c4t6d0BESTb /dev/rmt/c4t6d0BESTnb tape 4 0/5/0/0. run /opt/OMImag/bin/atdd_mksf to create the new special files for the device.0. Modify /etc/rc. atdd_mksf -ti <instance> Where: <instance> is the number from the ioscan output for the newly installed device. pipe the command to sh as follows: # atdd_mksf -ti <instance> | sh Note: A manual process is required for applications using the HP native spt or sctl drivers as a changer driver (the sctl driver for the ext_bus C700 or C720. perform the following steps: 1. Other Administrative Tasks To determine the versions of ATDD currently installed on the default root file system: # swlist -a state atdd To determine the versions of ATDD stored in the default depot: # swlist -d state atdd To view the set of files that is installed with ATDD: # swlist -l file atdd To remove ATDD from the depot: # swremove -d atdd If more than one level of ATDD exists in the depot. For program usage. explicitly specify the level to remove it. Chapter 4. possibly a binding statement in the kernel. use the atdd_cfg program located in /opt/OMImag/bin for the static PB driver and in /opt/atdd/bin for the PCI driver. Table 9 on page 74 shows the parameters that are device-specific.HP-UX Device Driver (ATDD) driver in the kernel. Related man pages are scsi_ctl (7) and scsi_pt (7). To check your current configuration. If you are experiencing difficulties. it is necessary to use configuration values that perform reliably on all devices attached to your system. The configuration parameters are global. The ATDD is shipped with default values that allow the most reliable execution across various device types. Modifying the default settings is not recommended unless instructed to do so. execute as follows: For PB driver: # /opt/OMImag/bin/atdd_cfg -h For PCI driver: # /opt/atdd/bin/atdd_cfg -h Configuration Parameter Definitions This section describes the configuration parameters and values. and making a device file. ensure that your driver is configured properly.9. Because the configuration parameters are global to all devices.0 Supported Configuration Parameters This chapter describes the supported configuration values for multiple device types being configured on the same system.0. HP-UX Tape and Medium Changer Device Driver 73 . For example: # swremove -d atdd. and their values. while others are driver-specific. what they mean. Device-Specific Parameters Some of the configuration parameters are device-specific.r=4. by default) v 1=Narrow (8 bit wide data transfers) DISABLE_COPYIN_THRESHOLD (Precision Bus Driver only) Protect against nonaligned buffers v 0=Off (check buffers for alignment. by default) v 0=Off (do not reserve the device after to open) (multiple open support) WFM_IMMEDIATE Immediate Mode for Write File Mark v 0=Off (wait for write file mark completion. Size in bytes. 28 by default. by earlier. Supported in HP-UX 11i default) v3 only.HP-UX Device Driver (ATDD) Table 9. by default) v 1=On (return before rewind is complete) TRAILER Trailer Label Processing v 0=Off (do not allow writes past early EOT warning. by default) v 1=On (use buffers without checking alignment) COPY_THRESHOLD (Precision Bus Minimum buffer size to start Driver only) checking for proper alignment BLOCKSIZE COMPRESSION Block Size Compression Mode Size in bytes to force alignment check. by default) BUFFERING Buffering Mode v 0=Off (do not buffer data) v 1=On (buffer data to hardware buffers. v 0=Off (do not use compression at drive) v 1=On (use compression at drive. v 1=On (reserve the device after to open. by default) v 1=On (suppress) v 0=Wide (16 bit wide data transfers. 0 by default. by default) v 1=On (return before write file mark is complete) PRE_V3_COMPAT Use to share tapes with blocksize v 0=Off (always write or read the date > 256kb with HP-UX 11i v2 or using the blocksize defined by user. 0 by default. v 1=On (split the blocksize less than 256 kb during the read or write) FORCE_NARROW (Precision Bus Driver only) 74 IBM Tape Device Drivers Installation and User’s Guide . by default) IMMEDIATE Immediate Mode v 0=Off (wait for rewind completion. by default) v 1=On (allow writes past early EOT warning) ERRNO_LEOT RESERVE Error Number return for Logical End Of Tape) Multiple open for the device Value returned for writes past EOM. Device-Specific Parameter Definitions Parameter DENSITY SILI Meaning Density to use when writing/reading tape Suppress Incorrect Length Indicator Width at which the driver negotiates for data transfers Values In hexadecimal v 0=Off (do not suppress. 11i v1 and v2: For example.HP-UX Device Driver (ATDD) Driver-Specific Parameters Some of the configuration parameters are device-specific. run #atdd_cfg -d special_file -o parameter For example. You must use this INSTANCE value (1) to set the COMPRESSION value for this device.1.0 INSTANCE: 2 The ATDD instance number for this device is returned. what they mean. do the following: # atdd_cfg -g INSTANCE 0/4/0/0.1.0 # atdd_cfg -s COMPRESSION 0 0/4/0/0. Table 10 shows the parameters that are driver-specific.0 v In HP-UX 11i v3: The usage of atdd_cfg command is: atdd_cfg -d special_file [-o parameter [-w value]] All configurable parameters for the specified device are displayed by entering #atdd_cfg -d special_file only For instance: # /opt/atdd/bin/atdd_cfg -d /dev/rtape/tape14_BEST DENSITY=0 SILI=1 BLOCKSIZE=0 COMPRESSION=1 BUFFERING=1 REWIND_IMMEDIATE=0 TRAILER=1 SCALING=0 WRITEPROTECT=0 ERRNO_LEOT=28 WFM_IMMEDIATE=0 RESERVE=1 PRE_V3_COMPAT=0 To display a specific parameter.0. Chapter 4. HP-UX Tape and Medium Changer Device Driver 75 . if you want to change the COMPRESSION parameter to 0 for the device at hardware path 0/4/0/0. and their values. You can update the current value. # atdd_cfg -s COMPRESSION 0 2 Or. while others are driver-specific. use the atdd_cfg program located in /opt/OMImag/bin for the PB driver and in /opt/atdd/bin for the PCI driver. Driver-Specific Parameters (Global) Parameter INSTANCE DEVICES MINPHYS (Precision Bus Driver only) Meaning ATDD Device Number Number of Configured Devices Check/Adjust Transfer Count Values (Read Only) (Read Only) v 0=Use OMI minphys v 1=Use HP-UX minphys Modifying Configuration Parameters To change a configuration parameter. Table 10. v In HP-UX 11. to get or modify COMPRESSION by using the hardware path: # atdd_cfg -g COMPRESSION 0/4/0/0.0.1.1. Special Files For each drive configured by ATDD.d. Accumulate. Automatic.config. To change the value of tunable. you must modify or add an entry in the atdd. add the following line to your configuration file: v In HP-UX 11. For additional instructions about using the configuration program. This parameter is enabled by default on 11i v3 and later. 76 IBM Tape Device Drivers Installation and User’s Guide .cfg configuration file located in /etc/rc. use the -h option as follows: # atdd_cfg -h Configurable Kernel Parameters (Tunable) ATDD provides the following variety of configurable kernel parameters that allow the users to customize for specific setup: v atdd_log_trace Log the sense data in syslog when a hardware or medium error is occurred. run #atdd_cfg -d special_file -o parameter -w value For example. For example. twelve or thirteen special files are created: twelve special files are generated for a 3590 with ACF set to Manual. v alternate_pathing/atdd_alternate_pathing Enable or disable the alternate path support for CPF/DPF (see the specific operating system section that covers CPF and DPF support for detail).HP-UX Device Driver (ATDD) #/opt/atdd/bin/atdd_cfg -d /dev/tape/tape14_BESTn -o COMPRESSION COMPRESSION=1 To set a specific parameter. v atdd_disable_reserve/atdd_disable_res Allows the user to disable the reservation management from ATDD. # atdd_cfg -d /dev/rtape/tape14_BESTn -o Success COMPRESSION -w 0 To set a new BOOT default value for the configuration parameter. see “Sense Data Logging” on page 84 for additional details. Random. System. but disabled by default in 11iv3 and earlier. if you want the COMPRESSION default set to 0 for the device at ATDD_HWPATH[0] or tape14_BESTn. run the command kctune/kmtune or SAM (System Administration Manager) tool. A thirteenth special file is created for independent operation of the ACF. or Library mode. This parameter is enabled by default. This parameter off by default. if the 3590 mode is set to Random 2 LUN operation (/dev/rmt/<instance#>chng). 11i v1 and v2: ATDD_COMPRESSION[0]=0 v In HP-UX 11i v3: /opt/atdd/bin/atdd_cfg -d /dev/rtape/tape14_BESTn -o COMPRESSION -w 0 Note: The configuration parameters are prefixed with ATDD_ in the configuration file.0.d for the static driver or the atdd configuration file located in /sbin/init. For example. Table 11. Each set of special file names (long and short) contains four special files that have all combinations of n and b options. New Special Files in HP-UX 11i v3 Special File Name /dev/rtape/tape#_BEST /dev/rtape/tape#_BESTb /dev/rtape/tape#_BESTn /dev/rtape/tape#_BESTnb /dev/rchgr/autoch# BSD Compatibility No Yes No Yes N/A Rewind on Close Yes Yes No No N/A BSD Compatibility No Yes No Yes No Yes No Yes No Yes No Yes N/A Rewind on Close Yes Yes No No Yes Yes No No Yes Yes No No N/A v In HP-UX 11. refer to the mt(7) man pages. including the highest density/format and data compression. HP-UX Tape and Medium Changer Device Driver 77 . BEST represents the operational capabilities likely to be required. To display special file information. if supported by the device. Best Format. and an alternative short file name not based on the instance number. enter the lssf command. insf and rmsf commands. Berkeley. For more information. as shown in Table 11 and Table 12. Special Files Special File Name /dev/rmt/<instance#>m /dev/rmt/<instance#>mb /dev/rmt/<instance#>mn /dev/rmt/<instance#>mnb /dev/rmt/s<#>m /dev/rmt/s<#>mb /dev/rmt/s<#>mn /dev/rmt/s<#>mnb /dev/rmt/<instance#>t<target>d<LUN>BEST /dev/rmt/<instance#>t<target>d<LUN>BESTb /dev/rmt/<instance#>t<target>d<LUN>BESTn /dev/rmt/<instance#>t<target>d<LUN>BESTnb /dev/rmt/<instance#>chng Table 12. an alternative short file name based on the instance number. 11i v1 and v2: atdd_lssf in /opt/OMImag/bin for the static driver and in /opt/atdd/bin for the DLKM driver lists information about a special file.0. For example: #atdd_lssf /dev/rmt/393mnb atdd card instance 30 available at address Major = 79 settings = No Rewind.HP-UX Device Driver (ATDD) ATDD creates the tape device special files in three forms: the standard or long file name. IBM 03590H1A /dev/rmt/393mnb Minor = Ox1E90C0 v In HP-UX 11i v3: ATDD supports the HP-UX lssf. # lssf /dev/rtape/tape14_BESTnb atdd Berkeley No-Rewind best density available at address 64000/0xfa00/0x32 /dev/rtape/tape14_BESTnb Chapter 4. 25. use the # insf command to generate them. Refer to “Supported Devices and Feature Codes” on page 14 for what feature code may be required for your machine type.2. HP introduces the native multi-pathing and path-independent persistent Device Special Files (DSFs) and the auto discovery of devices greatly to enhance the overall manageability.7. Persistent Naming Support Persistent naming support is used to ensure that attached devices are always configured with the same logical name across system reboots. the HP-UX tape driver creates an additional set of device special files with a prefix of “s” for the configured tape drives in HP-UX 11. The persistent DSF format for tape devices introduced with the Agile view in HP-UX 11i v3 is: # ioscan -funNC tape Class I H/W Path Driver S/W State H/W Type Description =================================================================== tape 1 64000/0xfa00/0x7 estape CLAIMED DEVICE IBM 03592E05 /dev/rtape/tape1_BEST /dev/rtape/tape1_BESTn /dev/rtape/tape1_BESTb /dev/rtape/tape1_BESTnb # ioscan -funNC autoch Class I H/W Path Driver S/W State H/W Type Description ================================================================= autoch 8 64000/0xfa00/0xa acdd CLAIMED DEVICE IBM 03584L22 /dev/rchgr/autoch8 To map a persistent DSF to its legacy DSF.0. such as s55m in the following example. 2. The library control path failover feature code must be installed prior to enabling the path failover support in the HP-UX ATDD device driver. enter the following: # ioscan -m dsf /dev/rtape/tape1_BESTb Persistent DSF Legacy DSF(s) ======================================== /dev/rtape/tape1_BESTb /dev/rmt/c3t15d0BESTb /dev/rmt/c9t6d0BESTb Control Path Failover Support for Tape Libraries Notes: 1.97. # ioscan -funC tape Class I H/W Path Driver S/W State H/W Type Description =================================================================================== tape 103 1/0/0/0.HP-UX Device Driver (ATDD) # lssf /dev/rchgr/autoch1 acdd section 0 at address 64000/0xfa00/0x21 /dev/rchgr/autoch1 If the device special files are not created on the system. 11i v1 and v2.0 atdd CLAIMED DEVICE IBM 03592E05 /dev/rmt/103m /dev/rmt/c10t7d0BESTn /dev/rmt/s55mb /dev/rmt/103mb /dev/rmt/c10t7d0BEST /dev/rmt/s55mn /dev/rmt/103mn /dev/rmt/c10t7d0BESTb /dev/rmt/s55m /dev/rmt/103mnb /dev/rmt/c10t7d0BESTnb /dev/rmt/s55mnb In HP-UX 11i v3. It is a requirement that applications must open the primary path for CPF 78 IBM Tape Device Drivers Installation and User’s Guide .255. For this purpose. The ATDD does not create the additional set of device special files with a prefix of “s”. The other Chapter 4. * The requested changes have been applied to the currently running configuration. 11i v1 and v2. perform the following steps: v In HP-UX 11. HP-UX Tape and Medium Changer Device Driver 79 . however. If you want to turn off the control path failover feature in the ATDD driver. # kctune atdd_alternate_pathing=0 * The automatic 'backup' configuration has been updated.0. perform the following steps after installing the driver: v In HP-UX 11. In HP-UX 11i v3. 11i v1 and v2: 1. To enable the failover support in the ATDD driver.altpath next to one of the special files in HP-UX 11. ATDD handles the CPF in the next open.HP-UX Device Driver (ATDD) Configuring and Unconfiguring Path Failover Support Path failover support is enabled automatically when the device driver is installed. * The requested changes have been applied to the currently running configuration. the first logical medium changer device that it sees in the system is the primary path for that medium changer.0. Tunable Value Expression Changes atdd_alternate_pathing (before) 0 0 Immed (now) 1 1 You can check if the driver has recognized multiple control paths for your library by running: #ioscan -funC autoch If you see . 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 path failover setting is retained even if the system is rebooted. After the path failover support is enabled. Reconfigure CPF for the devices: v In HP-UX 11i v3: Run kctune to disable the kernel tunable of atdd_alternate_pathing. Set the alternate_pathing parameter: # /opt/atdd/bin/atdd_failover -a 1 /opt/atdd/bin/atdd_claim 2. Clear the alternate_pathing parameter: # # /opt/atdd/bin/atdd_failover -a 0 /opt/atdd/bin/atdd_claim 2. # kctune atdd_alternate_pathing=1 * The automatic 'backup' configuration has been updated. Reconfigure CPF for the devices: # v In HP-UX 11i v3: Run kctune to enable the kernel tunable of atdd_alternate_pathing. the driver provides a kernel parameter you can use to enable library control path failover. use the # ioscan -m dsf command and the option 53 of “Display Path” in tapeutil to verify that the multiple path is configured by the system and ATDD. ATDD manages the CPF in the next open. then you have successfully enabled the control path failover feature for your library.0. it remains set until atdd_claim is run with the alternate_pathing driver parameter set to OFF . 11i v1 and v2: 1. Tape Utility Program (tapeutil)” on page 335. The device driver supports up to 16 physical paths for a single device. The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. 11i v1 and v2: # ioscan -funC autoch The following is an example of what you might see: autoch autoch 0 0/1/0/0.1.Tape Utility Program (tapeutil)” on page 335 Data Path Failover and Load Balancing Support for Tape Drives The HP-UX device driver path failover support configures multiple physical paths to the same device within the device driver and provides two basic functions: 1.1 acdd CLAIMED /dev/rmt/1chng.0. Automatic failover to an alternate physical path when a permanent error occurs on one path. the HP-UX system always selects the best path for ATDD to open so the primary path is dynamically assigned from the system.255.altpath DEVICE DEVICE IBM IBM ULT3582-TL ULT3582-TL Querying Primary and Alternate Path Configurations You can display the primary and alternate path configuration for all devices by running the ioscan command.” on page 255 or “HP-UX System . If it is necessary to disable a path and not perform path fail over (for example due to maintenance). “IBM Tape Diagnostic Tool (ITDT). The primary and alternate path information can be obtained by using the following command on HP-Ux 11.1. ATDD does not provide any .HP-UX Device Driver (ATDD) logical medium changers that ATDD attached for the same medium changer are configured as alternate paths. Note: See Chapter 10.altpath special file. HP-UX system always pickups a best path for ATDD to open. “IBM Tape Diagnostic Tool (ITDT).1 acdd CLAIMED /dev/rmt/0chng 1 0/1/0/0.22. ATDD doesn't perform a dynamic load balancing in open. as explained in section “Determine the Device Hardware Path for IBM Tape Drives” on page 58. run commands to disable and then later enable the primary and alternate paths.101. Disable and Enable Primary and Alternate Paths When you load the ATDD device driver with the alternate_pathing parameter set to ON.1.255. On HP-UX 11i v3.” on page 255 or “HP-UX System . 80 IBM Tape Device Drivers Installation and User’s Guide . by default. refer to Chapter 10. 2. On HP-UX 11i v3. Dynamic load balancing for devices using multiple Host Bus Adapters (HBA).22. all the available paths for a physical device are enabled. Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions.2.101. . A DPF key is required for Ultrium-3 tape drives only. Save the file.d/atdd file if you are running the most recent drive code. HP-UX Tape and Medium Changer Device Driver 81 .altpath" next to one of the special files. ″1234567890123456″ is an example of a data path failover feature key. It is required that applications must open the primary path for Data Path Failover (not in HP-UX 11i v3). 11i v1 and v2.)# /opt/atdd/bin/atdd_failover -a 0 2.d/atdd file: DPF_KEYS="1234567890123456. Edit the following line in your /sbin/init. However. then you have successfully enabled control path failover feature for your library." b. Reconfigure DPF for the devices: # /opt/atdd/bin/atdd_claim Chapter 4. (You can ignore the message about rebooting the system. Clear the alternate_pathing parameter. Data Path Failover is supported for 3592 tape drives on HP-UX 11. Data Path Failover is not supported when using block sizes greater than 256K. No DPF key needs to be added into the /sbin/init. “IBM Tape Diagnostic Tool (ITDT). 11i v1 and v2: 1. 2. and for Ultrium-3 and Ultrium-4 drives on HP-UX 11i v1. then run the following command in HP-UX 11.HP-UX Device Driver (ATDD) Notes: 1. In HP-UX 11. To enable the failover support in the IBMtape device driver software. you need to provide the data path failover feature key and reclaim the devices using the atdd_claim script. Note: See Chapter 10. If you want to turn off the data path failover feature in the ATDD driver. input your keys as follows:DPF_KEYS="key1. you can check whether the driver has recognized multiple data paths for your drives by running: #ioscan -funC tape If you see a ". 0987654321123456 " Notes: a. v2 and v3. Configuring and Unconfiguring Path Failover Support Path failover support is turned on automatically when the device driver is installed. 11i v1 and v2: # /opt/atdd/bin/atdd_claim 3. use the # ioscan -m dsf command and the option 53 of “Display Path” in tapeutil to verify that the multiple path is configured by the system and ATDD.Tape Utility Program (tapeutil)” on page 335 After path failover support is enabled. perform the following steps: In HP-UX 11. it remains set until atdd_claim or kctune is run with the alternate_pathing driver parameter set to OFF.. If you have multiple 3584 libraries and multiple data path failover feature keys. 2.0. 11i v1.0. The path failover setting is retained even if the system is rebooted. perform the following steps after installing the driver: 1.0. except in HP-UX 11i v3. .0.” on page 255 or “HP-UX System . In HP-UX 11i v3. 3. The feature key is a string with 16 characters and numbers. v2 and v3. key2. Tunable Value Expression Changes atdd_alternate_pathing (before) 1 1 Immed (now) 0 0 If you want to turn the data path failover feature back on in the ATDD driver. The primary and alternate path information can be obtained by issuing the following command except in HP-UX 11i v3: # ioscan -funC tape The following is an example of the output for this command: /home/root# ioscan -funC tape Class I H/W Path Driver S/W State H/W Type Description =============================================================================== tape 0 0/1/0/0. Reconfigure DPF for the devices: # In HP-UX 11i v3: Run kctune to enable the kernel tunable of atdd_alternate_pathing.HP-UX Device Driver (ATDD) In HP-UX 11i v3: Run kctune to disable the kernel tunable of atdd_alternate_pathing. In HP-UX 11i v3.101. 11i v1 and v2: 1. * The requested changes have 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.1.22. ATDD does not provide any . (You can ignore the message about rebooting the system. The other logical paths that ATDD attached for the same tape drive are configured as alternate paths.1.1 atdd CLAIMED DEVICE IBM ULT3580-TD3 /dev/rmt/1m. The device driver supports up to 16 physical paths for a single device.2. Set the alternate_pathing parameter. # kctune atdd_alternate_pathing=1 * The automatic 'backup' configuration has been updated.) # /opt/atdd/bin/atdd_failover -a 1 /opt/atdd/bin/atdd_claim 2. the HP-UX system always pickups a best path for ATDD to open so the primary path is dynamically assigned from the system.0.22.atlpath special file. ATDD handles the DPF in the next open.1. ATDD handles the DPF in the next open.altpath 82 IBM Tape Device Drivers Installation and User’s Guide .101. * The requested changes have been applied to the currently running configuration.1 atdd CLAIMED DEVICE IBM ULT3580-TD3 /dev/rmt/0m tape 1 0/1/0/0. the first logical device that it sees in the system is the primary path for that medium changer. perform the following steps: In HP-UX 11.255. # kctune atdd_alternate_pathing=0 * The automatic 'backup' configuration has been updated.255. Note: See Chapter 10. Here are the log examples: 1. Reservation Conflict Logging When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the HP-UX system log of /var/adm/syslog/syslog.Tape Utility Program (tapeutil)” on page 335. Device reserved with legacy reserve. or hardware that doesn't support interactive reservation.” on page 255 or “HP-UX System . The ATDD logs messages to this file which provide information regarding the problem.HP-UX Device Driver (ATDD) Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices by running ioscan. please check for firmware update! Chapter 4. The information is logged when the drive is reserved with a SCSI-2 Reserve. Reserving host key DF25382049E627E6 WWPN 21:00:00:E0:8B:11:8B:B1 2.” on page 255 or “HP-UX System . Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name) and reserve key.log. If successful. Error Logging Read the system log file (typically /var/adm/syslog/syslog. HP-UX Tape and Medium Changer Device Driver 83 . Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. atdd: device=rtape41 Reserved. “IBM Tape Diagnostic Tool (ITDT). After initially logging the reserving host WWPN. Disable and Enable Primary and Alternate Paths If it is necessary to disable a path and not perform path fail over (for example due to maintenance). “IBM Tape Diagnostic Tool (ITDT).log) if you are having problems. the device driver will log this information in the detail data below. as explained in section “Primary and Alternate Paths” on page 82. subsequent reservation conflicts from the same reserving host WWPN and reservation key will not be logged to prevent multiple entries in the system log until either the reserving host WWPN or reservation key is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs.log) and the ATDD log file (/var/adm/atdd/atdd_d. refer to Chapter 10. The commands to enable and disable primary and alternate paths are tape diagnostic and utility functions. The information is logged when the drive is reserved with a Persistent Reservation. run commands to disable and then later enable the primary and alternate paths.Tape Utility Program (tapeutil)” on page 335 Problem Determination A set of tools is provided with the device driver to determine if the device driver and the tape device are functioning correctly. Issuing atdd_trace -f 0x1fffffff turns on every trace.0. To enable the support dynamically. the sense data is logged into the system log file (typically /var/adm/syslog/syslog. located in the /opt/OMImag/bin for the static driver and in /opt/atdd/bin for the DLKM driver. Then run the script and redirect the output to an end of a file: Static: /opt/OMImag/bin/support_info > support_info.out Tracing Facility Running the ATDD_trace utility. Enter the following commands to start the trace: 1.log). which shows driver configuration and per instance drive attribute configuration and errors. run the sam utility or # kctune atdd_trace_level=1 command to set the trace level to 1. Log in as userid ″root″ on the system which experienced a problem. The set of trace flags is displayed in Table 13. # /opt/atdd/bin/atdd_cfg -c 1 * The requested changes have been applied to the currently running system. located in the /opt/OMImag/bin directory for the static driver and in /opt/atdd/bin for the DLKM driver.out DLKM /opt/atdd/bin/support_info > support_info. Trace Flags COMMAND Configuration General errors Routine entry points VALUE 0x00000001 0x00000002 0x00000004 84 IBM Tape Device Drivers Installation and User’s Guide . The sense data logging feature is disabled by default on 11. The default debug level is 0x00001003. You can increase the amount of debug information displayed by enabling more trace flags. indicating information that should be verified for correctness. 0x3 (Medium Error). run /opt/atdd/bin/atdd_cfg with the -c option. to trace everything: For the Static driver:/opt/OMImag/bin/atdd_trace -f 0x1fffffff For the DLKM driver:/opt/atdd/bin/atdd_trace -f 0x1fffffff In HP-UX 11iv3. Tunable Value Expression Changes atdd_log_trace (before) 0 Default Immed (now) 1 1 Support_info Script Run the support_info script. determine which items need to be traced and set the trace flags using the atdd_trace command. 11i v1 and 11i v2 and enabled by default on 11i v3. The utility traces can be started at any time before an operation on a tape device. displays debug information. 0x4 (Hardware Error) and 0xB (Aborted Command) for a hardware or medium error. There are several sections with the keyword VERIFY. The default set is 3. First. This script gathers important system and configuration information. Table 13. For example.HP-UX Device Driver (ATDD) Sense Data Logging When the tape drive responds with CHECK CONDITION status and associated sense keys of 0x1 (Recovery Error). The following steps document how to start and configure the daemon: 1. To set a value (0 or 1) to atdd_direct_trace. and to log error messages into the /var/adm/atdddirectory.log once the kernel tunable of atdd_direct_trace is enabled.0. Trace Flags (continued) COMMAND Returns TRACE_DBG information Open/Close routine Trace motion commands Read/Write Strategy Open/Close states IOCTLs Trace device config routines Trace SCSI level stuff Configuration Entry point General information Memory VALUE 0x00000008 0x00000010 0x00000020 0x00000040 0x00000100 0x00000200 0x00000400 0x00000800 0x00001000 0x00004000 0x10000000 0x01000000 0x00400000 0x00200000 2. to retrieve and store SIM/MIM (Service and Media Information Messages) data.txt 7. Clear the trace buffer: For the Static driver:/opt/OMImag/bin/atdd_trace -c For the DLKM driver:/opt/atdd/bin/atdd_trace -c 3. The atdd_d log daemon is not automatically started in 11. when the driver is installed. the ATDD trace is logged into syslog of /var/adm/syslog/ syslog. 11i v1 and v2 but not in 11i v3. The atdd_trace output can be redirected to place the trace data in a readable format into a file.HP-UX Device Driver (ATDD) Table 13. 5. HP-UX Tape and Medium Changer Device Driver 85 . Start the daemon by running: For the Static driver: #/opt/OMImag/bin/atdd_d Chapter 4. run # kctune atdd_direct_trace=value.txt For the PCI driver:/opt/atdd/bin/atdd_trace >trace. Start the operations on a tape device. by entering: For the PB driver:/opt/OMImag/bin/atdd_trace >trace. In HP-UX 11i v3. To have trace data displayed immediately in a readable format as it is collected: For the Static driver:/opt/OMImag/bin/atdd_trace -b For the DLKM driver:/opt/atdd/bin/atdd_trace -b 4. To display collected trace data in a readable format at any time: For the Static driver:/opt/OMImag/bin/atdd_trace -d For the DLKM driver:/opt/atdd/bin/atdd_trace -d 6. Atdd_d Log Daemon The device driver provides a log daemon (atdd_d) facility for the Enterprise Tape System 359x to automatically store drive dumps. log Output Note: No entry is made in the log file when the daemon stops.HP-UX Device Driver (ATDD) For the DLKM driver: #/opt/atdd/bin/atdd_d 2. and size. Run #ps -ef | grep atdd_d to check if the daemon is stopped. message type (1 for the drive dump. To view and/or modify the settings for the daemon. time stamp. H/W path. and 3 for Error message).log. to decrease the number of drive dumps to store from 10 to 6 and change the log directory to /tmp/drive_dump. 2 for SIM/MIM data. do the following: For the Static driver: #/opt/OMImag/bin/atdd_d -n 6 -d/tmp/drive_dump For the DLKM driver: #/opt/atdd/bin/atdd_d -n 6 -d/tmp/drive_dump 4. enter: For the Static driver: # /opt/OMImag/bin/atdd_d -h usage: atdd_d [options] For the DLKM driver: # /opt/atdd/bin/atdd_d -h usage: atdd_d [options] [-d [-n [-z [-s <log directory>] <maximum number of dumps>] <maximum size of a dump>] <maximum size of a log>] default default default default is is is is /var/adm/atdd 10 1048576 100000 For example. Check whether the daemon is running by entering: #ps -ef | grep atdd_d 3. Figure 7. Example of atdd_d. Stop the daemon by using the following commands: 86 IBM Tape Device Drivers Installation and User’s Guide . View the atdd_d. Refer to an example in Figure 7. which provides information about the daemon start time. 5. kmsystune_lock was removed manually. Problems.prev #mv /stand/build/system /stand/system #kmupdate /stand/build/vmunix_test #shutdown -ry now A message in the file /var/adm/syslog/syslog. HP-UX Tape and Medium Changer Device Driver 87 . Use the following command to create the . the driver may be statically bound to the kernel or the ATDD package may not be installed. verify the drivers loaded in the running kernel using `kmadmin -s` If status is ″LOADED″ then run 'atdd_claim -b' to claim all IBM devices. If status is still ″UNLOADED″. then run 'atdd_claim -t' to claim the tape drives. then run 'kmadmin -L acdd' to load the ACDD. then run 'atdd_claim -c' to claim the changers. then check the entries of the files ’atdd’ and/or ’acdd’ in /etc/loadmods If no atdd and/or acdd file entries exist. then run 'atdd_claim' to claim the tape devices.kmsystune_lock As ″root″. Reasons. Table 14./stand/.kmsystune_lock ATDD DLKM Module’s component files are not copied to certain subdirectories of /usr/conf and /stand Remove ATDD and try to install it again. 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 #mv /stand/system /stand/system.log ″modld: Attempt to load unregistered module ″ # kmtune | grep atdd kmtune: Cannot open file -. A message in the file /var/adm/syslog/syslog. If status is ″UNLOADED″ then run 'kmadmin -L atdd' to load the ATDD.HP-UX Device Driver (ATDD) Get the daemon process id: kill the daemon process: #ps -ef | grep atdd_d #kill -9 process_id Problems and Solutions Table 14 describes problems and possible solutions for errors you may encounter with the DLKM driver. and Solutions Problem The system hangs running rmsf -H on HP-UX 11i. Check the installation running the following command: # swlist atdd ATDD DLKM modules are not loaded in the running kernel.kmsystune_lock file again: # touch /stand/. Reason and Solution DLKM Infrastructure does not set the correct flag in the device switch table entry for a DLKM driver that uses. The file .log ″vmunix: WARNING: modpath: DLKM is not initialized″ IBM tape devices not claimed in ioscan -fnk display Chapter 4. try setting the value to 1. Troubleshooting (Problems and Solutions) Problem No special files found in /dev/rmt Solution Issue the following commands: cd /opt/OMImag/bin atdd_mksf | sh Verify that the hardware path for the device is listed in the configuration file: /etc/rc. If you are using the PB drivers or are not using the standard device driver defaults with PCI drivers: 88 IBM Tape Device Drivers Installation and User’s Guide . This can be checked by running the command: atdd_cfg -g SILI If the value of SILI = 0.d/atdd. To create the files you must ″pipe″ the output to shell (sh). Check the current value by running the command: atdd_cfg -g DENSITY Try setting value to 0 (zero) by running the command: atdd_cfg -s DENSITY 0 Make sure the SILI configuration parameter is ″1″. the driver was not installed properly. Remove all of the special files for the device in /dev/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.cfg If the hardware path is missing or incorrect.config. Reasons. Problems. by running the following command: atdd_cfg -s SILI 1 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: Invalid 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.HP-UX Device Driver (ATDD) Table 14. Table 15 describes problems and possible solutions for errors you may encounter with the static driver. and Solutions (continued) Problem No special files found in /dev/rmt Reason and Solution Execute the atdd_mksf and acdd (if you have changers managed by the acdd driver) 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. using the following commands: atdd_mksf | sh acdd_mksf | sh The special files for a device are duplicates. Table 15. Troubleshooting (Problems and Solutions) (continued) Problem Claimed by HP Stape driver Solution Run the command: # lsdev to check that the atdd is in the current kernel: 1. rebuild the kernel or reinstall atdd. Cannot open Special File.HP-UX Device Driver (ATDD) Table 15... Check the current value 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. 2) Reboot the system.. enter the command: # /sbin/ioinit -c while the autobooting is halted.timestamp. Wrong DENSITY setting. 2. Rebuild the system I/O configuration: 1) Remove /stand/ioconfig and /etc/ioconfig after to backup the files. The system log has the following messages: A SCSI command timed out and was aborted. scsi3: .date code. 3) On System Console. If the atdd is in the output: a. The system log has the following messages: A SCSI command timed out and was aborted. An attempt to read data times out and returns an error. The system log has the following message: Invalid SCSI request in data at bit 7 of byte 4 An attempt to read data times out and returns an error. scsi3: .... 4) Run the command: # /sbin/insf -e 5) Enter the command: # ^D to exit the I/O configuration b. Consider reinstalling the HP-UX operating system if the system is new or this is a new update. HP-UX Tape and Medium Changer Device Driver 89 . try setting it to 1: atdd_cfg -s SILI 1 <atdd_inst> Check that the FORCE_NARROW parameter is valid for this device by executing: atdd_cfg -g FORCE_NARROW <atdd_inst> If FORCE_NARROW is 1.. If the atdd is not in the output.... try setting it to 0: atdd_cfg -s FORCE_NARROW 0 <atdd_inst> Chapter 4. LLIO: Detected PowerFail (probably caused by SCSI bus or device reset). HP-UX Device Driver (ATDD) 90 IBM Tape Device Drivers Installation and User’s Guide . 95 Updating Procedure . . . . . . . . . . . . lin_taped Daemon . . . . IBMtape and lin_tape Comparison . . . . . . Primary and Alternate Paths . 91 Data Flow . . . 96 Verifying Installation and Updating . . . . . . . Data Flow The software described in this chapter covers the Linux Device Driver (lin_tape device driver) and the interface between the application and the tape device. . For tape diagnostic and utility functions refer to Chapter 10. . . . . . . 91 Product Requirements . . . . . . . . . . . Testing Data Encryption Configuration and Connectivity . . Primary and Alternate Paths . . . . . . . . 105 105 105 106 106 106 107 107 108 109 109 109 110 110 110 110 111 111 111 111 112 113 114 114 118 119 This chapter describes the IBM Linux Tape and Medium Changer Device Driver (lin_tape). . 92 Hardware Requirements for Intel and AMD Opteron Processors . . . . Reservation Conflict Logging . . . . . . . . . . . . . Querying Primary and Alternate Path Configuration . . . . . . 98 Uninstall Procedure . . . . Disable and Enable Primary and Alternate Paths Open Source Device Driver . . . . . . . . . .Tape Utility Program (IBMtapeutil)” on page 345. . . . 98 Configuring Tape and Medium Changer Devices on IBM System z Models . . . . . . . . . . . . . . . . . . . . . Tape Drive Service Aids . . 94 Software Requirements for IBM System p Models 94 Software Requirements for IBM System z Models 94 Installation and Configuration Instructions . . . . . 92 Hardware Requirements for IBM System p Models . . . . . Querying Primary and Alternate Path Configuration . . . . . . 100 Tape Drive. . . . . . . Whenever possible. . . . . . . . . . © Copyright IBM Corp. 102 Special Files . . . . . . . . . . . . . . . . . . . . . Path Failover Support . . . . . . . . . . . . . . Media. 97 Configuring Tape and Medium Changer Devices on Intel-Compatible Systems . . as well as to the advanced functions needed by full tape management systems. . . and Device Driver Parameters 100 Configuration Parameters . . . . 93 Hardware Requirements for IBM System z Models . The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges). . . . . . . . . Problem Determination . 94 Components Created During Installation . . . . . . . . Installation . . Driver parameters and special device files . . . . . . . . . . . Linux Tape and Medium Changer Device Driver Purpose . .Chapter 5. . .lin_tape . . . .” on page 255 or “Linux System . . . . . . . . . . . . . . . . 2009 91 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007. Special Files for the Medium Changer Device Control Path Failover Support for Tape Libraries Configuring and Unconfiguring Path Failover Support . . . . . 93 Software Requirements for Intel and AMD Opteron Processors . . . . . . . . “IBM Tape Diagnostic Tool (ITDT). . . . Purpose The lin_tape and medium changer device driver is designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. . . . . . . . 101 Changeable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . System-Managed Encryption . . . . . . . Device Driver Configuration . . . . . 95 Installation Procedure . 96 Querying the Installed Package . Disable and Enable Primary and Alternate Paths Data Path Failover and Load Balancing Support for Tape Drives . . the driver is designed to take advantage of the device features transparent to the application. . . . . . . . . Configure and Run lin_taped Daemon . . . . . . . . . . . . Special Files for the Tape Device . . . . . . . . . . . . . . 97 Configuring Tape and Medium Changer Devices on IBM System p Models . . . . . 100 Nonchangeable Parameters . . . . . Querying Tape Drive Configuration . . . . 94 Conventions Used . . . . . and LP11002 Fibre Channel Adapters v v v v 92 IBM Tape Device Drivers Installation and User’s Guide a250181 Application Program lin_tape Device Driver Host Bus Adapter Driver Tape Device . and QLA2462 Fibre Channel Adapters v Emulex LP1150. QLA2310FL. QLA2342L. QLA2300F. Information there includes: v Specifics on Linux distributions and kernel levels v Supported Host Bus Adapter cards and required firmware and HBA device driver levels v Other important information that is not included in this manual Hardware Requirements for Intel and AMD Opteron Processors One or more of the following processors is required by the lin_tape device driver: v 32-bit Intel-compatible processors (uniprocessor or SMP) capable of running the Linux operating system v 64-bit Intel Itanium processors (uniprocessor or SMP) capable of running the Linux operating system v Intel processors that support Extended Memory 64 Technology (EM64T) v AMD Opteron processors capable of running the Linux operating system One or more of the following host bus adapters: v Adaptec 2940U2W (LVD.Dual Port LVD LSI Logic SAS3800X SAS Adapters IBM SAS Host Bus Adapter Controller Part Number 25R8060 QLogic QLA2200F. Figure 8. QLA2460. which is located at: ftp://ftp.Dual Port LVD v Adaptec SCSI Adapter 29320 . LP9802.ibm. The most current information is found in the README files on the IBM Device Drivers FTP site. Ultrium drives only) v Adaptec 2944UW (HVD) SCSI Host Bus Adapter v Adaptec SCSI Adapter 29160 or IBM P/N 19K4646 for IBM System x™ .Single Port LVD Adaptec SCSI Adapter 39320 . LP9002L.Linux Device Driver (lin_tape) Figure 8 illustrates a typical data flow process. LP11000. Data Flow for Linux Device Driver (lin_tape) Product Requirements More current information on supported hardware and software configurations for lin_tape is in the README files. QLA2340L.Single Port LVD v Adapted SCSI Adapter 39160 . LP10000.com/storage/devdrvr/Linux Information specific to certain distributions are in the README files in the distribution-specific directories under the Linux directory.software. Linux Tape and Medium Changer Device Driver 93 . 3322. Chapter 5. disk. IBM is focused on assuring server and storage configuration interoperability. Tape and disk devices require incompatible HBA settings for reliable operation and optimal performance characteristics. or high range System p (also known as pSeries) servers running a 64-bit Linux operating system v IBM POWER5™ servers running a 64-bit Linux operating system One or more of the following host bus adapters: v PCI-X DDR Dual -x4 SAS Adapter (FC 5900) v System p (also known as pSeries) Feature Code 5712 PCI-X Dual Channel Ultra320 SCSI Adapter v System p (also known as pSeries) Feature Dual Channel Ultra320 SCSI Adapter v System p (also known as pSeries) Feature v System p (also known as pSeries) Feature Adapter v System p (also known as pSeries) Feature Adapter v System p (also known as pSeries) Feature PCI-X Adapter v System p (also known as pSeries) Feature PCI-E Adapter Code 5736 (571A) or 1912 PCI-X DDR Code 6228 Fibre Channel Adapter Code 6239 Fibre Channel PCI-X Code 5716 Fibre Channel PCI-X Code 5758 and 5759 Fibre Channel Code 5773 and 5774 Fibre Channel Hardware Requirements for IBM System z Models One or more of the following processors is required by the lin_tape device driver running Linux on System z in 31-bit or 64-bit: v IBM System z 800 (z800) or 900 (z900) models v IBM System z 890 (z890) or 990 (z990) models v IBM System z9® models One or more of the following host bus adapters with Fibre Channel Protocol support: v FICON® Express card (feature 2315 or 2318) v FICON Express card (feature 2319 or 2320) v FICON Express2 card (feature 3319 or 3320) v FICON Express4 card (feature 3321. middle. or 3324) Note: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. Under stress conditions (high I/O rates for tape. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention.Linux Device Driver (lin_tape) Hardware Requirements for IBM System p Models One or more of the following processors is required by the lin_tape device driver: v IBM low. or both) where disk and tape subsystems share a common HBA. stability problems have been observed. IBM strongly recommends that your implementation plan includes provisions for separating disk and tape workloads. x. See the README file at: ftp://ftp. The utility tools for lin_tape are supplied in binary rpm packages.software. 94 IBM Tape Device Drivers Installation and User’s Guide .ibm. which changes as IBM releases new driver levels. The x.x. configuration.x.x.x. They can be downloaded from the following FTP site: ftp://ftp. ″>cd IBMtapeutil. for example.com/storage/devdrvr/Linux The following sections describe installation.i386 Note: This is performed using tape diagnostic and utility functions.x. You must have root authority to proceed with the installation of the driver. and verification procedures for lin_tape and its utility tools.x.x in them. you see file names with x.x. Some of the commands have a ″—some text″ string after them. The ″—some text″ items are explanatory comments to the reader and should not be specified when you enter these commands.software.i386 — to change the directory″. Use the actual driver version numbers as you perform the instructions.Linux Device Driver (lin_tape) Software Requirements for Intel and AMD Opteron Processors The lin_tape device driver supports the following Linux distributions: v Red Hat Enterprise Linux Server v SUSE LINUX Enterprise Server v Asianux Software Requirements for IBM System p Models The lin_tape device driver supports the following Linux distributions for Linux for System p (also known as pSeries) (64-bit kernel): v Red Hat Enterprise Linux v SUSE LINUX Enterprise Server v Asianux Software Requirements for IBM System z Models The lin_tape device driver supports the following Linux distribution for Linux on System z 31-bit and 64-bit: v Red Hat Enterprise Linux v SUSE LINUX Enterprise Server Installation and Configuration Instructions The lin_tape device driver for Linux is provided in a source rpm package.x refers to the version of the driver. In the previous example. uninstalling.ibm. Conventions Used In subsequent pages. Commands that you are to type are indicated with a leading ″>″ character. Refer to Linux documentation for tar command information and any Linux distribution supporting rpm for rpm command information. which indicates the shell prompt. all you would specify is the command: cd IBMtapeutil.com/storage/devdrvr/Linux/README This file contains the latest driver information and supersedes the information in this publication. refer to the “Updating Procedure” on page 96 in this chapter.ko /usr/bin/lin_taped /etc/lin_taped. Linux Tape and Medium Changer Device Driver 95 .Readme (for SUSE LINUX) /usr/share/doc/lin_tape-xxx/copying (for Red Hat) /usr/share/doc/packages/lin_tape/copying (for SUSE LINUX) License documentation for lin_tape ReadMe file for lin_taped daemon Description Device driver module for current kernel version lin_taped daemon lin_taped daemon configuration file ReadMe file for lin_tape using IBM TotalStorage devices The IBMtapeutil package consists of IBMtapeutil. Table 17. To install the lin_tape driver with all the added value of the lin_taped daemon. and the source files for IBMtapeutil. Please refer to the section “Configuring Tape and Medium Changer Devices on IBM System z Models” on page 98 in this chapter for how to configure and install zfcp. Note: This is performed using tape diagnostic and utility functions. ensure that the OpenFCP adapter device driver zfcp is loaded in the kernel. Components Created During lin_tape Installation Component /lib/modules/(Your system’s kernel name)/kernel/drivers/scsi/lin_tape.Readme (for SUSE LINUX) /usr/share/doc/lin_tape-xxx/lin_taped. This section assumes you are installing the lin_tape device driver onto a system where it is not currently installed. IBMtapeconfig. If you are installing lin_tape on a system running Linux for S/390® or Linux for zSeries®.conf /usr/share/doc/lin_tape-xxx/ lin_tape_359X. perform the following steps: Chapter 5. Components Created During IBMtapeutil Installation Component /usr/bin/IBMtapeconfig /usr/bin/IBMtapeutil Description Utility to create special files Utility and service aid program Installation Procedure If lin_tape is already installed on your system.Readme (for Red Hat) /usr/share/doc/packages/lin_tape/ lin_tape_359X. Components created during lin_tape installation (from the rpm package) are listed in Table 17.Readme (for Red Hat) /usr/share/doc/packages/lin_tape/ lin_taped. Make sure that the C/C++ development and kernel development packages are installed on your system. Table 16.Linux Device Driver (lin_tape) Components Created During Installation The lin_tape package consists of the device driver and a number of associated files. Components created during lin_tape installation (from the rpm package) are listed in Table 16. 0-1.x.i386. not installed.x.x. Near the end of the output.x.x. For example: >rpm -ivh /usr/src/redhat/RPMS/i386/lin_taped-1.x.rpm 3.src.x. there is a line that indicates the filename and location of your binary RPM package. if there is at least one tape device attached to your system: > IBMtapeutil -f /dev/IBMtape0 qryversion Note: This is performed using tape diagnostic and utility functions. For example: >rpmbuild --rebuild lin_tape-1. a line similar to the following is output to your screen: Wrote: /usr/src/redhat/RPMS/i386/lin_tape-1.x. 2.i386. For example. For example: >rpm -e lin_tape >rpmbuild -rebuild lin_tape. run >rpm -ivh <filename> For example: >rpm -ivh /usr/src/redhat/RPMS/i386/lin_tape-1. download it to your Linux filesystem and run rpm -ivh on the daemon RPM file. normal.x.x.0-1. If your current lin_tape device driver was installed from a rpm package previously.rpm Updating Procedure Before using this procedure to update your device driver to a different level. Run rpmbuild --rebuild <filename>. To install the lin_taped daemon.x. The installed rpm package can be queried by running the following commands to display information associated with the package. enter the command: >rpm -ql lin_tape To display the states of files in the package.rpm>rpm -i lin_tape. for example. Download the appropriate level of the source RPM package to a directory of your choice on the Linux kernel for which you wish to install it.rpm 4.rpm Note: All tape devices that use the lin_tape device driver must be closed and cannot be in use when lin_tape is uninstalled. To install the lin_tape driver from the binary package.i386.rpm 5.x. use the following command to obtain your existing lin_tape device driver version.i386. where: <filename> is the name of the RPM file.x. Output from the build is printed to your screen. Querying the Installed Package The query is supported for the lin_tape device driver rpm package only. then install the newer version. To display information about lin_tape: >rpm -qi lin_tape To display the file list.x.Linux Device Driver (lin_tape) 1. or replaced: >rpm -qs lin_tape 96 IBM Tape Device Drivers Installation and User’s Guide .0-1.x. This creates a binary RPM package for your kernel from the source RPM package.i386.x.x.x.0-rhel5. you may uninstall the driver first. Power on the tape and medium changer devices. it creates special files in the /dev directory. log onto the router and use the fcShowDevs command. For further information about the StorWatch Specialist.htm When you run the lin_tape kernel module. To view the LUNs of attached devices. before installing the Qlogic driver. Choose Query/Set Tape Parameters in the menu. Physically attach the tape and medium changers to the host bus adapter cards. After the driver software is installed and a tape device is connected to the adapter. Configuring Tape and Medium Changer Devices on Intel-Compatible Systems If you have not physically attached your tape and medium changer devices to your Linux server. If the LUNs are not contiguous. 3. you can use the Specialist to do this configuration. You can download the guide from the Web at: http://www.storage. Note: Hot plugging SCSI devices while the Linux server is running may cause hardware damage. 5. Access to the device is not provided until the device is configured. 2. use the mapCompressDatabase command to delete the invalid LUNs and make the valid LUNs contiguous. medium changer. use the IBMtapeutil application program. Linux Tape and Medium Changer Device Driver 97 . set the host type of the router to solaris and make sure that the logical unit numbers of the control unit. and the connected tape drives are contiguous (otherwise. Power on and boot the Linux server.com/hardsoft/products/sangateway/support/cdr/ Document/sdgdoc. Consult your hardware documentation for details. If your system is attached to an IBM 3583 Tape Library with the integrated router. the device can be configured and made available for use. 4. Note: This is performed using tape diagnostic and utility functions. Verify that they have completed the initialization process. refer to the IBM Storage Area Network Data Gateway Installation and User’s Guide. perform the following steps: 1. Halt the Linux server. Power down the Linux server.ibm. the Qlogic device driver does not recognize all of the attached devices).Linux Device Driver (lin_tape) Verifying Installation and Updating Run the following command to verify the lin_tape device driver version if there is at least one tape device attached to the system: IBMtapeutil -f /dev/IBMtape0 qryversion Note: This is performed using tape diagnostic and utility functions. To configure the tape devices. Chapter 5. If you have the StorWatch Specialist installed. conf: 0xf1c0 0x1:0x5005076300402733 0x0:0x0000000000000000. 1. unit scsi-lun Linux internal SCSI Logical Unit Number (32-bit). It is ″0x0″ in the previous example.Linux Device Driver (lin_tape) Configuring Tape and Medium Changer Devices on IBM System p Models Follow the same instructions as documented in the previous section.." Where: devno The device number of the host bus adapter (16 bits.ibm. For 2.. Every time you reboot the system. port scsi-id Linux internal SCSI ID assigned to the Fibre Channel port of the SCSI target device (32-bit. must not be 0.4 kernels. Features. Configuring Tape and Medium Changer Devices on IBM System z Models The fibre channel topology supported for System z is point-to-point and fabric. The following is an example of zfcp. It is ″0xf1c0″ or ″0xf1c1″ in the previous example.6 and 2. You need to configure the Emulex Linux device driver if you have fibre channel tape devices attached to your System p (also known as pSeries) system. The zfcp device configuration methods in 2.. fcp-lun Logical Unit Number associated with the SCSI target device (64-bit). Please refer to the Linux on System z fibre channel documents for more details on the supported configurations for fibre channel device attachment. First you need to add the device map into this file. For 2. Create a /etc/zfcp.conf file and make a ramdisk to statically attach tape devices into your system.software.ReadMe at ftp://ftp.6 kernels. there are three ways to load the zfcp device driver in order to see the attached tape devices. In 98 IBM Tape Device Drivers Installation and User’s Guide .4 kernels are different. refer to the lin_tape_359X_pSeries. see /proc/subchannels). It is ″0x5005076300402733″ in the previous example. It is ″0x1″ in the previous example.com/storage/devdrvr/Linux. For instructions on how to configure the Emulex device driver. must be a unique one-to-one mapping for each World Wide Port Name. refer to appropriate chapter in the Linux on System z document entitled ″Linux on System z: Device Drivers.\ 0xf1c1 0x1:0x5005076300402733 0x0:0x0001000000000000 The zfcp device driver uses the ″map″ module parameter to recognize a physically attached tape device. and Commands″. You can use this method only if you have a persistent mapping in a SAN environment. the zfcp is automatically loaded and the tape devices can be seen from the system. The Linux fibre channel adapter device driver zfcp is available in the kernel that supports zSeries Fibre Channel Protocol. ″map″ takes the following format: map="<devno><port scsi-id>:<wwpn><unit-scsi-lun>:<fcp-lun>. wwpn World Wide Port Name identifying the Fibre Channel port of the SCSI target device (64-bit).. Note: Do not use this choice together with the first one.conf file. Modify the /etc/modules. Run the ″modprobe zfcp″ command first.Linux Device Driver (lin_tape) the previous example. > echo 0xf1c1 > echo > echo "0xf1c0 0x1:0x5005076300402733 0x0:0x0000000000000000.conf file. Then run the following commands to install zfcp: >rmmod zfcp >modprobe zfcp 3. ″Id″. 2. and ″Lun″ in the /proc/scsi/scsi file.conf always takes higher priority than the map in /etc/zfcp. you should ensure that each <unit-scsi-lun> is unique. then run the ″depmod –A″ and ″modprobe zfcp″ command. Then run the following command: >depmod -A >modprobe zfcp This installs the zfcp device driver and all of its prerequisite kernel modules. For example. reboot the system.conf file to add the zfcp module parameters. and so on. The value of ″Channel″ can start from 0 for each different ″scsi″ value. The value of ″Id″ is the one you use for <unit scsi-lun> in the previous mapping. ″0x0000000000000000″ is the Logical Unit Number 0.conf: options zfcp map="\ 0xf1c0 0x1:0x5005076300402733 0x0:0x0000000000000000. you may issue the following commands. to add two logical units from the example in Step 2 into the system.conf is created. We recommend. and ″0x0001000000000000″ is the Logical Unit Number 1.\ 0xf1c1 0x1:0x5005076300402733 0x0:0x0001000000000000" The map arguments are the same as the ones listed in for the /etc/zfcp. If you physically attach a tape device on the switch and zfcp is already loaded. otherwise it causes conflicts. such as the fibre cables.conf. then dynamically add a tape device into the system after you physically attach a fibre channel tape device to the switch. The zfcp map in /etc/modules. for tape attachment. save and close it. etc. corresponding to the four parameters ″scsi″. After it is booted up. If you use the same devno numbers for several logical units. that each logical unit number be associated with a unique devno. Linux Tape and Medium Changer Device Driver 99 . The value of ″Lun″ is the logical unit number of the Chapter 5. After modifying the /etc/modules. you do not need to reboot the Linux system in order to add this entry in the /proc/scsi/scsi file. or if the devices are powered on. then check the fibre channel connection. your tape device should be shown in /proc/scsi/scsi file. ″Channel″. The value of ″scsi″ is 0 for the first devno. The zfcp device driver provides an ″add_map″ proc system entry under the directory /proc/scsi/zfcp to allow you to dynamically add the device into the system.\ 0x1:0x5005076300402733 0x0:0x0001000000000000" > /proc/scsi/zfcp/add_map "scsi add-single-device 0 0 1 0" > /proc/scsi/scsi "scsi add-single-device 1 0 1 1" > /proc/scsi/scsi The ″scsi add-single-device″ takes four parameters. If not. Now you can check the file /proc/scsi/scsi to see if all of the attached tape devices are shown in this file. The following example demonstrates the zfcp configuration in /etc/modules. run the following commands: >mk_initrd>zipl Then. 1 for the second devno (if it is different from the first devno). After /etc/zfcp. the zfcp device driver does not support dynamically removing the attached devices. Note: This is performed using tape diagnostic and utility functions. Currently. for example. Configuration Parameters The configuration parameters are used to set the operating mode of the tape drive and device driver when a device is opened.conf and reload zfcp. you have successfully attached those devices to your system. do ″rmmod zfcp″. The installation defaults are provided for all parameters initially. but are always restored back to the default values when the lin_tape device driver is reinstalled. Media. The nonchangeable configuration parameters are: v Autoloading v Density code v Emulate autoloader v Hook word v Maximum block size v Minimum block size v Medium type v Read SILI bit v Record space mode v Volume ID for logging v Write protect The changeable configuration parameters are: v Block size v Buffered mode v Capacity scaling 100 IBM Tape Device Drivers Installation and User’s Guide . After you have done all the mapping. Refer to the "“Installation Procedure” on page 95″ section in this chapter for the instructions on how to install lin_tape.Linux Device Driver (lin_tape) target device. If you need to remove the tape devices from the system. These parameters are kept on reopen. Uninstall Procedure Note: All tape devices that use the lin_tape driver must be closed and cannot be in use when lin_tape is uninstalled or the uninstall fails. Query/Set Tape Parameters in the menu. Then you can delete the entry in /etc/modules. Some of these parameters can be queried and set by IBMtapeutil. if you can see all of the attached tape devices in /proc/scsi/scsi. Next you may install the lin_tape device driver. Run the following command: >rpm -e lin_tape ---to remove Tape Drive. the last number in the previous mapping. or reload zfcp first and dynamically add the devices you want. and Device Driver Parameters This chapter describes the parameters that control the operating modes of the IBM Linux Tape and Medium Changer Device Driver. Capacity Scaling This parameter sets the capacity or logical length of the current tape. It is disabled by default and cannot be changed. By reducing the capacity of the tape. Minimum Block Size This parameter is the minimum block size for the device. Logical Write Protect This parameter sets or resets the logical write protect of the current tape. the tape drive 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. Some tape devices support multiple densities and report the current setting in this field. Linux Tape and Medium Changer Device Driver 101 . The nonchangeable parameters are detailed as follows: Autoloading This parameter enables the autoloading feature of the device driver. Chapter 5. Medium Type This parameter is the media type of the current loaded tape. This feature is not supported currently but might be supported in future releases of the lin_tape. Maximum Block Size This parameter is the maximum block size for the device. Some tape devices support multiple media types and different values are reported in this field.Linux Device Driver (lin_tape) v v v v v v v v v v Compression Disable auto drive 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 drive and device driver when a device is opened. Hook Word This parameter is not supported in the lin_tape device driver. It cannot be changed by the application. Density Code This parameter is the density setting for the currently loaded tape. Emulate Autoloader This parameter currently is not supported and should be ignored. The lin_tape device driver ignores this field. 102 IBM Tape Device Drivers Installation and User’s Guide . Only the SCSI mode is supported by lin_tape. 3. The changeable parameters are detailed as follows: Block Size This parameter specifies the block size used for read and write operations. SILI bit support may be enabled in future releases of the lin_tape. Any other value is a fixed block size. A value of zero means a variable block size. For example. Changing this parameter destroys any existing data on the tape. Capacity Scaling This parameter sets the capacity or logical length of the current tape on Enterprise Tape System 3590 or 3592 tape subsystems. On the backward space operation. Note: 1. Changeable Parameters The configuration parameters are used to set the operating mode of the tape drive and device driver when a device is opened. Write Protect This parameter is set to TRUE if the currently mounted tape is logically or physically write protected. The tape position must be at the start of the tape to change this parameter from its current value. Refer to “Maximum SCSI Transfer Length” on page 104 for additional guidance. capacity scaling is only supported for the standard 300 GB rewritable data cartridge. Buffered Mode This parameter specifies if read and write operations should be buffered by the tape device. the tape is positioned before the filemark (the beginning of tape side of the filemark). Capacity scaling remains with the tape across mounts until it is changed. Record Space Mode This parameter specifies how the device driver operates when a forward or backward space record operation encounters a filemark. the tape drive can access data faster at the expense of data capacity. the tape is left-positioned after the filemark (the end of tape side of the filemark). the device driver returns -1 and the errno variable is set to input/output error (EIO). Capacity scaling can be set at 100% for the entire tape (which is the default). the 60GB (Economy Data) cartridge for the IBM 3592 cannot be capacity scaled and is always 100%. The installation default is zero (variable length block size). Attempting to set capacity scaling that is not supported by a device or the current media loaded always returns 100% and cannot be changed. or set at 75%. For 3592 media types. 50%. When a forward or backward space record operation is issued to the driver and a filemark is encountered. 2. On the forward space operation. By reducing the capacity of the tape. or 25% of the 3590 tape cartridge and more available capacity scaling for the 3592 standard 300 GB rewritable data cartridge. The default (recommended) value is TRUE. Volume ID for Logging This parameter is the volume ID of the currently loaded tape.Linux Device Driver (lin_tape) Read SILI Bit SILI bit currently is not supported due to limitations associated with the Linux environment. 2 or later. the lin_tape device driver automatically retrieves the drive dump and saves it under the /var/log directory by default. 2.Linux Device Driver (lin_tape) Compression Hardware compression is implemented in the device hardware. Please refer to “Configure and Run lin_taped Daemon” on page 114 in this chapter for details. 1. You may specify another directory in the /etc/lin_taped. This capacity is not applicable to IBM Ultrium tape drives. the effective performance can increase. which is different from error logging. WORM protect also remains with the tape across mounts. Associated protect remains only while the current tape is mounted or associated with the tape drive. the lin_tape device driver provides this support. If compression is enabled. the lin_tape device driver automatically retrieves the data and saves it in a formatted text file under the /var/log directory by default. it can never be written on again. The log file is saved in binary format under the directory /var/log by default. If logging is On and the lin_taped daemon is running. Please refer to “Configure and Run lin_taped Daemon” on page 114 in this chapter for details. This parameter turns the hardware compression feature On and Off. The installation default is On (use compression). Disable SIM logging This parameter is provided in the lin_tape version 1. based on the compressibility of the data. Persistent protect remains or persists with the tape across mounts until it is reset. or the drive reaches a log threshold.conf file.2 and later. but unlike persistent protect it cannot be reset on the tape. If it is FALSE and the lin_taped daemon is running and SIM/MIM data is generated by the drive. Logging (Volume Logging) This parameter turns the volume information logging On or Off. Please refer to “Configure and Run lin_taped Daemon” on page 114 in this chapter for details on error logging.conf file. It is reset when the tape is unloaded or the tape drive is reset.2 or later. It is set to FALSE by default. 3.conf file. It is set to On by default. Logical Write Protect This parameter sets or resets the logical write protect of the current tape on Enterprise Tape System 3590 tape subsystems. With the lin_tape version 1. After a tape is WORM protected. Linux Tape and Medium Changer Device Driver 103 . If it is FALSE and the lin_taped daemon is running and if an error occurs in the drive which creates a drive dump. You may specify another directory in the /etc/lin_taped. Disable Auto Drive Dump This parameter is provided in the lin_tape version 1. persistent protect.2. Chapter 5. Note: This is volume logging. You may specify another directory in /etc/lin_taped.2. Please refer to “Configure and Run lin_taped Daemon” on page 114 in this chapter for details. the lin_tape device driver retrieves the full log sense data from the drive whenever a tape is unloaded. It is set to FALSE by default. The three types of logical write protect are: associated protect. and write-once read-many (WORM) protect. lin_tape provides error logging whenever the lin_taped daemon is running.2. 2. setting the transfer length greater than the default 256 KB does not guarantee a noticeable increase in data throughput. but the next command takes a long time to finish unless the physical rewind operation has completed. If no data was read. Read Past Filemark If this parameter is set to true. If trace is On and the lin_taped daemon is running. With the lin_tape version 1. with a fixed block size of 80000 bytes and maximum transfer length of 262144. Rewind Immediate This parameter sets the immediate bit for rewind commands. Variable block read/write requests with transfer length greater than the maximum transfer length fails [errno: EINVAL]. You may increase the maximum transfer length to enhance the data throughput. option 48 or the STIOCSETP ioctl call any more. 104 IBM Tape Device Drivers Installation and User’s Guide . then the read returns 0 bytes read and positions the tape head after the filemark. If it is set to On. However. it returns the number of bytes read before encountering the filemark and positions the tape head after the filemark. and positions the tape head before the filemark.5 or higher and the open source driver lin_tape. the lin_tape device driver retrieves the trace from the driver if trace level is set to 1 or 2 in the /etc/lin_taped.0. a write request for 400000 bytes (5 blocks of 80000 each) is written to tape in two transfers. if data was read. the maximum transfer length per device per SCSI command is 262144 bytes (256 KB) by default. Trace This parameter turns the trace facility On or Off. the rewind tape operation executes faster. In lin_tape driver with level 3.Linux Device Driver (lin_tape) Note: The tape position must be at the start of the tape to change this parameter from its current value. the maximum transfer length is defined as the minimum length that the host bus adapter and the tape drive can support. The trace file is saved under the directory /var/log by default. The installation default is Off (no rewind immediate). when the read operation encounters a filemark. option 48 – Query/Set Tape Parameters.conf file. the read function returns the number of bytes read. This number is usually greater than 256KB.0.3. Setting this parameter reduces the amount of time it takes to close a device for a Rewind on Close special file. the lin_tape device driver provides this support. You may specify another directory in /etc/lin_taped. When a fixed block size has been defined. This installation default is FALSE. Maximum transfer length of 256 KB is highly recommended. Maximum SCSI Transfer Length In the lin_tape drivers with level lower than 3. or a customized STIOCSETP input/output control (ioctl) call. If the read_past_filemark parameter is set to false. It is set to On by default.2 and later. The first transfer is 240000 bytes (3 blocks) and the second transfer is 160000 (the remaining two blocks). This can be done either using IBMtapeutil. Please refer to “Configure and Run lin_taped Daemon” on page 114 for details. It can not be changed by the IBMtapeutil.conf file. Note: This is performed using tape diagnostic and utility functions. For example. large write requests are subject to both the granularity of the block size and the maximum transfer length. when a read operation encounters a filemark. No data is written during the operation. Table 18 shows the attributes of the special files. access to the robotic device is provided through the IBMchanger special file in the /dev directory. The IBMchanger* special file provides a path for issuing commands to control the medium changer robotic device. Note: The asterisk (*) in lin_tape* represents a number assigned to a particular device. then writing records past the early warning mark is not allowed. The installation default is On (with trailer labels).Linux Device Driver (lin_tape) Trailer Labels If this parameter is set to On. When this special file is opened. The asterisk (*) represents a number assigned to a particular device. the application can view the medium changer as a separate device. The file descriptor that results from opening the IBMchanger special file does not support the following operations: v Read v Write v Open in Append mode v Commands designed for a tape device Chapter 5. the IBMchanger* special file provides a separate path for issuing commands to the medium changer. All subsequent write operations are allowed to continue until the physical end of the volume is reached and errno EIO is returned. access is provided through the special files. If this parameter is set to Off. Linux Tape and Medium Changer Device Driver 105 . These special files. For tape drives with attached medium changer devices. such as IBMchanger0. Special Files After the driver is installed and a device is configured and made available for use. The first write operation after detecting the early warning mark fails and the errno variable is set to ENOSPC. such as lin_tape0. which consist of the standard Linux special files for devices. are in the /dev directory. then writing records past the early warning mark on the tape is allowed. Table 18. Errno variable is set to ENOSPC. The term IBMchanger is used for a SCSI medium changer device. Special Files for the Tape Device Each tape device has a set of special files providing access to the same physical drive but providing different attributes. Special Files for IBM TotalStorage Tape Devices Special File Name /dev/lin_tape* /dev/lin_tape*n Rewind on Close YES NO Special Files for the Medium Changer Device After the driver is installed and a medium changer device is configured and made available for use. Both the tape and changer special file can be opened at the same time. Linux Device Driver (lin_tape) Control Path Failover Support for Tape Libraries Note: The library control path failover feature code must be installed prior to enabling control path failover support in the Linux lin_tape device driver. Refer to “Supported Devices and Feature Codes” on page 14 to determine which feature code is required for your machine type. The Linux lin_tape device driver control path failover support configures multiple physical control paths to the same logical library within the device driver and provide automatic failover to an alternate control path when a permanent error occurs on one path. This is transparent to the running application. Configuring and Unconfiguring Path Failover Support Control path failover support is not enabled automatically when the device driver is installed. The Linux lin_tape device driver provides a driver parameter alternate_pathing for you to enable the library control path failover. To enable the failover support in the lin_tape device driver 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 driver 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 driver into memory) 6. lin_taped (re-start lin_taped daemon) You can ignore the ″Unresolved symbols in /lib/modules/<your kernel name>/drivers/scsi/lin_tape.ko″ message after the ″depmod″ command. You can check if the lin_tape driver has recognized multiple control paths for your library by reading the /proc/scsi/IBMchanger file. v cat/proc/scsi/IBMchanger If your library lists ″Primary″ or ″Alternate″ under ″FO Path″, you have successfully enabled control path failover feature for your library. If it is ″NA″ listed under ″FO Path″, then the control path failover is not enabled. After control path failover support is enabled, it remains set until the lin_tape driver is reloaded with the alternate_pathing driver parameter set to OFF . The path failover setting is retained even if the system is rebooted. If you want to turn off the control path failover feature in the lin_tape device driver, 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: 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 device that lin_tape sees in the system is the primary path for that medium 106 IBM Tape Device Drivers Installation and User’s Guide Linux Device Driver (lin_tape) changer. The other logical medium changers that lin_tape attached for the same medium changer are configured as alternate paths. The device driver supports up to 16 physical paths for a single device. The primary and alternate path information can be obtained by the following command: v cat /proc/scsi/IBMchanger The following is an example of a /proc/scsi/IBMchanger file: v lin_tape version: 3.0.3 v lin_tape major number: 253 Attached Changer Devices: Number 0 1 2 Model 03584L22 03584L22 03584L22 SN IBM1234567 IBM1234567 IBM1234567 HBA qla2xxx qla2xxx qla2xxx FO Path Primary Alternate Alternate The labeling of a logical device as either a primary or alternate path is for information only, in order to: v Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. There is only one logical device labeled as the primary path for each physical device. However, there can be multiple logical devices labeled as an alternate path for the same devices. v Provide information about which logical devices configured on the system have path failover support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices by reading the /proc/scsi/IBMchanger file, as explained in section “Primary and Alternate Paths” on page 106. Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions, refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 255 or “Linux System - Tape Utility Program (IBMtapeutil)” on page 345. Disable and Enable Primary and Alternate Paths Once you load the lin_tape device driver with the alternate_pathing parameter to be ON, by default, all the available paths for a physical device are enabled. If it is necessary to disable a path and not perform path fail over (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 10, “IBM Tape Diagnostic Tool (ITDT),” on page 255 or “Linux System - Tape Utility Program (IBMtapeutil)” on page 345 Chapter 5. Linux Tape and Medium Changer Device Driver 107 Linux Device Driver (lin_tape) Data Path Failover and Load Balancing Support for Tape Drives Data path failover support is not enabled automatically when the device driver is installed. The Linux lin_tape device driver provides a driver parameter alternate_pathing for you to enable the data path failover. To enable the failover support in the lin_tape device driver 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 driver from the memory If you have IBM 3592 tape drives, 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 have IBM LTO tape drives, the library needs to have path failover feature code. The data path failover license keys are needed to enable the failover if you are running LTO2 drives or if you are running LTO3 drives with old levels of drive code. DPF keys do not need to be added if you are running the latest drive code on LTO3 or LTO4 drives. 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 failover feature key. If you have multiple libraries and multiple data path failover feature keys, input your keys as follows: dpf_keys="key1;key2;..." Save the file, then run the following commands: >depmod >modprobe lin_tape (re-load the lin_tape driver into memory) >lin_taped (re-start lin_taped daemon) You may ignore the ″Unresolved symbols in /lib/modules/<your kernel name>/drivers/scsi/lin_tape.ko″ message after the depmod command. You can check if the lin_tape driver has recognized multiple paths for your tape drive by reading the /proc/scsi/IBMtape file: >cat /proc/scsi/IBMtape If your tape drive lists ″Primary″ or ″Alternate″ under ″FO Path″, you have successfully enabled data path failover feature for your tape drive. If it is ″NA″ listed under ″FO Path″, then the data path failover is not enabled. After the path failover support is enabled, it remains set until the lin_tape driver is reloaded with the alternate_pathing driver parameter set to OFF . The path failover setting is retained even if the system is rebooted. If you want to turn off the data path failover feature in the lin_tape device driver, you may do the following steps: >lin_taped stop >rmmod lin_tape Delete the following line in your /etc/modules.conf file: options lin_tape alternate_pathing=1 108 IBM Tape Device Drivers Installation and User’s Guide Linux Device Driver (lin_tape) >depmod >modprobe lin_tape >lin_taped Primary and Alternate Paths When the lin_tape device driver is loaded into kernel memory with path failover support enabled, the first logic device that lin_tape sees always becomes the primary path. The other logical devices that lin_tape sees are configured as the alternate paths. The device driver supports up to 16 physical paths for a single device. 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 version: 3.0.3 lin_tape major number: 253 Attached Tape Devices: Number 0 1 Model 03592 03592 SN IBM1234567 IBM1234567 HBA qla2xxx qla2xxx FO Path Primary Alternate The labeling of a logical device as either a primary or alternate path is for information only to: v Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. There is only one logical device labeled the primary path for each physical device. However, there may be many (multiple) logical devices labeled as an alternate path for the same devices. v Provide information about which logical devices configured on the system have path failover support enabled. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices 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 device using tape diagnostic and utility functions, refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 255 or “Linux System - Tape Utility Program (IBMtapeutil)” on page 345. Disable and Enable Primary and Alternate Paths If it is necessary to disable a path and not perform path fail over (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. Chapter 5. Linux Tape and Medium Changer Device Driver 109 Linux Device Driver (lin_tape) Note: See Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 255 or “Linux System - Tape Utility Program (IBMtapeutil)” on page 345 Open Source Device Driver - lin_tape The lin_tape device driver is the new device driver for the Linux 2.6 kernels to replace the closed-source driver IBMtape. In most respects, it behaves the same as the closed-source IBMtape device driver. This section covers significant differences between the IBMtape driver and the lin_tape driver. IBMtape and lin_tape Comparison Table 19 compares the names for various components of the IBMtape and lin_tape device drivers. Table 19. IBMtape and lin_tape Comparison Component Driver name Module name Special files proc entry Daemon name Daemon configuration file Daemon trace files IBMtape IBMtape IBMtape.ko /dev/IBMtape0 /dev/IBMchanger0, etc. /proc/scsi/IBMtape /proc/scsi/IBMchanger IBMtaped /etc/IBMtaped.conf /var/log/IBMtape.trace /var/log/IBMtape.errorlog Lin_tape lin_tape lin_tape.ko No change No change lin_taped /etc/lin_taped.conf /var/log/lin_tape.trace /var/log/lin_tape.errorlog The IBMtapeutil utility is the same for both the IBMtape driver and the lin_tape driver. Note: This is performed using tape diagnostic and utility functions. Installation Installation of the lin_tape driver is the same as for the IBMtape driver, 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 driver cannot be installed if the IBMtape driver is already installed. If the IBMtape driver is installed, first uninstall the IBMtape driver, and then install the lin_tape driver. With RHEL4 and SLES10, driver removal also requires a reboot of the server, since the IBMtape driver module is ″permanent″ in these distributions. Driver parameters and special device files The driver parameters have not changed for the lin_tape driver. However, 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 failover: 110 IBM Tape Device Drivers Installation and User’s Guide Linux Device Driver (lin_tape) options lin_tape alternate_pathing=1 dpf_keys="abcdefghijklmnop" abckdefghijklmnop is an example of a data path failover feature key. The special device files for the lin_tape driver are the same as for the IBMtape driver. Refer to “Special Files for the Tape Device” on page 105 and “Special Files for the Medium Changer Device” on page 105 of this chapter for details on special device files. Path Failover Support Path failover support in lin_tape is the same, except that with the lin_tape driver, failover support is provided through the lin_taped daemon. If the lin_taped daemon is not running, neither control path failover nor data path failover is attempted. The lin_taped daemon is started automatically when the lin_tape driver 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 failover support for that device 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 failover support, refer to the sections "“Control Path Failover Support for Tape Libraries” on page 106″ and "“Data Path Failover and Load Balancing Support for Tape Drives” 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 Device Driver Configuration Note: System-managed encryption (SME) on Linux requires that the lin_taped daemon is running. The device driver SME settings can be set for all drives at once using the ″default_sys_encryption_proxy″ and ″default_sys_encryption_write″ module options. If no options are specified in the registry, the driver uses the default values for the parameters. v The default value for default_sys_encryption_proxy is 1. This value causes the device driver to handle encryption key requests, if the drive is set up for system-managed encryption. This value should not need to be Chapter 5. Linux Tape and Medium Changer Device Driver 111 Linux System-Managed Encryption changed. A value of 0 causes the device driver to ignore encryption key requests for system-managed encryption drives, and is not desirable. v The default value for default_sys_encryption_write is 2. This value causes the device driver to leave 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 drive. If encryption has not been set up previously, then the drive writes unencrypted data. A value of 0 causes the device driver to write unencrypted data. A value of 1 causes the device driver 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 drives. To modify the settings for individual drives, the settings are ″sys_encryption_write″ and ″sys_encryption_proxy″, and have the same definitions and values as the similarly named ″default″ parameters, except that the settings only apply to individual drives. These settings are available as part of the sysfs infrastructure. For each drive, there are two files, named ″sys_encryption_write″ and ″sys_encryption_proxy″, in the /sys/class/lin_tape/{DEVICE}/ directory, where: {DEVICE} is the device name, such as IBMtape0. The contents of these files indicate the current setting for the parameter for that particular drive. The setting can be changed by writing a different value for the parameter to the file. For example, to change the ″sys_encryption_write″ setting for IBMtape0 to ON (which has a value of 1), enter the following at a command prompt: echo 1">/sys/class/lin_tape/IBMtape0/sys_encryption_write Note: The driver encryption parameters for individual drives are not persistent between loads of the lin_tape driver. If you remove the lin_tape driver, and then reload it, the individual settings for all drives are the same as the ″default″ settings in /etc/modprobe.conf or /etc/modprobe.conf.local. The ibmekm.conf file, which contains the configuration that the EKM servers 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 Drive Configuration There is an IBMtapeutil command to query the encryption settings of a tape drive. The IBMtapeutil command is menu option 57, “Query Encryption Status”. Note: This is performed using tape diagnostic and utility functions. 112 IBM Tape Device Drivers Installation and User’s Guide Linux System-Managed Encryption The following is an example of the output when the drive is configured for system-managed encryption, with encryption turned on: issuing query encryption status... encryption capable......Yes encryption method.......METHOD_SYSTEM encryption state........ON Testing Data Encryption Configuration and Connectivity There is an IBMtapeutil command to validate the ibmekm.conf file server entries and test tape drive to server connectivity operations. This test can be run using the IBMtapeutil menu option 58, “EKM Test”. Note: See “Linux System - Tape Utility Program (IBMtapeutil)” on page 345 for information on the IBMtapeutil application. The process involves three tests. 1. The first test checks the server configuration defined in the ibmekm.conf file and then communication to the configured servers. This test reports back the number of servers available. 2. The second test runs a basic diagnostic that checks the tape drive to server communication and reports success or fail. 3. The third test runs an enhanced diagnostic that checks a key operation between the tape drive and server then reports success or fail. The following is an example of the output of a successful test: Testing Testing Running Testing Running Testing server configuration and connections... complete, servers available 1 basic drive to server encryption test... complete, completion code 3 full drive to server encryption test... complete, completion code 3 If the first server test fails with one of the following errors, then the remaining tests are not run. Perform the recommended problem determination to resolve the problem: v “Invalid argument or Operation not supported on device” System encryption is not configured for the tape drive in the device driver. Use SMIT to set system encryption to “yes” for the tape drive. If system encryption can not be set then the tape drive is not encryption capable. v “Can’t assign requested address” Either the ibmekm.conf file is missing or is invalid. Check and correct. v “Network is down” All configured servers in the ibmekm.conf file are not available. Check all servers configured in the ibmekm.conf file are currently running on the server IP address and configured correctly. Chapter 5. Linux Tape and Medium Changer Device Driver 113 all sense data is also recorded. Configure lin_taped You can customize the operation of lin_taped by modifying its configuration file. where: timestamp reflects the time that the file was archived. 114 IBM Tape Device Drivers Installation and User’s Guide . then stop the daemon and restart it so that your modifications are recognized by the daemon. by default. Configure and Run lin_taped Daemon Starting with lin_tape version 1. If the lin_tapeTrace variable is set to an invalid number. 1. lin_taped records information associated with each ioctl called. the filename is renamed to lin_tape. if you make modifications to the configuration file. lin_taped records tracing messages for each SCSI command. the lin_taped daemon does not start. and/or SIM/MIM error information are created by the tape drive. Full error logging and tracing of the lin_tape device driver 2. consequently. the file is archived (using the Linux ar command) into file lin_tape. IBM recommends that you leave the daemon enabled at all times. 2 Set the lin_tapeTrace variable in the /etc/lin_taped. This is the default setting for tracing. After 1 MB of information is written. very minimal tracing is recorded from the lin_tape device driver. Because lin_taped requires a minimal amount of system resource and because it provides these necessary diagnostic capabilities. Information is written into the file until it is 1 MB in size. Tracing information is written to a file named /var/log/lin_tape. the lin_tape device driver provides an error diagnostic daemon (lin_taped) which provides the following capabilities: 1.timestamp. When drive dumps. Install lin_taped lin_taped is automatically installed at /usr/bin/lin_taped when you install the lin_tape device driver using the rpm or tar package. Tracing: Three levels of tracing are supported for the lin_tape device driver and are defined as follows: 0 1 With tracing set to 0. The daemon only reads the configuration file when it starts. or 2.a in the same directory.trace.conf.trace.Linux System-Managed Encryption Problem Determination A set of tools is provided with the device driver to determine if the device driver and the tape device are functioning correctly.conf file to 0. log sense data. which is located at /etc/lin_taped. With tracing set to 1. the daemon automatically retrieves that data and saves it to the hard drive on your Linux system. If a device error occurs and SCSI sense data is obtained from the device.5.2. Refer to “Installation and Configuration Instructions” on page 94 for instructions on installing the lin_tape device driver. a subset of that sense data is also recorded. With tracing set to 2. by default. In the archive. This tracing level should only be used when a specific problem is being diagnosed due to the potential for huge amounts of data being generated. If a device error occurs and SCSI sense data is obtained from the device. depending on what level of tracing you desire. etc. Sense key is 8. In the archive. It matches the order of the scsi/Channel/Id/ Lun information in the /proc/scsi/scsi file. Information is written into the file until it is 1 MB in size. 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. Whenever the lin_taped daemon is running. After 1 MB of trace information is written. or a tape is unloaded from the drive.conf file. and the ASC/ASCQ indicates the end of data Volume Logging: The lin_tape device driver retrieves the full log sense data from the tape drive whenever the drive reaches a log threshold.timestamp. Each time log sense data is obtained. The volume logging data is stored in the /var/log directory by default. Sense key is 0. by default.log. Sense key is 6. respectively. Sense key is 2.a in the same directory. ″Description″ is a person-readable text string obtained by parsing the sense key field of the sense data. Use the appropriate tape drive hardware reference manual to decode the log sense data. lin_tape1. This data is stored in binary in a file named lin_tape. host_byte. and the sense data indicates an overlength or an underlength read. or the drive is reset through an application. You may specify another directory in the /etc/lin_taped. indicating a unit attention 4. The four bytes represent driver_byte. the filename is renamed to lin_tape.conf file for details. Following is an example an error log record: IBMtape0---E0001 Scsi Path : CDB Command : Status Code : Sense Data : Tue Sep 03 00 00 01 00 00 08 00 00 70 00 04 C4 77 00 10 01 00 00 00 00 Description : Hardware 10 14:04:57 00 00 00 00 01 00 00 00 00 00 00 06 01 00 00 00 00 00 00 00 00 Error 2002 58 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF 01 00 00 0B 00 00 00 The first line indicates the tape device special file name and the device serial number.conf file. The following circumstances are not logged in the lin_tape. where: timestamp reflects the time that the file was archived. Error Logging: lin_taped records certain error messages from the lin_tape device driver in a file named /var/log/lin_tape. ″Status Code″ is the returned result from the Linux SCSI middle layer device driver (scsi_mod. Refer to the instructions in the lin_taped.errorlog.Linux Device Driver (lin_tape) 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. ″CDB Command″ is the command data block of the SCSI command. lin_tape2.conf file for details.timestamp.o). error logging is enabled if tracing is enabled. the file is archived (using the Linux ar command) into file lin_tape. and the ASC/ASCQ indicates the device is becoming ready 3.conf file. ″Sense Data″ is the full SCSI sense data returned from the target. Chapter 5. it is written to a new file. Refer to the instructions in the lin_taped. msg_byte. Linux Tape and Medium Changer Device Driver 115 . and status_byte. ″Scsi Path″ is the SCSI path for this logical unit. and the timestamp when the error message was recorded. where: lin_tapen is the device special file (for example. by default. or encountering a file mark or the end of data 2.) and timestamp reflects the time the file was created.errorlog.errorlog file: 1. which means that every time a drive dump is obtained. then lin_taped stops creating new files. which means that every time log sense data is created. where lin_tapen is the device special file (for example.Linux Device Driver (lin_tape) There are two configuration parameters in the /etc/lin_taped. lin_tapeAutoDriveDumpFileOverWrite is ignored. only the newest data is kept. each time log sense data is created. You may specify another directory in the /etc/lin_taped. it is written to a new file. and each time a drive dump is obtained. The IBM service organization may request that you forward drive dumps to them for analysis. lin_taped deletes the oldest log sense file and creates a new file with the newest log sense data. There are two configuration parameters in the /etc/lin_taped. If lin_tapeMaxDumpFiles is a positive number and lin_tapeAutoDriveDumpFileOverWrite is 0. lin_taped writes that data to a file until lin_tapeMaxDumpFiles have been created. then when new log sense data is detected. If lin_tapeMaxDumpFiles is a positive number and lin_tapeAutoDriveDumpFileOverWrite is 1. it is written to a new file. lin_taped writes that data to a file until lin_tapeMaxDumpFiles have been created. The drive dumps are stored in the /var/log directory by default. lin_tapeMaxLogSenseFiles is 0 and lin_tapeAutoLogSenseFileOverWrite is 1. lin_tape2.) and timestamp reflects the time the file was created. By default. etc. lin_taped writes that data to a file until lin_tapeMaxLogSenseFiles have been created. thus.conf file that you can tailor to affect the number of log sense files that are kept on your system: v lin_tapeMaxLogSenseFiles which can have a value of 0 or a positive decimal number. lin_tapeAutoLogSenseFileOverWrite is ignored. By default. and each time log sense data is obtained. each time a dump is obtained.conf file. even if new drive dumps are produced. it is written to a new file. Automatically Retrieve a Drive Dump: If a condition occurs in the drive such that a drive dump is created.conf file that you can tailor to affect the number of drive dumps that are kept on your system: v lin_tapeMaxDumpFiles which can have a value of 0 or a positive decimal number. lin_tape1. each time log sense data is created. v lin_tapeAutoLogSenseFileOverWrite which can have a value of 0 or 1. If lin_tapeMaxLogSenseFiles is a positive number and lin_tapeAutoLogSenseFileOverWrite is 1.dmp.timestamp. If lin_tapeMaxDumpFiles is 0. then lin_taped stops creating new files. then when 116 IBM Tape Device Drivers Installation and User’s Guide . v lin_tapeAutoDriveDumpFileOverWrite which can have a value of 0 or 1. lin_taped retrieves the drive dump and saves it in a file named lin_tapex. Each time a drive dump is obtained. lin_taped writes that data to a file until lin_tapeMaxLogSenseFiles have been created. even if new log sense data is produced. If lin_tapeMaxLogSenseFiles is 0. it is written to a new file. If lin_tapeMaxLogSenseFiles is a positive number and lin_tapeAutoLogSenseFileOverWrite is 0. it is written to a new file. each time a dump is obtained. lin_tapeMaxDumpFiles is 0 and lin_tapeAutoDriveDumpFileOverWrite is 1. conf file that you can tailor to affect the number of SIM/MIM files that are kept on your system: v lin_tapeMaxSimMimDataFiles which can have a value of 0 or a positive decimal number. Linux Tape and Medium Changer Device Driver 117 . Chapter 5. By default. thus. These settings persist until the device driver is restarted. Automatically Retrieved SIM/MIM Data: If a condition occurs in the drive such that a drive SIM/MIM data is created. lin_taped writes that data to a file until lin_tapeMaxSimMimDataFiles have been created. lin_tape2. There are two configuration parameters in the /etc/lin_taped. then when new SIM/MIM data is detected. each time SIM/MIM data is obtained. auto-retrieving drive dumps. it is written to a new file. it is written to a new file. lin_taped writes that data to a file until lin_tapeMaxSimMimDataFiles have been created. which means that every time SIM/MIM data is obtained. and each time SIM/MIM data is obtained.timestamp. The IBM service organization may request that you forward SIM/MIM data to them for analysis. error logging. even if new SIM/MIM data are created. lin_taped deletes the oldest drive dump file and creates a new file with the newest drive dump data.simmim. v lin_tapeAutoSimMimDataOverWrite which can have a value of 0 or 1. The parameters and their definitions are as follows: trace This parameter is set to On by default. lin_tapeAutoSimMimDataOverWrite is ignored. then lin_taped stops creating new files. or the host system is rebooted. which enables lin_tape tracing of activities and error logging on a particular tape drive.Tape Utility Program (IBMtapeutil)” on page 345 for information on the IBMtapeutil application. You may selectively enable/disable them through the IBMtapeutil Query/Set Tape Parameters operation or through an application program which uses the STIOC_SETP ioctl.Linux Device Driver (lin_tape) a new drive dump is detected. and auto-retrieving SIM/MIM data. only the newest data is kept. Note: See “Linux System . The SIM/MIM data is stored in the /var/log directory by default. lin_taped deletes the oldest SIM/MIM file and creates a new file with the newest SIM/MIM data. thus. lin_taped retrieves the data and save it in a file named lin_tapex.) and timestamp reflects the time the file was created. etc. If lin_tapeMaxSimMimDataFiles is a positive number and lin_tapeAutoSimMimDataOverWrite is 1. Set this parameter to off to stop tracing and error logging. If lin_tapeMaxSimMimDataFiles is 0. it is written to a new file. only the newest data is kept. each time SIM/MIM data is obtained.conf file. Each time SIM/MIM data is obtained. You may specify another directory in the /etc/lin_taped. Selective Tracing: lin_tape provides facilities by which you can disable and enable tracing. lin_tape1. where lin_tapen is the device special file (for example. If lin_tapeMaxSimMimDataFiles is a positive number and lin_tapeAutoSimMimDataOverWrite is 0. lin_tapeMaxSimMimDataFiles is 0 and lin_tapeAutoSimMimDataOverWrite is 1. version 1.4. By default it is set to Off which causes drive dumps to be saved. 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.3. lin_taped automatically creates a special file under the /dev directory. the device driver will post the message lin_tape: reserve held by xxxxxxxx 118 IBM Tape Device Drivers Installation and User’s Guide . By default it is set to Off which causes SIM/MIM data to be logged. will get the reserving host initiator WWPN (World Wide Port Name). You can invoke lin_taped from the command line.x or less. no information is saved. you need to stop the lin_taped daemon first. Reservation Conflict Logging When the device driver receives a reservation conflict on a tape drive command it will log the conflict to the kernel debug buffer (which is typically echoed to /var/log/messages). disable_sim_logging This parameter controls the logging of SIM/MIM data for a device. Note: If you run ″rmmod lin_tape″ command to remove the lin_tape device driver from the running kernel. Set this flag to On to suppress the logging of SIM/MIM records. lin_taped does not automatically start if there is no tape device attached. When the daemon is stopped. If you add a new tape device into your Linux system. if it is. Setting this flag to Off suppresses volume logging for this device.conf file. version 1. after installing lin_tape lin_taped starts running even if your system does not have a tape device attached. the new one is aborted. you’ll need to start the lin_taped daemon. Set this flag to On to suppress the saving of drive dumps.Linux Device Driver (lin_tape) logging This parameter is set to On by default and enables logging of log sense data. (Use ″lin_taped restart″ if lin_taped is already running. If there is already a lin_taped running. lin_taped status Prints a message on stdout indicate whether the daemon is running or not. This command should be used after modifying the /etc/lin_taped.conf file while lin_taped is running. If successful. Run lin_taped If you are running the lin_tape device driver.1 or higher.) lin_taped stop Terminates the daemon and frees all the resources associated with the daemon. If you are running the lin_tape device driver. Prior to logging the error the device driver will determine if a SCSI Persistent Reservation is active on the target tape drive and. lin_taped restart Terminates the currently running daemon and starts a new one. otherwise you get a ″Device or Resource Busy″ error. disable_auto_drive_dump This parameter controls the saving of drive dumps for a device. After you attach a new tape device. The new daemon reads the /etc/lin_taped. Linux Device Driver (lin_tape) to the debug buffer. or a tape cartridge. then choose ″Dump Device″ under ″Service Aids Commands″ in the menu or issue the following command: IBMtapeutil -f /dev/IBMtape0 dump [filename] If the filename is not specified. invoke IBMtapeutil. then choose ″Force Dump″ under ″Service Aids Commands″ in the menu or issue the following command: IBMtapeutil -f /dev/IBMtape0 forcedump Read Dump: This utility transfers the dump data from the device to a file. To access this utility. Reset Drive: This utility resets the tape drive. Refer to “Service Aid Subcommands” on page 352. It follows a force drive dump operation. To prevent multiple identical entries in the error log. Tape Drive Service Aids The service aids described here are accessible through both the interactive and command-line mode of the IBMtapeutil. then choose ″Load Ucode″ under ″Service Aids Commands″ in the menu or issue the following command: IBMtapeutil -f /dev/IBMtape0 ucode filename Note: The filename has to be specified. a diskette. invoke IBMtapeutil. Linux Tape and Medium Changer Device Driver 119 . dump0001. subsequent reservation conflicts from the same reserving host WWPN will not be logged. All the dump files are stored under the current directory. please refer to the IBM System Storage Virtualization Engine TS7510 Installation and Planning Guide at: http://www-03. For information on using tape drive service aids with the IBM Virtualization Engine TS7510. After the dump operation is performed.com/ systems/storage/index/tape.dmp is used as the default. invoke IBMtapeutil. To access this utility. To access this utility.html Details of Tape Drive Service Aids The following service aid utilities are available through the utility program IBMtapeutil installed with the lin_tape device driver. v Force Microcode Dump v Read Dump v Load Microcode v Reset Drive Force Drive Dump: This utility forces a dump operation on the tape drive. Otherwise.ibm. then choose ″Reset Drive″ under ″Service Aids Commands″ in the menu or issue the following command: IBMtapeutil -f /dev/IBMtape0 resetdrive Chapter 5. Load Microcode: This utility downloads microcode to the tape drive or medium changer from a file. invoke IBMtapeutil. To access this utility. IBMtapeutil returns an error. the dump data can be saved to a file using the Read Dump utility. Linux Device Driver (lin_tape) 120 IBM Tape Device Drivers Installation and User’s Guide . . . . Software Requirements . . . . . . . . . . . 125 . Device Behaviors . and the IBM tape system. . . Special Files . . . . . . . . Deconfiguring Tape Devices . . . . . . . . 146 . . . . Reservation Conflict Logging . element information. . . . . Installation Problems . . . . . 147 This chapter provides an overview of the IBM SCSI Tape and Medium Changer Device Driver for Solaris. . . . . . . . . . . . . . . . Persistent Naming Support . . . . . . . 2009 121 . . . . . . It is designed specifically to take advantage of the features provided by IBM tape and library systems. . . . . . . . . Whenever possible. . Control Path Failover Support for Libraries . . . . . . . . . Configuring and Deconfiguring Path Failover Support . . . and inventory) present in some devices. . . . . Configuring and Deconfiguring Path Failover Support . Dynamic Tracing Utility . the application program. . . . . . . . . . Product Requirements . . . . Purpose This device driver product provides attachment for IBM Magnetic Tape and Library System products to Sun Microsystems SPARC Servers running the Solaris operating system. . . 125 131 134 136 139 139 140 141 142 143 144 145 146 Disable and Enable Primary and Alternate Paths Data Path Failover and Load Balancing Support for Tape Drives . . Installing and Updating IBMtape . Hardware Requirements. . . . . . . . Configuration Parameters . . . . Data Flow . . . . . . . . . . . . . . . . . . . including control of the random access medium changer facility (move. . Tracing Facility . . . Tapelist Utility Program . . . . . . . . . Querying Tape Drive Configuration . . . . . . . . . . . . . . . 146 . . . . . . . . . . . iostat Command . . . . . . . . . 121 121 122 122 124 124 125 . . . . . . . . . . . Setting the IBM_trace Level for Static Tracing Running Diags_info Script . File Naming Conventions . . . . . . . Preventing Conflicts with Other Device Drivers Preinstallation Considerations . . . . . . Primary and Alternate Paths . Device Driver Configuration . . . . . . . . . . . Solaris Zones Support . © Copyright IBM Corp. . . . . . . . . . . . . . . Installation and Configuration Instructions . .Chapter 6. . Testing Data Encryption Configuration and Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . Tape Monitor Daemon (tmd) . . . Removing IBMtape . . . . . . . . . . . . . . . . . Disable and Enable Primary and Alternate Paths System-Managed Encryption . Functional Verification . . . . . . . Querying Primary and Alternate Path Configuration . . . . . . . . Solaris Tape and Medium Changer Device Driver Purpose . . . Figure 9 on page 122 shows the data flow between IBMtape. . . . Configuring IBM tape devices with Fibre Channel and SAS HBAs . . . . . . . . . Adding or Removing Devices . . . . . . the SCSI adapter device driver. as well as the advanced functions needed by full tape management systems. . . Data Flow Both data and commands flow between the application program and the tape subsystem by way of IBMtape. . . 2007. . . 147 147 147 149 149 150 150 150 151 151 152 152 152 153 153 154 156 156 157 157 158 . . . . . . . . Problem Determination . . . The goal is to give applications access to the functions required for basic operations (such as backup and restore). . . . . Primary and Alternate Paths . . . . Field Support Information . . . also known as IBMtape. . . the device driver is designed to take advantage of the IBM tape system features transparent to the application. . . . . . . . . . . . . . Querying Primary and Alternate Path Configuration . . v The Ultrium tape drives and Enterprise Tape drives 3590 (Model E) and 3592 with Fibre Channel Attachment are supported with the following adapters: 122 IBM Tape Device Drivers Installation and User’s Guide . Data Flow for Solaris Device Driver (IBMtape) Product Requirements The following hardware and software components are required and supported by IBMtape. and VTS of products with any of the supported FC–AL host bus adapters.Solaris Device Driver (IBMtape) Figure 9. 3590. PCI (P/N X6541A) v One or more of the following SCSI Low Voltage Differential (LVD) host bus adapters on Solaris Version 8. Hardware Requirements The following hardware is required and supported by IBMtape: v 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) v 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. or later (Ultrium only): – Sun StorageTek PCI-X SAS HBA (SG-XPCI8SAS-E-Z) – Sun StorageTek PCI-Express SAS HBA (SG-XPCIE8SAS-E-Z) v 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. 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 ) v One or more of the following Serial Attached SCSI (SAS) host bus adapters on Solaris Version 10. Tape and disk devices require incompatible HBA settings for reliable operation and optimal performance characteristics. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. Models B11. and E1A VTS model B18 VTS models B10. LP9802(PCI-X). QLA2340L. LP9002S(S-Bus). SG-XPCIE2FC-EM4. – AMCC FCX/2-6562(PCI-X). PCI Fibre Channel Adapters QLE2460/2462 Fibre Channel Host Bus Adapter on x64 system only. QLA2310FL. B1A. – Emulex LightPulse LP8000(PCI). and LP11002 Fibre Channel Adapters LPe11000/11002 Fibre Channel Host Bus Adapter on x64 system only. Table 20. QLA2340. B18. Under stress conditions (high I/O rates for tape. LP11000. and B20) Notes: 1. models B11. disk. FCE-6460(PCI) and FCE-1473(S-Bus) Fibre Channel Adapters – 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 HBA (SG-XPCI2FC-QF4 and SG-XPCI1FC-QF4) – Sun StorageTek Enterprise Class 4 Gb FC PCI-E HBAs (SG-XPCIE2FC-QF4. QLA2342. QLA2342L. LP9002C(cPCI). and SG-XPCIE1FC-EM4) v Table 20 indicates which SCSI-attached devices 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. IBM is focused on assuring server and storage configuration interoperability. QLA2462. FCC-6562(cPCI). and E1A Magstar MP 3570 Tape Subsystem Model C Magstar MP 3575 Tape Library Dataserver TotalStorage Virtual Tape Server (Models B10. E11. QLA2460. LP9002L(PCI). Chapter 6. It strongly recommends that your implementation plan includes provisions for separating disk and tape workloads.Solaris Device Driver (IBMtape) – QLogic QLA2200F. B20 QLogic QLA2100 X X X X X X QLogic QLA2200F Emulex LP8000 Emulex LP8000S X X X X X X X IBM IBM IBM IBM Enterprise Tape Drive 3590. Solaris Tape and Medium Changer Device Driver 123 . LP8000S(S-Bus). LP9042DC(PCI-X). E11. stability problems have been observed. or both) where disk and tape subsystems share a common HBA. Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. FCX-6562(PCI-X). SCSI Supported Devices DEVICE Magstar MP 3570 Magstar MP 3575 Enterprise 3590. FCC/2–6562(cPCI). SG-XPCIE1FC-QF4. LP10000(PCI-X). B1A. Refer to the Solaris documentation for general information about installable packages.h /usr/include/sys/svc. For IBM Ultrium drives with the Fibre Channel attachment. For Solaris Version 2. The IBMtape package consists of the device driver and a number of associated files and utilities. Refer to the manufacturer’s documentation for the SCSI adapter driver to determine which adapter driver is required. 9. v SCSI Host Bus Adapter (HBA) driver as supplied by the HBA manufacturer. reference version Utility program Tape Monitor Daemon (TMD) program TMD configuration file.ibm. working version Package subdirectory Utility and service aid program Utility/service program sample source code Diagnostic script SME configuration file. configuration. 3.h Description SME configuration file.conf /opt/IBMtape/ztapelist /opt/IBMtape/tapedtrc /usr/kernel/drv/IBMtape /usr/kernel/drv/IBMtape.Solaris Device Driver (IBMtape) 2. 7. its package name is IBMtape.6. v Sun Microsystems Solaris operating system Version 10 on x64 servers. Sun patch 105867-01 is required. reference version Shell script for Solaris zones use Dynamic tracing utility program Kernel module device driver Configuration file. the Sun Solaris operating system requires that the Fibre Channel addressing mode of the drive be set to hard addressing. Software Requirements The following software is required and supported by IBMtape: v Sun Microsystems Solaris operating system Version 2. refer to Table 21.conf /opt/IBMtape /opt/IBMtape/tapeutil /opt/IBMtape/tapeutil. Installation and Configuration Instructions IBM SCSI Tape Drive and Medium Changer Device Driver for Solaris is an installable kernel module.conf /opt/IBMtape/IBMtape.conf /etc/tmd.conf /usr/include/sys/smc. working version Medium changer application programming interface (API) header file Tape drive API header file Service aid API header file 124 IBM Tape Device Drivers Installation and User’s Guide . IBMtape Components Component (Note) /etc/ibmekm. The most recent supported HBA information can be found at: http://www-03.com/systems/support/storage/config/hba/index. reference version Configuration file. or 10 on SPARC servers. Table 21. and verification procedures for IBMtape. When installed. For components created during IBMtape installation. working version TMD configuration file.wss . removal.conf /opt/IBMtape/tapelist /opt/IBMtape/tmd /opt/IBMtape/tmd.c /opt/IBMtape/diags_info /opt/IBMtape/ibmekm. supplied as a standard Solaris software package. 8.6.h /usr/include/sys/st. The following sections describe installation. Solaris Tape and Medium Changer Device Driver 125 . 3. 2. v As a consequence of installing or reinstalling IBMtape. Attention: Failure to prevent more than one device driver from operating the same tape drive may cause system panics or data loss on the tape drive. then return to this section. device special file numbers under /dev/rmt may change. Notify users that system maintenance and a restart is performed. tmd. Preinstallation Considerations Follow these steps to install or update IBMtape. v You may restart the system as part of the IBMtape installation. including devices that IBMtape manages.Solaris Device Driver (IBMtape) Table 21. Refer to the differential SCSI adapter documentation for instructions on installing the adapter and adapter driver. These numbers are assigned by Solaris during the driver attachment process. other suppliers’ SCSI tape device drivers that you have installed must be prevented from claiming IBMtape-owned devices. However. Select a time when all system activity can be stopped to perform the installation.conf. Examples of installation commands and their results throughout this chapter use a percent sign (%) to indicate the shell prompt. Install and configure one of the supported differential SCSI adapters first.conf are not overwritten by the package file contents. you must prevent st from claiming and attempting to operate IBMtape-owned devices. v You must have root authority to install or remove IBMtape. This allows tape drive configuration options to be preserved across IBMtape updates. and the sequencing cannot be specified by the device driver or installer.conf and ibmekm. which claims any SCSI-compliant tape drive that it detects. note the following general considerations: v Differential SCSI-2 support must already exist on the machine before installing IBMtape.conf are always installed in the /opt/IBMtape directory. The reference copies of IBMtape. tmd. In order to avoid conflicts between IBMtape and st. the working copies of IBMtape. The following installation and update steps describe how to prevent conflicts between IBMtape and other SCSI tape device drivers. Before starting the step-by-step procedure. the Solaris operating system includes a SCSI tape device driver named st. These are: 1.conf. Take appropriate precautions that this does not adversely affect users or active processes on the system. Chapter 6. Likewise. IBMtape Components (continued) Component (Note) /usr/include/sys/oldtape. Installing and Updating IBMtape There are several steps that must be taken prior to installing or updating IBMtape on your system to ensure proper installation and system integrity. Login to the target system as root. Preventing Conflicts with Other Device Drivers IBMtape only attempts to claim and operate the devices described in “Hardware Requirements” on page 122.conf and ibmekm.h Description Compatibility API header file Note: When updating IBMtape. 126 IBM Tape Device Drivers Installation and User’s Guide . Record the device type. refer to Table 22. % ls -l /dev/rmt/*l lrwxrwxrwx 1 root root 72 Aug 26 15:47 /dev/rmt/5l -> .4000/scsi@3/
[email protected]/
[email protected]:l In the preceding example. Select one of the following methods to prevent conflicts between IBMtape and other SCSI tape device drivers. Table 22.IBMtape .0:st lrwxrwxrwx 1 root other 47 Aug 26 16:36 /dev/rmt/1smc -> . depending on the equipment that is attached to your system. LUN 0. and so on.Equipment Listing Example 1 DEVICE 3590-B11 drive 3590-B11 changer Old Special File /dev/rmt/2st /dev/rmt/3smc Old Driver IBMtape IBMtape SCSI Address/LUN (Old) 8/0 8/1 7. suppose an installation has only an IBMtape-owned device installed at SCSI address 8. For example. Solaris Device Driver . /dev/rmt special file number. Ensure that all user and tape drive activity on the system is halted.1:smc In this example.e0001000/QLGC./devices/pci@6. and the medium changer as /dev/rmt/3smc. /dev/rmt/5l and the related 5m. This information is required later in the installation.4000/scsi@3/IBMtape@b. list the low-density device special files and find the SCSI addresses with which they are currently associated. Table 23. /dev/rmt special file number.. there are already IBMtape-owned devices installed. IBMtape Install or Update DEVICE QIC QIC Old Special File /dev/rmt/5l /dev/rmt/6l Old Driver st st SCSI Address/LUN (Old) 2/0 8/0 6././devices/pci@6. Record the device type. This information is required later in the installation.. The address is reported in hexadecimal format: The file /dev/rmt/1smc (a SCSI medium changer) is associated with the device at SCSI address b. For a similar equipment listing after recording the device information. If this is an update to IBMtape. refer to Table 23./.Solaris Device Driver (IBMtape) 4. The low-density devices are accessed as special files /dev/rmt/5l and /dev/rmt/6l. owning driver.. list the primary device special files and find the SCSI addresses with which they are currently associated. The device consists of both a tape drive and SCSI medium changer... LUN 1. For the equipment listing after recording the device information. /dev/rmt/0st (a SCSI tape drive) is controlled by IBMtape and is associated with the device at SCSI address b. For example..isp@3. are controlled by the st device driver and are associated with the device at SCSI address 2. suppose an installation has two non-IBM devices owned by st at SCSI addresses 2 and 8. owning driver.e0000000/sbus@f. SCSI target address and LUN. % ls -l /dev/rmt/*st /dev/rmt/*smc lrwxrwxrwx 1 root other 46 Aug 26 16:36 /dev/rmt/0st -> . SCSI target address and LUN. 5./devices/iommu@f. If tape drives not owned by IBMtape are installed on the system. 5h. The tape drive is accessed as /dev/rmt/2st./. In that case. LUN 0. If a driver is for both tape and disk devices. follow these steps to configure st and other non-IBM SCSI tape device drivers so that they control a range of target addresses distinct from the range that IBMtape uses. because SCSI adapters typically use one of those two addresses. it should not be needed. follow the suppliers’ instructions to disable its access to all SCSI tape devices. 3) Later.Solaris Device Driver (IBMtape) Attention: Failure to prevent more than one device driver from operating the same SCSI tape drive may cause system panics or data loss on the tape drive. follow the suppliers’ instructions to disable their access to all SCSI tape devices in the address range 7–15. b. #name="st" class="scsi" #target=1 lun=0.conf. and comment out all SCSI target entries by placing a pound sign (#) in the first column of each target entry. Remove all special file entries under /dev/rmt. 1) Edit /kernel/drv/st. a. a.conf. If the system has only IBMtape-owned devices attached. 8. 1) Edit /kernel/drv/st. % /usr/sbin/pkgrm IBMtape Respond to the pkgrm prompts. These steps leave target addresses 7 and 15 unclaimed by all target device drivers. Use pkgrm to remove the current level. % rm /dev/rmt/* 9. New entries are created when the system is restarted. If this is a new installation of IBMtape. 2) For other non-IBM installed SCSI tape device drivers. Repeat this operation for all entries in the target address range 7–15. #name="st" class="scsi" #target=7 lun=0. #name="st" class="scsi" #target=0 lun=0. the entries for SCSI address 7 and 8 have been commented out. If a driver is for SCSI tape devices only. follow these steps to prevent st and other non-IBM SCSI tape device drivers from claiming the IBM devices. #name="st" class="scsi" #target=8 lun=0. Repeat this operation for all target entries. In the following example. If you are updating the level of IBMtape. you must alter its configuration file so it does not use SCSI target addresses in the range 0–7 or address 15. This ensures that stale entries do not exist after the system is restarted. remove the drivers if they are not needed. If the system has a mixture of IBMtape-owned devices and other tape drives. Now st and other non-IBM SCSI tape device drivers have been configured to avoid conflicting with IBMtape. and comment out SCSI target entries for addresses 7–15 by placing a pound sign (#) in the first column of each target entry. 2) For other non-IBM installed SCSI tape device drivers. skip this step. Solaris Tape and Medium Changer Device Driver 127 . The following example shows the entries for SCSI target addresses 0 and 1 commented out. remove the currently installed IBMtape package. Chapter 6. after the IBMtape package has been installed. 2.conf.. Device busy Cannot unload module: IBMtape Will be unloaded upon reboot. If the distribution medium is a package file in a Unix file system.7 located in the /tmp directory.. after you have cabled IBM drives to the system and restarted. LUN 0 and address 0. and end the processes that are using them. #name="IBMtape" class="scsi" #target=0 lun=0 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0. If your system environment includes a mixture of IBMtape-owned devices and devices owned by st or another third-party SCSI tape device driver. Note that each SCSI target address has a stanza for both LUN 0 and LUN 1. contact your IBM service representative. pkgadd error messages similar to the following are output: .. b. then continue with the installation from this point. You may have obtained a package file by extracting it from a distribution diskette or by downloading it from IBM’s anonymous FTP site. If you see these messages.Solaris Device Driver (IBMtape) b. pkgadd: ERROR: postinstall script did not complete successfully .4. the entries for address 0.0. Place the package file in the target system’s /tmp directory. 10.. In the following example. This example presumes a package file named IBMtape..7 11. Use pkgadd to install the driver: % /usr/sbin/pkgadd -d /tmp/IBMtape.. 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. Later. perform the following steps. you must restart the system to free the tape drive. Repeat the operation for all stanzas in the address range 0–7 and address 15. 128 IBM Tape Device Drivers Installation and User’s Guide . ## Ensure that the SCSI adapter device driver is installed/configured. you should have already modified the configuration files for the non-IBM device drivers and restricted them to target addresses in the range 0–6. Note: If this is a new install of IBMtape.2. depending on the package distribution medium and the location of system resources. . Select one of the following methods to install the IBMtape package. Identify the drives and TMD process ID (pid). drvconfig: Driver (IBMtape) failed to attach Warning: Driver (IBMtape) successfully added to system but failed to attach ## The device driver was unable to detect any supported devices! ## Verify that the device(s) are properly connected and powered on.4. Edit IBMtape. ## Then try reinstalling the device driver as follows: ## -enter the command: rem_drv IBMtape ## -enter the command: add_drv -m '* 0666 bin bin' IBMtape ## If problems persist. one or more IBMtape-owned tape drives or tape monitor daemon (TMD) were still in use. If you cannot identify the processes. Use binary transfer mode. Examine the results from pkgrm. . a. If necessary. FTP the package file to the target system. located in /usr/kernel/drv... LUN 1 have been commented out. the driver attaches normally.0. IBM devices are not yet attached to the system. refer to Table 24 Table 24. record the new SCSI address along side the special file number and old SCSI address that you recorded previously. Shut down the system. a IBM tape device is mapped to the SCSI target 32 and LUN 15. % /usr/sbin/shutdown -y -g0 -i0 13. you may select addresses in the range 0–6 or 8–14. Solaris Device Driver . One common method to perform a shutdown is shown here but use your installation’s normal procedures. 12. Solaris Tape and Medium Changer Device Driver 129 . readdress the tape drives now. Then readdress each device to an address in the range 0–6. 1) For each device. SCSI address. If you are using distinct address ranges to separate tape drives that are IBMtape-owned from devices that are owned by st or another supplier’s driver. Then set the address and record the device type. For each tape drive that is readdressed.conf. For example. Alternatively. You create a new entry with the mapped SCSI target in IBMtape. It is addressed at target 4 and the information is recorded. Leave addresses 7 and 15 unused.Equipment Listing Example 2 Old Special File – – SCSI Address/LUN (Old) – – SCSI Address/LUN (New) 4/0 4/1 DEVICE 3590-B11 drive 3590-B11 changer Old Driver – – b.Solaris Device Driver (IBMtape) #name="IBMtape" #target=0 lun=1 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0. the fibre channel HBA driver may map the SCSI target address out of the range 15 and LUN over the number 1. If the system has only IBMtape-owned devices attached. suppose an installation has only IBMtape-owned devices attached.IBMtape . refer to the appropriate IBM hardware reference for any special instructions about addressing. 1) For each device to be owned by st or another SCSI tape device driver. class="scsi" In SAN environment. refer to the manufacturer’s hardware reference for any special instructions about readdressing. In the following example. For the results. An IBM device with tape drive and medium changer is added. because these addresses are used typically by the SCSI adapter. and LUN. Address or readdress devices as determined by your installation: a. 2) Readdress all tape drives that are owned by IBMtape to addresses in the range 8–14. you can modify the configuration file or use the utility provided by the fibre channel HBA driver to persistently bind the tape device to the expected SCSI target address. Refer to the appropriate IBM hardware references for Chapter 6. name="IBMtape" class="scsi" target=32 lun=15 block_size=0 buffering=1 immediate=0 trailer=0 sili=0. record the new SCSI address along side the special file number and old SCSI address. % ls -l /dev/rmt/*l % ls -l /dev/rmt/*st /dev/rmt/*smc Compare the SCSI addresses obtained from ls with the readdressed SCSI targets you recorded. For example. 14. or X'0A'. The new IBM device is addressed in the range 8–14. For example. Depending on the addresses chosen. For each tape drive that is readdressed. Table 25. Table 26. Refer to the manufacturer’s hardware references for any special instructions about cabling. Depending on the addresses chosen for the non-IBM devices. 16. Write the new device special file numbers and owning driver next to the matching new SCSI addresses. after completing installation and recording device information. Ensure that each SCSI bus is terminated properly. suppose an installation has two non-IBM devices owned by st at SCSI addresses 9 and B (12 in decimal). The new IBM device is addressed in the range 8–14. 15. Cable the tape drives to the system. An IBM device with tape drive and medium changer is added. if any. An IBM device with tape drive and medium changer is added. that you recorded previously. after readdressing and recording device information.IBMtape . Solaris Device Driver .Equipment Listing Example 4 Old Special Old File Driver /dev/rmt/5l /dev/rmt/6l – – st st – – SCSI Address/ LUN (Old) 2/0 8/0 – – SCSI Address/ LUN (New) 2/0 0/0 8/0 8/1 New Driver st st IBMtape IBMtape New Special File (Note) /dev/rmt/0l /dev/rmt/1l /dev/rmt/2st /dev/rmt /3smc DEVICE QIC QIC 3590-B11 drive 3590-B11 changer 130 IBM Tape Device Drivers Installation and User’s Guide . the non-IBM devices are all placed at addresses in the range 0–6. Log on as root and list the device special files in /dev/rmt as you did earlier during the install. the non-IBM devices are all placed at addresses in the range 0–6.IBMtape . Start the system according to your installation’s normal procedures. refer to Table 26 for the possible equipment listing entries. suppose an installation previously had two non-IBM devices owned by st at SCSI addresses 2 and–8. To prevent conflicts between IBMtape and st.Equipment Listing Example 3 Old Special File /dev/rmt/2l /dev/rmt/3l – – SCSI Address/LUN (Old) 9/0 b/0 – – SCSI Address/LUN (New) 3/0 5/0 a/0 a/1 DEVICE QIC QIC 3590-B11 drive 3590-B11 changer Old Driver st st – – Note: The SCSI target address of fibre channel tape device may be over 15.Solaris Device Driver (IBMtape) any special instructions about readdressing. at address 10. To prevent conflicts between IBMtape and st. if not yet done. Solaris Device Driver . refer to Table 24 on page 129 for the possible equipment listing. The current entry in the IBMtape. the following command opens the entry for QLogic QLA2462 running QLogic HBA driver qla2300: name="IBMtape" parent="qla2300" target=0.Solaris Device Driver (IBMtape) Table 26. Emulex. Chapter 6. # for qla2300 only 3. Notify users of any changed device special files numbers. Update the entry for the device in the IBMtape.conf file. Unload and reload the IBMtape driver: # # # # /opt/IBMtape/tmd -s rem_drv IBMtape add_drv -m '* 0666 bin bin' IBMtape /opt/IBMtape/tmd 5. For lpfc. Display information on the configured devices by running /opt/IBMtape/tapelist -l. Solaris Tape and Medium Changer Device Driver 131 . Remove the comment at the beginning of the entry for the QLogic HBA in the /usr/kernel/drv/IBMtape. 4.conf file. Run the Emulex HBAnyware utility to find and record the mapped target and LUN of the tape device. For instance. you can see that the tape drive accessed previously as /dev/rmt/5 is now accessed as /dev/rmt/0. 2. Solaris Device Driver . 17. 18. complete the following steps: 1. 2.IBMtape .30g or later. Configuring IBM tape devices with Emulex FC HBAs To configure an IBM tape device with an Emulex FC HBA.Equipment Listing Example 4 (continued) Old Special Old File Driver SCSI Address/ LUN (Old) SCSI Address/ LUN (New) New Driver New Special File (Note) DEVICE Note: Based on the listing. the new medium changer is accessible as /dev/rmt/3smc.conf and reboot the system. if necessary. For example. the following command adds an entry for a mapped device with target 200 and LUN 3: name="IBMtape" class="scsi" target=200 LUN=3. Verify operation of the newly installed or readdressed equipment.conf file is added to target 255 with LUN 0 and 1. The following sections describe how to configure IBM tape devices with QLogic. update the parameters setting in /kernel/drv/lpfc. Sun and AMCC Fibre Channel HBAs: v “Configuring IBM tape devices with QLogic FC HBAs” v “Configuring IBM tape devices with Emulex FC HBAs” v “Configuring IBM tape devices with Sun FC and SAS HBAs” on page 132 v “Configuring IBM tape devices with AMCC FC HBAs” on page 133 Configuring IBM tape devices with QLogic FC HBAs To configure an IBM tape device with a QLogic FC HBA. and so on. Configuring IBM tape devices with Fibre Channel and SAS HBAs Users may experience difficulty attaching an IBM tape device with an IBM tape driver on a fibre network. Run the QLogic SANSurfer Control FX utility to find and record the mapped target and LUN of the tape device.6. complete the following steps: 1. vIBM. IBMtape "scsiclass.pULT3580-TD1" "scsiclass. 2. Display information on the configured devices by running /opt/IBMtape/tapelist -l.08.vIBM. name="IBMtape" parent="lpfc" target=X lun=1.conf file.pULTRIUM-TD2" "scsiclass.conf: name="IBMtape" parent="lpfc" target=0.01.vIBM.pULT3580-TD3" 132 IBM Tape Device Drivers Installation and User’s Guide .vIBM.01. For instance. modify the setting for IBMtape: target-tapechanger="IBMtape" 3. Unload and reload the IBMtape driver: # # # # /opt/IBMtape/tmd -s rem_drv IBMtape add_drv -m '* 0666 bin bin' IBMtape /opt/IBMtape/tmd 6. Where: 01 and 08 stand for the type of tape drive and medium changer and XXX is the product ID string in the standard inquiry data. The following entry is added in the file for the IBM LTO2 drive: IBMtape "scsiclass. you may need to add the entries for LUN 0 and 1: name="IBMtape" parent="lpfc" target=X lun=0. The current entry in IBMtape. Run # cfgadm -c configure device to configure the tape device with the HBA if needed.conf adds target 255 with LUN 0 and 1.vIBM. ULT3580-TD2 is the product ID of the IBM LTO2 drive.01. Enter the following appropriate lines in /etc/driver_aliases: IBMtape "scsiclass. For the tape drives: IBMtape IBMtape IBMtape IBMtape IBMtape "scsiclass. Remove the comment at the beginning of the entry for the Emulex HBA in /usr/kernel/drv/IBMtape. 4. 4. 3. the following command adds an entry for a mapped device with target 200 and LUN 3: name="IBMtape" class="scsi" target=200 lun=3. complete the following steps: 1.vIBM.01.pXXX" for tape drive. Attach the IBM tape devices on the host.01.vIBM. change the parameter for IBMtape: target-tape="IBMtape If IBMtape driver is used as a changer driver. if necessary. Run # cfgadm -al -o show_FCP_dev Ap_Id to show the medium changer configuration with the HBA.pULT3580-TD2" "scsiclass.pULT3580-TD2" The following is a list of the entries for the supported IBM tape devices. Install the appropriate patch for the Sun HBA driver. If this fails to configure the changer. Configuring IBM tape devices with Sun FC and SAS HBAs To configure an IBM tape device with a Sun FC HBA. Update the entry for the device in the IBMtape. 5.pULTRIUM-TD1" "scsiclass. 5.01. Install the IBMtape tape driver by running the # pkgadd -d IBMtape command.vIBM.pXXX" for medium changer. For example.01.Solaris Device Driver (IBMtape) If IBMtape driver is used as a tape driver. Run # cfgadm -al to display the configuration between the HBA and the tape device. complete the following steps: 1.vIBM.p03592E06" "scsiclass.01. Update the change in jnic146x. Solaris 9. It is strongly recommended that you back up these entries in a file. Modify and add the following parameters in /kernel/drv/jnic146x.vIBM.vIBM. Configuring IBM tape devices with AMCC FC HBAs To configure an IBM tape device with an AMMC FC HBA.p3573-TL" "scsiclass. lun_throttle=1. For instance.conf if necessary.conf: CmdTaskAttr=1.vIBM.pULTRIUM-HH3" "scsiclass.pULTRIUM-TD4" "scsiclass.vIBM.08.08. Update the entry for the device in IBMtape.p03584L22" "scsiclass.conf adds target 255 with LUN 0 and 1.pULT3580-HH3" "scsiclass. tape-changer="IBMtape".vIBM.08. 7. and that you re-enter the entries when you upgrade the IBMtape driver before running the #pkgadd command.vIBM. rem_drv. The current entry in IBMtape. 6.01.vIBM.08.01.08.08.01. For example: # update_drv -av -i '"scsiclass. Unload and reload the IBMtape driver: Chapter 6.pULT3581-TA" "scsiclass.pULT3580-TD4" "scsiclass. 4.vIBM.Solaris Device Driver (IBMtape) IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape IBMtape "scsiclass. Remove the comment from the beginning entry for AMCC HBA in /usr/kernel/drv/IBMtape.vIBM. Run # /opt/IBMtape/tapelist -l to display the configured tape device information.vIBM.conf: name="IBMtape" parent="jnic146x" target=0.08.08.p3577-TL" For the medium changers: Note: The entry is also added running the # update_drv command on Solaris 8 (patch 111804-03 is required). Run the EZ Fibre utility to find and record the mapped target and LUN of the tape device.p03592J1A" "scsiclass.vIBM. Note: All of the added entries are removed by the operating system automatically after IBMtape is unloaded from the kernel by running the # pkgrm.-r. or modunload commands.01.vIBM. and later versions of the operating system.p03592E05" "scsiclass.01. 5.pULT3582-TL" "scsiclass.01.p03584L32" "scsiclass.vIBM.01.vIBM.pULT3583-TL" "scsiclass. Solaris Tape and Medium Changer Device Driver 133 . 3. Reboot the system by running # reboot -.pULTRIUM-TD3" "scsiclass.pULT3580-TD2"' IBMtape 6.p3576-MTL" "scsiclass. 2.01.pULT3581-TA2" "scsiclass.08. use the following command to add an entry for a mapped device with a target 200 and LUN 3: name="IBMtape" class="scsi" target=200 lun=3.conf. tape-device="IBMtape".vIBM.vIBM.vIBM. run the pkgadd system command from the global zone: #pkgadd -G -d IBMtape.5. a script program called ztapelist was developed to help the user display the IBM tape devices and to dynamically assign or remove IBM tape devices in non-global zones without the non-global zone reboot requirement.. Every Solaris system contains a global zone with ID 0. 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 -c -z zonename -a Displays IBM tape device information with the column headers for all zones Displays IBM tape device information without the column headers for all zones Shows IBM tape devices in a zone Dynamically adds IBM tape devices to each non-global zone without additional arguments zonename inst#_1 inst#_2 inst#_3 .x. and storage assignment. The utility (available in IBMtape 4.x. Zones hosted by a global zone are known as non-global zones. Solaris Zones Support The Solaris Zones partitioning technology on Solaris 10 is used to virtualize operating system services and provide an isolated and secure environment for running applications.Solaris Device Driver (IBMtape) # # # # /opt/IBMtape/tmd -s rem_drv IBMtape add_drv -m '* 0666 bin bin' IBMtape /opt/IBMtape/tmd 7. virtual network interface.x The IBMtape install script installs the driver in the global zone and installs some of IBMtape utilities running a non-root user in all zones. To install IBMtape on the system with the virtualized zones..1.2 or later) is installed on Solaris 10 and runs in the global zone only. Display information on the configured devices by running /opt/IBMtape/tapelist -l. Since the tape devices in non-global zones are configured from the global zone. Dynamically sets IBM tape devices not greater than 7 in a non-global zone zonename all Dynamically sets all IBM tape devices on the system in a non-global zone Removes the IBM tape device from a non-global zone Displays help information -d -h 134 IBM Tape Device Drivers Installation and User’s Guide . which have their own node name.x. The IBMtape driver supports the Solaris Zones environment. where the IBMtape driver is installed. --------------193 /dev/rmt/27st 03592E05(e/e) 000001365066 2/0 1A38 500507630019F016 500507630059F016 Do you wish to continue to add the devices? [y/n]: n # The ztapelist command also allows the user to remove all or some assigned tape devices from the non-global zone.-------------193 /dev/rmt/27st 03592E05(e/e) 000001365066 2/0 1A38 500507630019F016 500507630059F016 194 /dev/rmt/28smc 03584L22 0000000T003904E5 2/1 805r N/A N/A 200 /dev/rmt/29st ULT3580-TD4(e) 1300000044 4/0 82F0 500507630019F009 500507630059F009 201 /dev/rmt/30smc 03584L32 0000000T00390401 4/1 805r N/A N/A 206 /dev/rmt/31st ULT3580-TD3 1210003557 7/0 73P5 500507630019F007 500507630059F007 38 /dev/rmt/32smc 03584L32 0000000T00390401 7/1 805r N/A N/A Enter Instance Number (Inst #) of a device 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 device will be added: camshaft Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------.------.------------------------4/0 82F0 500507630019F009 500507630059F009 4/1 805r N/A N/A World Wide PN -----------------500507630059F016 N/A Running in non-global zone softail . run # /opt/IBMtape/ztapelist -a.---------------.----------------.---------..-------.------.--------------200 /dev/rmt/29st ULT3580-TD4(e) 1300000044 4/0 82F0 500507630019F009 500507630059F009 Do you wish to continue to add the devices? [y/n]: y Enter Instance Number (Inst #) of a device to be added: 193 Enter the zonename where the device will be added: softail Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------. Inst# Special File Device ------.----------------. # /opt/IBMtape/ztapelist -l Running in global zone .-----------.------------193 /dev/rmt/27st 03592E05(e/e) 194 /dev/rmt/28smc 03584L22 Serial No TGT/LUN Ucode World Wide NN --------------------. Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------.--------------.--------------000001365066 2/0 1A38 500507630019F016 0000000T003904E5 2/1 805r N/A To add the tape devices in non-global zones.--------.-------------.. as shown in the following example: # ztapelist -a Issuing this function will assign the tape devices in non-global zone Do you wish to continue? [y/n]: y Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------.---------.--------------.-----------------ULT3580-TD4(e) 1300000044 03584L32 0000000T00390401 TGT/LUN Ucode World Wide NN World Wide PN -------.------------200 /dev/rmt/29st 201 /dev/rmt/30smc zone camshaft .------------.---------. Device Serial No ----------------..---------.----------------.-----------------------------------.--------------.----------------193 /dev/rmt/27st 03592E05(e/e) 000001365066 2/0 1A38 500507630019F016 500507630059F016 194 /dev/rmt/28smc 03584L22 0000000T003904E5 2/1 805r N/A N/A 200 /dev/rmt/29st ULT3580-TD4(e) 1300000044 4/0 82F0 500507630019F009 500507630059F009 201 /dev/rmt/30smc 03584L32 0000000T00390401 4/1 805r N/A N/A 206 /dev/rmt/31st ULT3580-TD3 1210003557 7/0 73P5 500507630019F007 500507630059F007 38 /dev/rmt/32smc 03584L32 0000000T00390401 7/1 805r N/A N/A Running in non-global Inst# Special File ------.--------..----------------. An option of ztapelist -z zonename is also provided to show all of the assigned tape devices in a particular zone.---------------.---------------...---------------.--------------. Solaris Tape and Medium Changer Device Driver 135 .Solaris Device Driver (IBMtape) The ztapelist command displays all of the IBM tape devices in the global zone and the tape devices in the non-global zones as shown in the following example. as shown in the following example: Chapter 6. . A reference copy of IBMtape. Note: IBM requires that the Solaris native SCSI tape device driver st be configured so that it does not attempt to support SCSI targets that are controlled by IBMtape. such as the default block size..-----------------200 /dev/rmt/29st ULT3580-TD4(e) 1300000044 4/0 82F0 500507630019F009 500507630059F009 Do you wish to continue to remove the devices from this zone? [y/n]: n Do you wish to continue to remove the devices 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 devices will be removed: softail Do you want to remove all of the tape devices from this zone? [y/n]: y Removing all of tape devices for this zone softail .-----------------. ensure that no IBMtape-owned devices are in use.conf.---------------.----------------200 /dev/rmt/29st ULT3580-TD4(e) 1300000044 4/0 82F0 500507630019F009 500507630059F009 201 /dev/rmt/30smc 03584L32 0000000T00390401 4/1 805r N/A N/A Enter Instance Number (Inst #) of a device to be removed: 201 Removing this tape device /dev/rmt/30smc for this zone camshaft . The working copy of this file is located in the /usr/kernel/drv directory.conf is preserved. Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN ------. During removal of IBMtape.--------.-------.-----------------.-------. certain device characteristics.------------.--------------. if it exists.conf with factory default settings is always installed in the /opt/IBMtape directory. Configuration settings are applied only at start time.. then issue the following: 136 IBM Tape Device Drivers Installation and User’s Guide .----------------. then reloaded into.-------------Do you wish to continue to remove the devices from other zone? [y/n]: n World Wide PN ------------------- Configuration Parameters When using devices controlled by IBMtape. The IBMtape configuration file is named IBMtape.------------------.----------. Refer to “Preventing Conflicts with Other Device Drivers” on page 125 for more information about multiple driver access to a device. you can make the changes effective by restarting the system. the working copy of IBMtape. the working copy of IBMtape. During installation of IBMtape.. These conventions allow configuration settings to remain across updates of IBMtape.---------------. If you change configuration settings in IBMtape.conf is not deleted. or when IBMtape is unloaded manually from. Attention: Failure to prevent more than one device driver from operating the same tape drive may cause system panics or data loss on the tape drive.---------. As an alternative to restarting.-------------.Solaris Device Driver (IBMtape) # /opt/IBMtape/ztapelist -d Issuing this function will remove the tape devices from non-global zone Do you wish to continue? [y/n]: y Do you want to remove the tape devices 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 devices will be removed: camshaft Do you want to remove all of the tape devices from this zone? [y/n]: n Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------. can be controlled through the device driver configuration file. Inst# Special File Device Serial No TGT/LUN Ucode World Wide NN World Wide PN ------.-----------------. memory.-------.conf.------------------. 2 and later /usr/sbin/rem_drv IBMtape /usr/sbin/add_drv -m '* 0666 bin bin' IBMtape /opt/IBMtape/tmd for IBMtape.4. If immediate is set to 1 and rew_immediate is set to 0. On systems with multiple SCSI adapters. The following example shows the stanza for target 0.conf can be overridden for a particular device (and only while the device is kept open) using the ioctl application programming interface (API) of the device driver. The name variable identifies IBMtape as the device driver. The reference IBMtape.conf file supplied with the package contains a stanza for every possible SCSI target and LUN combination supported by IBM tape systems. In Chapter 6.conf the next time the device is opened. with IBMtape’s default configuration parameter values. the setting of rew_immediate is ignored.0.4. Refer to the IBM TotalStorage and System Storage Tape Device Drivers: Programming Reference for more information about changing configuration parameters under program control. and class identifies the type of device supported as SCSI. Thus. The parameter settings made through the API revert back to the default values in IBMtape. After installation of the IBMtape package is complete. which means that SCSI commands Write FM.9.9. a single target/LUN stanza controls the configuration settings for all devices addressed with that target address and LUN. LUN 0. 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. Load-Unload. The target and the lun variables determine the target address and LUN of IBM devices that are controlled by that stanza. LUN 0. The following example shows the stanza for target 0. The parameter immediate is disabled. which causes the SCSI rewind command to return control to the application program before the command actually completes on the tape drive: name="IBMtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 rew_immediate=1 trailer=0 sili=0.0. Solaris Tape and Medium Changer Device Driver 137 . two or more supported IBM devices on the system that have the same target and LUN settings but are attached to different SCSI buses are all affected by the configuration parameters of the single stanza having that target address and LUN. you may eliminate unnecessary probing for devices by commenting out unused target/LUN pairs.conf contains one stanza for each SCSI target address/LUN pair owned by IBMtape.Solaris Device Driver (IBMtape) % % % % /opt/IBMtape/tmd -s for IBMtape.2 and later Default settings in IBMtape. with IBMtape’s default configuration parameter values and the rewind immediate mode set on. IBMtape. Erase. Locate. If you attempt to read or write using an odd-byte-count fixed block size.Solaris Device Driver (IBMtape) this example. Those address/LUN combinations are not probed. the read or write returns -1. then transfer one block’s worth of data per read or write. Remember that modifying a value in the configuration file determines the value of the parameter at device open time. Refer to the appropriate hardware reference manual for additional information. invalid argument. #name="IBMtape" class="scsi" #target=0 lun=0 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0. LUN 1. Table 27. LUN 0 and target 0. but 4097 is not. Table 27 lists and describes the set of configuration parameters recognized by the IBMtape device driver. the value of a parameter can be altered using an ioctl function call. Refer to the IBM Tape Device Drivers: Programming Reference for more information about changing configuration parameters through program control. The default configuration parameters are adequate for most purposes. set block size to 0 (variable block size). which saves time during a restart or manual reload of IBMtape. The maximum supported block size varies for each tape device. Configuration Parameters Recognized by IBMtape Parameter block_size Values (0=variable length) Description This option specifies the device block size that is established with the SCSI Mode Select command during an open function call. the values in the configuration file can be modified to suit the specific requirements of the application or the user. class="scsi" The remaining five configuration parameters specifically affect the behavior of the IBM device or devices associated with that stanza (target and LUN). but the change is effective only while the device remains open. Until this value is changed. For instance. it is not detected. LUN 1 have been commented out. Any other positive value represents a fixed block size. a fixed block size of 4096 or 4098 is allowed. Working configuration parameters revert back to the default values (established by the configuration file) when the device is closed and reopened. 138 IBM Tape Device Drivers Installation and User’s Guide . the stanzas for target 0. If you must read or write odd-byte-count blocks. #name="IBMtape" #target=0 lun=1 #block_size=0 #buffering=1 #immediate=0 #trailer=0 #sili=0. When the device is open. LUN 0 or target 0. However. All of these parameters are specific to tape drive device operation only and have no effect on medium changer device behavior. Variable block size is established using a value of zero. However. it is the working block size. with errno set to 22. if an IBM device is addressed at target 0. Note: IBMtape does not allow odd-byte-count fixed block reads or writes. 1=On) sili (0=Off. However. When physical end of media is reached. this driver error processing results in less than optimum read performance in some scenarios.conf file in the /usr/kernel/drv directory to reflect the change in IBM device support. If immediate is set to 1. the SCSI Rewind command returns with status when the command actually completes on the tape drive. or remove (comment out) a stanza for a device that is no longer supported.Solaris Device Driver (IBMtape) Table 27. regardless of the trailer setting. Erase. The actual number of bytes read is still returned to the application in SILI mode. the effective performance of the device may be degraded seriously. When trailer is enabled. writing records past EOT is allowed by the device driver. If immediate is set to 1. perform the following steps: 1. it returns a check condition status. 1=On) Description When a write command is processed. Solaris Tape and Medium Changer Device Driver 139 . If a tape drive encounters logical end-of-tape (EOT) during a write operation. if a larger block of data is requested than is actually read from the tape. the Rewind command returns with status before the command actually completes. these commands return with status before the command actually completes. Following the first time the write operation notifies the application of EOT. the tape device raises a check condition. 1=On) trailer (0=Off. Buffering can be turned On and Off with this option. Chapter 6. The IBMtape driver does not surface this as an error condition to the application and ultimately returns the actual number of bytes read. and the actual number of bytes written is returned. When SILI mode is enabled. the tape device is forced to Suppress Illegal Length Indication during read operations. during a read operation. Use the pkgrm command to remove the IBMtape package from the system. If trailer is enabled. % /usr/sbin/pkgrm IBMtape Adding or Removing Devices To add support for a new IBM tape system or to remove support for a previously attached IBM tape system. the setting of rew_immediate is ignored. Either add a new stanza to provide support for a device that is to be added. 1=On) rew_immediate (0=Off. Load-Unload. The driver returns 0 bytes written to notify the application of this EOT situation. A check condition is also returned by the tape drive for every subsequent write operation when past EOT. If buffering is disabled. which add overhead to the read operation. Normally. Locate. the SCSI commands Write FM. Buffer flushing (or committing data to the tape) can be controlled by the application through the STIOC_SYNC_BUFFER ioctl function If immediate is set to 0. all write operations fail with a return code of -1. all subsequent EOT notifications are suppressed by the driver. and Rewind return with status when the command actually completes on the tape drive. Configuration Parameters Recognized by IBMtape (continued) Parameter buffering Values (0=Off. because the tape devices cannot take advantage of their buffering optimization. immediate (0=Off. managing the media past EOT is the application’s responsibility. 1=On) Removing IBMtape All active processes using IBM devices supported by the IBM SCSI Tape and Medium Changer Device Driver for Solaris must be stopped in order for the removal procedure to complete successfully. the data is either directly stored on the physical tape or buffered in device hardware. If it is set to set to 1. Edit the IBMtape. This eliminates the error processing performed by the driver and results in improved read performance for some scenarios. The IBMtape device driver must perform error handling procedures. If rew_immediate is set to 0. Running the /opt/IBMtape/tmd command restarts the daemon afterwards to reload the device driver. Hot plugging SCSI devices can cause hardware damage and disruption of reliable system operation.0.0.. when more than one device is configured with the same target address. 10-characters long for LTO drive.Solaris Device Driver (IBMtape) 2. ensure that the target and LUN values in the configuration file stanza match the target and LUN settings of the IBM device. 12-characters long for 359x drive and 16-characters long for changer. then reloading the device driver into kernel memory.4.2 and later The commands to reload the device driver are: % /usr/sbin/add_drv -m '* 0666 bin bin' IBMtape % /opt/IBMtape/tmd for IBMtape.2 and later When the IBMtape device driver is reloaded.4. This is done by first unloading the device driver.9. Plug the new device into the SCSI bus or unplug the existing device from the bus.9. When adding support for a new device.conf located in /usr/kernel/drv.2 and later.. Pay particular attention to proper SCSI cabling and termination. For the version of IBMtape. The serial number can be found running the following command: /opt/IBMtape/tapelist -l 2. the user cannot modify IBMtape. Deconfiguring Tape Devices In some special situations.9. The commands to unload the device driver are: % /opt/IBMtape/tmd -s % /usr/sbin/rem_drv IBMtape for IBMtape. b. exclude_dev_list=”sn1.1.0. 140 IBM Tape Device Drivers Installation and User’s Guide . Deconfigure the tape device using the following: 1.conf to deconfigure some tape devices with IBMtape driver.conf file and acknowledge changes made in the file. Note: It is strongly suggested that the host system and all devices attached to the SCSI bus be powered Off before adding or removing devices from the SCSI bus.9. In IBMtape.” . or the tape devices are attached on the FC or SAS HBA running with Sun HBA driver. 4. Power On and start the host system.sn2. Shut down and power Off the host system. It is possible to reinitialize the IBMtape device driver without restarting the system.4. Where: “sn” is the serial number of the excluded device. the TMD daemon has to be stopped by running the /opt/IBMtape/tmd -s command to unload the IBMtape driver from the kernel. This method can be used to modify configuration parameters. Add the entry of “exclude_dev_list” in IBMtape. 3. it reads the IBMtape. Refer to “Configuration Parameters” on page 136 for more information about the IBMtape. 5.4. Notes: a.2 and later.conf configuration file. a configuration parameter defined exclude_dev_list is introduced to allow users to exclude some devices from the configuration with IBMtape. Re-install IBMtape driver or reboot the system to allow IBMtape update the configuration.sn3.. It also displays the information of HBA with IBM tape drive attachment and the current status of load balancing. The following is an example of a Tapelist Utility Program output.2000/fibre-channel@1 2 lpfc 4 2 /devices/pci@6. Solaris Tape and Medium Changer Device Driver 141 .----------.------.--------------------------– 0 qla2300 4 1 /devices/pci@4. The number of IBM tape drives attached on the HBA. The SCSI target and LUN of the device. A number indicating Fibre Channel World Wide Node Name of the device. The current microcode (firmware) loaded on the device. medium changer and SAN data gateway devices configured with the IBMtape driver.----. The tapelist utility provides the user a listing of tape.2000/pci@1/fibre-channel@4 3 lpfc 1 0 /devices/pci@6. The instance number of the particular HBA assigned by the Solaris system.Solaris Device Driver (IBMtape) Tapelist Utility Program A Tapelist Utility Program called tapelist is installed in the /opt/IBMtape directory as part of the IBMtape package. The device special file used to access this device. The number of IBM tape drives currently using the HBA. A string indicating the HBA device path in the device tree. A number indicating Fibre Channel World Wide Port Name of the device.qla@1/IBMtape@7. # tapelist -L Addr Inst# Special File Device ----.----------.------------. A string indicating the device model and encryption information (e/e: encryption capable/encryption enable).0:st Path Type : N/A # tapelist hba_index --------0 1 2 -t hba_inst hba_driver reg_count usage_count HBA Path -------. # tapelist Instance : 697 Special File : /dev/rmt/6st Device : 03592E05(e/e) Serial Number : 000001300168 TGT/LUN : 7/0 Ucode : 04C4 World Wide NN : 5005076302000127 World Wide PN : 5005076302400127 Dev Phy Path : /devices/
[email protected]–-0000000T003904E5 000001365066 000001326803 3/1 3/0 14/0 806c 1D10 2444 World Wide PN ------------–-- N/A N/A 500507630019F016 500507630059F016 500507630019F019 500507630059F019 Library (/dev/rmt/7smc) Info: 2899 /dev/rmt/7smc 03584L32 0000000T00390401 6/1 265 2898 /dev/rmt/6st ULT3580-TD4(e) 1300000044 6/0 Library 3494 Info: 322 /dev/rmt/10st 03592J1A 000001300147 1/0 806c 82F0 0464 N/A N/A 500507630019F009 500507630059F009 5005076300000000 5005076300400000 The following is a definition of the fields and headers that appear in the previous screens: Inst # Special File Device TGT/LUN Ucode level World Wide NN World Wide PN Dev Phy Path Path Type hba_index hba_inst hba_driver reg_count usage_count HBA Path The instance number of the particular device. A primary or alternate path used for failover. A string indicating the device path in the device tree. The index number of the particular HBA in the HBA list. Serial No: The serial number of the device.2000/pci@1/fibre-channel@5 A new feature is added in tapelist to display the drive information in the library that is running /opt/IBMtape/tapelist -L.------------Library (/dev/rmt/5smc) Info: 2894 /dev/rmt/5smc 03584L22 274 2893 /dev/rmt/13st 03592E05(e/e) 276 2914 /dev/rmt/14st 03592E06(e/e) Serial No TGT/LUN Ucode World Wide NN --–-------------.2000/QLGC. The HBA driver name with IBM tape drive attachment.----. Chapter 6. e0001000/
[email protected]:st lrwxrwxrwx root other 79 Aug 26 18:54 0stb -> /devices/iommu@f. This listing is system dependent. 10000/IBMtape@2. 10000/
[email protected]/
[email protected]@3.e0000000/
[email protected]:stcb lrwxrwxrwx root other 81 Aug 26 18:54 0stcbn -> /devices/iommu@f. Special Files After the IBMtape driver is installed. a set of special files is available for performing input/output (I/O) operations to each supported device.e0001000/QLGC. 10000/IBMtape@2. The special files are created in the /dev/rmt directory.e0001000/QLGC.e0000000/
[email protected]@3. lrwxrwxrwx root other 79 Aug 26 18:54 0smc -> /devices/
[email protected]:stbn lrwxrwxrwx root other 79 Aug 26 18:54 0stc -> /devices/iommu@f. 142 IBM Tape Device Drivers Installation and User’s Guide . 10000/
[email protected]/
[email protected]@3. There may also be entries included for other devices that are not supported by the IBMtape device driver. These minor numbers are accessed through variations of the special file name for that device.e0001000/QLGC.e0000000/
[email protected]/QLGC.e0000000/sbus@f. The following example shows entries returned by this command for a single IBM tape subsystem. Issuing the ls -la /dev/rmt command gives useful information about these device special files.isp@3. but each minor number provides a different function or behavior for the tape
[email protected]:stb lrwxrwxrwx root other 80 Aug 26 18:54 0stbn -> /devices/
[email protected]:stcbn lrwxrwxrwx root other 80 Aug 26 18:54 0stcn -> /devices/
[email protected]/QLGC. 10000/
[email protected]/
[email protected]/QLGC.isp@3. 10000/IBMtape@2. so entries vary slightly in format.0:smc lrwxrwxrwx root other 78 Aug 26 18:54 0st -> /devices/iommu@f. Each tape instance has a set of minor numbers that provides access to the same physical device. 10000/
[email protected]@3. The device special file names created by the IBMtape device driver are similar to the SCSI tape special files generally used on Solaris systems.0:stc lrwxrwxrwx root other 80 Aug 26 18:54 0stcb -> /devices/iommu@f. depending on the operating system and SCSI adapter support. The usage of the tapelist program is as follows: -l -L -c -t -f -h Print for all of the configured devices with the column headers in long list Display the tape drives information in the tape library Don't print column headers in long list for all of the configured devices Display HBA information and current load balancing status Print the list for a particular file only Help menu Running tapelist without any options displays the device information line by line for all of the configured devices. The first and second instances of "e" stand for encryption capable and encryption enable.e0000000/
[email protected] Device Driver (IBMtape) Addr e/e The element address where the drive is located in the library. These special files are actually symbolic links to files created within the /devices subdirectory hierarchy.e0001000/QLGC. isp@3. based on the IBM device type being configured.0:stb
[email protected] 109. isp SCSI adapter device driver). The smc special file does not support the read and write entry points.10000 command presents further information about the same special files.0:stn These entries show the device hierarchy established to support I/O for an IBM SCSI tape system.0:smc
[email protected] 109. Chapter 6.1688 109. through the S-bus.0:stcn lrwxrwxrwx root other 79 Aug 26 18:54 0stn -> /devices/
[email protected]:stn These entries show the major and minor numbers associated with each special file. Here. issuing the ls -la /devices/iommu@f. Only one st type special file for a particular device may be opened at any one time.e0001000/QLGC.1752 109.0:stcn
[email protected]:stbn IBMtape@2. to the IBM device at SCSI target 2 and LUN 0 (supported by the IBMtape device driver). crw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rw1 1 1 1 1 1 1 1 1 bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin 109.Solaris Device Driver (IBMtape) 10000/IBMtape@2. as shown in the following example.e0000000/sbus@f. only the eight st type special files are created. For IBM tape libraries and autoloaders. The attachment path of the device special files spans from the system board.isp@3. The IBMtape device driver decides which types of special files to create during installation. the major number is 109 and identifies to the system that the IBMtape device driver is in support of these special files. For more information on device special files and major and minor numbers. consult the Solaris mtio man pages. 10000/
[email protected]:stcb
[email protected] 109. the actual path information specified in the command varies from system to system.1696 109. For other IBM tape drives. Major numbers are assigned by the system at the time the driver is installed and vary from system to system. With the information from the previous command. the minor number 1696 indicates to the driver that the device was opened by way of the smc special file. The nine different minor numbers are specific to the special file names and are used by the device driver to determine which special file was used to access the device and control the device behavior accordingly. Device Behaviors Certain device behaviors are determined by which special file in the set is opened for device access.e0001000/QLGC. All nine of these special files are associated with the same IBM device (device number 0).0:stcbn
[email protected] 109.0:stc IBMtape@2. The smc special file may be opened concurrently with any one of the st special files. to the Sun F/W SCSI adapter (supported by the QLGC. all nine special files shown previously are created. For example. only a single smc special file is created. For the IBM 3490E Magnetic Tape Subsystem. Again. The smc special file controls only the medium changer portion of the device and accepts only medium changer operations by way of the ioctl entry point.e0000000/
[email protected] Aug Aug Aug Aug Aug Aug Aug Aug Aug 26 26 26 26 26 26 26 26 26 18:54 18:56 18:54 18:54 18:54 18:54 18:54 18:54 18:54 IBMtape@2. Solaris Tape and Medium Changer Device Driver 143 .0:st
[email protected] 109. 5. both st and smc special files accept a limited subset of medium changer commands. Table 28. In such a case. the tape is left positioned exactly where it was following the last block read. Aside from the normal configuration with the medium changer answering as a distinct target/LUN pair. The BSD (b) device special file modifies close behavior for non-rewind devices. invalid argument. and if the last command before closing the device was a read. For the non-rewind special files. Tape drive commands issued to the medium changer fail. If the last operation before closing the device was a write or write filemark. BSD Compatibility (Note 1) N/A No No No No Yes Yes Yes Yes Rewind on Close (Note 2) N/A No No Yes Yes No No Yes Yes Compression (Note 3) N/A No Yes No Yes No Yes No Yes 144 IBM Tape Device Drivers Installation and User’s Guide . The compression (c) device special file determines whether the tape device uses built-in hardware compression while storing data on the tape. it is separated by a single filemark from the previous data. the tapes are positioned between the trailing filemarks before closing. The smc special file is created only for IBM tape systems that provide medium changer capability. and if the last command before closing the device was a read. there is no smc special file created. If the device is opened for no rewind on close in non-BSD mode. 4. Otherwise. 2. IBM SCSI Tape/Medium Changer Special Files for Solaris Special File Name /dev/rmt/[0–255]smc (Note 4) /dev/rmt/[0–255]stn (Note 5) /dev/rmt/[0–255]stcn (Note 5) /dev/rmt/[0–255]st (Note 5) /dev/rmt/[0–255]stc (Note 5) /dev/rmt/[0–255]stbn (Note 5) /dev/rmt/[0–255]stcbn (Note 5) /dev/rmt/[0–255]stb (Note 5) /dev/rmt/[0–255]stcb (Note 5) Notes: 1. consult the appropriate hardware reference to determine whether the drive supports such a configuration. the tape is rewound when the device is closed. The smc special file accepts only medium changer commands. The compression mode of the device can also be set to the desired state programmatically through the STIOC_SET_PARM ioctl. If the device is then reopened and more data is written. If you want to use this nonstandard mode. the smc special file is the only file created because the IBMtape device driver supports only the medium changer portion and does not support the tape drive portion of these devices. For the IBM 3490E Magnetic Tape System. If the device is opened for rewind on close the BSD mode is not relevant. 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. If the device is opened for no rewind on close in BSD mode. then a sufficient number of filemarks is written so that two filemarks follow the data. then the tape is positioned after the filemark immediately following the last block read.Solaris Device Driver (IBMtape) File Naming Conventions Table 28 shows the special file naming convention and the associated device attributes recognized by the IBMtape device driver. The no rewind on close (n) device special file does not rewind the tape during a close operation. with errno set to 22. For IBM tape libraries and autoloaders. some supported devices can be configured with a nonstandard integrated medium changer reporting at the same target and LUN as the tape drive. regardless of the default compression mode established by the special file originally used to open the device. 3. Solaris Device Driver (IBMtape) Persistent Naming Support The device special file names are created by the IBMtape driver in the order that the tape devices are presented by the Solaris system. HBA mapping changes.--------------.2000/pci@1/fibre-channel@5/IBMtape@3. Chapter 6.0 (target 3.0. LUN 0) at the device physical paths of /devices/pci@6. type=ddi_byte:tape. Create the entry for persistent naming. Before the persistent name binding.0.tab system file for the persistent name binding and reloading the IBMtape driver as follows: 1. Add the address and device file name into the entries: type=ddi_byte:tape. The Ultrium-3 tape drive is connected to two Emulex HBAs with the same address of target 3 and LUN 0 via a switch in the following example. follow HBA vendor instructions. # tapelist -l Inst# Special File Device Serial No TGT/LUN Device Physical Path -----. the logical names of devices may be changed due to the swapping of connecting cables. Each device special file name is maintained with the same logical name across reboots.2000/pci@1/fibre-channel@5/
[email protected]/pci@1/fibre-channel@5/
[email protected] and /devices/pci@1f. 2) The 0 in the entry is the zero in M0. Here.-----------. LUN 0 on HBA 2 after device persistent binding.2000/pci@1/fibre-channel@5/
[email protected] /dev/rmt/4st ULT3580-TD3 1136 /dev/rmt/7st ULT3580-TD3 Serial No TGT/LUN --------. You have to use the HBA utility.0 The tape drive is mapped at target 3. a.-------------.---------1210003557 3/0 1210003557 24/0 Device Physical Path ---------------------------------------/devices/
[email protected]/pci@1/fibre-channel@5/
[email protected]=3. or both to persistently bind the tape devices at the different mapped target and LUN. even when an existing device is powered off or not connected. tape device driver updates.0 (target 24 (0x18). Solaris Tape and Medium Changer Device Driver 145 .addr=18. However.0 Note: Device persistent binding is not provided on Sun HBAs. 4st and 7st drives are located at 3.------------. and rmt/10\M0. so this persistent name approach cannot be used with the same physical drive that is attached to multiple Sun HBA ports. # tapelist -l Inst# Special File Device -----. 2.2000/pci@1/fibre-channel@5/
[email protected]. LUN 0) and 18. make sure that the IBM tape devices are configured at the different target and LUN addresses if the devices are attached on more than one HBA. In this example. rmt/10\M0 rmt/11\M0 Notes: 1) A tab is entered between addr=3. Start persistent name binding. or other reasons. LUN 0 on HBA 1 and target 24. Determine the target address from the Device Physical Path in the output of tapelist -l and add the planned device special file name in the entry.0. the user renames 4st and 7st to 10st and 11st.0 582 /dev/rmt/8st ULT3580-TD3 1210003557 3/0 /devices/
[email protected] /dev/rmt/2st ULT3580-TD3 1210003557 3/0 /devices/pci@6. The user can rename the logical name by editing the /etc/devlink.0 /devices/pci@1f. -----------. To disable the CPF support for all of the paths or a particular path.conf file in the directory of /usr/kernel/drv. Run the # devfsadm command without any options to enable IBMtape to create the new device special file name as defined in the entries in /etc/devlink.0 Control Path Failover Support for Libraries Configuring and Deconfiguring Path Failover Support Control path failover (CPF) support is enabled automatically by default when the IBMtape device driver is installed on Solaris system. Add the above entry into the /etc/devlink.0 for the tape drive on the Sun HBA with the path of /devices/pci@1. use the following steps: 1. e.0/tape@w500507630059f007. Run tapelist to list the device special files.------------------------454 /dev/rmt/10st ULT3580-TD3 1210003557 3/0 /devices/pci@6. The device driver supports up to 16 physical paths for single a device. be sure to assign a higher number for the persistent name.tab system file. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ’ 0666 bin bin’ IBMtape # /opt/IBMtape/tmd Primary and Alternate Paths When the device driver configures a logical device with path failover support enabled.---------. no any action is required. the first device configured always becomes the primary path. name=″IBMtape″ class=″scsi″ target=3 lun=1 failover=0.conf file. add and set the failover parameter to off at the beginning of IBMtape. To disable CPF support for all the paths. Remove existing links created by the IBMtape driver from /dev/rmt by running the # rm command.tab.------------. # tapelist -l Inst# Special File Device Serial No TGT/LUN Device Physical Path -----.2000/pci@1/fibre-channel@5/IBMtape@18. The Solaris IBMtape device driver provides a driver configuration parameter failover for you to enable or disable the library control path failover support.Solaris Device Driver (IBMtape) 3) To avoid conflicts with the current device special files assigned by the system automatically. c. b. 4) The address is w500507630059f007.141@1/
[email protected]/pci1022. add and set the failover parameter to off in the path entry in IBMtape. To disable a particular path. 3. When a second or more logical device is configured with path failover support enabled for the same physical device.2000/pci@1/fibre-channel@5/
[email protected] 1136 /dev/rmt/11st ULT3580-TD3 1210003557 24/0 /devices/pci@1f. 2. d. For example. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 4. A system reboot is also required if the tape device is attached on Sun HBA.7450@1/pci1077.0. 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 146 IBM Tape Device Drivers Installation and User’s Guide . it configures as an alternate path. To enable the CPF support for all of the paths. Provide information about which logical devices configured on the system have path failover enabled. Data Path Failover and Load Balancing Support for Tape Drives Note: The tape drive failover feature code must be installed prior to enabling the DPF for IBM Ultrium tape drive in the Solaris IBMtape device driver. refer to Chapter 10. Identify the actual number of physical devices configured on the system and a specific logical device associated with them.Tape Utility Program (tapeutil)” on page 357. “IBM Tape Diagnostic Tool (ITDT). by default. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices with the tapelist utility. it is used to: 1. #tapelist -1 Inst# Special File Device Serial No TGT/LUN Ucode WWNN WWPN Device Physical Path Path Type ---------------------------------------------------------------------------------------------------------------------------------------------------686 /dev/rmt/12smc 03584L32 0000000T0039 1/1 402j N/A N/A /devices/pci@If. There is only one logical device labeled the primary path for each physical device.” on page 255 or “Solaris System .2000/QLGC. Configuring and Deconfiguring Path Failover Support Path failover support for tape drives is not enabled automatically when the device driver is installed. Refer to “Supported Devices and Feature Codes” on page 14 to determine which feature code is required for your machine type.1 Primary 688 /dev/rmt/14smc 03584L32 0000000T0039 2/1 402j N/A N/A /devices/
[email protected]@1/IBMtape@2. there can be multiple logical devices labeled as an alternate path for the same devices.” on page 255 or “Solaris System . 2. Solaris Tape and Medium Changer Device Driver 147 .2000/QLGC. “IBM Tape Diagnostic Tool (ITDT). it remains Chapter 6. However. Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. all the available paths for a physical device are enabled.qla@1/IBMtape@5. It must be configured initially on each logical device after installation.2000/QLGC. Disable and Enable Primary and Alternate Paths Once you install the IBMtape device driver.1 Alt_path_2 Figure 10.1 Alt_path_1 694 /dev/rmt/26smc 03584L32 0000000T0039 5/1 402j N/A N/A /devices/pci@If. Example of Control Path Failover Support Command Output The labeling of a logical device as either a primary or alternate path is for information only.Tape Utility Program (tapeutil)” on page 357. When path failover support is enabled for a logical device.Solaris Device Driver (IBMtape) example in Figure 10.qla@1/IBMtape@1. refer to Chapter 10. Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. To disable a particular path.Solaris Device Driver (IBMtape) set until the device is deleted or the support is deconfigured. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd To disable the support on a single logical device. 148 IBM Tape Device Drivers Installation and User’s Guide .. a729e60f7b118460". to enable a particular path. DPF keys do not need to be added in IBMtape. The parameter dpf_keys is in the format “key1." and a space " ". key3. For the IBM Ultrium tape drive.conf file.. b. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 3. . To enable the support globally on all currently configured devices.conf file.conf file. To enable the support globally on all currently configured devices. The IBMtape driver supports up to 36 dpf keys..conf file. 3. For example. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 5. Or. remove or comment out the entry dpf_support=1 at the beginning of the IBMtape. add the parameter dpf_support and turn it off in the path entry in the IBMtape. add an entry dpf_support=1 at the beginning of the IBMtape. logical paths to a device with the support enabled. Each key is 16 characters long with a comma ". It may be desirable at times to configure some. # dpf_support=1. The path failover setting is retained even if the system is rebooted. following these steps: 1. key2. name="IBMtape" class="scsi" target=3 lun=0 dpf_support=0.conf file. you need to enter the DPF feature key(s) in the parameter dpf_keys at the beginning of the IBMtape. Notes: a. 4. name="IBMtape" class="scsi" target=3 lun=0 dpf_support=1. but not all. and reboot the system or deconfigure and reconfigure all devices.. C7A0B9ef2c1a4360. ”. 2.conf file. * comment out the parameter 2. such as dpf_support=1.conf file in the directory /usr/kernel/drv. 2. add the parameter dpf_support and turn it on in the path entry in the IBMtape. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd This deconfigures all devices to remove or comment out the parameter dpf_support in the IBMtape.. or it can be enabled or disabled selectively by logical device.conf if you are running the latest drive code on Ultrium-3 and Ultrium-4 drives. add an entry of dpf_support=1 at the beginning of the IBMtape. For example. For example. such as dpf_support=1. Path failover support can be enabled on all configured devices at one time. 1. To disable the support globally on all currently configured devices. Follow the above steps to enable the DPF support: 1. For example: dpf_keys="A729E60F7B119411. FCR@2/IBMtape@1. Provide information about which logical devices configured on the system have path failover support enabled. the /opt/IBMtape/tapelist command output is similar to the example in Figure 11. then 5st (port 1). Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd Primary and Alternate Paths When the device driver configures a logical device with path failover support enabled.4000/JNI.0 Alt_path_2 670 /dev/rmt/21st 03592J1A 000001300168 3/0 04CE 5005076302000127 5005076302400127 /devices/pci@1f. WWPN 5005076302400127 from port 0 and 5005076302800127 from port 1). However. it configures as an alternate path. For example. There is only one logical device labeled the primary path for each physical device. if 0st (port 0 of 3592) is configured first. 18st (port 1) and 21st (port 0) to the two HBAs through a switch (here.2000/QLGC. there may be many (multiple) logical devices labeled as an alternate path for the same devices. Querying Primary and Alternate Path Configuration You can display the primary and alternate path configuration for all devices with the tapelist utility.FCR@2/
[email protected] Alt_path_3 Figure 11. Solaris Tape and Medium Changer Device Driver 149 .Solaris Device Driver (IBMtape) 3. When a second logical device is configured with path failover support enabled for the same physical device. 2. A third logical device is configured as the next alternate path. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 4. Example of Data Path Failover Support Command Output The labeling of a logical device as either a primary or alternate path is for information only.2000/QLGC.4000/JNI. in order to: 1. #tapelist -1 Inst# Special File Device Serial No TGT/LUN Ucode WWNN WWPN Device Physical Path Path Type ------------------------------------------------------------------------------------------------------------------------------------------------------685 /dev/rmt/0st 03592J1A 000001300168 1/0 04CE 5005076302000127 5005076302400127 /devices/pci@1f.” on page 255 or “Solaris System . Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. Chapter 6.0 Alt_path_1 666 /dev/rmt/18st 03592J1A 000001300168 1/0 04CE 5005076302000127 5005076302800127 /devices/
[email protected]@1/IBMtape@7. the first device configured always becomes the primary path. refer to Chapter 10. “IBM Tape Diagnostic Tool (ITDT).0 Primary 697 /dev/rmt/5st 03592J1A 000001300168 7/0 04CE 5005076302000127 5005076302800127 /devices/
[email protected] Utility Program (tapeutil)” on page 357. The device driver supports up to 16 physical paths for a single device. Be able to identify the actual number of physical devices configured on the system and a specific logical device associated with them. and so on.qla@1/IBMtape@1. When set to ON. run commands to disable and then later enable the primary and alternate paths. an application can not open a tape drive using the append mode.Tape Utility Program (tapeutil)” on page 357 System-Managed Encryption Device Driver Configuration System-Managed Encryption can be set on global or a specific tape drive in IBMtape. When set to CUSTOM. Note: See Chapter 10. all the available paths for a physical device are enabled. 150 IBM Tape Device Drivers Installation and User’s Guide . # System Encryption for Write Commands at BOP 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. the tape drive uses encryption for both read/write operations.conf: sys_encryption_write=1. When set to OFF.” on page 255 or “Solaris System . The custom setting is intended for applications using system-managed encryption to control write encryption without device driver intervention. write operations do not use encryption.conf in /usr/kernel/drv. the device driver does not modify current tape drive setting. “IBM Tape Diagnostic Tool (ITDT).Solaris Device Driver (IBMtape) Disable and Enable Primary and Alternate Paths Once you enter the parameter dpf_support in the IBMtape. If it is necessary to disable a path and not perform path fail over (for example due to maintenance). Note: If sys_encryption_write is set to ON. the tape drive uses encryption for read operations. The sys_encryption_write parameter controls if the device driver can set the tape drive to encryption enabled for write commands. 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 device driver system-managed encryption for a tape drive by setting the value to ON (default set).conf file and install the IBMtape device driver. The parameter is set to “CUSTOM” by default. To make a global setting to enable SME in IBMtape. Yes Encryption Method ..Solaris System-Managed Encryption 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. Following is an example of a correct tape drive configuration with sys_encryption_write set to “on”.. The second test runs a basic diagnostic that checks the tape drive to server communication and reports success or fail.. Note: See “Solaris System . System Encryption State. This test can be run using the tapeutil menu in the option “EKM Test” or the command line “tapeutil –f/dev/rmt/device_special_file ekmtest”. Encryption settings: Encryption Capable . Solaris Tape and Medium Changer Device Driver 151 . Note: See “Solaris System .. # tapeutil -f /dev/rmt/38stn encryption GET_ENCRYPTION_STATE command succeeded... ON Testing Data Encryption Configuration and Connectivity There is a tapeutil command added to validate the ibmekm. If the sys_encryption_write parameter is set to “no”..Tape Utility Program (tapeutil)” on page 357 for information on the tapeutil application. The first test checks the server configuration defined in the ibmekm. The current tape drive encryption settings can be queried using the tapeutil menu with the option “Get Drive Encryption Settings” or the command line “tapeutil –f /dev/rmt/device_special_file encryption”. Following is an example of a successful test: Chapter 6. This test reports back the number of servers available..conf file and then communication to the configured servers.... Querying Tape Drive Configuration There is a tapeutil command available for encryption to query tape drive encryption settings.conf file server entries and test tape drive to server connectivity operations.Tape Utility Program (tapeutil)” on page 357 for information on the tapeutil application. then the tape drive “Encryption State” is Off. The third test runs an enhanced diagnostic that checks a key operation between the tape drive and server then reports success or fail.. “Permission denied” .x. Check and correct.Tape Utility Program (tapeutil)” on page 357 for information on the tapeutil application..If the full drive to server encryption test fails with a permission error . Problem Determination The following sections describe the service and diagnostic aids that are part of the IBM SCSI Tape and Medium Changer Device Driver for Solaris package. Enter this command to verify installation was successful /usr/bin/pkginfo IBMtape The following information should be displayed: system IBMtape IBM SCSI Tape & Medium Changer Device Driver x. basic problem determination guidelines. 3. 2. To verify that device driver support for a specific IBM tape system attached to the system is functioning correctly. then the remaining tests are not run. Test complete. 4.x is the version of the device driver.x. Procedures for verifying correct installation of the device. 2..x. Set sys_encryption_write to “ON” in IBMtape. follow these steps: 1.. Test complete. If sys_encryption_write can not be set then the tape drive is not encryption capable or encryption support disable.Solaris System-Managed Encryption # tapeutil –f /dev/rmt/38stn ekmtest Testing server configuration and connections.. Field Support Information When encryption failures require field support and/or development analysis. run /opt/IBMtape/diags_info script to generate a file of diags.conf for the tape drive. Note: See “Solaris System .x.conf file are currently running on the server IP address and configured correctly. check if either the EKM server isn’t available recently or the drive isn’t claimed in EKM server. Check all servers configured in the ibmekm. “Network is down” – All configured servers in the ibmekm.Either the ibmekm.conf file is missing or is invalid. Tape drive dumps and EKM server logs may be needed in addition to this information.x Where: x. If the problem is persistent. and outlines of the utility program included with the IBMtape package are included. servers available 2 Running basic drive to server encryption test. Perform the recommended problem determination to resolve the problem: 1. Functional Verification If you wish to verify that the installation of the IBM SCSI Tape and Medium Changer Device Driver for Solaris package was successful.out. completion code 0 Running full drive to server encryption test.System encryption is not configured for the tape drive in the device driver. “Can’t assign requested address” . enter the following command: /opt/IBMtape/tapeutil -f /dev/rmt/nst -o chk -v 152 IBM Tape Device Drivers Installation and User’s Guide . unload the tape and run the command again. Test complete. “Invalid argument or Operation not supported on device” ... completion code 0 If the first server test fails with one of the following errors.conf file are not available. 4. it indicates that the IBMtape device driver was not loaded because it did not detect the presence of any supported IBM devices on the SCSI bus. even no any tape device is attached on the system. Warning: Driver (IBMtape) configuration failed.Solaris Device Driver (IBMtape) substituting for n the number associated with the device special file assigned to the IBM tape system that you want to check. It is designed to run concurrently with the IBMtape driver and to automatically retrieve and store the IBM tape drive diagnostic information (drive dump) into the /var/opt/IBMtape directory.0. v If you receive the following message during installation: drvconfig: System call 'modctl_modconfig' failed: No such device or address. verify that you are using the correct special file. For medium changer devices. Ensure that the Sun native tape device driver (st) is not contending for the same IBM device by consulting the st. size. enter the following command: /usr/sbin/modinfo | /usr/bin/grep IBMtape The following information should be displayed: 165 f5f10000 15c0s 109 1 IBMtape (IBM SCSI Tape/Medium Changer DD) The first five fields shown probably do not match your specific output. If you cannot solve the problems after checking the following. Solaris Tape and Medium Changer Device Driver 153 . the special file name /dev/rmt/nsmc should be used. An entry ″ name=″IBMtape″ parent=″pseudo″ instance=16383. Verify that the IBM tape subsystem is connected properly to the SCSI bus. Tape Monitor Daemon (tmd) The Tape Monitor Daemon is introduced in the version of IBMtape. the following information may be of assistance. load address. To verify that the IBMtape device driver is loaded in kernel memory. and online. contact the appropriate IBM service representative. major number.9. The fields indicate the ID.conf file in the /kernel/drv directory and commenting out conflicting stanzas. It is not necessary for the tape drive to have a cartridge loaded to be recognized by the IBMtape device driver.conf automatically for the daemon during the IBMtape driver installation. The IBM tape special files are of the form *st* in the /dev/rmt directory. System could not install driver. v If you cannot open an IBM device. Listing the contents of the /dev/rmt directory (using the ls command) can be helpful in determining the proper special file name. Where: xxxxxxxx is the model number of the IBM tape system and n is the same number specified in the verify command. 3. and revision for the IBMtape device driver and vary from machine to machine Installation Problems If you are experiencing problems with installation of the IBM SCSI Tape and Medium Changer Device Driver for Solaris package.2 or later. The IBM medium changer special files are of the form *smc in the /dev/rmt directory. The daemon is automatically started when the driver is installed. Chapter 6. ″ is also entered into the configuration file of /usr/kernel/drv/IBMtape. powered On. The following information should be displayed: IBM xxxxxxxx configured at /dev/rmt/nst. Verify that SCSI adapter device driver support is installed and configured correctly. The file name of dump presents some useful information. the tmd only writes status information to the syslog file of /var/adm/messages.conf configuration file. This option is enabled by default. A message is also logged in the syslog file of /var/adm/messages after a drive dump is retrieved by tmd. Turn off compression. Restart the tape monitor daemon and reload all configuration settings. Most options can also be specified in the /etc/tmd. Turn off drive error diagnostic retrieval and storage. so trace level 3 also posts items for levels 2. Table 29. Default directory is /var/opt/IBMtape <filename> Specify a file for writing daemon related log messages. 2004-04-09-14:54:14 is the time stamp for the dump retrieval. 1. Tracing Facility IBMtape incorporates a tracing facility that is useful for performing problem determination. <directory> Specify an alternate directory for the storage of drive diagnostic information. Most options can also be specified in the /etc/tmd. The following options can be used to configure the tape monitor daemon running it on the command line.000001300148.dump. and 0. However. For installations with extremely small /var file systems.conf configuration file. However. Apr 9 14:54:21 Java tmd[3279]: Drive dump saved to /var/opt/IBMtape IBMtape.2004-04-09-14:54:14. the command line options override any configuration file options: -s -r -d -D -p -l -y -z Stop any currently running instance of the tape monitor daemon.2004-04-09-14:54:14. Device sense data. For example.Solaris Device Driver (IBMtape) The following options can be used to configure the tape monitor daemon running it on the command line. Tracing Facility Trace Level 0 Items Traced Severe error conditions only. the command line options override any configuration file options. By default. The tracing facility logs diagnostic information to /var/adm/messages based on the control variable IBM_trace. 1 154 IBM Tape Device Drivers Installation and User’s Guide . Sense data can help in diagnosing the source of unexpected error conditions.000001300148. with little or no degradation of throughput. IBM_trace values of 4 and higher increasingly degrade performance and should generally be used only when directed by IBM support personnel.dump. Postings are cumulative. Turn on drive error diagnostic retrieval and storage.gz Here. this may be at the cost of not recording messages related to serious device or system environment errors. An example of the dump file is: IBMtape. 000001300148 represents the serial number of the tape device. Refer to “Setting the IBM_trace Level for Static Tracing” on page 156 for instructions on how to set the trace value. IBM_trace values range from 0–13 and result in posted messages as shown in Table 29. Turns off writing log messages to syslog. this setting can prevent filling the file system unexpectedly. By default. the tmd will use a form of file compression to reduce the size of stored diagnostic information. A trace value of 2 or 3 is suitable for most normal production environments. However. Decoded SCSI command. Minor 9412 (drv). The Sense Key/ASC/ASCQ shows that a filemark was encountered during the space.conf take effect after the next system restart. including IBMtape trace messages. Tracing Facility (continued) Trace Level 3 4–13 Items Traced Device opens and closes. with system date and time stamps removed. key/asc/ascq 0x0/0/1.conf to redirect system error messages. sense key.0. Solaris Tape and Medium Changer Device Driver 155 .8 IBMtape(390) check_sense: cmd 0xa5(move_medium). are placed in /var/adm/messages. Minor 12450 (smc).conf man page and the comments in syslog. ASC and ASCQ for sense data. rc 22 IBMtape(390) 03590B11 SENSE DATA: IBMtape(390) 70 0 5 0 0 0 0 58 0 0 0 0 3b e ff 2 IBMtape(390) 0 20 1 40 a 9 1 0 0 0 0 0 0 0 a5 0 IBMtape(390) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 last message repeated 1 time IBMtape(390) 0 0 0 0 0 0 0 0 36 33 39 20 20 20 20 0 IBMtape(390) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IBMtape(390) _close: Inst 390.2. Changes made to syslog.0. defer 0. Device instance 390 is opened on the first line. followed by a repeat count. Refer to the syslog. rather than printing multiple sixteen byte lines of hexidecimal zeroes. Minor 9412 (drv). Increasingly verbose tracing information. we find that the command failed because the move from location was empty. Minor 12450 (smc). retry 0. If your installation has modified /etc/syslog. The second line decodes selected fields from the sense data that follows it. Message content and selection differed significantly from current IBMtape versions. Note: Solaris. Flags 0x5. Flags 0x5.8 IBMtape(292) check_sense: cmd 0x11(space). system error messages. exit(0) In the next example. Flags 0x5. The device minor number 12450 is decoded and shows that the SCSI medium changer (smc) special file was opened. The following shows trace level 2 output. These tracing levels are generally useful only to IBMtape developers.0. By default. Looking up the decoded Sense Key /ASC/ASCQ combination in the 3590 hardware reference. The decoded information shows that sense data was generated during a Move Medium command.7 had only IBM_trace values 0–4. the device open line shows that a tape drive (drv) device special file was opened. rc 5 IBMtape(292) 03570B02 SENSE DATA: IBMtape(292) f0 0 80 0 0 0 1 48 0 0 0 0 0 1 ff a IBMtape(292) c4 b1 0 20 0 5 1 91 0 34 0 0 0 0 11 0 IBMtape(292) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 IBMtape(292) 6f 28 0 ad 73 32 0 0 0 0 0 0 0 0 0 0 IBMtape(292) 0 0 0 0 0 0 20 0 31 42 41 20 20 20 20 0 IBMtape(292) _close: Inst 292. retry 0.2.Solaris Device Driver (IBMtape) Table 29. 4. TL 2/0/0.2. TL 2/0/0. The sense data for device instance 292 was generated during a space operation. key/asc/ascq 0x5/3b/e. exit(0) Chapter 6. The actual sense data follows the decoded fields. IBMtape(292) _open: 554 Inst 292.conf for information about the system logging operation. Note: IBMtape earlier than Version 4. IBMtape(390) _open: 374 Inst 390. defer 0. Flags 0x5. IBMtape tracing is handled as other kernel messages. 4. prints only the first such line. /devices/pci@6. occurred during a test unit ready and indicates that no tape is loaded in the drive. /dev/rmt/8stb. Use the tapedtrc program from the command line as follows: /opt/IBMtape/tapedtrc options: [set] [set] level [get] [start] [stop] [clean] [help] [option] Set IBMtape trace level and/or start the tracing Set trace to a particular trace level Query the current IBMtape trace level Start IBMtape tracing Stop IBMtape tracing without the trace level reset Stop the IBMtape tracing and reset IBMtape trace level to 0 .4.0" 292 "IBMtape" 2.0" lrwxrwxrwx 1 root other 48 Aug 26 11:49 8st -> . 4.1/
[email protected] or later driver to dynamically set. Minor 7366 (drv). Minor 7366 (drv). a tape drive. rc 5 IBMtape(230) 03570B02 SENSE DATA: IBMtape(230) 70 0 2 0 0 0 0 48 0 0 0 0 3a 0 ff 2 IBMtape(230) c4 8 0 30 0 6 1 40 0 0 0 0 0 0 0 0 IBMtape(230) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 last message repeated 1 time IBMtape(230) 0 0 0 0 0 0 0 0 31 42 41 20 20 20 20 0 IBMtape(230) _close: Inst 230. Find the instance number in /etc/path_to_inst: $ grep 292 /etc/path_to_inst "/
[email protected]/scsi@2. retry 0. If the tracing is enabled or disabled using the adb command. The program is located in the /opt/IBMtape directory.IBM tapedtrc help menu Setting the IBM_trace Level for Static Tracing The user can still enable or disable static IBMtape tracing and set the IBM trace level in /etc/system or by running the adb system command. List long the contents of /dev/rmt and search for the path name you found in the previous step: $ ls -l /dev/rmt | grep "/
[email protected]:st lrwxrwxrwx 1 root other 49 Aug 26 11:49 8stb -> . and so on..0:stb In this example.4000/scsi@2. IBMtape(230) _open: 728 Inst 230. are symbolic links to the device special files that are associated with device instance 292.2../. with the tracing level set to 0 by default. defer 0.. the tracing starts or stops at the next device open.. exit(0) You can match an instance number with its corresponding device special file in two steps. /dev/rmt/8st. The IBMtape driver must be loaded in the kernel. key/asc/ascq 0x2/3a/0. TL 2/0/0./. Flags 0x5./devices/pci@6. The host is required to reboot to enable or disable the tracing when the trace level is set in /etc/system. 156 IBM Tape Device Drivers Installation and User’s Guide .1/IBMtape@2. stop and query IBMtape tracing at any time for debugging use. 1.Solaris Device Driver (IBMtape) Finally. Flags 0x5. Dynamic Tracing Utility A dynamic tracing utility named tapedtrc is introduced in the IBMtape. the sense data for device instance 230.4000/
[email protected]/
[email protected] IBMtape(230) check_sense: cmd 0x0(test_unit_ready). reset.1/
[email protected]/IBMtape@2. start. You can define another IBM_trace value by placing an entry in /etc/system. which reports I/O statistics for the supported tape drives in IBMtape. gathers important system HBAs and configuration information. In this sample session. Commands that you enter are in boldface. iostat Command IBMtape driver supports the iostat system command. adb> $q # # Back to the shell. Explanatory comments follow pound signs (#) or exclamation and pound sign pairs (!#). To facilitate capture of data. Refer to man (1M) iostat for the command usage. Send the output file to the location identified by your IBM service representative. 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. adb> IBM_trace/u IBM_trace: IBM_trace: 0 !# !# Set new IBM_trace value.out in the directory locating the script. ksh> adb -P "adb> " -k -w /dev/ksyms /dev/mem physmem 7c5e !# !# Set default for input values to base 10. Chapter 6. # # Start adb session and set session prompt. adb> IBM_trace/w 2 IBM_trace: 0 = 2 !# !# Quit session. it affects tracing during driver loading. initialization. the script places information in a file called diags. and adb> is the adb session prompt. This script detects the problems on the configuration files. the information should be labeled as such. If not run as root. ksh> Running Diags_info Script Run the diags_info script located in the /opt/IBMtape directory.7 and later versions. For example.1. ksh> is a shell prompt.4. but the value of the information is degraded when run as a non-root user. the trace value that is set is active only during driver operation. adb> a$d radix=10 base ten !# !# Display current IBM_tape value as unsigned decimal integer. and operation.2. You may also set or modify the IBM_trace value manually in an adb session. !# adb will confirm the old and new values. Text lines without a prefix are adb session responses to commands. The script should be run as root. so that IBM_trace is set at each restart. Solaris Tape and Medium Changer Device Driver 157 . Because the driver must already be loaded and initialized before using this method.Solaris Device Driver (IBMtape) The default value for IBM_trace is zero (0). log_reserve: Reservation Conflict: read full status failure (rc 16) 3. The information is logged when the drive is reserved but the host reservation information isn’t available. the device driver will log this information in the detail data below. If successful. The information is logged when the drive is reserved with a SCSI-2 Reserve.Solaris Device Driver (IBMtape) Reservation Conflict Logging When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the Solaris system log of /var/adm/messages. After initially logging the reserving host WWPN. subsequent reservation conflicts from the same reserving host WWPN and reservation key will not be logged to prevent multiple entries in the system log until either the reserving host WWPN or reservation key is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs. log_reserve: Reservation Conflict: No reserving host information is available. Here are the log examples: 1. 158 IBM Tape Device Drivers Installation and User’s Guide . Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name) and reserve key. log_reserve: Reserving host key 46E48C49413E6EB1 WWPN 210000E08B118BB1 2. The information is logged when the drive is reserved with a Persistent Reservation. . . . . Querying Tape Drive Configuration Settings . . . Device Driver Configuration . . Installation and Configuration Instructions . . . . . . Product Requirements . . . . . . . . . . . . . . . . . . . . 159 159 160 160 161 161 161 Data Path Failover Support for Tape Drives . System-Managed Encryption . . . . . . . . . . . . . . . . Querying Primary and Alternate Path Configuration . . . . . Figure 12. . . . . . . . . . . . . . . . . Checking Disablement of Data Path Failover Setting. . . . 178 This chapter describes the hardware requirements. . 173 . . . Data Flow . . . Reservation Conflict Logging . . . 178 . Windows 2000/Windows Server 2003/Windows Server 2008 Instructions . . . . . . software requirements. . . . . . . . . . . . and installation notes for the Microsoft Windows device drivers for IBM TotalStorage and System Storage tape devices. . . . . . Persistent Naming Support on Windows Server 2003 and Windows Server 2008 . . . the driver is designed to take advantage of the device features transparent to the application Data Flow The software described in this chapter covers the Windows device driver and the interface between the application and the tape device. . Hardware Requirements. . . . Windows NT Instructions . . as well as to the advanced functions needed by full tape management systems. Windows Server 2003. . . . . . . . Configuration File . . Querying Primary and Alternate Path Configuration . . . . . . . . . . . . . . . Problem Determination . . . . . . . . . Data Flow for Windows Device Driver (IBMmag) a250181w Application Program Windows Tape and Medium Changer Device Driver Host Bus Adapter Driver Tape Device © Copyright IBM Corp. . . . . . . .Chapter 7. The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges). . . . and Windows Server 2008 Instructions . . . . 179 179 179 179 180 180 180 181 181 181 182 184 . . . 2009 159 . Purpose The Windows tape and medium changer device driver is designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. 2007. . . . . . . . . . . . Configuring and Unconfiguring Data Path Failover Support . . . . . . . . . Windows Tape and Medium Changer Device Driver Purpose . . . . . . . . . . Windows 2000. Software Requirements . . Figure 12 illustrates a typical data flow process. 178 . . . 177 178 . . . . Control Path Failover Support for Tape Libraries Configuring and Unconfiguring Control Path Failover Support . . . . . . . Whenever possible. . Windows NT Instructions . . Checking Disablement of Control Path Failover Setting. . Hardware Requirements One of more of the following processors is required by the IBMtape device driver: v For the Windows NT® operating system.software. v For the Windows 2000.com/storage/devdrvr/Windows. a 32-bit Intel compatible processor. and Windows Server 2008 operating systems. which is located at ftp://ftp. v For the Windows Server 2003 and the Windows Server 2008 operating systems.ibm. a processor that supports extended 64-bit architectures (Intel EM64T and AMD64).Windows Device Driver Product Requirements The most current information on supported hardware and software configurations for the Windows tape and medium changer device driver can be found in the README files on the IBM Device Drivers FTP site. Intel compatible processors with a minimum processor level of Intel 486DX or Pentium®.Single Port LVD v Adaptec SCSI Adapter 39160 . One or more of the following SCSI host adapters: v Adaptec 2940U2W or IBM P/N 33L5000 for IBM System x (also known as xSeries®) (LVD) v Adaptec 2944UW (HVD) v Adaptec SCSI Adapter 29160 or IBM P/N 19K4646 for IBM System x (also known as xSeries) . v For the Windows Server 2003 and the Windows Server 2008 operating systems. a 64-bit Itanium processor. Windows Server 2003.Dual Port LVD v Adaptec SCSI Card 39320-R (LVD) and 39320D-R (dual port LVD) v Adaptec SCSI Card 29320ALP or IBM P/N 13N2249 (LVD) v Symbios SYM22910 64-bit PCI-to-Ultra-2 SCSI Dual Channel Host Adapter (LVD) from LSI Logic Corporation v IBM Ultra320 SCSI Controller 2 P/N 13N2249 (SCSI LVD) v IBM Ultra320 SCSI Controller 2 P/N 39R8743 (SCSI LVD) One or more of the following SAS host bus adapters: v LSI Logic SAS3800X SAS Adapters v IBM SAS Host Bus Adapter Controller Part Number 25R8060 One or more of the following Fibre Channel host bus adapters: v IBM xSeries and Netfinity® FAStT Host Adapter P/N 19K1246 v IBM xSeries and Netfinity FAStT Host Adapter P/N 24P0960 v DS4000™ FC 4Gbps PCI-X Single Port HBA P/N 39M5894 v DS4000 FC 4Gbps PCI-X Dual Port HBA P/N 39M5895 v QLogic 4Gb FC Single-Port PCIe HBA P/N 39R6525 v QLogic 4Gb FC Dual-Port PCIe HBA P/N 39R6527 v Qlogic QLA2310 v Qlogic QLA2340 v v v v Qlogic Qlogic Qlogic Qlogic QLA2342 QLA2460 QLA2462 QLE2460 (not supported for Windows 2008 SPI for IA64 servers) 160 IBM Tape Device Drivers Installation and User’s Guide . LP11002 Fibre Channel Adapters v IBM Netfinity P/N 00N6881. QLA2342L. Select Start. Verify that the prerequisites have been satisfied. QLA2340. QLA2342L. 39M5894. Windows NT Instructions This section describes how to install. IBM is focused on assuring server and storage configuration interoperability. 3. LP402DC. remove. stability problems have been observed. QLA2342. 2. LP952L. start. 4. and Find from the Windows NT desktop. or v Microsoft Windows Server 2003 Build 3790 or later v Microsoft Windows Server 2008 SP1 Build 6001 or later Installation and Configuration Instructions This section includes instructions for installing and configuring the Windows tape and medium changer device driver on Windows NT and Windows 2000/Windows Server 2003/Windows Server 2008. Connect the TotalStorage/Magstar or Ultrium device to the adapter. QLA2462 Fibre Channel Adapters v Emulex LPe11000/2 4Gb PCI-E FC HBA. Install the SCSI or FC adapter device driver. Installation Overview The installation process consists of the following steps: 1. 39M5895 Attention: Using a single Fibre Channel host bus adapter (HBA) for concurrent tape and disk operations is not recommended. 7. Under stress conditions (high I/O rates for tape. Windows Tape and Medium Changer Device Driver 161 . 6. LP11000. LP9802. These issues are resolved by separating disk and tape I/O streams onto separate HBAs and using SAN zoning to minimize contention. 19K1246. LP9802DC. 24P0960. Type Emergency in box 1. It strongly recommends that your implementation plan includes provisions for separating disk and tape workloads. Tape and disk devices require incompatible HBA settings for reliable operation and optimal performance characteristics. LP8000 and LP9002L. disk. LP10000. 5. Help. QLA2310FL. and stop the Windows tape and medium changer device driver on Windows NT. QLA2340L. Software Requirements The software requirements are supported: v SCSi or FC adapter device driver v Microsoft Windows NT Version 4.Windows Device Driver v Qlogic QLE2462 (not supported for Windows 2008 SPI for IA64 servers) One or more of the following FC-AL host bus adapters: v Qlogic QLE2460/2 4Gb PCI-E FC HBA. b. or both) where disk and tape subsystems share a common HBA. Chapter 7. Install the SCSI or FC adapter. Create an emergency repair disk (optional) using the following procedure: a. Power On the TotalStorage/Magstar or Ultrium device. QLA2460. LP1150. Reboot the system.0 with Service Pack 6 or later v Microsoft Windows 2000 Build 2195 or later. Log on as Administrator. a. Go to the directory in which you saved the . If you select custom installation.exe 3. Install the TotalStorage/Magstar or Ultrium tape device driver. 162 IBM Tape Device Drivers Installation and User’s Guide . select IBMMag. Click Display. which includes copying all available versions included in the InstallShield package to a user defined directory. Note: This option overwrites any previous versions of the TotalStorage/Magstar or Ultrium device driver installed on your system. If you select typical installation. the program allows you to select the components to install. b. 4. then follow the instructions to make an emergency repair disk (ERD).WinNT. Also. which is located at ftp://ftp. follow this procedure: 1. Note: This option overwrites previous versions of the TotalStorage/Magstar or Ultrium device driver installed on your system.ibm. Follow the InstallShield directions to install the package.Windows Device Driver c. d.software. Refer toFigure 13 on page 163. If you select compact installation. Download the appropriate driver from the IBM Device Drivers FTP site. Installation Procedure To install the device drivers. This step is highly recommended.exe file and double click it. Select Using the Repair Disk utility to make an emergency repair disk. the program copies the system files of the latest IBM TotalStorage/Magstar or Ultrium Device Driver (Device Driver System Files component) to the system directories. select IBMUltrium.WinNT. 8. Note: Refer to “Software Requirements” on page 161.exe v For Ultrium tape devices. the Device Driver Depot component is installed. 2. c. v For TotalStorage or Magstar tape devices.com/storage/devdrvr/Windows/ WinNT. This provides the latest support necessary for TotalStorage or Magstar devices. all support included in the compact installation is done. Chapter 7. After you have completed installing the device driver.WinNT. move to Settings. If you install this component. The Documentation component copies the PDF version of the Installation and User’s Guide and the Programming Reference to your hard drive. Refer to Figure 14 on page 164.exe) The Device Driver Depot component includes the most recent versions of the device drivers. The Device Driver System Files component copies all the files needed for device driver support to the system directory. you are able to select which versions of the device drivers to install. Windows Tape and Medium Changer Device Driver 163 .Windows Device Driver Figure 13. enable the driver. 5. Click Start. Select Components Menu (using IBMUltrium. then click Control Panel. Creating Driver List If Microsoft Windows NT did not detect the attached TotalStorage or Magstar device. If the TotalStorage/Magstar or Ultrium tape or changer device was already powered On and attached to the system during boot up. Figure 16. and Windows NT should start to generate the driver list. click Detect to select the device. Refer to Figure 15. the devices should appear in the box. Start Menu 6. Figure 15. and Microsoft Windows NT rescans the bus. Refer to Figure 16. Double-click Tape Devices.Windows Device Driver Figure 14. Rescanning for Tape Device 164 IBM Tape Device Drivers Installation and User’s Guide . Select Cancel.. Figure 17.. Cancel the multiple driver installation requests. Click Drivers. then click Add. Install Driver Menu . the device is powered On. Refer to Figure 18 on page 166. and the adapter driver is enabled.. Also. Chapter 7. the operating system prompts multiple times for the same driver.Windows Device Driver If you still cannot see the device. ensure that the device is terminated properly. ensure that the cable is attached properly. Windows Tape and Medium Changer Device Driver 165 . If you have more than one IBM TotalStorage/Magstar or Ultrium device attached on the same host system. skip to step 8 on page 167. Refer to Figure 19 on page 167. You can also Browse. 166 IBM Tape Device Drivers Installation and User’s Guide . to select the directory. If you installed the Device Driver System Files component in step 4 on page 162.. Tape Devices Menu 7. click Have Disk.inf) is located in the box labeled Copy manufacturer’s files from:. then enter the directory where your device driver setup file (IBMUltrium..inf or IBMMagstar. If you did not install Device Driver System Files component.Windows Device Driver Figure 18. Windows Tape and Medium Changer Device Driver 167 . Note: If you are using both a tape drive and a medium changer (as you would find in a tape library. select one of the IBM Tape Libraries. Refer to Figure 20 on page 168. for example). Have Disk Menu 8.Windows Device Driver Figure 19. Click IBM Corporation. Chapter 7. then click OK. select the device driver that matches your device. This installs drivers for both the medium changer and the tape drives. 11.sys or Magstar. then skip to step 11. The system may also prompt you for ntutil. If you did not install the Device Driver System Files component in step 4 on page 162. The operating system prompts you for the location of the driver files. Browse to the system32 directory (c:\winnt\system32). Reboot the operating system to start the drivers. browse to select the drivers directory (c:\winnt\system32\drivers). Windows NT Statement 10. Windows NT might ask the question shown in Figure 21. Removal Procedure The Windows NT tape and medium changer device drivers manage all TotalStorage/Magstar or Ultrium devices and changers exclusively. If your system prompts you for ibmtape. 168 IBM Tape Device Drivers Installation and User’s Guide .Windows Device Driver Figure 20. Figure 21. If you use applications that have their own device drivers that access TotalStorage/Magstar. If you installed the Device Driver System Files component in step 4 on page 162. Note: See “Microsoft Windows System .Utility Program (ntutil)” on page 366 for information on the ntutil application. click No to the question in step 9.exe. Install Driver Menu 9. Click Yes.sys. Highlight the IBM tape device. When you see the message Are you sure you want to remove this driver?. move to Settings.Windows Device Driver or Ultrium devices and changers. Click the Drivers tab. Refer to Figure 22. Double-click Tape Devices. 5. Log on as Administrator. 1. you must remove the Windows NT tape and medium changer device drivers before installing and configuring those other applications. Click Start. Figure 22. click Yes. Chapter 7. 3. then click Control Panel. Windows Tape and Medium Changer Device Driver 169 . Tape Devices and Remove Driver Menu 6. Click Add/Remove Programs in the Control Panel window. Refer to Figure 23 on page 170. then click Remove. 2. 4. Refer to Figure 24 on page 171. then click Add/Remove.. 170 IBM Tape Device Drivers Installation and User’s Guide .. Control Panel Selection 7. Highlight the IBM tape device driver.Windows Device Driver Figure 23.. Add/Remove Programs Properties 8. Chapter 7.Windows Device Driver Figure 24. Select the Remove option. Windows Tape and Medium Changer Device Driver 171 . then follow the InstallShield Wizard to uninstall the drivers. and other components. 9. Manual Starting and Stopping Procedures The TotalStorage/Magstar or Ultrium device and medium changer drivers support being stopped and started without a reboot.Windows Device Driver Figure 25. Click Next >.. Select the driver. such as the Installation and User’s Guide and Device Driver Depot. then click OK. then click Control Panel. you are able to switch between device drivers without rebooting the system. 2. set the startup mode to Manual. Note: Uninstalling the drivers removes all TotalStorage/Magstar or Ultrium device driver files. then start the device driver manually when required. 3.. Drive Removal Menu. 172 IBM Tape Device Drivers Installation and User’s Guide . To control manually when the TotalStorage/Magstar or Ultrium device drivers start or stop. registry settings. move to Settings. 10. If the TotalStorage/Magstar or Ultrium device and medium changer drivers are used in conjunction with other drivers that support being stopped and started without a reboot. Refer to Figure 26 on page 173. Click Start.. Shut down and reboot the system. Scroll down to find the IBM tape device and medium changer drivers. Log on as Administrator. click Startup. To set the startup mode to Manual: 1. select Manual. Double-click Device. 4. 5. repeat steps 4 on page 172 and 5 on page 172 of this procedure for each driver. Note: The last driver level to include support for Windows 2000 is V6. and Windows Server 2008 Instructions This section describes how to install. then click Stop. Perform steps 1 through 4 of the procedure outlined above. Manual Starting and Stopping Menu 6.8.1. To start a driver manually: 1.Windows Device Driver Figure 26. Chapter 7. Windows Server 2008 is supported beginning at V6. Windows Server 2003. Select the driver. 2. If required for other drivers.1. if necessary. Windows 2000. Select the driver. 4.5. Repeat for the other driver. and Windows Server 2008. To stop a driver manually: 1. and uninstall the Windows tape and medium changer device drivers on Windows 2000. remove. 2. Perform steps 1 through 4 of the procedure outlined above.9. Windows Server 2003. then click Start. 3.4. Windows Tape and Medium Changer Device Driver 173 . Ensure that the other drivers that may conflict are not started. Subsequent levels include support for Windows Server 2003. x86_w08_nnnn. If there is more than one version.i64_nnnn. 9. v Drivers are identified by the following conventions. Set the tape and medium changer device addresses. 2.x64_w08_nnnn. v The host bus adapter is installed. Download the appropriate driver from a subdirectory of: ftp://ftp. Verify that the hardware and software requirements have been met. 6. v If you are updating the device driver from a Microsoft certified version to an uncertified version. Connect the tape and medium changer devices to the host bus adapters. 3. Log on as Administrator.zip – Windows Server 2008 for extended 64-bit architectures (Intel EM64T and AMD64) IBMTape. use the latest. where: nnnn refers to a version of the driver.Windows Device Driver Installation Overview The installation process consists of the following steps: 1. 5.com/storage/devdrvr/Windows Drivers for Windows 2000 are in the Win2000 subdirectory. Drivers for Windows Server 2003 are in the Win2003 subdirectory. 2.zip – Windows Server 2008. follow this procedure: 1. configured properly.zip – Windows Server 2008 for Itanium (IA64) 64-bit architecture IBMTape.ibm. 32-bit IBMTape.zip – Windows Server 2003 for Itanium (IA64) 64-bit architecture IBMTape. Log on as Administrator.zip – Windows Server 2003 for extended 64-bit architectures (Intel EM64T and AMD64) IBMTape. Power on the tape and medium changer devices. 32-bit IBMTape. Reboot the system. Shut down the system. 4. and is running supported microcode and driver levels.x86_nnnn. – Windows 2000 and Windows Server 2003. 7.zip To install the device drivers.x64_nnnn. 8. All drives accessible from a medium changer must be on the same physical SCSI bus as the changer. it is recommended that you first uninstall the certified driver by referring to the uninstall procedures in this documentation.i64_w08_nnnn.software. Installation Procedures These procedures make the following assumptions: v No other driver is installed that claims the tape and medium changer devices. Install the host bus adapters and drivers. Drivers for Windows 174 IBM Tape Device Drivers Installation and User’s Guide . Install and configure the devices and device drivers using the installation application. When you download the files.exe. v With install_exclusive. v With install_nonexclusive.exe. 4. For driver packages prior to v6. double-click either install_exclusive. Windows Tape and Medium Changer Device Driver 175 .exe or install_nonexclusive. The necessary . 3. 5. Figure 27. For all subsequent levels.exe in the driver package.8. as is required by applications such as Microsoft Removable Storage Manager (RSM). the driver issues automatic reserves on open and also prevent multiple open handles from the host to a drive from existing at the same time.9.Windows Device Driver Server 2008 are in the Win2008 subdirectory. Refer to Figure 27.1. Unzip the driver package to a hard drive directory of your choice.exe. and all IBM devices are associated with the driver. Installation Application in Windows Explorer Notes: a. There are additional installation features available through the command line interface (CLI). double-click install. Ensure that the tape and medium changer devices are connected to your host bus adapter and configured properly by locating the devices in Device Manager. the driver permits open handles from the host to a drive to exist at the same time. other than the root directory.sys files for correct driver operation are installed. ensure that you use FTP ″binary″ mode. as is required by applications such as Tivoli Storage Manager. which include the following: v Installing only the tape or medium changer device drivers ( -t or -c) Chapter 7. exe -h at the prompt. open a command-line window and cd to the driver package directory. If you want to continue installing the driver. Figure 28. which suppresses pop-up messages requiring user intervention. Refer to Figure 28.6 and later v Disabling DPF from installation (-f). Note: All drivers released by IBM have been through a complete test to ensure that they are stable and conform to specified requirements. instead of double clicking the install executable file. cancel the wizard. provided you click the Always trust software box. If you are installing a driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL). it likely has a Verisign digital signature.exe -h or install_nonexclusive. you may be presented with a prompt to install the software.Windows Device Driver v Running in debug mode.txt in the driver package directory (-d) v Running in silent mode. The install application performs the necessary steps.0. which creates the file debug.2. During installation. a warning screen opens. 176 IBM Tape Device Drivers Installation and User’s Guide a250215 .1. 6. For the usage information. You should only see this screen the first time that you install the drivers. If you are installing a Windows Server 2008 driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL). If the Windows "Found New Hardware" Wizard begins during installation. available in driver packages v6. but only with Microsoft-certified IBM drivers (-s) v Disabling the Microsoft RSM service (-r). type install_exclusive. select Continue Anyway. available in driver packages v6. Mark the ″Always trust software from IBM Corporation″ check box and click Install. b.1 and later To install the device drivers using any of these features. Windows Logo Testing screen 7.8. Perform the following steps to enable this feature: 1. On reboot. Right-click My Computer.\tape4801101 and the persistent naming option is used. Chapter 7.” on page 303. right click Changer Bus Enumerator and select Uninstall. Add a DWORD value to the registry called PersistentNaming and assign it a value 1 at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2kx 2. if your tape drive has the name \. 1.zip file.exe in the driver package. then \\. or if you are altering the hardware configuration. which includes deleting the system files and deallocating other system resources. Complete the steps under Device Removal or Disable Procedure to remove the tape and medium changer devices. Right-click the TotalStorage or Magstar device you wish to uninstall and select Uninstall . 3. 3. or if the drive is a virtual (that is.. 2. Windows Tape and Medium Changer Device Driver 177 . To verify that the tape and medium changer devices and drivers are installed correctly. Note: This removal procedure removes the device from the device tree. It does not delete the . If you wish to disable the device without uninstalling it. Reboot your system.. but it does not uninstall the device driver files from your hard disk. under System devices. v If the World-Wide Node Name is unavailable. 0x83 with the persistent name used by the operating system. right click Tape Bus Enumerator and select Uninstall. In Device Manager. Note: This removes all the files in the system directories that were created during the installation of the device driver. 2. Double-click uninst. under System devices. Persistent Naming Support on Windows Server 2003 and Windows Server 2008 The Windows tape driver has an option for enabling device object names that persist across reboots of the operating system. In Device Manager. emulated) drive. the system writes information to the registry to associate the World-Wide Node Name from Inquiry p. 4.\tape4801101 is reserved for use by that device after an operating system reboot. 5.. If you desire to remove these files. Uninstalling the Device Drivers To uninstall the device drivers from the system. complete the following: 1. you need to delete them manually. “Verifying Proper Attachment of Your Devices. then the device serial number is used rather than the World-Wide Node Name. Reboot the system.zip file or the files that were extracted from the .Windows Device Driver 8. For example. and click Device Manager. you should uninstall or disable the device first. you may select Disable. follow the instructions in Appendix B. You are prompted to confirm the uninstallation. select Manage to open the Computer Management Console. Device Removal or Disable Procedure If you need to remove a device. Click OK. ” on page 255 or “Microsoft Windows System Utility Program (ntutil)” on page 366. “IBM Tape Diagnostic Tool (ITDT).reg or EnableCPF.reg. Control Path Failover Support for Tape Libraries To take advantage of Windows Control Path Failover (CPF) support. Querying Primary and Alternate Path Configuration To check if the control path failover has been enabled in the device driver and display the primary and alternate paths. 3. Checking Disablement of Control Path Failover Setting If you have disabled the control path failover in device driver’s setting by double clicking the DisableCPF. This is necessary for any registry modification to take effect. You can find registry subkeys with persistent naming information at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtpbs2kx Alternately. Persistent names contain tape device numbers based at 4801101 (which is the decimal equivalent of hexadecimal 0x49424D and ASCII "IBM"). 1. Refer to “Supported Devices and Feature Codes” on page 14 for what feature code may be required for your machine type. Open the reg folder of the driver package. then there is no guarantee that your devices can claim the same device name after reboot or driver initialization. 2. and any subsequent paths that connect to the same device receive names according to the order in which they are discovered by the Windows Device Manager. for example. the appropriate feature code must be installed. refer to Chapter 10. Look for a line like the following if your system is Windows Server 2003 or Windows Server 2008: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2kx] "FailoverDisabled"=dword:00000001 178 IBM Tape Device Drivers Installation and User’s Guide . Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions. Configuring and Unconfiguring Control Path Failover Support Control Path Failover support is enabled automatically when the device driver is installed.reg file and reboot your system. If two physical paths exist to a drive and different Windows device names are required (which happens. It may be disabled or reenabled for the entire set of attached medium changers by modifying the registry. you can use the Windows Device Manager to examine the device number in order to determine that persistent naming is enabled on your host. Reboot the system. when two different HBAs are connected to the drive and Data Path Failover is disabled) the first path discovered claims the persistent device name. Double click DisableCPF. you may use the tape diagnostic and utility tool. you may go into the registry by issuing the Windows regedit command to confirm that CPF has been disabled.Windows Device Driver v If the PersistentNaming option is not specified in the registry. the appropriate feature code must be installed. Look for a line like the following if your system is Windows Server 2003 or Windows Server 2008: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2kx] "FailoverDisabled"=dword:00000001 This indicates that DPF has been disabled in the driver. typically C. This is necessary for any registry modification to take effect. The driver looks for this file at initialization. the DPF feature is enabled and any eligible devices have multi-path support. 2. you may go into the registry by issuing the Windows regedit command to confirm that DPF has been disabled. Data Path Failover Support for Tape Drives To take advantage of Windows Data Path Failover (DPF) support. the device driver looks for a file called %system_root%:\IBM_DPF. The file should contain the key on a single line. Double click DisableDPF. For LTO generation 3 or lower. Reboot the system.Windows Device Driver This indicates that CPF has been disabled in the driver. Windows Tape and Medium Changer Device Driver 179 . Checking Disablement of Data Path Failover Setting If you have disabled the data path failover in device driver’s setting by double clicking the DisableDPF. refer to Chapter 10. there is no longer a requirement to provide a DPF license key in IBM_DPF. It may be disabled or reenabled for the entire set of attached drives or medium changers by modifying the registry.txt). Note: Display the primary and alternate path configuration for any device using tape diagnostic and utility functions.reg. and if the file contains a valid DPF license key. Note: For LTO generation 3 running the latest drive microcode. where: %system_root% is the drive letter where Windows has been installed. Configuring and Unconfiguring Data Path Failover Support Data Path Failover support is enabled automatically when the device driver is installed. 3. (for example. Querying Primary and Alternate Path Configuration To check if the data path failover has been enabled in the device driver and display the primary and alternate paths you may use the tape diagnostic and utility tool.reg file and reboot your system. 1. Chapter 7. Refer to “Supported Devices and Feature Codes” on page 14 for what feature code may be required for your machine type.txt. This setting only takes effect after your system is rebooted. C:\IBM_DPF.txt for the key. Open the reg folder of the driver package. The microcode now handles the enablement of the DPF feature. place each key in the file on its own line. If multiple keys are required. for tape drives that require a data path license key on the host side to enable DPF. This setting only takes effect after your system is rebooted. with no spaces and no other text on the line.reg or EnableDPF.” on page 255 or “Microsoft Windows System Utility Program (ntutil)” on page 366. “IBM Tape Diagnostic Tool (ITDT). The format for the EKM server parameters is: 180 IBM Tape Device Drivers Installation and User’s Guide . the settings established for all drives are overridden by the serial-number specific settings described the previous paragraph. A value of 1 causes the device driver to write encrypted data. Note: Leading zeros in the serial number should be excluded. during new installations of the driver. Changes to the registry require a reboot before the settings are able to be viewed. the driver uses the default values for the parameters. It does not turn on or turn off encryption writing. v The default value for sys_encryption_proxy is 1.Windows System-Managed Encryption System-Managed Encryption Device Driver Configuration System-managed encryption parameters on Windows are placed in the registry under the key for the device driver. A value of 0 causes the device driver to ignore encryption key requests for system-managed encryption drives. For example. This value causes the device driver to handle encryption key requests. The registry keys (sys_encryption_proxy and sys_encryption_write) are used to determine SME enablement and invocation of the EKM proxy on write. v The default value for sys_encryption_write is 2. if the serial number of the encryption-capable tape drive were 0123456789. typically C (for example C:\IBMEKM. the user would create the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3\123456789 Under this key. however. Configuration File The file %system_root%:\IBMEKM. The parameters are populated in user-created subkey containing the serial number of the device. the old settings remain in place and no reboot is required. If no options are specified in the registry. and is not desirable. The phrase %system_root% refers to the drive letter where the Windows installation is located. if the old driver is not uninstalled. but instead uses the settings that are already in the drive.conf is used to store the IP address of the EKM server and other network-related parameters. A value of 0 causes the device driver to write unencrypted data. This value causes the device driver to leave the encryption write-from-BOP settings alone. then the drive writes unencrypted data. respectively. found at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3 When this option is chosen. This value should not need to be changed. if the drive is set up for system-managed encryption. The device driver SME settings can be set for all drives at once by placing the ″sys_encryption_proxy″ and ″sys_encryption_write″ registry options under the device driver key.conf). the user would create DWORD values called sys_encryption_proxy and/or sys_encryption_write. If encryption has not been set up previously. and assign them values corresponding with the desired behavior. Refer to “Manual Starting and Stopping Procedures” on page 172 for details on stopping the driver. 3.0.n\checked for Ultrium devices...n.Windows System-Managed Encryption Server<tab>Timout<tab>IPAddress:Port For example.0.sysinternals.sys or magstar.1 at port 4242. 5. select Properties.n are integers that indicate the driver level.n. you must install the Device Driver Depot component of the Windows Device Driver Installation Package.0.sys) using Windows Explorer.1:4242 Querying Tape Drive Configuration Settings There is an ntutil command to query the encryption settings of a tape drive.. you must start a debugger or use a tool like Debug View.sys). the desired timeout is 10 seconds.\checked directory for your driver. Where: n. Go to the root prompt. To determine the driver level. perform the following steps after the driver has initially been installed: 1.n. The debug version of the driver issues DbgPrint messages at various places during device driver execution. Windows Tape and Medium Changer Device Driver 181 . if the Windows installation is installed at c:\.sys or IBMtape. and the IP address is 127.. If you chose the default installation location when you installed the drivers. If you do not find a .0. Chapter 7.\checked directory for the device driver level that you are running. 4.conf as follows: ekmtest<tab>10<tab>127. v c:\Program files\IBM Corporation\IBM Ultrium Device Drivers\n. right-click the file. then select the Version tab.n. c:.Utility Program (ntutil)” on page 366 for information on the ntutil application. with encryption turned on: Encryption capable: True Encryption method: System Managed (2) Encryption state: On (1) Problem Determination There is a debug version of the device driver that can be used if you encounter problems. Note: See “Microsoft Windows System . Exit all applications that are using the tape and medium changer devices.n. Locate the . available from: http://www. Quiesce all activity on the tape and medium changer devices. the debug drivers are found at: v c:\Program files\IBM Corporation\IBM Magstar Device Drivers\n.com Windows NT Instructions Using the Debug Version To install and use the debug version of the device driver. To capture these messages. “get encryption state”. 2. The ntutil command is menu option 59. find c:\winnt\system32\drivers\(ibmtape.n\checked for TotalStorage or Magstar devices. Then create a line in c:\IBMEKM.n. the ekm server is named ekmtest. Stop the device drive (MagStar. for example. The following is an example of the output when the drive is configured for system-managed encryption. 6. 2. 4. c:. if you installed the Ultrium device drivers at the default installation location and your driver level was 1. 10.sys or IBMtape. Go to the root prompt. Exit all applications that are using the tape and medium changer devices. or blank for the base driver. For example. 9.sys or ibmtape. Start the device driver. or 2k8 for Windows Server 2008. The greater the value. to any value from REG_DWORD 0x0 to REG_DWORD 0x5. Quiesce all activity on the tape and medium changer.sys. Refer to “Manual Starting and Stopping Procedures” on page 172 for details on stopping the driver.sys or ibmtape.sys ibmtape. perform the following steps: 1. \checked directory to c:\winnt\system32\drivers\(magstar. This folder is in the highest level directory of the driver package. bs for the bus driver.9. Start the debugger or tool that captures the DbgPrint messages. 2.Windows System-Managed Encryption 6.sys. Registry variable HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/ (Magstar or Ultrium)/MsgLevel determines how many messages are issued by the debug version of the driver. you can set the value of this variable.sys. Windows 2000/Windows Server 2003/Windows Server 2008 Instructions Using the Debug Version To install and use the debug version of the device driver. 3. and it contains checked versions of the tape and medium changer device drivers.sys).. inclusive. The variable is ignored by the non-debug version of the driver. Stop the device driver (Magstar. 5. Refer to Figure 29 on page 183. Refer to “Manual Starting and Stopping Procedures” on page 172 for details on starting the driver. Using regedt32.sys). 8. Copy magstar. Copy magstar. the more messages are issued.orig or IBMtape. Exit all applications that are using the tape and medium changer devices. 7. Restoring the Non-Debug Version To restore the non-debug version of the driver. When the debug version of the driver is started for the first time. where: v xx = ft for the filter driver.6. Quiesce all activity on the tape and medium changer devices.sys c:\winnt\system32\drivers\ibmtape. Refer to “Manual Starting and Stopping Procedures” on page 172 for details on starting the driver.orig IBMtape.1.1. 6. Start the Windows device driver.sys and ibmcgxxyyy. Copy magstar. or 2k3 for Windows Server 2003.sys from the appropriate . for example. Change to the appropriate directory by entering cd \winnt\system\drivers. it defines the registry variable. Change to the appropriate directory by typing cd \winnt\system\drivers..sys or IBMtape. and v yyy = 2k for Windows 2000. 3. ibmtpxxyyy. 7.orig magstar.orig. 182 IBM Tape Device Drivers Installation and User’s Guide . you would issue the following command: copy c:\Program files\IBM Corporation\IBM Ultrium Device Drivers\1. Locate the \checked folder for the device driver level that you are running.9\checked\ IBMtape. perform the following steps after the driver has initially been installed: 1.sys magstar. 4. where: v xx = ft for the filter driver. bs for the bus driver. Reboot the system. 4. Issue the commands to the driver.1. and v yyy = 2k for Windows 2000.sys and ibmcgxxyyy. and therefore only contain a2k3 files. Subsequent levels include support for Windows Server 2003 and Windows Server 2008 only. or 2k3 for Windows Server 2003. overwriting the version of the file already there. Subsequent levels include support for Windows Server 2003 and Windows Server 2008 only.sys. perform the following steps: 1. Restoring the Non-Debug Version To restore the non-debug version of the driver. overwriting the version of the file already there. Windows Tape and Medium Changer Device Driver dd000002 183 .sys or ibmcgxxyyy. Located in the highest level directory of the driver package. Figure 29. and only contain 2k3 files. 7. Copy the non-debug version of ibmtpxxyyy.1. 2. 6. or blank for the base driver. 3.Windows System-Managed Encryption Note: The last driver level to include support for Windows 2000 is V6. Checked folder.sys to \winnt\system32\drivers.4. Exit all applications that are using the tape and medium changer devices. or 2k8 for Windows Server 2008.4. Refer to Figure 29.8. 5.8. You should see debug statements printed to the debugger window. Quiesce all activity on the tape and medium changer devices.sys to \winnt\system32\drivers. Note: The last driver level to include support for Windows 2000 is V6. Copy the checked version of ibmtpxxyyy.sys or ibmcgxxyyy. Chapter 7. Start the debugger to capture the DbgPrint messages. are non-debug versions of the tape and medium changer device drivers. ibmtpxxyyy. subsequent reservation conflicts from the same reserving host WWPN will not be logged to prevent multiple entries in the error log until either the reserving host WWPN is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs.Windows System-Managed Encryption 5. When the driver has started and commands are issued to it. After initially logging the reserving host WWPN. the driver no longer produces debug output. the device driver will log this information as follows: Reserving host key: kkkkkkkk WWPN: xxxxxxxx Where kkkkkkkk is the actual reserve key and xxxxxxxx is the reserving host initiator WWPN. 184 IBM Tape Device Drivers Installation and User’s Guide . If successful. Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name). Reboot the system. Reservation Conflict Logging When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the Windows eventlog. 3581 and 3583 Tape Libraries – IBM TotalStorage Enterprise Tape Drive 3590. .1A is properly installed. . . see “Tru64 System . . . 2007. . . . . .1A Operating System with native device driver and medium changer device driver. . . . . Hardware Requirements The following hardware is supported by the Tru64 Native Tape and Medium Changer driver: v One or more of the following IBM tape and medium changer device: – IBM Ultrium LTO1 tape drive – IBM System Storage TS3500. . .81A4 Software Requirements Tru64 5. The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges). . .32a. . Setting Up the Environment . 2. . 2009 185 . 185 Software Requirements . . Confirm that the Host Bus Adapter card and appropriate firmware levels are properly installed on a Compaq Alpha system. Tru64 Device Driver Purpose . Confirm that Tru64 Operating System version 5.Chapter 8. Product Requirements The following hardware and software components are supported by IBM. . Hardware Requirements. 185 .RAS Utility Program (IBMrasutil)” on page 385 for information on the IBMrasutil application. 185 . F/W Rev: 3. cam_changer) are designed to take advantage of the features provided by tape drives and medium changer devices. . Model E1A or H1A (3494 Tape Library Model) with FC interface v One or more of the following Fibre Channel Host Bus Adapter: – 64 bit PCI to Fibre Channel Host Bus Adapter (Compaq part # DS-KGPSA-CA) Version: 1. . Product Requirements . Setting Up the Environment To set up IBM Tape and Medium changer devices to operate with the Tru64 operating system: 1. The IBM Tape Diagnostic Tool (ITDT) is not supported on the Tru64 operating system. . . . . . . . . © Copyright IBM Corp. . . . Purpose The Tru64 Native tape and medium changer device drivers (cam_tape. 185 This chapter describes the Tru64 support available for the IBM TotalStorage Enterprise Tape System 3590 and the IBM 3584 UltraScalable Tape Library. Model E11 or H11 (Rack Mount with ACF) with FC interface – IBM TotalStorage Enterprise Tape Drive 3590. . . . . . . . 185 . To verify the scanned results. Issue the /sbin/ddr_config -c /etc/ddr. Connect the tape and medium changer devices to the host bus adapter card following the instructions for the devices.dbase file. 6. 10. Login as root administrator or use the su command to gain superuser privileges. if not already powered up. Power up the tape and medium changer devices.dbase file for the particular tape or medium changer devices. The native driver creates device special files based on the information given in the ddr. 186 IBM Tape Device Drivers Installation and User’s Guide . issue the /sbin/hwmgr -scan scsi command to detect tapes or medium changers that are connected to the host.base command to compile and link the new entry to the driver module.Figure 30 on page 187 is an example output of a working device configuration for an IBM TotalStorage 3590 tape drive. For more information on ddr_config utility and the ddr. At the command line.Tru64 Device Driver 3. 5. 8. refer to the Tru64 documentation and man pages. and wait until they have initialized. 4. 7. issue /sbin/hwmgr -view dev at the command prompt. 9. Add a new entry to the /etc/ddr.dbase file. *SCSIDEVICE # type = tape Name = "IBM" "03590E1A" # PARAMETERS: TypeSubClass MaxTransferSize ReadyTimeSeconds CMD_PreventAllow CMD_ExtReserveRelease DENSITY: DensityNumber DensityCode DENSITY: DensityNumber DensityCode Blocking Buffered DENSITY: DensityNumber DensityCode CompressionCode Blocking Buffered DENSITY: DensityNumber DensityCode CompressionCode Blocking Buffered DENSITY: DensityNumber DensityCode CompressionCode Blocking Buffered = = = = = #Vendor ID and Product ID rdat 0x0ffffff #(16M-1) 45 supported supported = 0 = Default = = = = = = = = = = = = = = = = = = = 1 Default 0x200 1 2 Default 0x00 0x8000 1 3 Default 0x00 0x10000 1 4. Example Output for Tru64 Device Driver and IBM 3590 Tape Drive Chapter 8. Tru64 Device Driver 187 .5.7 Default 0x01 0x20000 1 #block size #buffered mode #compression off #block size #buffered mode #compression off #block size #buffered mode #compression on #block size #buffered mode Figure 30.6. 188 IBM Tape Device Drivers Installation and User’s Guide . . . . . . . . . . . . . . . . . . . . . . MTLIB Program . . . . 217 217 218 219 222 224 224 225 226 229 230 230 231 232 235 236 236 237 238 242 243 243 244 245 247 249 249 250 251 Purpose The IBM 3494 Library device driver is a device driver providing attachment for the IBM TotalStorage 3494 Enterprise Automated Tape Library and IBM TotalStorage Virtual Tape Server (VTS) to a server. . . . . . . . . . . . Data Flow . . . . . Installation Instructions . . Unsolicited Notification . AIX . . . . . Software Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous Library Operations . . . . . . . . . . . . . Performance Considerations . . . . . . . . 3494 Emulation Design . . . TRU64. . . . . . . . . . . . . . . . . . . . . . . Problem Determination . . . . . . Problem Determination . . Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . Data Flow . . . . . . . Using the 3494 API Emulation and MTLIB Program . . . . Product Requirements . . . . . . . . . . . . . . . . . . . . . Driver Message Queue . . . . . Data Flow . Product Requirements . . Library Manager Event Notification . . . . . . . . . Data Flow . . . . . . . 2009 189 . . . . . 189 190 190 201 201 201 201 202 202 202 202 202 203 205 205 205 206 206 206 207 207 208 208 208 209 215 215 HP-UX . Installation and Configuration Instructions Problem Determination . . . . . Installation Instructions . . . . . . . . . . . . . . Volume Categories . . . . . . . . MTEVENT Program . . . . Windows . Data Flow . . . . . Product Requirements . . . . . . . . . . . . . . . . . Linux . . . Installation and Configuration Instructions Problem Determination . . Operation Complete Notification . . . . . . . Product Requirements . . Special Files . . . . . . . . . . . . . . . . . . 2007. . . . . . Installation Instructions . . . . Problem Determination . Overview. . . . . . . . . 3494 Enterprise Tape Library Support Purpose . .Chapter 9. . . . . . . . . . . . . . . . Product Requirements . . Data Flow . . . . . . Product Requirements . . . . . . . . . . . . . . . . . . . Library Driver Information . . . . . . . . . 3494 Library Emulation . . . . . . . . . . . . . . Syntax and Examples. The programs described in this chapter support the 3494 Enterprise Automated Tape Library on the following operating systems: v AIX on IBM POWER-based servers v HP-UX v Linux v Sun/Solaris v v v v v v Microsoft Microsoft Microsoft Microsoft Tru64 SGI/IRIX Windows Windows Windows Windows NT 2000 2003 2008 © Copyright IBM Corp. . . . . . . . . . . Problem Determination . . . SMC Library Names . . . . . . . . . . . Solaris . . . . Installation Instructions . . . Volume Categories . . . . . . . . . . . . . . . . . Product Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM TotalStorage Virtual Tape Server Subsystem Attachment . . . . . . . . . . . . . . . . . . . . . . . . Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous and Asynchronous Operations . SGI IRIX . . . . . . . . . . . . . . . . . . . . . . . . . The attached VTS libraries are named logically vts1. The mtlib program provides an interface to the physical tape drives and volumes within a 3494 Tape Library and also to the virtual tape drives and volumes within an attached IBM TotalStorage Virtual Tape Server (VTS). such as libmgrc7. specify a device special file name.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. Syntax Diagram for mtlib program 190 IBM Tape Device Drivers Installation and User’s Guide . and so on and correspond to the order in which they were configured in the Tape Library. specify a device special file name or the logical name of the library with the name of the logical VTS library appended with a slash (/). The -D flag. to issue commands to the first attached VTS library. use /dev/lmcp0/vts1 or libmgrc7/vts1. To issue commands to the virtual tape drives and volumes in an attached VTS library. by default. such as /dev/lmcp0 or the logical name of the library. in conjunction with the -E flags. vts2. To issue commands to the physical tape drives and volumes. for execution by all users on the system. Refer to “MTEVENT Program” on page 201. For example. Syntax and Examples Figure 31 shows the syntax for the mtlib program . can be used to display the attached VTS devices and the number of the VTS library. GA32-0566. Figure 31. This program provides the full interface (except for the MTIOCLEW library system call) as specified in the IBM Tape Device Drivers: Programming Reference. for example.\tape0 (Windows) Device number of the drive. /dev/IBMtape0 (Linux). Query the library information option: Type V L S I C D E K R A M -D -E Description Volume data Library data Statistical data Inventory data Category inventory data Device data Expanded volume data Inventory volume count data Reserved category list Category attribute list All mounted volumes -x[number] -l[filename] -q[type] Return an array of devices configured in the specified library Return (if used with the -D option) an array of expanded information for all devices configured in the specified library. 518350 On AIX. the logical name of the library. for example.3494 Enterprise Tape Library Support The mtlib program has the following flags: Flag -f[filename] Description Device special file for the drive. libmgrc7. for example. /dev/rmt/0m (HP). /dev/rmt/0st (Sun). \\. 3494 Enterprise Tape Library Support -m -d -c[requestid] -n -i[requestid] -C -a -k[flags] 191 . device. and VTS library number Mount option Demount option Cancel the pending request option No wait mode Query the request ID status option Change the category of a volume Audit the specified volume Assign a category (with one of the following flags) to a device in the library: Type O C G A Description Enable the category order Clear the cartridge loader Generate the first mount Enable the auto mount Chapter 9. /dev/lmcp0/vts1. For non-AIX. including the control unit ID. library special file name. /dev/lmcp0. for example. /dev/rmt0 (AIX). The default is the ISO format with a period separator.3494 Enterprise Tape Library Support X Remove the device category assignment Note: Valid combinations are OG.mm. *. Help text Note: The -l argument is required. 192 IBM Tape Device Drivers Installation and User’s Guide . Each Volume Serial should be entered as one per line in the file. Category name to assign to the category (valid characters are uppercase A-Z. Include usage date in the expanded volume data (used in conjunction with the -qE option).dd. or blank).mm.dd.yyyy U. mm. 0-9. The format can be specified with the -F option. OA.yyyy Dash separator mm-dd-yyyy Slash separator mm/dd/yyyy Verbose -F[flags] -#[num_categories] Number of categories to reserve -A -? Query library addresses and status.dd Europe dd. -s[category] -t[category] -V[volser] -L[list] -N[name] -h[hostid] -u Source or starting category Target category Volume serial number Filename containing a list of the volume serial numbers. Host ID for the reserve or release category or the R/A option for the query command.S. GA. and OGA.yyyy Period separator mm.A. Format or separator for volume usage and date with the -u option: Type I E U p d s -v Description ISO/Japan yyyy. -r -R -S Reserve the category Release the category Set the category attribute Note: The categories must be reserved before using this option. -. ..0000 device state..00 Figure 32.Device installed in Library........3590-B1A extended device status..........00 logical volume.. HP.FE00 subsystem affinity.CS2000 category..04 03 05 06 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Figure 33......... and Windows) Volume Data: volume state. device class....No volume class......... Linux.... 3494 Enterprise Tape Library Support 193 ...... SGI...3494 Enterprise Tape Library Support The report in Figure 32 was produced by: mtlib mtlib mtlib mtlib mtlib mtlib -l -l -1 -1 -1 -l /dev/lmcp0 -f /dev/rmt5 -qD (for AIX physical library) /dev/lmcp0/vts1 -f /dev/rmt5 -qD (for AIX VTS library 1) libmgrc7 -f /dev/rmt/5st -qD (for Sun) libmgrc7 -f /dev/rmt/5m -qD (for HP) libmgrc7 -f /dev/IBMtape5 -qD (for Linux) libmgrc7 -f \\..... Tru64.........HPCT 320m nominal length volser. Device Query The report in Figure 33 was produced by: mtlib -l /dev/lmcp0 -qV -VCS2000 (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qV -VCS2000 (for AIX VTS library 1) mtlib -l libmgrc7 -qV -VCS2000 (for Sun.. ACL is installed.......... Device available to Library. Volume is loaded.......TAF500 mounted category................\tape0 -qD (for Windows) Device Data: mounted volser...3590 1/2 inch cartridge tape volume type..................... Volume Query Chapter 9...FF00 device category.. Tru64....... HP.. Expanded Volume Query The report in Figure 35 was produced by: mtlib -l /dev/lmcp0 -qE -u -VCS2000 (for AIX physical library) mtlib -1 libmgrc7 -qE -u -VCS2000 (for Sun. Tru64. Expanded Volume Data with Usage The report in Figure 36 was produced by: mtlib -l /dev/lmcp0 -qK -v (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qK -v (for AIX VTS library 1) mtlib -l libmgrc7 -qK -v (for Sun......... Tru64.. SGI...........FF00 Figure 34.. and Windows) Performing Query Inventory Volume Count Data using /dev/lmcp0 Inventory Volume Count Data: sequence number..... Inventory Count Data The report in Figure 37 was produced by: mtlib -l /dev/lmcp0 -D (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -D (for AIX VTS library 1) mtlib -l libmgrc7 -D (for Sun.. SGI..CS2000 device category...3590 1/2 inch cartridge tape volume type..12345 number of volumes.....No volume class.dd)... and Windows) Expanded Volume Data with Usage: volume status. HP....2001.......00 logical volume... Linux.....HPCT 320m nominal length volser.. SGI...0000 Figure 36.....207 category.08.......... SGI..FF00 last used (yyyy..26 Figure 35.........00 logical volume.HPCT 320m nominal length volser.... HP.. Linux..... 194 IBM Tape Device Drivers Installation and User’s Guide ........3494 Enterprise Tape Library Support The report in Figure 34 was produced by: mtlib -l /dev/lmcp0 -qE -VCS2000 (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qE -VCS2000 (for AIX VTS library 1) mtlib -l libmgrc7 -qE -VCS2000 (for Sun.. Linux...........mm.......... and Windows) Refer to also the tapeutil subcommand mtdevice..... and Windows) Expanded Volume Data: volume status............3590 1/2 inch cartridge tape volume type..No volume class..... Tru64...... Linux. HP.CS2000 device category.. Expanded Tape Library Device List Chapter 9. Tape Library Device Number The report in Figure 38 was produced by: mtlib -l /dev/lmcp0 -DE (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -DE (for AIX VTS library 1) mtlib -1 libmgrc7 -DE (for Sun. 00515821 003490C2A01 Figure 37. Type 003590 003590 003590 003590 003590 003590 003490 003490 003490 003490 003490 003490 003490 003490 Mod B1A B1A B18 B18 B18 B18 C2A C2A C2A C2A C2A C2A C2A C2A Serial # 13-10800 13-10800 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 13-01817 Devnum Cuid 00108000 1 00108001 1 00018170 2 00018171 2 00018172 2 00018175 2 00FF0100 3 00FF0101 3 00FF0110 3 00FF0111 3 00FF0120 3 00FF0121 3 00FF0130 3 00FF0131 3 Device 0 1 0 1 2 3 0 1 2 3 4 5 6 7 VTS Library 1 1 1 1 1 1 1 1 1 1 1 1 Figure 38.3494 Enterprise Tape Library Support 0. Tru64. SGI. 3494 Enterprise Tape Library Support 195 . Linux. HP. and Windows) Refer to also the tapeutil subcommand mtdevice. 00515820 003490C2A00 1. ..... Primary hard drive installed...........All input stations empty All output stations empty machine type...................00 input stations...01 accessor status...........10491 number of cells........0 bulk output capacity..... Library Data 196 IBM Tape Device Drivers Installation and User’s Guide .. Primary library manager available..... library facilities...............................00 bulk input capacity... Convenience input station available.......0 bulk input empty cells. Convenience input station installed...3494 Enterprise Tape Library Support The report in Figure 39 was produced by: mtlib -l /dev/lmcp0 -qL (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qL (for AIX VTS library 1) mtlib -l libmgrc7 -qL (for Sun...............Accessor available Gripper 1 available Gripper 2 installed Vision system operational comp avail status. HP.. Secondary hard drive installed..... and Windows) Library Data: Operational state.....Paused Operational State Intervention Required functional state....... SGI.1014 subsystems..0 bulk output empty cells...... Secondary hard drive available.........3494 sequence number....0 avail 3490 cleaner cycles... Linux.. Tru64.. Primary hard drive available..1 output stations..6 convenience capacity..91 Figure 39..... Secondary library manager available.....Primary library manager installed... Convenience output station installed.....1 input/output status. Secondary library manager installed..1056 available cells......0 avail 3590 cleaner cycles.... Convenience output station available..30 accessor config.. ..0 max demount time..2 min pending demounts........003494 model number..............19 avg demount time.19 pending mounts...............0 pending audits.0 avg eject time..0 demounts/hour.0 avg pending ejects...2 min pending mounts.....L10 manufacturer...........0 post-demounts/hour...13 sequence number.0 max pending mounts...2 min mounted drives.18 index mounts/hour..0 Figure 40..24 pending ejects..19 pending demounts.......... Statistical Data Chapter 9.......0 min pending ejects......0 audits/hour....0 max audit time. HP..0 input stores/hour....0 min pending audits..16 index demounts/hour..........0 max eject time.........0 min audit time......10 machine type... and Windows) Statistical Data: hour index.0 avg pending audits....0 max pending demounts.....0 avg pending demounts......1 avg mounted drives.0 ejects/hour..........1 max mounted time..............IBM plant..3494 Enterprise Tape Library Support The report in Figure 40 was produced by: mtlib -l /dev/lmcp0 -qS (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qS (for AIX VTS library 1) mtlib -l libmgrc7 -qS (for Sun..............22 min mounted time......1 max mounted drives... Tru64.000000010491 drives........0 max mount time..0 avg audit time.0 max pending ejects.6 mounted drives... SGI...0 min eject time.28 min demount time.................27 min mount time.....16 avg mounted time......... Linux... 3494 Enterprise Tape Library Support 197 ........16 avg mount time...0 max pending audits.............0 pre-mounts/hour.0 avg pending mounts.............0 mounts/hour.... .......44 inventory records record 1.category.........category.3494 Enterprise Tape Library Support The report in Figure 41 was produced by: mtlib -l /dev/lmcp0 -qI-v (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qI -v (for AIX VTS library 1) mtlib -l libmgrc7 -qI -v (for Sun.......008273 volume state......FF00 volser..HPCT 320m nominal length record 2....TST039 volume state....category value..................00 logical volume..HPCT 320m nominal length • • • record 42..00 logical volume................ but Inaccessible record 44........00 logical volume.FF00 volser.............10491 number of volumes......HPCT 320m nominal length Note: All available records are produced as output per request....Volume present in Library....FF00 volser.3590 1/2 inch cartridge tape volume type.. Tru64..........3590 1/2 inch cartridge tape volume type...........3590 1/2 inch cartridge tape volume type...............................ALTML1 volume state.....HPCT 320m nominal length record 43...00 logical volume... Fewer records are shown here for the sake of brevity...3590 1/2 inch cartridge tape volume type....012C volser.....category.00 logical volume................category value.....................No volume class........TST182 volume state....No volume class. HP........ SGI...........064435 volume state...........No volume class.........No volume class..3590 1/2 inch cartridge tape volume type................ Linux. and Windows) Performing Query Inventory Data using /dev/lmcp0 Inventory Data: sequence number.........XYZ464 volume state..FF00 volser...... Inventory Query 198 IBM Tape Device Drivers Installation and User’s Guide .category value................. Figure 41...No volume class.FF00 volser............HPCT 320m nominal length record 3.... Figure 42.................. SGI.3590 1/2 inch cartridge tape volume type........category ...10491 number of volumes............category .No volume class.....3494 Enterprise Tape Library Support The report in Figure 42 was produced by: mtlib -l /dev/lmcp0 -qC -sFF00 -v (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qC -sFF00 -v (for AIX VTS library 1) mtlib -l libmgrc7 -qC -sFF00 -v (for Sun...........HPCT 320m nominal length record 30........HPCT 320m nominal length record 2..FF00 volser............No volume class......3590 1/2 inch cartridge tape volume type.00 logical volume............FF00 volser.category .category .................No volume class.....................00 logical volume.category .......No volume class.HPCT 320m nominal length Note: All available records are produced as output per request..MOO801 volume state. Fewer records are shown here for the sake of brevity......FF00 volser..........FVT896 volume state.... Category Inventory Query Chapter 9.........30 category......00 logical volume...................category ...3590 1/2 inch cartridge tape volume type..HPCT 320m nominal length • • • record 28.......................FF00 volser... and Windows) Performing Query Category Inventory Data using /dev/lmcp0 Inventory by Category Data: sequence number............. Linux....TAF195 volume state.IHG319 volume state..HPCT 320m nominal length record 3....FF00 volser. Tru64........No volume class...................3590 1/2 inch cartridge tape volume type.............CS2017 volume state......3590 1/2 inch cartridge tape volume type................ HP.......No volume class........3590 1/2 inch cartridge tape volume type...........HPCT 320m nominal length record 29...FF00 inventory records record 1... 3494 Enterprise Tape Library Support 199 ...00 logical volume..........SLT500 volume state...........FF00 volser...00 logical volume..............00 logical volume........ Tru64... Tru64.. and Windows) libmgrc7 -S -S102 -NWORKING (for Sun. and Windows) Reserved Category List: sequence number.0101 category. SGI.. Tru64. and Windows) Reserved Category List: sequence number.0002 category..... SGI.0102 Figure 43...0101 category....10491 system token..... Linux... HP... SGI..... Linux......... Reserve Category List The report in Figure 45 was produced by: mtlib mtlib mtlib mtlib mtlib mtlib mtlib mtlib mtlib -l -l -l -l -l -l -l -l -l /dev/lmcp0 -S -S101 -NSCRATCH (for AIX physical library) /dev/lmcp0 -S -S102 -NWORKING (for AIX physical library) /dev/lmcp0 -qA -h roadster (for AIX physical library) /dev/lmcp0/vts1 -S -S101 -NSCRATCH (for AIX VTS library 1) /dev/lmcp0/vts1 -S -S102 -NWORKING (for AIX VTS library 1) /dev/lmcp0/vts1 -qA -h roadster (for AIX VTS library 1) libmgrc7 -S -S101 -NSCRATCH (for Sun.... HP... Tru64..... Reserve Category Command The report in Figure 44 was produced by: mmtlib -l /dev/lmcp0 -qR -h roadster (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -qR -h roadster (for AIX VTS library 1) mtlib -l libmgrc7 -qR -h roadster (for Sun....roadster category 0101 –– name: SCRATCH category 0102 –– name: WORKING Figure 45..... Linux.... HP.. Category Attribute List 200 IBM Tape Device Drivers Installation and User’s Guide ..... Tru64.....roadster total number reserved.....roadster total number reserved...........0102 Figure 44.... and Windows) Category Attribute List: sequence number.0002 category.. Linux...... Linux.. SGI..........10491 system token.... SGI.. HP....3494 Enterprise Tape Library Support The report in Figure 43 was produced by: mtlib -l /dev/lmcp0 -r -#2 -h roadster (for AIX physical library) mtlib -l /dev/lmcp0/vts1 -r -#2 -h roadster (for AIX VTS library 1) mtlib -l libmgrc7 -r -#2 -h roadster (for Sun. and Windows) libmgrc7 -qA -h roadster (for Sun. HP....10491 system token.. it checks a list of processes waiting for an event to determine where to deliver it.115. close_ibmatl.3494 Enterprise Tape Library Support The report in Figure 46 was produced by: mtlib -l /dev/lmcp0 -A (for AIX physical library) mtlib -l tire -A (for Sun.tire host identification.......115. one symbolic name must be defined for use on the library... If the -t flag is not supplied. /dev/lmcp0.conf file.. or libmgrc7 Number of seconds to wait for the event to occur (0=no timeout) Notes: 1.Online alternate address.. SGI... The mtevent program has the following flags: Flag -l[filename] -t[timeout] Description Library special file name or logical name of the library..45.. and Windows) Library Address Information: library name... Library Driver Information The lmcpd communicates to the tape library through symbolic names defined in the /etc/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). If no process is waiting for the event Chapter 9...9.... Tru64... The -l flag is required.. the lmcpd is responsible for receiving the various Library Manager notifications..roadster primary address...Offline Figure 46.. /dev/lmcp0/vts1.. 3494 Enterprise Tape Library Support 201 ... HP..45.... for example.... Software Interface The C object module provides three subroutines for communicating with the IBM TotalStorage 3494 Enterprise Tape Library. These subroutines are open_ibmatl.. Linux.... 2.... To send commands to the 3494 Tape Library.. When the daemon receives an event. then no timeout is performed.9. Library Address Information MTEVENT Program The mtevent program is a command-line interface to the MTIOCLEW command... The ioctl_ibmatl subroutine is used to send commands to the Library Manager on the 3494 Tape Library.. A symbolic name is used to perform the various library functions (such as mounting and demounting volumes)...52 primary status. and ioctl_ibmatl...51 alternate status.. One or more symbolic names can be configured for each tape library online to the system.. The daemon monitors several types of events...... Library Manager Event Notification In addition to performing library operations.... Volume Categories To facilitate the management of the tape volumes within the 3494 Tape Library. or Set Volume category operations have an option that allows the user process to wait or not wait for the operation complete message. Another potential use is managing volumes for daily. then any process waiting with the Library Event Wait call is notified. an installation can have one or more scratch categories that are assigned by media type or class of user. an unsolicited notification is sent to the device daemon. Demount. the driver returns the oldest entry from the message queue and deletes it. The applications can use the Library Event Wait call to request notification of all Library Manager events. and it can be used in subsequent Library Query Message ID operations to solicit the status of the asynchronous operation. it returns a delayed response message indicating the status of the operation. In this case. Demount. the capability to associate the tape volumes into logical groupings is provided. then the event is discarded. first-out basis. The lmcpd also allows a user process 202 IBM Tape Device Drivers Installation and User’s Guide . then the calling process is put to sleep until a message is received. the initial message identifier is returned to the caller. Operation Complete Notification When the Mount. is implemented on a first-in. a message identifier is assigned to the operation. For example. An asynchronous operation (such as a mount operation) takes longer to complete. The purpose of this message is to reduce the possibility of missing a message when several messages occur in a short period of time. Refer to the IBM Tape Device Drivers: Programming Reference for a list of unsolicited notifications received by the lmcpd. Synchronous and Asynchronous Operations Two types of library operations are supported: synchronous and asynchronous. Unsolicited Notification There are situations when the Library Manager has a condition to report that is not related to any I/O operation. If a notification is received. and monthly backups or volumes owned by a specific user. an operation complete notification is sent to the daemon. An example of a synchronous operation is the Library Query call. the library returns an initial response when the command is accepted for execution. Audit. In an asynchronous operation.3494 Enterprise Tape Library Driver that has arrived. weekly. If no entries are in the queue. This queue. The daemon makes a determination (based on the initial message identifier) as to which user process to notify that the operation is complete. An example of an unsolicited notification is the operational state change of the library (from the Auto mode to the Pause mode). If the user process does not wait for the final complete. Refer to the IBM Tape Device Drivers: Programming Reference for more information. When the operation is completed. Audit. or Set Volume category operation is sent to the library. All queue entries are discarded when the LMCP file descriptor is closed. Driver Message Queue The driver maintains a message queue for any process that has an open LMCP file descriptor. When the command is completed. Each logical grouping is known as a category. These operations are completed when the library responds to the request. This identifier is returned to lmcpd. The Library Manager responds to the synchronous operation immediately. The Mount. which has a depth of four entries. When an application issues the MTIOCLEW input/output control (ioctl) call. 3494 Enterprise Tape Library Support 203 . Refer to the IBM TotalStorage Enterprise Automated Tape Library Operator Guide for more information about the bulk output area. The volumes that are assigned to this category are moved from their current cell to the bulk output area in the 3494 Tape Library. The Library Set Volume Category command is the only command that can change the category of a volume to the eject category. A logical tape volume appears Chapter 9. HP-UX. The assigned categories are: X'0000' X'0001'–X'FEFF' X'FFFF' NULL category (not usable or not assigned) General programming use VOLSER specific The X'FF00'–X'FFFE' categories are reserved for hardware functions: X'FF00' X'FF01'–X'FF0F' X'FF10' X'FF11' X'FF12'–X'FFF8' X'FFF9' X'FFFA' X'FFFB' X'FFFE' Insert Reserved Eject Bulk eject Reserved Service volume Manually ejected Purge volume Cleaner volume The following three categories are available for programming use: Insert When a tape volume is received in the input station. and Sun/Solaris systems. Eject Bulk eject The X'FFFF' category is available for general programming use. This process allows all the volumes associated with the category to be mounted as determined by the flags of the command on the specified device. Volumes within the VTS subsystem are logical tape volumes. except that any mount request to this category must apply to a specific volume assigned to the category (and not based on the category alone). the volume label is read and assigned to this category. IBM TotalStorage Virtual Tape Server Subsystem Attachment The device driver supports the IBM TotalStorage Virtual Tape Server (VTS) subsystem attachment with a 3494 Enterprise Tape Library on AIX. The Library Set Volume Category command is the only command that can change the category of a volume to the bulk eject category. Windows. The volumes assigned to this category are moved from their cell into the output station. A category is a four digit hexadecimal number in the X'0000'–X'FFFF' range. An attached VTS subsystem provides virtual tape drives that are accessible with the VTS SCSI attachment feature. After the volume is delivered. it is removed from the inventory. This category cannot be assigned by a user process.3494 Enterprise Tape Library Driver to assign a particular category to a tape device in the library. vts2. For example. where: 3494 lib is a library configured in the /etc/ibmat1. issuing a Query Inventory command to the 3494 lib returns the physical volumes in the 3494 Tape Library.3494 Enterprise Tape Library Driver to the host as a normal physical tape volume. Issuing a Query Inventory command to 3494 lib/vts1 returns the logical volumes in the first VTS subsystem attached to the 3494 Enterprise Tape Library. and so on. 204 IBM Tape Device Drivers Installation and User’s Guide . Access to a VTS subsystem is specified to the device driver as a logical library within the attached Tape Library as vts1. except that the VTS logical volumes are unique to the VTS subsystem and are accessible only by virtual tape drives within the VTS subsystem.conf file. o object module in order to use the emulation support.3494 Library Emulation 3494 Library Emulation The 3494 Library Emulation support provides the ability to use applications that were written for the 3494 API on host attached SCSI Medium Changer Libraries. Figure 47 and Figure 48 on page 206 show the 3494/SMC data flow between existing applications and components and the new libsmc extension. 3494 Emulation Design The 3494 Emulation support adds a libsmc extension to the current libibm.O Object Module LMCPD TCP/IP 3494 Library Manager LIBSMC Figure 47. Customer and ISV applications only need to be recompiled with the new libibm. The mtlib 3494 user command line interface program that has the same syntax and output on every operating system and also provides a common utility for SCSI Medium Changer Libraries. depending on the 3494 functions being used. specifically for migration to the 3584 Ultra Scalable Library with 3592 drives. The libsmc extension contains the 3494 API Emulation support. Overview Existing customer scripts using the mtlib program and customer or ISV applications require no or minor changes to use. 3494/ SMC Library Data Flow Tape Device Driver Application Adapter Device Driver Library Tape Drive LIBIBM. which issues SCSI Medium changer commands to the library using the operating system SCSI Medium Changer device driver. Current operating system device driver utilities vary by syntax/output. require a knowledge of SCSI Medium Changers to use. and require multiple commands to perform a single mtlib command. 3494/SMC Library Data Flow a28t1001 SMC Device Driver Adapter Device Driver SCSI Medium Changer Chapter 9. 3494 Enterprise Tape Library Support 205 .o object module that applications compile with for existing 3494 support. 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 volumes into categories that can be assigned by an application and operations that can specify a category only rather than a specific volume. smc1.c libsmc_linux.c 3494 API Emulation libsmc_sun.c Figure 48. LIBSMC and OS Components Using the 3494 API Emulation and MTLIB Program Refer to the IBM Tape Device Drivers Installation and User’s Guide and the IBM Tape Device Drivers Programmer’s Reference for the complete description of 3494 library support and the mtlib program and syntax.3494 Library Emulation LIBSMC and O/S Components libsmc_aix. For example. If the library name is a logical operating system SMC library name then the libsmc support is used. All volumes in an SMC library are category 0000. 206 IBM Tape Device Drivers Installation and User’s Guide a28t1002 . the NULL category. Otherwise.c libsmc_win. SMC libraries on AIX are named smc0. SCSI Medium Changers do not provide a similar function.c AIX Atape Device Driver Solaris IBMtape Device Driver HPUX atdd Device Driver Linux IBMtape Device Driver Windows IBMtape Device Driver SCSI Medium Changer Commands libsmc_hp. the lmcpd support is used.c libsmc. 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. For example. The request id can then be queried at any time to determine if the operation is still pending. or is unknown. 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. These applications and mtlib scripts do not require any changes. the following API and mtlib command options cannot be used. The mtlib commands such as -qV and -qI for example that require reading all the slot information from the library also vary in the amount of time it takes for the command to complete. demount. the shorter time it takes to complete the mtlib command and a larger number of slots in the library takes longer.3494 Library Emulation Because volume categories are not supported. and eject operations asynchronously and initially returns a request id to the host for the operation. completed. 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. v v v v v v Reserve category mtlib -r option Release category mtlib -R option Change a volume 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. Performance Considerations The performance time of mtlib commands issued to a SCSI 3584 library versus a 3494 vary and some performance times may be significantly higher. using the no wait option on a demount operation so the application can continue while the library is demounting the volume. 3494 Enterprise Tape Library Support 207 . The fewer the number of slots that are in the library. Chapter 9. The operation is synchronous on both a 3494 and SMC library and no request id is returned to the application. 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. audit. the operation on an SMC library is still synchronous and request id 0 is returned to the application. Applications that use the Query Message ID or mtlib -i option to determine when the return request id operation completes may require changes. 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. Applications and mtlib scripts that use these functions might require changes. These applications and mtlib scripts do not require any changes but do take the same amount of time as using the wait option. communicates with tape libraries defined in a configuration file. Customization of this file is described in “Defining Tape Libraries to the Daemon” on page 210. which provides a command-line interface to the library.conf. Data Flow for AIX 3494 Enterprise Tape Library Driver Product Requirements The following hardware and software components are supported by IBM. This file.or fibre-attached tape drives providing backup and restore functions. an application daemon (lmcpd) that communicates with the 3494 Library Manager (LM). Figure 49. ibmatl. 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. known to AIX specifically as the IBM Library Manager Control Point Daemon (lmcpd). The daemon. A typical environment for the AIX 3494 Enterprise Library Driver is an RS/6000 or System p (also known as pSeries) server on a local area network (LAN) with SCSI. Data Flow The software described in this chapter covers the library device driver and the interface between the application and the library device driver. and a utility program (mtlib). 208 IBM Tape Device Drivers Installation and User’s Guide .AIX 3494 Enterprise Tape Library Driver AIX The software consists of an Automated Tape Library Device Driver (atldd). is placed in the /etc directory when the software package is installed. For more information refer to Figure 49. 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 native serial port or on the eight port or 16 port asynchronous adapter.” on page 301 Installation Instructions Use the standard set of AIX methods to install and configure the LMCP devices. and later releases on IBM POWER-based servers. connect the LAN cable from the Token Ring or Ethernet adapter card in the workstation to the 3494 Tape Library. If a LAN connection is needed. You must have root authority to perform these operations.AIX 3494 Enterprise Tape Library Driver Hardware Requirements The library driver supports the following hardware: v 3494 Enterprise Tape Library with SCSI-attached IBM 3490E (Model C1A. C2A. Enter the following command to list the currently installed version of the 3494 Enterprise Library Driver: lslpp -l atldd. Chapter 9. and 3592 tape drives v One of the following options. 3590.LAN cabling (as required) v IBM System Storage TS1120 Tape Drive Model EO5 v IBM Virtualization Engine TS7510 Software Requirements The following software is required for the library driver: v AIX 5L. Installation Procedure Refer to Appendix A.24 meters [50 feet]) IBM TotalStorage Virtual Tape Server (models B10. “Accessing Documentation and Software Online. refer to Appendix A.2.driver Connecting the IBM TotalStorage Enterprise Tape Library If a TTY connection is needed. v AIX Tape and Medium Changer Device Driver (Atape) To obtain the most current service and documentation for this software. or F1A). B18. 3494 Enterprise Tape Library Support 209 .Token Ring or Ethernet Adapter support in an RS/6000 or pSeries workstation attached to the Library Manager . and B20) – LAN: .1 and 5. Note: The cable (RS-232 or LAN) must be in place before the software is installed to ensure proper initialization of the driver. “Accessing Documentation and Software Online.” on page 301 for information on obtaining the latest versions of the device driver and the latest documentation. 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 15. Versions 5. Note: Ensure that duplicate IP addresses are not used in this file or unpredictable results can occur. you must configure all 3490E or 3590 tape drives in the 3494 Tape Library. Enter the following command: smit tty Select the following options: 1. Refer to “Configuring the Library Manager Control Point” on page 211 for instructions. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each library. Add TTY Menu: Enter the port number. 6. Use smit to configure the serial port. Connection type is used to define the type of connection to the library (either RS-232 or TCP/IP). Press F4 to generate a list of possible values. The symbolic names must be unique across all libraries defined in the /etc/ibmatl. this type is the device special file name of the tty device (for example. this type is the IP address of the Library Manager. If the High Availability Library has a dual 210 IBM Tape Device Drivers Installation and User’s Guide . you must configure the serial port to which it is connected. The host name of the workstation is usually the best name to use (although it is not necessary). 3.conf file. one stop bit. the second IP address of the dual LAN card should be entered after the first IP address. Repeat steps 1 through 8 for each tape library connected to the workstation. For RS-232 connections. 5. TTY Menu: Add a tty device.conf file must be edited to define the tape libraries to the lmcpd. 7. This identifier has a maximum of eight characters. Press the Return key to configure the tty device. Press F4 to generate a list of possible values. 4. Add TTY Menu: Set Enable program to Off. For TCP/IP connections. no parity. This parameter is used only to identify a particular host to the 3494 Enterprise Library Manager. /dev/tty0 or /dev/tty1). Identifier is used to specify a name by which the Library Manager identifies the host machine. Add TTY Menu: Set baud rate to 9600. Configuring the IBM 3490E or TotalStorage 3590 Tape Drive To operate the 3494 Enterprise Tape Library successfully through the configured LMCPs. Selection Menu: Select the appropriate parent serial adapter. Use the Tab key to toggle the value. Add TTY Menu: Set Enable LOGIN to disable. Alternate LAN Connection is used to specify an alternate IP address for a 3494 High Availability LAN attached configuration.AIX 3494 Enterprise Tape Library Driver Configuring the Serial Port After the 3494 Tape Library is connected to the workstation. the /etc/ibmatl. Defining Tape Libraries to the Daemon After the software is installed and the desired tape libraries are connected to the system. If the Library has a dual LAN card installed. Add TTY Menu: eight data bits. 2. 8. 32. Chapter 9. The following stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation.115.14. The address of the Library Manager on the 3494 Tape Library is 9. The library uses the mercury identifier for the host.115. libmgrc7 9. The library uses the mercury identifier for the host.22 mercury 9. The first address of the Library Manager on the 3494 Tape Library is 9.21 9.13 and 9.32.115.115.115.22.32. Enter the following command: smit The system management interface tool (smit) main menu is displayed (refer to Figure 50).32. you can configure the instances of the LMCP. The library uses the jupiter identifier for the host. The IP addresses of the first Library Manager are 9.115.115.13 9.115.46.46.22 mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation.22.32.115.17 This stanza defines the libmgrc9 High Availability library connected through TCP/IP to the workstation. The IP addresses of the second Library Manager are 9.21. Note: For RS-232 attachments.21 and 9.46. and the serial port is configured.32. a tape library is connected to the workstation. 3494 Enterprise Tape Library Support 211 .32.115.115. libmgrc9 9. libmgrc8 9.46. The IP addresses of the dual Library Managers are 9.115.115.26.32.14 Configuring the Library Manager Control Point After the driver is installed.32. The following examples show how to define the library name: libmgrc7 /dev/tty0 mercury This stanza defines the libmgrc7 library connected by /dev/tty0 to the workstation. libmgrc7 9.15 telos 9.21 9.21 and the second address is 9.AIX 3494 Enterprise Tape Library Driver LAN card installed.115.26. the alternate LAN connection is not applicable.115.115. The library uses the mercury identifier for the host. Perform the following procedure to define and configure the LMCP: 1.21 jupiter This stanza defines the libmgrc8 library connected through TCP/IP to the workstation. Failover for RS-232 connections proceeds over the single serial line.26.15 and 9.115.17. the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address.26.32.115. 3. Configure Devices Added after IPL Printer/Plotter TTY Asynchronous Adapters PTY Console Fixed Disk CD ROM Drive Optical Disk Drive Diskette Drive Tape Drive • • • Figure 51.AIX 3494 Enterprise Tape Library Driver System Management Move cursor to desired item and press Enter. Use the up (↑) arrow and down (↓) arrow keys to move the cursor to the desired item on the menu. Software Installation and Maintenance Devices Physical & Logical Storage Security & Users Diskless Workstation Management & Installation Communications Applications and Services Spooler (Print Jobs) Problem Determination Performance & Resource Scheduling System Environments Processes & Subsystems Applications Using SMIT (information only) F1=Help F9=Shell F2=Refresh F10=Exit F3=Cancel Enter=Do F8=Image Figure 50. Select Devices (item 2) from the smit main menu. Select Tape Drive from the Devices menu (refer to Figure 51). Press Enter or click Do if you are processing smit in a windowed environment. SMIT Devices Menu The Tape Drive menu is displayed (refer to Figure 52). SMIT Main Menu 2. Devices Move cursor to desired item and press Enter. 212 IBM Tape Device Drivers Installation and User’s Guide . including mount and demount commands. The default is to wait forever until the command completes. 5. 8mm 9trk 150mb ost drive drive drive atl scsi scsi scsi scsi 3420 3480 3490 library 2. [Entry Fields] [] [libmgrc7] [] Logical Name of LMCP (optional) Library Name (F4 to list library names) Command Timeout in Minutes + Figure 54. Select the Library Manager control point from the Tape Drive Type menu (refer to Figure 53).conf file. a unique name is assigned automatically. Tape Drive Type Move cursor to desired item and press Enter. where: n is a number that indicates the LMCP entry and starts with zero for the first LMCP defined. List All Defined Tape Drives List All Supported Tape Drives Add a Tape Drive Change / Show Characteristics of a Tape Drive Remove a Tape Drive Configure a Defined Tape Drive Generate Error Report Trace a Tape Drive Figure 52. If the field remains blank. SMIT Tape Drive Menu 4. The Tape Drive Type menu is displayed (refer to Figure 53). Press Enter AFTER making all desired changes.AIX 3494 Enterprise Tape Library Driver Tape Drive Move cursor to desired item and press Enter. The Logical Name field for the Library Manager control point is optional. 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. Select Add a Tape Drive from the Tape Drive menu (Figure 52). Refer to “Defining Tape Libraries to the Daemon” on page 210 for a description of this file. Add an LMCP Logical Device Menu Chapter 9. The assigned name is lmcpn. Add an LMCP Logical Device Type or select values in entry fields. The Library Name field must be one of the library names defined in the /etc/ibmatl. Tape Drive Type Menu The Add an LMCP Logical Device menu is displayed (refer to Figure 54).3 GB 8 mm Tape Drive 1/2 Inch 9 Track Tape Drive 150 MB 1/4 Inch Tape Drive Other SCSI Tape Drive 3420 Tape Drive 3480 Tape Drive 3490 Tape Drive LAN/TTY Library Manager Control Point Figure 53. 3494 Enterprise Tape Library Support 213 . Return to the smit Tape Drive menu (refer to Figure 52). Cancel the COMMAND STATUS window by pressing F3. lmcp0 Defined Figure 55. Continue selecting the Library Manager control points for configuration until all the devices are configured. COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion. Configure a Defined LMCP COMMAND STATUS Window 11. you must load the daemon manually using the following command: 214 IBM Tape Device Drivers Installation and User’s Guide . 13.AIX 3494 Enterprise Tape Library Driver 6. 12. The COMMAND STATUS window opens with the Command: OK status. additional instructions may appear below. A list of LMCP devices is displayed (refer to Figure 56). You have completed the configuration of Library Manager control points to the system. LMCP COMMAND STATUS Window 7. lmcp0 Available Figure 57. additional instructions may appear below. and the Library Manager control point is shown as Available (refer to Figure 57). Loading the Daemon The lmcpd is loaded during the system initialization. COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion.3 GB 8 mm Tape Drive Defined 00-01-01-20 IBM SSD 3490E Tape Drive Defined LAN/TTY Library Manager Control Point F2=Refresh F10=Exit F3=Cancel Enter=Do Figure 56. Exit from the smit menu. Configure an LMCP Selection List 10. Select Configure a Defined Tape Drive from the smit Tape Drive menu. rmt0 rmt1 lmcp0 F1=Help F8=Image Available 00-00-0S-50 2. The logical name of the Library Manager control point is displayed as Defined (refer to Figure 55). 8. Select a defined Library Manager control point to configure from the LMCP Selection list. 9. Tape Drive Move cursor to desired item and press Enter. The COMMAND STATUS window opens with the Command: OK status. Repeat steps 4 through 6 to define any additional Library Manager control points. The LMCP Selection window opens again. During the initial installation of the driver. driver Special Files After the driver is installed and a Library Manager control point is configured and made available for use.driver or use the following installp command: installp -u atldd. It is similar to taking the device offline. Chapter 9. Deconfigure the LMCP device using one of the following procedures: 1. Uninstall Procedure All devices using the atldd driver must be closed and not in use when atldd is uninstalled or the uninstall fails. /dev/lmcp0) associated with it. replace the letter n with the appropriate number for the chosen device. access is provided through the special files. The first method deconfigures the device but leaves the device defined in the configuration database. Deconfiguring the Library Manager Control Point In the following examples.AIX 3494 Enterprise Tape Library Driver cfgmgr You can access the 3494 Enterprise Tape Library after the above command is executed. The second method takes the device offline and removes the device definition from the device database. Enter the following command to deconfigure the /dev/lmcpn device but leave it defined in the device database: rmdev -l lmcpn 2. enter the following command: ps -efa | grep lmcpd You can see multiple instances of the daemon running (which is typical). The error templates follow the same form as the default AIX error log entries. To verify that the daemon is loaded correctly. These special files are in the /dev directory. The standard AIX interface is provided for problem determination. Error Logging The driver provides logging to the system error log for various errors. 3494 Enterprise Tape Library Support 215 . but only one instance has a parent process ID of 1. You can uninstall the atldd using the smit command menu to uninstall software and selecting atldd. View the error log using the smit or the errpt command. Each instance of an LMCP has exactly one special file (for example. Problem Determination A set of tools is provided with the device driver to determine if it is functioning correctly. Enter the following command: rmdev -l lmcpn -d The device driver modules are not unloaded from the kernel until the last tape device is deconfigured. Enter the following command to view the trace: trcrpt > lmcp. 216 IBM Tape Device Drivers Installation and User’s Guide .trcfmt file is installed into /etc during installation.conf) (name of library) (delete all log files.out This command formats the trace output into a readable form and places it in a file for viewing. requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument. The hookword used by the device driver is 426.trace.AIX 3494 Enterprise Tape Library Driver AIX Device Driver Trace Facility The AIX trace facility is supported for the device driver. The /etc/lmcp. Daemon Trace Facility The following trace facility is available for the lmcp daemon and device driver: trcatl -[ald] Arguments: -a -l <name> -d (trace all libraries defined in /etc/ibmatl. Enter the following command to stop the trace: trcstop This command stops the trace after the tape operations are performed. The trace can be initiated at any time before an operation on a tape device. The trace event is identified with a hookword. It provides the formatting statements needed by trcrpt. 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 events with the 426 hookword. That is. The /etc/ibmatl. Refer to “Defining the Symbolic Name to the lmcpd” on page 233 for more information.conf configuration file is used to define the attachment for each library. it is not an extension of the operating system kernel. The lmcpd is a process that is always running on the system. The Library Manager control point daemon (lmcpd) is provided in the package. The interface between the application and the library driver is described in the IBM Tape Device Drivers: Programming Reference. a utility program that provides a command-line interface to the daemon and a C object module that can be linked with user applications to provide a communication interface with the daemon. this is a program that runs unattended in the background to perform a standard service. This software is known as a driver throughout this document because it provides the software and interface necessary to drive the 3494 Tape Library. Chapter 9. the product does not consist of a device driver in the true sense of the term. Figure 59 on page 225 illustrates the data flow. Data Flow The software described in this chapter covers the library driver. others operate periodically. such as a SCSI tape device driver. Some daemons are triggered automatically to perform their task. A typical environment for the HP-UX Automated Tape Library Driver is an HP workstation that acts as a data server on a network with SCSI tape devices providing backup or restore and data server functions. It provides direct communication with the 3494 Enterprise Library Manager.HP-UX 3494 Enterprise Tape Library Driver 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. 3494 Enterprise Tape Library Support 217 . An application links with the supplied C object module using the interface described in the IBM Tape Device Drivers: Programming Reference. The lmcpd communicates with the Library Manager through TCP/IP. However. Note: In the HP-UX operating system. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX namespace sockets. 0. B18.HP-UX 3494 Enterprise Tape Library Driver Tape Device Driver Adapter Device Driver Physical Tape Drive Application C Object Module Figure 58. v2.20. Hardware Requirements The following hardware is required for the library driver: v 3494 Enterprise Tape Library with 3590 drives in HP-UX 11. “Accessing Documentation and Software Online. and v3 v IBM Tape and Medium Changer Device Driver for HP-UX To obtain the most current service and documentation for this software. and B20 Virtual Tape Server (direct attached only) v 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 driver: v HP-UX Version 10. 11. 11i v1. 11i v1 and v2 v Enterprise Model B10. refer to Appendix A.” on page 301.0.0. 11i v1 and v2 and 3592 drives in 11.0. 11i v1. v2 and v3. v IBM Virtualization Engine TS7510 and TS7520 in HP-UX 11. Data Flow for HP-UX 3494 Enterprise Tape Library Driver Product Requirements The following software and hardware are required to use this product. 218 IBM Tape Device Drivers Installation and User’s Guide a250106 LMCPD TCP/IP Library Manager . you can reissue the command without the ’-p’ flag to perform the actual operation. v The SD commands are moderately complex scripts that usually proceed in several steps. Installation Overview LAN support must exist on the machine before installing the IBM Tape Library driver for HP-UX. 2. swinstall. refer to the HP-UX documentation appropriate for the LAN support that you are using. Install and configure the LAN support before proceeding with the installation of the lmcpd package. Note: If an earlier version of the product is installed on the machine.0 (32 bit application interface object module with +z option) Chapter 9.o (64 bit application interface object module) v /usr/lib/libibmz. The IBM Tape Library Driver for HP-UX is the lmcpd package. The steps are typically Selection. If you run into unexpected results during the installation. filenames given on the command line must be referenced with an absolute path. Copy the software from the distribution medium to the depot. 1. so it is a good idea to observe carefully the results of the installation process as it occurs. Analysis. For more information. The following files are installed on the system: v /etc/lmcpd (Library Manager control point daemon) v /etc/ibmatl.HP-UX 3494 Enterprise Tape Library Driver Software Compatibility The following optional software is supported by the library driver: IBM Tivoli Distributed Storage Manager for HP-UX Installation Instructions This chapter describes how to install.conf (configuration file) v /usr/lib/libibm. Check the README file and verify that your system is configured appropriately for installing the lmcpd software. swcopy) can be run initially with the ’-p’ flag to preview the command. After observing the preview output. v All the SD commands (for example. Refer to “Uninstall Procedure” on page 235 for more information. Using ’pwd’/filename to reference a file instead of filename ensures this. check the associated log file. and uninstall the HP-UX Automated Tape Library Support for the 3494 Enterprise Tape Library. The IBM Tape Library driver for HP-UX is installed using the standard swinstall process. execute the uninstall procedure before you enter the following commands. Each step may produce useful information and error messages. 3. and Execution. configure.o (32 bit application interface object module) v /usr/lib/libibm64. 3494 Enterprise Tape Library Support 219 . The distribution diskette contains a swinstall process that includes the lmcpd daemon with other associated files and utilities. You must have root authority to perform this installation procedure. Install and configure the software. Command Sequence Information Please take note of the following facts about the command sequences described in this section: v In some of the examples. It is not overwritten. detailed in the following sections: 1.x.conf file is preserved. “Install the Product” on page 220 Copy the Software to the Software Depot Attention: If you do not copy the lmcpd software into a depot.0 (64 bit application interface object module with +Z option) v /usr/lib/libibm_ia64.x lmcpd (preview option) # swcopy -s /driver_location/lmcpd.x. The following commands install lmcpd from the depot to the default root file system: # swinstall -p lmcpd (preview 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 swverify command: 220 IBM Tape Device Drivers Installation and User’s Guide . “Copy the Software to the Software Depot” on page 220 2.hpux. Copy the appropriate driver to the Software Depot. Install the Product Manually Installing the product manually requires two steps. the lmcpd software can be installed to the root file system using the HP-UX swinstall command. For example: # swcopy -p -s /driver_location/lmcpd.x.x. A copy of ibmatl. you cannot easily uninstall the software.h (application interface header file) v /usr/bin/mtlib (tape library driver utility program) v /usr/bin/intlib64 (64 bit tape library driver utility program) v /usr/bin/mtevent (tape library driver utility program) v /usr/bin/trcatl (tape library driver diagnostic program) v /opt/lmcpd (subdirectory) v /opt/lmcpd/ibmatl.HP-UX 3494 Enterprise Tape Library Driver v /usr/lib/libibm64z.conf is also installed in the /opt/lmcpd directory.hpux.0 (64 bit application interface object module with +Z option for Itanium system) v /usr/include/sys/mtlibio.x.conf (backup configuration file) Note: If this is an update of the lmcpd package.x lmcpd Use swlist to verify that the lmcpd software is in the depot: # swlist -d lmcpd Install the Product When the software is in the depot.x.0 (64 bit application interface object module with +z option for Itanium system) v /usr/lib/libibm_ia64z. the existing /etc/ibmatl. 32. The symbolic names must be unique across all libraries defined in the ibmatl.46. libmgrc7 9.32. Alternate LAN Connection is used to specify an alternate IP address for an Enterprise High Availability LAN configuration. For TCP/IP connections. This parameter is used only to identify a particular host to the 3494 Library Manager. the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address.115.conf file must be edited to define the library devices to the lmcp daemon.32.115.32. although any name is acceptable. Connection type defines the type of connection to the library.115. Defining the Library Device to LMCPD After the software is installed and all desired tape libraries are connected to the system. the second IP address of the dual LAN card should be entered after the first IP address.115. The address of the Enterprise Library Manager is 9.21 jupiter This stanza defines the 3494a library connected to the host. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library. If the High Availability Library has a dual LAN card installed. The IP addresses of the dual Library Managers are 9.115.115. The library uses the mercury identifier for the host.32.32.115. The IP Chapter 9. The connection must be in place before the software is installed to ensure proper initialization of the daemon. If the Library has a dual LAN card installed.115.HP-UX 3494 Enterprise Tape Library Driver # swverify 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.46. The symbolic network name of the host is usually the best name to use. For each 3494 Enterprise Tape Library connected through TCP/IP.conf file. The first address of the Library Manager on the 3494 Tape Library is 9.21 and the second address is 9. Identifier is used to specify a name by which the Library Manager identifies the host machine. Consult your network administrator if you need help with this task.46.115. libmgrc9 9. The tape library uses jupiter as the identifier for the host. ensure that your machine has access to the Library Manager on the 3494 Enterprise Tape Library.17. This identifier has a maximum length of eight characters.15 telos 9. 3494 Enterprise Tape Library Support 221 .21.46. The following stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation. this type is the IP address of the 3494 Enterprise Library Manager.21 9.22 mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation.22. the /etc/ibmatl. Use the ping utility to verify that you have network connectivity to the Library Manager.17 This stanza defines the libmgrc9 High Availability library connected through TCP/IP to the workstation.15 and 9.115. The following examples show how to define the library name: 3494a 9. then enter the /etc/lmcpd command to start the daemon again. Uninstall Procedure Attention: Do not try to uninstall the lmcpd software by deleting the files that make up the lmcpd fileset.115. Kill the lmcpd daemon if it is currently executing. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process.14 Adding or Deleting Entries in the Library Device You can add or delete entries in /etc/ibmatl.22.115. changes do not take effect until the daemon is started again. However.13 and 9.1.26.115.21 9.conf at any time.115. Ensure that the library activity on all of the libraries is completed before starting the lmcpd again. It is best to use the swremove command. The library uses the mercury identifier for the host.32. Halt all library activity before starting the uninstall procedure.22 mercury 9.115.26. To remove the lmcpd software from the root file system enter: # swremove -p lmcpd # swremove lmcpd Other Administrative Tasks To determine what versions of the lmcpd software are currently installed on the default root file system: # swlist -a state lmcpd To determine what versions of the lmcpd software are stored in the default depot: # swlist -d state lmcpd To view the set of files installed with the lmcpd software: # swlist -l file lmcpd To remove the lmcpd software from the depot: # swremove -d lmcpd If more than one level of lmcpd exists in the depot.14.115. 222 IBM Tape Device Drivers Installation and User’s Guide .13 9.26.0 Problem Determination A set of tools is provided with the software to determine if the lmcpd is functioning correctly. For example: # swremove -d lmcpd.8.32.21 and 9.r=4. explicitly specify the level to remove it.32. libmgrc7 9.32.26. The IP addresses of the second Library Manager are 9.115.HP-UX 3494 Enterprise Tape Library Driver addresses of the first Library Manager are 9.115. refer to your system administration manuals.conf file. The lmcpd uses the daemon facility for logging errors. Chapter 9. For more information about using syslog.HP-UX 3494 Enterprise Tape Library Driver Error Logging The lmcpd uses the syslog facility to log the errors. Errors are logged according to the /etc/syslog. requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument. 3494 Enterprise Tape Library Support 223 . Daemon Trace Facility The following trace facility is available for the lmcpd daemon: trcatl -[ald] Arguments: -a -l <name> -d (trace all libraries defined in /etc/ibmatl.conf) (name of library) (delete all log files. Only errors are logged with this facility. others operate periodically.conf configuration file is used to define the attachment for each library.Linux 3494 Enterprise Tape Library Driver 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 provides a command-line interface to the daemon. A typical environment for the Linux Automated Tape Library Driver is a Linux workstation that acts as a data server on a network with tape devices providing backup or restore and data server functions. The lmcpd is a process that is always running on the system. Note: In the Linux operating system. to perform a standard service. However. This software is known as a driver throughout this document because it provides the software and interface necessary to drive the 3494 Tape Library. That is. The /etc/ibmatl. 224 IBM Tape Device Drivers Installation and User’s Guide . in the background. An application links with the supplied C object module using the interface described in the IBM Tape Device Drivers: Programming Reference. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX namespace sockets. It provides direct communication with the Library Manager. Data Flow The software described in this chapter covers the library driver. The lmcpd communicates with the Library Manager through TCP/IP. such as a tape device driver. the product does not include a device driver in the true sense of the term. and a C object module that can be linked with user applications to provide a communication interface with the daemon. it is not an extension of the operating system kernel. Refer to “Defining the Symbolic Name to the lmcpd” on page 233 for more information. this is a program that runs unattended. The Library Manager control point daemon (lmcpd) is provided in the package. The interface between the application and the library driver is described in the IBM Tape Device Drivers: Programming Reference. Figure 59 on page 225 illustrates the data flow. Some daemons are triggered automatically to perform their task. 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 driver: v For Linux distribution support. refer to 94 v IBM Tape and Medium Changer Device Driver (IBMtape) for Linux Chapter 9. 3494 Enterprise Tape Library Support a250106 LMCPD TCP/IP Library Manager 225 .Linux 3494 Enterprise Tape Library Driver Tape Device Driver Adapter Device Driver Physical Tape Drive Application C Object Module Figure 59. Hardware Requirements The following hardware is required for the library driver: v IBM TotalStorage 3494 Enterprise Tape Library with IBM 3590 and 3592 drives with the Fibre Channel Attachment v IBM System Storage TS1120 Tape Drive v IBM Virtualization Engine TS7510 v One of the following options. Data Flow for Linux 3494 Enterprise Tape Library Driver Product Requirements The following hardware and software components are required and supported by IBM. In the subsequent pages.x.x. (ibmatl).x in them.x. refer to Appendix A. 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.x is the version) /usr/share/doc/ibmatl-x. configuration.x. The following sections describe installation.x. This section assumes that you are installing ibmatl on a system where it is not installed. Installation Procedure If ibmatl is already installed on your system.x. removal.x refer to the version of the driver.x. The xxxx or x. where x. Install and configure the LAN support before proceeding with installation of the ibmatl package. refer to the Linux documentation appropriate to the LAN support you are using. Installation and Configuration Instructions The IBM Tape Library driver for Linux.x.x.” on page 301.x.os.x. For each 3494 Tape Library connected through 226 IBM Tape Device Drivers Installation and User’s Guide .x.x. where . is supplied in an rpm package.o (application interface object module) /usr/lib/libibm64.x is the version) Note: If this is an update of the ibmatl package. “Accessing Documentation and Software Online.x.h (application interface header file) /usr/bin/mtlib (tape library driver utility program) /usr/bin/mtlib64 (64-bit tape library driver utility program for 64-bit IBM zSeries system only) /usr/bin/mtevent (tape library driver utility program) /usr/bin/trcatl (tape library driver diagnostic program) On the IBM Linux for IBM S/390 and zSeries systems.rpm Connecting the TotalStorage Enterprise 3494 Tape Library Use a LAN connection (either Ethernet or Token Ring) through TCP/IP. For more information.conf (configuration file) /usr/lib/libibm.x/license (license file.x.x. Run the following command to install ibmatl rpm package: >rpm -ivv ibmatl.x. refer to “Updating Procedure” on page 228. The following files are installed on your system: /etc/lmcpd (library manager control point daemon) /etc/ibmatl. The connection must be in place before the software is installed to ensure proper initialization of the daemon. Use the actual driver version numbers as you perform the procedures. which will change as IBM releases new driver levels. Refer to any Linux distribution supporting rpm for rpm command information.conf file is preserved (it is not overwritten). documentation files are installed at: /usr/share/doc/ibmatl-x. and verification procedures for ibmatl. you will see file names with xxxx or x. You must have root authority to proceed with the installation of the driver. the existing /etc/ibmatl.Linux 3494 Enterprise Tape Library Driver To obtain the most current service and documentation for this software.o (64-bit application interface object module for 64-bit IBM zSeries system only) /usr/include/sys/mtlibio.x/README (readme file. 21 9. The IP addresses of the first Library Manager are 9.115. libmgrc7 9. the second IP address of the dual LAN card should be entered after the first IP address.21 jupiter This stanza defines the 3494a library that is connected to the host.21.32. For TCP/IP connections.46.26. libmgrc9 9.22 mercury 9.17. The library uses the mercury identifier for the host. This identifier has a maximum length of 8 characters.32.32. The IP addresses of the dual Library Managers are 9. The tape library uses jupiter as the identifier for the host.22.115.26.15 telos 9.15 and 9. The address of the 3494 Library Manager is 9.115.14. Defining the Library Device to the lmcpd After the software is installed and tape libraries are connected.13 and 9. The following examples show how to define the library name: 3494a 9. libmgrc7 9. If the Library has a dual LAN card installed.115.115. Connection type is used to define the type of connection to the library.conf file must be edited to define the library devices to the lmcpd.32. 3494 Enterprise Tape Library Support 227 . The first address of the Library Manager on the 3494 Tape Library is 9. The symbolic network name of the host is usually the best name to use.46.32.26.115. ensure that your machine has access to the Library Manager on the 3494 Tape Library.Linux 3494 Enterprise Tape Library Driver TCP/IP. the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. the /etc/ibmatl. The symbolic names must be unique across all libraries defined in the ibmatl.115. Identifier parameter is used to specify a name by which the Library Manager identifies the host machine.115.115. Consult your network administrator if you need help with this task.46.115.32.21 9.22 mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation.32.21 and 9.26.conf file.115.115. The IP addresses of the second Library Manager are 9. The library uses the mercury identifier for the host. Use the ping utility to verify that you have network connectivity to the Library Manager.17 This stanza defines the libmgrc9 High Availability library that is connected through TCP/IP to the workstation.115. Chapter 9.32. This parameter is used only to identify a particular host to the 3494 Library Manager.14 This stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation.21 and the second address is 9.46. Alternate LAN Connection is used to specify an alternate IP address for a 3494 High Availability LAN configuration.115.32.115.22.115.115.32. although any name is acceptable. this type is the IP address of the 3494 Library Manager.13 9. If the High Availability Library has a dual LAN card installed. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library.115. Note: Halt all library activity before starting the uninstall procedure.x.x. run the command rpm -e: rpm -evv ibmatl 228 IBM Tape Device Drivers Installation and User’s Guide .x. or replaced: >rpm -qs ibmatl Verifying the Install/Update If the IBMtape device driver 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 removing the files that make up the ibmatl fileset. Updating Procedure If your current ibmatl was installed from an rpm package previously. Ensure that activity on all libraries is completed before restarting the lmcpd. For the rpm package. issue the following command: rpm -Uvv rpm -Uvv ibmatl.x.rpm --for IBM Linux on S/390 systems --for Red Hat Intel PC based systems Querying the Installed Package The query function is supported for the ibmatl rpm package only. and enter the /etc/lmcpd command to start the daemon again. To display information about ibmatl: >rpm -qi ibmatl To display the package’s file list.x.s390.rpm ibmatl.x. However.Linux 3494 Enterprise Tape Library Driver Adding or Deleting Entries in the Library Device You can add or delete entries in /etc/ibmatl.x. It is best to use the rpm -e command or the uninstall script.conf at any time. The installed rpm package can be queried by running the following commands to display information associated with the package. normal. enter the command: > rpm -ql ibmatl To display the states of files in the package. changes do not take effect until the daemon is started again.i386. for example. not installed.x. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process. Chapter 9. The ibmatl uses the daemon facility for logging errors. refer to your system administration manuals.0 Problem Determination A set of tools is provided with the software to determine if the ibmatl is functioning correctly.conf) (name of library) (delete all log files. 3494 Enterprise Tape Library Support 229 . rpm -evv ibmatl-5. requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument.conf file.0. Only errors are logged with this facility. explicitly specify the level to remove it. Daemon Trace Facility The following trace facility is available for the lmcpd daemon: trcatl -[ald] Arguments: -a -l <name> -d (trace all libraries defined in /etc/ibmatl. Error Logging The ibmatl uses the syslog facility to log the errors.Linux 3494 Enterprise Tape Library Driver If more than one level of ibmatl exists on the system. For more information about using syslog.7. Errors are logged according to the /etc/syslog. This software is known as a driver throughout this document because it provides the software and interface necessary to drive the Tape Library. The /etc/ibmatl.Solaris 3494 Enterprise Tape Library Driver Solaris The software consists of a daemon that communicates directly with the Library Manager of the 3494 Tape Library through RS-232 or LAN. Refer to “Defining the Symbolic Name to the lmcpd” on page 233 for more information. Data Flow The software described in this chapter covers the library driver. the product does not consist of a device driver in the true sense of the term. Figure 60 on page 231 illustrates the data flow. a utility program that provides a command-line interface to the daemon. such as a SCSI tape device driver. An application links with the supplied C object module using the interface described in the IBM Tape Device Drivers: Programming Reference. it is not an extension of the operating system kernel. It provides direct communication with the 3494 Library Manager. 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 lmcpd is a process that is always running on the system.conf configuration file is used to define the type of attachment for each library. 230 IBM Tape Device Drivers Installation and User’s Guide . and a C object module that can be linked with user applications to provide a communication interface with the daemon. A typical environment for the IBM Sun Automated Tape Library Driver is a Sun workstation that acts as a data server on a network with SCSI tape devices providing backup or restore and data server functions. However. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX namespace sockets. The Library Manager control point daemon (lmcpd) is provided in the package. The interface between the application and the library driver is described in the IBM Tape Device Drivers: Programming Reference. That is. LAN cable Chapter 9.24 meters [50 feet]) – LAN: . and B20) v 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 15. Hardware Requirements The following hardware is supported by the library driver: v 3494 Enterprise Tape Library with SCSI-attached 3490E (Model C1A or C2A). 3494 Enterprise Tape Library Support 231 a250093 Native TTY Device Driver .Token-Ring or Ethernet adapter card in a Sun workstation attached to the 3494 Enterprise Library Manager . Data Flow for Solaris 3494 Enterprise Tape Library Driver Product Requirements The following software and hardware are supported by this product. B18.Solaris 3494 Enterprise Tape Library Driver Tape Device Driver Adapter Device Driver Physical Tape Drive Application C Object Module TCP/IP LMCPD Library Manager Figure 60. 3590 and 3592 drives v IBM System Storage TS1120 Tape Drive v IBM Virtualization Engine TS7510 v IBM TotalStorage Virtual Tape Server (Models B10. Installation Procedure Use the following commands to install the lmcpd package. or 10 v IBM Tape and Medium Changer Device Driver for Solaris To obtain the most current service and documentation for this software. Preinstallation Considerations The LAN or TTY support must exist on the machine before installing the IBM Tape Library daemon for SunOS. It is not overwritten. 7. Note: If an earlier version of the product is installed on the machine. execute the uninstall procedure before you enter the following commands. refer to Appendix A.conf (configuration file) /usr/lib/libibm.o (64 bit application interface object module) /usr/include/sys/mtlibio.o (application interface object module) /usr/lib/libibm64. 232 IBM Tape Device Drivers Installation and User’s Guide .conf (backup configuration file) Note: If this is an update of the lmcpd package.h (application interface header file) /usr/bin/mtlib (tape library driver utility program) /usr/bin/mtevent (tape library driver utility program) /usr/bin/trcatl (tape library driver diagnostic program) /opt/lmcpd (subdirectory) /opt/lmcpd/ibmatl.conf file is preserved.conf is also installed in the /opt/lmcpd directory. Refer to “Uninstall Procedure” on page 235 for more information. 9. A copy of ibmatl. The IBM Tape Library Driver for Solaris is the lmcpd package. The following files are installed on the system: /etc/lmcpd (Library Manager control point daemon) /etc/ibmatl.Solaris 3494 Enterprise Tape Library Driver Software Requirements The following software is required for the library driver: v Sun Microsystems Solaris Version 2. Install and configure the LAN or TTY adapter and the associated LAN or TTY adapter device driver before proceeding with the installation of the lmcpd package.” on page 301. Software Compatibility The following optional software is supported by the library driver: IBM Tivoli Distributed Storage Manager for Solaris Installation Instructions The IBM Tape Library driver for Solaris is installed using the standard Sun package facility. For more information. the existing /etc/ibmatl. “Accessing Documentation and Software Online. You must have root authority to perform this installation procedure. 8.6. Substitute the device special file name for the installation source device that is appropriate for your system. refer to the documentation appropriate for the LAN or TTY adapter and the LAN or TTY adapter device driver that you are using. Solaris 3494 Enterprise Tape Library Driver If a previous version is installed on the system, uninstall the previous version first, enter the following command: /usr/sbin/pkgrm lmcpd To install the package from the directory that the driver is located, enter the following command: /usr/sbin/pkgadd -d lmcpd.x.x.x.x To verify 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: v Use a standard 25 pin null modem D-shell RS-232 cable. Place the cable on the native serial port or on the eight-port or 16 port asynchronous adapter. v 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 233. For each 3494 Tape Library connected through TCP/IP, ensure that your machine has access to the Library Manager on the Enterprise device. Use the ping utility to verify that you have network connectivity 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, in the Add 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: Data bits: Stop bits: Parity: 9600 8 1 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 device special file name of the tty device (for example, /dev/ttya or /dev/tty1). For TCP/IP connections, this type is Chapter 9. 3494 Enterprise Tape Library Support 233 Solaris 3494 Enterprise Tape Library Driver 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 Availability LAN-attached configuration. If the High Availability 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. Failover for RS-232 connections proceeds over the single serial line. The following examples show how to define the library name: 3494a /dev/ttya mercury This stanza defines the 3494a library that is connected by /dev/ttya to the workstation. The library uses the mercury identifier for the host. 3494b 9.115.32.21 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 9.115.32.21. The library uses the jupiter identifier for the host. libmgrc9 9.115.46.15 telos 9.115.46.17 This stanza defines the libmgrc9 High Availability library that is connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are 9.115.46.15 and 9.115.46.17. libmgrc7 9.115.32.21 9.115.32.22 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 9.115.32.21 and the second address is 9.115.32.22. The library uses the mercury identifier for the host. The following stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are 9.115.32.21 and 9.115.32.22. The IP addresses of the second Library Manager are 9.115.26.13 and 9.115.26.14. The library uses the mercury identifier for the host. libmgrc7 9.115.32.21 9.115.32.22 mercury 9.115.26.13 9.115.26.14 Adding or Deleting Entries in the Library You can add or delete entries in /etc/ibmatl.conf at any time. However, 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 activity on all of the libraries is completed before restarting the lmcpd. 234 IBM Tape Device Drivers Installation and User’s Guide Solaris 3494 Enterprise Tape Library Driver Uninstall Procedure Halt all library activity 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 Problem Determination A set of tools is provided 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 available for the lmcpd daemon: trcatl -[ald] Arguments: -a -l <name> -d (trace all libraries defined in /etc/ibmatl.conf) (name of library) (delete all log files; requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument. Chapter 9. 3494 Enterprise Tape Library Support 235 Windows 3494 Enterprise Tape Library Driver Windows The software consists of a tape library service that communicates directly with the Library Manager of the 3494 Enterprise Tape Library through LAN, a utility program that provides a command-line interface to the service, and a static library and DLL that can be used to provide a communication interface with the service. A typical environment for the Windows Automated Tape Library Service is a workstation running Microsoft Windows operating system that acts as a data server on a network with SCSI tape devices providing backup or restore and data server functions. The IBM Automated Tape Library service is provided in the installation package. This service 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 Device Drivers: Programming Reference. The subroutines in this module communicate with the Enterprise Library Manager to perform the various library operations. The service 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 Service” on page 240 for more information. Data Flow The software described in this chapter covers the library driver. The interface between the application and the library driver is described in the IBM Tape Device Drivers: Programming Reference. Figure 61 on page 237 illustrates the data flow. 236 IBM Tape Device Drivers Installation and User’s Guide Windows 3494 Enterprise Tape Library Driver Figure 61. Data Flow for Windows 3494 Enterprise Tape Library Driver Product Requirements The following hardware and software components are required and supported by IBM. Hardware Requirements The following hardware is required for the library driver: v 3494 Enterprise Tape Library with Enterprise Tape System 3590 and 3592 drives v IBM System Storage TS1120 Tape Drive v IBM Virtualization Engine TS7510 v IBM TotalStorage Virtual Tape Server (Models B10, B18, and B20) The following options are required for operation of the Enterprise Library Manager: v Token-Ring or Ethernet adapter card in an Intel- compatible workstation (486DX or higher) running Microsoft Windows NT or Microsoft Windows 2000 and attached to the 3494 Enterprise Tape Library v LAN cable Software Requirements The following software is required for the library driver: v A workstation running Microsoft Windows NT 4.0 with Fix Pack 3 or later v A workstation running Microsoft Windows 2000 Build 2195 or later v A workstation running Microsoft Windows Server 2003 Chapter 9. 3494 Enterprise Tape Library Support 237 Windows 3494 Enterprise Tape Library Driver v A workstation running Microsoft Windows Server 2008 v IBM Windows Tape Device Driver or the ADSM/TSM Device Driver for Microsoft Windows NT if using ADSM/TSM To obtain the most current service and documentation for this software, refer to Appendix A, “Accessing Documentation and Software Online,” on page 301. Installation Instructions The IBM Tape Library service 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 Server 2003 and Windows Server 2008 running on AMD64 and EM64T. Installation Procedure Use the following procedure to install the IBM Automated Tape Library Service or to upgrade the software level of your service on your workstation. Follow these steps to perform the installation of the service and its associated software: 1. Verify that the prerequisites are satisfied. Refer to “Product Requirements” on page 237. 2. Ensure that the workstation is on the LAN. 3. Log on as Administrator. 4. If the IBM Automated Tape Library Service is currently installed, ensure that all programs and services that use the service are stopped, and then remove it from the system. 5. Ensure that the IBM Automated Tape Library Service is not running. v On Windows NT, click the Start button, move to Settings, then click Control Panel. Double-click the Services icon. v On Windows 2000 and 2003, click the Start button, move to Settings, then click Control Panel. Double-click the Administrative Tools icon, then double-click the Services icon. v On Windows 2008, click the Start button, double-click the Administrative Tools icon, then double-click the Services icon. The Services 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 service is not installed; click Close. If there is an entry and the status is blank, the service is not running; click Close. If the status is Started, click IBM Automated Tape Library, then click Stop. v On Windows NT, wait for the service to stop and the Status to be set to blank, then click Close. v On 32–bit Windows 200x, wait for the service to stop and the Service status to be set to Stopped, then close both windows. v On 64–bit Windows, the service is stopped and removed automatically during the uninstallation. 6. Obtain ibmatl driver from the IBM storage FTP server in binary. 7. Locate and execute ibmatl driver. 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, 238 IBM Tape Device Drivers Installation and User’s Guide Windows 3494 Enterprise Library Service 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. 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 view 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 10. 12. After you click Finish, if you did not select to view the Read Me file, the installation dialog exits. If you chose to view 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 Service” on page 240 for details. 15. On Windows NT, start the service by restarting the system or using the Services option in the Control Panel window. On Windows 2000 and 2003, start the service using the Services icon, which is on the Administrative Tools icon in the Control Panel window. On Windows 2008, start the service using the Services icon, which is on the Administrative 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 servers, 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 service is started to ensure proper initialization of the service. Ensure that your machine has access to the Library Manager on the Tape Library. Use the ping utility to verify that you have network connectivity to the Library Manager. Consult your network administrator if you need help with this task. Chapter 9. 3494 Enterprise Tape Library Support 239 Windows 3494 Enterprise Library Service 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, in the Add LAN Host section. Defining the Symbolic Name to the Service 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 service. 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 9.115.32.21. The library uses the jupiter identifier for the host. 3494b 9.115.32.21 jupiter The Alternate LAN Connection parameter specifies an alternate IP address for an Enterprise High Availability LAN configuration. If the High Availability 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 Availability library that is connected through TCP/IP to the workstation. The IP addresses of the dual Library Managers are 9.115.46.15 and 9.115.46.17. libmgrc9 9.115.46.15 telos 9.115.46.17 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 9.115.32.21 and the second address is 9.115.32.22. The library uses the mercury identifier for the host. libmgrc7 9.115.32.21 9.115.32.22 mercury The following stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the first Library Manager are 9.115.32.21 and 9.115.32.22. The IP addresses of the second Library Manager are 9.115.26.13 and 9.115.26.14. The library uses the mercury identifier for the host. libmgrc7 9.115.32.21 9.115.32.22 mercury 9.115.26.13 9.115.26.14 Adding or Deleting Libraries to the Service You can add or delete entries in c:\winnt\ibmatl.conf at any time. However, changes do not take effect until the tape service starts again. 240 IBM Tape Device Drivers Installation and User’s Guide the next time that the system is started. move to Settings. Microsoft Windows NT tries (unsuccessfully) to start the service again. stop and start the service using the Services icon. Follow these steps to uninstall the service and its associated software: 1..Windows 3494 Enterprise Library Service On Windows NT. click Close. then double-click the Services icon. Ensure that all programs and services that use the IBM Automated Tape Library Service are stopped. Click the Start button. press Enter. If the status is blank. Open a Command Prompt window. On Windows 200x.. which is on the Administrative Tools icon in the Control Panel window. Scroll through the entries until you find IBM Automated Tape Library. 8. a Remove Programs from Your Computer window opens. follow the steps in “Installation Procedure” on page 238. 5. Scroll to and select IBM Automated Tape Library. 7. 3. Ensure that the library activity on all of the libraries is completed before starting the service again. v On 32–bit Windows 200x. wait for the service to stop and the Service status to be set to Stopped. click Change/Remove. 3494 Enterprise Tape Library Support 241 . wait for the service to stop and the Status to be set to blank. which indicates the components that were removed successfully. Note: If you forget this step. 6. Chapter 9. v On 64–bit Windows. The Services window opens. After various dialogs run.conf file if you want to keep a copy of this file because the uninstall procedure erases the file. Click Yes. Ensure that the IBM Automated Tape Library Service is not running. the service is stopped and removed automatically during the uninstallation. A Confirm File Deletion window opens. double-click the Administrative Tools icon. v On Windows NT. Back up the c:\winnt\ibmatl. v On Windows NT. then wait for the command to complete. Log on as Administrator. Note: If you are upgrading the software level of your service.. 10. Click OK to exit the dialog. click Add/Remove. then uninstall it. Double-click Add/Remove Programs in Windows NT/200x or Programs and Features on Windows 2008 in the Control Panel window. To resolve this situation. If the status is Started. enter lmcpd -remove. then click Close. 9. then click Stop. then close both windows. Uninstallation Procedure Use the following procedure to remove the IBM Automated Tape Library Service permanently from your workstation. For Windows 200x. you must reinstall the service. For Windows NT. stop and start the service using the Services option in the Control Panel window. the service is not running. v On Windows 200x. 4. double-click the Services icon. click IBM Automated Tape Library. then click Control Panel. 2. click Cancel on the Add/Remove Programs Properties window.out 242 IBM Tape Device Drivers Installation and User’s Guide . Problem Determination A tracing tool is provided with the software to determine if ibmatl is functioning correctly. For Windows NT. 3.Windows 3494 Enterprise Library Service 11.conf delete all logfiles in c:\WINNT\ Notes: 1. close the Add/Remove Programs Properties window. The trace. close the Programs and Features window. For Windows 2000 and 2003. Run trcatl in the window of ″Command Prompt″ 2. The ″-a″ parameter takes precedence over the ″-l″ parameter.out is located under the directory where the trcalt runs Examples: trcatl -l libmgrc7 trcatl -a > trace. For Windows 2008. Daemon Trace Facility The following trace facility is available for the ibmatl service: trcatl -h usage: trcatl [-ald] [-l <name>] [-a] [-d] name of library all libraries defined in c:\WINNT\ibmatl. TRU64 Enterprise Tape Library Driver TRU64 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. However. It provides direct communication with the Library Manager. 3494 Enterprise Tape Library Support 243 . The lmcpd is a process that is always running on the system. a utility program that provides a command-line interface to the daemon. The Library Manager control point daemon (lmcpd) is provided in the package. The interface between the application and the library driver is described in the IBM Tape Device Drivers: Programming Reference. Note: In the Tru64 operating system. to perform a standard service. it is not an extension of the operating system kernel. Figure 59 on page 225 illustrates the data flow. The lmcpd communicates with the Library Manager through TCP/IP. Chapter 9. An application links with the supplied C object module using the interface described in the IBM Tape Device Drivers: Programming Reference. such as a tape device driver. Data Flow The software described in this chapter covers the library driver. That is. the product does not include a device driver in the true sense of the term. The subroutines in this module communicate with the lmcpd to perform the various library operations using standard UNIX namespace sockets. This software is known as a driver throughout this document because it provides the software and interface necessary to drive the 3494 Tape Library. The /etc/ibmatl. others operate periodically. this is a program that runs unattended. in the background. A typical environment for the Tru64 Automated Tape Library Driver is a Tru64 workstation that acts as a data server on a network with tape devices providing backup or restore and data server functions. and a C object module that can be linked with user applications to provide a communication interface with the daemon. Refer to “Defining the Symbolic Name to the lmcpd” on page 233 for more information.conf configuration file is used to define the attachment for each library. Some daemons are triggered automatically to perform their task. TRU64 Enterprise Tape Library Driver Tape Device Driver Adapter Device Driver Physical Tape Drive Application C Object Module Figure 62. 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 Tru64 workstation Token-Ring cables (as required) – Ethernet Attach: Enterprise FC 5220 (Ethernet Adapter) Ethernet port or adapter for Tru64 workstation Ethernet cables (as required) Software Requirements The following software is required for the library driver: v Tru64 5.” on page 301. refer to Appendix A. Data Flow for TRU 64 3494 Enterprise Tape Library Driver Product Requirements The following hardware and software components are required and supported by IBM. To obtain the most current service and documentation for this software. Hardware Requirements The following hardware is supported by and required for the library driver: v IBM TotalStorage 3494 Enterprise Tape Library with IBM 3590 Model E1A or H1A drives with Fibre Channel interface.1A operating system. v One of the following options. 244 IBM Tape Device Drivers Installation and User’s Guide a250106 LMCPD TCP/IP Library Manager . “Accessing Documentation and Software Online. x.conf file is preserved (it is not overwritten). 3494 Enterprise Tape Library Support 245 . the existing /etc/ibmatl. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Chapter 9. Use the actual driver version numbers as you perform the procedures. Use the ping utility to verify that you have network connectivity to the Library Manager. For more information. In the subsequent pages.x in them. For each 3494 Tape Library connected through TCP/IP. in those directories.conf (configuration file) /usr/lib/libibm.conf file must be edited to define the library devices to the lmcpd.TRU64 Enterprise Tape Library Driver Installation and Configuration Instructions The IBM Tape Library driver for Tru64. You must have root authority to proceed with the installation of the driver. The xxxx or x.x. The following files are installed on your system: /etc/lmcpd (library manager control point daemon) /etc/ibmatl.h (application interface header file) /usr/bin/mtlib (tape library driver utility program) /usr/bin/mtevent (tape library driver utility program) /usr/bin/trcatl (tape library driver diagnostic program) /usr/doc/ibmatl/README (readme file) /usr/doc/ibmatl/license (license file) Note: If this is an update of the ibmatl package. Defining the Library Device to the lmcpd After the software is installed and tape libraries are connected.x. configuration. ensure that your machine has access to the Library Manager on the 3494 Tape Library. is a 64-bit software supplied in a product kit package. (ibmatl). you will see file names with xxxx or x. and verification procedures for ibmatl. refer to the Tru64 documentation appropriate to the LAN support you are using.x. along with the files the installation process creates. removal. The connection must be in place before the software is installed to ensure proper initialization of the daemon.x. You will also need to remember the name of the top level directory in order to uninstall and/or update the driver and utilities.x. Installation Procedure Obtain ibmatl driver from the IBM storage FTP server in binary and execute setld command to install ibmatl driver: /usr/sbin/setld -l /driver_location/ibmatl.x.kit Connecting the TotalStorage Enterprise 3494 Tape Library Use a LAN connection (either Ethernet or Token Ring) through TCP/IP.o (application interface object module) /usr/include/sys/mtlibio.x. When you are installing from a tar package of the product kit from our web site. you need to unpack the tar files and keep them in directories that were created. which will change as IBM releases new driver levels.x refer to the version of the driver. The following sections describe installation. Install and configure the LAN support before proceeding with the installation of the ibmatl package. the /etc/ibmatl. Consult your network administrator if you need help with this task. If the High Availability Library has a dual LAN card installed.26. If the Library has a dual LAN card installed.17.21 and the second address is 9.115.26.TRU64 Enterprise Tape Library Driver Symbolic name is used to identify each tape library. Use the UNIX kill command (kill -kill <pid>) to kill the lmcpd process.115.115. remove the old version existing in the system first and them update it.32.115. libmgrc7 9.14. The IP addresses of the first Library Manager are 9.21 jupiter This stanza defines the 3494a library that is connected to the host.15 and 9.22.22 mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. The address of the 3494 Library Manager is 9.13 9.conf at any time. The following stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation.115. and enter the /etc/lmcpd command to start the daemon again. The tape library uses jupiter as the identifier for the host. Updating Procedure To update the ibmatl kit. The following examples show how to define the library name: 3494a 9.32. This identifier has a maximum length of 8 characters. the second IP address of the dual LAN card should be entered after the first IP address. although any name is acceptable. However.32.32.conf file.115.115.115. The library uses the mercury identifier for the host.32.115.26. The symbolic names must be unique across all libraries defined in the ibmatl.32. Connection type is used to define the type of connection to the library.22 mercury 9. Identifier parameter is used to specify a name by which the Library Manager identifies the host machine. The symbolic network name of the host is usually the best name to use.32. Issue the command to check which version of ibmatl is installed: setld -l 246 IBM Tape Device Drivers Installation and User’s Guide .46.14 Adding or Deleting Entries in the Library Device You can add or delete entries in /etc/ibmatl. libmgrc7 9.13 and 9.46.22. The IP addresses of the second Library Manager are 9. changes do not take effect until the daemon is started again. Ensure that activity on all libraries is completed before restarting the lmcpd.115.32.26.46.21 9.21.32. the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. For TCP/IP connections.21 9. libmgrc9 9.115. The library uses the mercury identifier for the host.115.15 telos 9.21 and 9.46.115.115. The first address of the Library Manager on the 3494 Tape Library is 9. The IP addresses of the dual Library Managers are 9.115.115.115. this type is the IP address of the 3494 Library Manager.17 This stanza defines the libmgrc9 High Availability library that is connected through TCP/IP to the workstation.115.32. Alternate LAN Connection is used to specify an alternate IP address for a 3494 High Availability LAN configuration. This parameter is used only to identify a particular host to the 3494 Library Manager. x.conf is modified. setld -i To display the ibmatl product kit fileset and located directory. the setld -v executes any V phase processing included in the subset control program. Note: Halt all library activity before starting the uninstall procedure. Querying the Installed Package The query function is supported for the ibmatl product kit. Status. except during installation: setld -v IBMATL_Vxxxx Use the fverify command to verify the files of a specific subset. enter: setld -i IBMATL_Vxxxx Verifying the Install/Update To verify the existence of the installed ibmatl subset. and Description. It is best to use the setld -d command. permissions. Starting ibmatl Start the daemon using the following command: /etc/lmcpd Uninstall Procedure Attention: Do not try to uninstall the ibmatl product kit simply by removing the files that make up the ibmatl fileset.inv Note: Once the ibmatl.x.kit After the update.x.TRU64 Enterprise Tape Library Driver Uninstall the old version (yyyy): setld -d IBMATL_Vyyyy Install the new version: setld -l /driver_location/ibmatl. you have to remove it manually./IBMATL_Vxxxx. The system state is listed on standard output in three columns: Subset. the lmcpd daemon is started automatically.smdb. user ID. Run this command to uninstall the product kit: setld -d IBMATL_Vxxxx The existing ibmatl. cd / /usr/lbin/fverify -n < /usr / .x. The fverify command reports missing files and inconsistencies in file size. If this file is no longer needed. checksum. it is normal to encounter verification errors on the file checksum and size. Chapter 9. group ID. 3494 Enterprise Tape Library Support 247 .conf file is always retained for future installation use after uninstall procedures. Problem Determination A set of tools is provided with the software to determine if the ibmatl is functioning correctly. Run the following commands to display whether the ibmatl kit is installed on the system. and file type. Daemon Trace Facility The following trace facility is available for the lmcpd daemon: trcatl -[ald] Arguments: -a -l <name> -d (trace all libraries defined in /etc/ibmatl. requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument. Errors are logged according to the /etc/syslog. For more information about using syslog.TRU64 Enterprise Tape Library Driver Error Logging The ibmatl uses the syslog facility to log the errors.conf) (name of library) (delete all log files. 248 IBM Tape Device Drivers Installation and User’s Guide . refer to your system administration manuals.conf file. The ibmatl uses the daemon facility for logging errors. Only errors are logged with this facility. demount. The subroutines in this module communicate with the daemon to perform mount. The daemon. The mtlib program (shipped with the software package) is an example of an application program that interacts with lmcpd. a daemon is a program that runs unattended in the background to perform a standard service. and other library control operations.conf. A C object module (libibm.o) is also provided that links with user written applications to provide control communication with the tape library. ibmatl.o) to interface software applications with lmcpd. A utility program (mtlib) provides a command-line interface to the daemon. The path from the top left to the top right is the data path from the application to the actual tape devices. specifically known to the SGI IRIX system as the IBM Library Manager Control Point Daemon (lmcpd). 3494 Enterprise Tape Library Support 249 . Chapter 9. Note: In a UNIX system. communicates with 3494 Enterprise Automated Tape Libraries that are defined in a configuration file. Refer to “SGI IRIX 3494 Enterprise Tape Library Driver in the IBM Tape Device Drivers: Programming Reference for details. This file. Some daemons are triggered automatically to perform their task while others operate periodically.SGI IRIX 3494 Enterprise Tape Library Driver SGI IRIX The software consists of an application daemon that communicates with the 3494 Automated Tape Library’s Library Manager (LM) through Ethernet or Token Ring LAN. such as SGI IRIX. is placed in the /etc directory when the software package is installed. The 3494 Enterprise Automated Tape Library Daemon for SGI IRIX is designed to be invoked at system IPL time and run continuously to service applications communicating with the Tape Library. Application developers can use the supplied ‘C’ object module (libibm. A typical environment for the 3494 Automated Tape Library daemon for SGI IRIX is an SGI server on a Local Area Network with SCSI attached tape devices providing backup and restore functions for network attached clients. or an RS-232 serial connection. Data Flow Figure 63 on page 250 illustrates the software and hardware components that comprise an application’s communication paths with the 3494 Enterprise Tape Library. The path from the application box proceeding to the right at the bottom of the diagram shows an application linked with the supplied ‘C’ object module communicating with lmcpd and the 3494 Enterprise Library Manager. Customization of this file is described in “Defining the Library Device to the lmcpd” on page 253. These software drivers are provided by the SGI IRIX operating system. Data Flow for SGI IRIX 3494 Enterprise Tape Library Driver Product Requirements The following software and hardware are required to use this product.Token-Ring or Ethernet adapter support in an SGI workstation attached to the 3494 Enterprise Tape Library .LAN cable . E1A.24 m [50 feet]) Note: One RS-422 to RS-232 converter is needed for direct attachment to an Enterprise Model HA1 (High Availability). Hardware Requirements The following hardware is required for the library driver: v 3494 Enterprise Tape Library with 3590 Model B1A.Enterprise FC 5219 (Token-Ring Adapter) . or H1A tape drives v One of the following options depending on which connection (RS-232 or LAN) is required for the Enterprise Tape Library: – RS-232: One standard 25 pin null modem D-shell RS-232 cable (maximum of 15. – LAN: .Enterprise FC 5220 (Ethernet Adapter) Software Requirements The following software is required: v IRIX Version 6.SGI IRIX 3494 Enterprise Tape Library Driver Tape Device Driver Adapter Device Driver Physical Tape Drive Application C Object Module TCP/IP LMCPD Library Manager Figure 63.4 or later 250 IBM Tape Device Drivers Installation and User’s Guide a250093 Native TTY Device Driver . 4.1. 3494 Enterprise Tape Library Support 251 .0 of the library driver. Note: If you are updating software to a newer version.conf file is preserved.h (application interface header file) /usr/bin/mtlib (tape library driver utility program) /usr/bin/mtevent (tape library driver utility program) /usr/bin/trcatl (tape library driver diagnostic program) Note: If this is an update of the lmcpd package.o (64 bit application interface object module) /usr/include/sys/mtlibio. you must restart the Enterprise Tape Library Daemon by either restarting your computer or restarting manually from a command prompt by entering: /etc/lmcpd Uninstallation Procedure Halt all library activity before starting the uninstall procedure. The package is named ibmatl. press Enter after you type: inst -a -u all -f ibmatl.conf (configuration file) /usr/lib/libibm.n.tardist For example.n.n. Install and configure the LAN or TTY support before proceeding with the installation of the lmcpd package.tardist The Tape Library Daemon for SGI IRIX can also be installed using the swmgr program. Chapter 9. (It is not overwritten. You must have root authority to perform this installation procedure. you need to uninstall the existing IBM Automated Tape Library software before installing new software. After installing the new software. The following files are installed on the SGI IRIX system: /etc/lmcpd (library manager control point daemon) /etc/ibmatl.0.SGI IRIX 3494 Enterprise Tape Library Driver v 3494 Enterprise Tape Library Daemon for SGI IRIX Note: The device driver for the 3590 Tape Drive is provided by SGI. For more information. Installation Procedure The LAN or TTY support must exist on the machine before installing the Enterprise software for IRIX.1.5. refer to the documentation appropriate for the LAN or TTY configuration in SGI IRIX. to install Version 4.) To install the 3494 Enterprise Tape Library driver. Installation Instructions The 3494 Enterprise Tape Library Daemon for SGI IRIX can be installed by either using the swmgr program menus or the inst command. Refer to “Uninstallation Procedure” on page 251 for more information.n. use the inst command. the existing /etc/ibmatl.o (application interface object module) /usr/lib/libibm64. Kill the lmcpd daemon if it is executing currently.5. 3. The serial port you have configured should show SerialPort under Type. Use System Manager to configure the serial port. in the Add LAN Host section. ensure that your system has access to the Library Manager on the 3494 Tape Library. you must configure the serial port to which it is connected. 7. Choose a name for the device.. Select System Manager. Place the cable on the native serial port or on the 8 port or 16 port asynchronous adapter. IRIX should set the port that you have just configured to the following settings that are needed to communicate with the 3494 Enterprise Tape Library: Baud rate: Data bits: Stop bits: Parity: Login: 9600 8 1 None Disabled 252 IBM Tape Device Drivers Installation and User’s Guide . e.SGI IRIX 3494 Enterprise Tape Library Driver The 3494 Enterprise Tape Library Daemon for SGI IRIX can be uninstalled by either using the swmgr program or from the command prompt by entering: inst -a -R ibmatl Connecting the 3494 Enterprise Tape Library Use one of the following methods to connect the workstation to the 3494 Enterprise Tape Library: v Use a standard 25 pin null modem D-shell RS-232 cable. to add or configure the serial port. Follow the instructions to: a. By default. Specify the type of serial device: Input Device b. Click Add. 6. Choose the name of the input device: Other d. Configuring the Serial Port After the 3494 Tape Library is connected to the workstation. c. Select the right port. For each 3494 Enterprise Tape Library connected with an RS-232 cable. Select Hardware and Devices from the System Manager window. v Use a LAN connection (either Ethernet or Token Ring) through TCP/IP.. follow the directions in “Configuring the Serial Port” on page 252. 2. For each Tape Library connected through TCP/IP. 4. Select System from the Toolchest. Use the ping utility to verify that you have network connectivity to the Library Manager. Click OK. Select Serial Device Manager. Select the right serial port in the Serial Device Manager window. 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. Select the following options: 1. Consult your network administrator if you need help with this task. 5. Alternate LAN Connection is used to specify an alternate IP address for an Enterprise High Availability LAN-attached configuration. libmgrc7 9.21 and the second address is 9.32. the second IP address of the dual LAN card should be entered after the first alternate LAN connection IP address. If the High Availability Library has a dual LAN card installed. this type is the device special file name of the TTY device (for example. the alternate LAN connection is not applicable.100.115. 3494 Enterprise Tape Library Support 253 . This stanza defines the 3494a library that is connected to the host. refer to the IRIX documentation.115. The first address of the Library Manager on the 3494 Tape Library is 9.32.22 mercury This stanza defines libmgrc7 with a dual LAN card connected through TCP/IP to the workstation. Identifier is used to specify a name by which the library manager identifies the host system. Chapter 9. this type is the IP address of the Enterprise Library Manager. The address of the Enterprise Library Manager is 9. Connection type is used to define the type of connection to the library (either RS-232 or TCP/IP).32. Define the library devices to the daemon by editing the /etc/ibmatl.100 jupiter 9.115. The symbolic network name of the host is usually the best name to use (although any name is acceptable). For example: 3494a 9.115. For RS-232 connections. Failover for RS-232 connections proceed over the single serial line.115.23.conf file.21 9. For additional information.115. The following examples show how to define the library name: tire /dev/ttyd2 sitlab1 This stanza defines the tire library that is connected by /dev/ttyd2 (com2) to the workstation.22.115. If the Library has a dual LAN card installed.32. For example: libmgrc9 9.32. where: n is the com port number.23.115.100 and 9.conf file. The format of the file is: Symbolic name Connection type Identifier Alternate LAN Connection Symbolic name is used to identify each tape library. /dev/ttyd1).100 jupiter Note: The ttydn name is usually the special file name for a standard serial port on IRIX.32. Note: For RS-232 attachments.115. The tape library uses the jupiter identifier for the host. the second IP address of the dual LAN card should be entered after the first IP address. This parameter is used only to identify a particular host to the Enterprise Library Manager.115.54.32. For TCP/IP connections. This identifier has a maximum length of eight characters. The library uses the mercury identifier for the host.SGI IRIX 3494 Enterprise Tape Library Driver Defining the Library Device to the lmcpd After the 3494 Enterprise Tape Library Daemon for SGI IRIX is installed. The IP addresses of the dual library managers are 9. The symbolic names must be unique across all libraries defined in the ibmatl. configure the attached Tape Libraries and start the daemon.54 This stanza defines the libmgrc9 library that is connected through TCP/IP to the workstation.32. 14 This stanza defines the libmgrc7 High Availability library with dual LAN cards connected through TCP/IP to the workstation. The IP addresses of the second Library Manager are 9. The IP addresses of the first Library Manager are 9.21 and 9.26. Starting the 3494 Enterprise Tape Library Daemon Start the 3494 Enterprise Tape Library Daemon for SGI IRIX by either restarting your computer or starting it manually from a command prompt by entering: /etc/lmcpd Problem Determination A set of tools is provided with the software to determine if thelmcpd is functioning correctly.32.13 9.SGI IRIX 3494 Enterprise Tape Library Driver libmgrc7 9.22 mercury 9. Daemon Trace Facility: The following trace facility is available 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.26. The library uses the mercury identifier for the host.22.32.115.26.26.21 9.32. 254 IBM Tape Device Drivers Installation and User’s Guide .115.115.115.14. requires root authority) Examples: trcatl -a >/tmp/trace-out trcatl -l libmgrc7 Note: The -a argument takes precedence over the -l argument.115.115.13 and 9.32.115.115. . . . . . . . . . . . . . Firmware Update . . . . Tape Usage . . . . [37] Report Density Supp (Support) . . . . . . . . . . . . [36] Display Message . . . . . . . . . . . . . . Graphical Edition (ITDT-GE) . . . . . [54] Move Medium . . . . Windows . [35] Query Encryption Status . . . . . . . . . . . Tape Usage . . . . . . Standard Edition . . . . . . [58] Read Device IDs . . . . . . . . . . . . . [28] Erase. . [22] Backward Space File Marks . . . . . . . . . . . . [5] Reserve Device. . . . . . . . . . . . . . . i5/OS Operating Systems . . . . [1] Open a Device . . . . . . [6] Release Device . . . . . . . (Version) . . . System Test . . . . . . . . . . . . . . . . . . . . . Graphical Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installation . . . . . . Manual Inspect . . . . . . . . . . . . . . . . . . . [4] Test Unit Ready . . Full Write . . . . . [33] Query/Set Parameter . . . . 282 282 282 282 282 283 283 283 283 283 283 284 284 284 284 285 285 285 285 285 285 285 286 286 286 286 286 286 287 287 287 288 288 288 288 288 289 289 291 291 292 294 295 296 297 299 299 300 This chapter describes the IBM Tape Diagnostic Tool. . . .Scan Menu Commands. . . . . . . . IBM Tape Diagnostic Tool (ITDT) Purpose . . . . . . . . . . . System Test . . . . . . . . . . . . . . . . . . . . . . © Copyright IBM Corp. . Scan . . 3494 Tape Library . . . . . . . . . . . . . . . . . . [10] Query Driver Ver. . . . . . . [57] Initialize Element Status Range . . [51] Position to Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . [50] Element Information . . . Standard Edition (ITDT-SE). Supported Equipment . . . . . . [70] Dump/Force Dump/Dump . . . . . . . . . . . . . . . . . . . [71] Firmware Update . Performance Issues . . . . . . . . . . . .Tapeutil Menu Commands . . . . . . . . . . . . . . . . Dump . . . . . . [59] Read Cartridge Location . . . . . . . . . . . . [24] Backward Space Records . . . . Encryption . . . . . . [21] Forward Space File Marks . . . . . 3576/TS3310 Tape Library . . . . . . . . Full Write . . . . . Graphical Edition . . . . . . . . . . . . . . . . . . . [3] Inquiry . . . . . . . . . . . . . Standard Edition . . [25] Space to End of Data . . . . Test. . . . . . . . . . . . . . . . . . Graphical Edition . . . . . . . . . . . . . . . . . . . . . . . . . [7] Request Sense . . . . 2009 255 . . . . . . . . . . . . . . . . HP-UX Operating Systems . . . . . . . . . . . .Scan Menu Commands . . . . . . .User Interface Description . . . . . [2] Close a Device . . . . . . . . . . . . . . . . [32] Synchronize Buffers . . . . . . . . . Standard Edition . . . [26] Read and Write Tests . [34] Query/Set Tape Position . Accessing ITDT . . . . . . . . . . . . . . . Test. . . . . [38] Test Encryp. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Known Issues and Limitations Command Timeout . . Solaris Operating Systems . . . . . . [8] Log Sense . . . . . Library Diagnostic Self-Test. . . . . . Linux Operating Systems . . . . . . . . . [56] Prevent/Allow Medium Removal . . . . . . . . . . . . . . . Standard Edition . . All Supported Operating Systems . .Start Menu Commands . . . . . . [31] Write File Marks . . . . Encryption . . . . . . . . . Library Self-Test . . . . . . . . [9] Mode Sense .Chapter 10. . . . . . . . . . . . . . . . Installing ITDT-SE on i5/OS Operating Systems Installing ITDT-SE on Other Supported Operating Systems . . . . Supported Systems . . . . . . . Standard Edition . . . . [20] Rewind . [53] Exchange Medium . . . . . . . . . . [30] Unload Tape . . . . . . . . . . . . . . [11] Display All Paths . . Other . . . . . . [29] Load Tape . . . . . . [55] Initialize Element Status . . . . . . . . . . . Devices Disappear After Firmware Update . .Known Issues and Limitations AIX Operating Systems . . . Linux . . . . . . . Scan . . . . . . . . . . . . . . . . . . 2007. . . . . . . . Dump . . . . . . Windows Operating Systems . Path (Test Encryption Key Path/Setup) . . . . . . . Return. . . . . . . . . . . . . . . Firmware Update . . . . . . . . . . . . Graphical Edition . [27] Read or Write Files . . . . . . . . . . . . . . . . [52] Element Inventory . . . . . .Installation and Initial Startup Installing ITDT-SE on Solaris Operating Systems Installing ITDT-SE on Windows Operating Systems . . 256 257 257 257 258 258 259 259 260 261 262 262 262 262 263 263 264 264 264 265 266 267 268 271 271 273 274 276 277 277 278 278 279 279 280 280 281 281 281 281 281 281 281 281 281 282 282 282 [23] Forward Space Records . . . . . . 256 IBM Tape Device Drivers Installation and User’s Guide . Note: The term tapeutil is a synonym for the tool that is delivered with the device driver. this tool is named tapeutil on Unix operating systems. The IBM Tape Diagnostic Tool is designed to: Run quick or extended diagnostics on tape drives Invoke tape library self-test operations Retrieve dumps from tape drives and libraries Perform a firmware update on tape drives or libraries Test the performance of the environment by completely writing a cartridge and measuring performance v Verify tape drive compression v Measure system performance v v v v v v Retrieve and display cartridge usage information v Verify the encryption environment This test is used to verify if data on the cartridge was actually written encrypted.IBM Tape Diagnostic Tool Purpose The IBM Tape Diagnostic Tool (ITDT) is available in two versions: v Standard Edition (ITDT-SE) . The available advanced operations provided by the IBM Tape Diagnostic Tool can be performed on Tape Drives and Tape Libraries. Currently only SE has tapeutil functionality. overwriting all previous data with varying block sizes containing either compressible or incompressible data and then outputs performance data. v Scan the system to discover all supported tape and library devices. it is named ntutil on Microsoft Windows operating systems. v Perform a connection test This test is used to verify that all devices are attached properly v Perform a sequence of sub-tests to check if the tape device is defective and output a pass/fail result Note: When this test is performed.This is a GUI version for the following: – Microsoft Windows operating systems – Linux operating systems Both versions provide the user with a single diagnostic program for tapeutil applications. By using this functionality. For example. v Graphical Edition (ITDT-GE) . all data on the cartridge is overwritten. v Perform a full write function This function writes the entire cartridge. This significantly reduces product downtime and increases productivity. v Perform a tape usage function to retrieve statistical data and error counters v Perform a manual inspect function for devices not recognized.This is a command line version. all data on the cartridge is overwritten. however it will soon be available in the GE version. Note: When this test is performed. the customer can perform maintenance tasks and run diagnostic tasks to determine tape drive issues. 5 and later (32-bit IX86) – Linux systems with Kernel 2.6.2 – AIX 5L 5.2. 4.IBM Tape Diagnostic Tool The ITDT-SE provides the most important functions of the previous tapeutil tools.1 v HP-UX operating systems – HP-UX Version 11i v1. Supported Systems ITDT is supported on the following systems. ITDT-SE can coexist with the application so that when the application disables the device internally.6.5 – Linux systems with Kernel 2.software. glibc 2. glibc 2.6.com/ storage/ITDT/Current/. click Download. glibc 2.6. Standard Edition (ITDT-SE) The Standard Edition (ITDT-SE) is supported on the following: v AIX operating systems (64-bit pSeries/System p) – AIX 5L 5. v2 and v3 (64-bit PA-Risc and Itanium) v Linux operating systems – Linux systems with Kernel 2.3 v Solaris operating systems – Solaris Version 9 and 10 (64-bit SPARC) v Windows operating systems and and and and later later later later (64-bit (64-bit (64-bit (64-bit x64) IA-64) pSeries/System p) zSeries/System z) – Microsoft Windows Server 2003. When this configuration exists.2. then choose the latest version of ITDT for your product. On the right side.ibm. Note: ITDT-GE is not providing the Tapeutil functions at this time.2. click Software. glibc 2.ibm.5 – Linux systems with Kernel 2. Accessing ITDT One option to access ITDT is through the ftp web site: ftp://ftp. In the Tool/Utility section.6. 2. Microsoft Windows Server 2008 (64-bit x64) – Microsoft Windows Server 2003.3. the set of operations and functions available with ITDT-SE is identical across all supported operating systems (unless a particular function is not available on a particular system). IBM Tape Diagnostic Tool (ITDT) 257 . Microsoft Windows Server 2008 (32-bit IX86) – Microsoft Windows Server 2003. Dedicated device drivers for tapes and libraries may be installed on the target system and there is usually an application installed that uses the tape/library devices.5 – Linux systems with Kernel 2. glibc 2.2. Go to the Tape Support page: http://www. Under Product: select your product.com/systems/support/storage/ tape. You can also navigate to the ITDT Web page: 1.3 – AIX 6. As an extension of the current tapeutil variants. 3. Microsoft Windows Server 2008 (64-bit i64) Chapter 10. ITDT-SE can perform the diagnostics on that device. 6. p/n 44E8895. glibc 2. p/n 59P6744. p/n 71P9146 High LTO Gen 2 High LTO Gen 3 SCSI (p/n 42C3942 and 40K2573) and Fibre High LTO Gen 3 SCSI (p/n 40K2596) and Fibre (p/n All other System x LTO tape drives are not supported by ITDT. replacement p/n 25R0003 and 23R4808 v IBM Half High LTO Gen 3.IBM Tape Diagnostic Tool v i5/OS® V5R3. Note: Replacement part numbers are only given for the stand alone IBM LTO tape drives. replacement p/n 37L5799 v IBM Full High LTO Gen 2. V5R4 and V6R1 (iSeries/System i) Graphical Edition (ITDT-GE) The Graphical Edition (ITDT-GE) is supported on the following: v Windows operating systems – Microsoft Windows Server 2003/2008 (32-bit x86) – Microsoft Windows Server 2003/2008 (64-bit x64) [with a 32-bit JVM]. p/n 25R0012 and 39M5657. All queries are to be addressed to IBM System x support. v Linux operating systems – Linux Distributions with Kernel 2. These drives are not tested by the IBM System Storage Test Lab. replacement p/n 45E1125 v 3600-XXX Library and Autoloader IBM Full High LTO Gen 1. p/n 00N8016.5 and later (X86) Supported Equipment The following equipment is supported for both the Standard Edition (ITDT-SE) and the Graphical Edition (ITDT-GE): v IBM Ultrium 3580 Tape Drive (Generation 3 and 4) v IBM Ultrium Tape Drives T800/F. p/n 43W8478. p/n 09N4048 v 4560-SLX IBM Full v 3623-2LX IBM Full v 3361-4LX IBM Full (p/n 40K2575) v 3362-2LX IBM Full 42D8769) High LTO Gen 2.2. replacement p/n 23R7036 v IBM Half High LTO Gen 4. T800V. They are also not supported by IBM System Storage support. replacement p/n 71P9141 v IBM Full High LTO Gen 3. v IBM Full High LTO Gen 1. 258 IBM Tape Device Drivers Installation and User’s Guide . T1600/F v IBM System Storage 3588/TS1030 model F3A and F3B Tape Drive v IBM System Storage 3588/TS1040 model F4A Tape Drive v IBM System Storage 3580 Half Height/TS2230 and TS2240 Tape Drive Express v IBM System Storage TS2340 Tape Drive Express v IBM 3592/TS1120/TS1130 Enterprise Tape System v v v v v IBM IBM IBM IBM IBM System System System System System Storage Storage Storage Storage Storage 3572/TS2900 3573/TS3100 3576/TS3310 3577/TS3400 3584/TS3500 Tape Autoloader Express and TS3200 Tape Library Express Tape Library Tape Library Tape Library The following equipment are supported System x LTO Tape drives. always reset the sgen device driver settings after you finish working with ITDT-SE. start the sgen_solaris_conf. see “i5/OS Operating Systems” on page 264 for product support limitations. we recommend you upgrade to the latest available IBM Tape Device Driver level. A script sgen_solaris_conf.sh script. 1. Standard Edition .sh script with root access. then configure the sgen driver. they will still use the IBM Tape Device Driver if it is installed. IBM Tape Diagnostic Tool (ITDT) 259 . using the sgen_solaris_conf. The following command line options are available on the SGEN driver configuration screen: v 1) Check driver: This option checks if the driver /kernel/drv/sgen is available. the [E] Encryption test will always exit with NO DRIVER SPECIAL FILE when ITDT-SE is started with -force-generic-dd. The [U] Tapeutil option will only work if the IBM Tape Device Driver is installed. Note: For system security reasons. Download itdtinst<version>Solaris to a directory of your choice.Installation and Initial Startup This section describes the installation and startup procedures for the Standard Edition of ITDT in various operating systems. In a System Managed Encryption setup. The -force-generic-dd startup option to bypass the IBM Tape Device Driver has no effect on the [U] Tapeutil option commands. Attention: Before using the IBM Tape Diagnostic Tool Standard Edition (ITDT-SE) with the IBM Tape Device Driver. To configure the sgen driver. ITDT-SE requires that the sgen device driver is configured so that the devices you want to work with can be found. Enter the following command to make itdtinst executable: chmod 700 itdtinst<version>Solaris 3. v 4) Stop sgen driver: This option stops the driver (that is.IBM Tape Diagnostic Tool For i5/OS operating systems. Execute itdtinst by entering the following command: itdtinst<version>Solaris 4. If the IBM Tape Device Driver is not used or not installed. 2. Chapter 10. rem_drv sgen). perform the following steps: Note: ITDT-SE can only be used by a user with root access rights. v 2) List driver settings: This option shows the current activated devices. Installing ITDT-SE on Solaris Operating Systems To install ITDT-SE on Solaris operating systems.sh is included in the ITDT-SE package. v 3) New driver configuration: This option displays the screen that is used to create a new driver configuration (see Step 5 on page 260). This script allows the user to configure the sgen generic SCSI driver that is shipped with Sun Solaris. After the new devices are found. During the initial program startup. v 7) Save configuration: This option saves the modifications. This task needs to be done manually.conf file. Please enter "update_drv sgen". Note: For Fibre Channel Host Bus Adapters (HBAs). Note: Option 4 allows for the removal of individual devices one at a time.. 7.sh script. v 2) Define device types: This option defines drive and changer types. If you have finished the editing. Option 6 allows for the removal of a range of devices. 260 IBM Tape Device Drivers Installation and User’s Guide .IBM Tape Diagnostic Tool v 5) Start sgen driver: This option stops and starts the sgen driver. Add the WW-PN number(s) into the sgen. Installing ITDT-SE on Windows Operating Systems To install ITDT-SE on Windows operating systems.. c4 fc-private connected configured c4::5005076302401924 tape connected configured .. v 8) Back to Main Menu: This option returns to the main menu. This option starts the sgen driver. v 3) or 5) Add target(s): This option adds targets to the list. ITDT-SE does not make changes outside the installation directory.. Enter option 3) to create a new driver configuration: The following command line options are available on the New Configuration screen. name="sgen" parent="fp" target=0 lun=1 fc-port-wwn="5005076302401924". name="sgen" parent="fp" target=0 lun=0 fc-port-wwn="5005076302401924". v 6) Exit program: This option closes the shell script. 6. special handling is required. After the sgen driver is configured. enter command line option 8 to go back to the main menu. enter option 6) to exit the sgen_solaris_conf. .. Use these options to configure the sgen driver: v 1) List targets: This option shows the targets in current configuration. Option 5 allows for the addition of a range of devices.sh script.. eliminating the need to remove a large number of devices one by one. it is not performed by using the sgen_solaris_conf. 8.. 9. eliminating the need to add a large number of devices one by one.conf file. perform the following steps: Note: ITDT-SE can only be used by a user with Administrator rights. The following is an example how to add those devices: Run the command "cfgadm -al" to get the WWPN number(s). Note: Option 3 allows for the addition of individual devices one at a time. the sgen driver has to be restarted.. 5. v 4) or 6) Remove target(s): This option removes targets from the list. On the SGEN driver configuration screen enter command line option 5).. Start ITDT. new devices are found using the definitions performed in Step 5. the license agreement text is displayed and the input and output directories are created. Attached devices need to be configured with their WWPN in the sgen. and so on).2 or higher. Note: The user name should be QSECOFR 4.exe.. Vary ON the TAPMLB using option 2. To use ITDT-SE to update firmware or pull dumps from a Tape Drive inside a Tape Library. 3. Issue the command WRKMLBSTS. When firmware updates and dumps are complete. Deallocate the corresponding drives using option 6. Start the installation by pressing the Install button. (for example. make sure the drives are varied online in STANDALONE MODE by performing the following steps: 1. Issue the command WRKMLBSTS. Execute the following command: itdtinst<version>windows<arch>. 4. IBM Tape Diagnostic Tool (ITDT) 261 . TAP02. Download itdtinst<version>windows<arch>. .4. 11. Start ITDT with the following command: . Vary OFF the TAPMLB using option 2.exe where <arch> can be: v AMD64 (64-bit Intel EM64T or AMD servers) v IA64 (64-bit Itanium server) v X86 (32-bit Intel-compatible servers) to a directory of your choice. Start ITDT by executing the following command: itdt.exe 3. Identify the Library and drives you want to work with. TAP01. 1. Start the installer itdtinst<version>I5OS. Enter the following command: WRKCFGSTS *DEV TAP* Identify the drives which were noted in Step 1. TAPMLB01.. TAP01.exe Installing ITDT-SE on i5/OS Operating Systems To install ITDT-SE on i5/OS operating systems. 9. Launch the iSeries® Q-Shell environment with the following command: QSH 6. See “Firmware Update” on page 271 and “Dump” on page 271. Read through the welcome and license screens.IBM Tape Diagnostic Tool 1. enter the following command: WRKCFGSTS *DEV TAP* 10. 2. 2. Chapter 10. 3. perform the following steps: Note: ITDT-SE on i5/OS requires a Microsoft Windows PC with a Java runtime 1. Identify the Library and drives you want to work with. Update Firmware and pull dumps. Change to the folder /home/itdt with the following command: cd /home/itdt 7. 2. 5. TAP02) and vary them ON using option 1. Enter your i5/OS system hostname or IP address and administrator credentials. Note their names (for example. TAPMLB01./itdt 8. the license agreement text is displayed and the input and output directories are created. AIX Operating Systems The following are the known scan limitations: v Only devices that have the device state ″available″.an escape sequence is inserted and the input is ignored after Enter is pressed. which is anything over 20 characters. For FC and SAS devices the ID and LUN might not be displayed if the lengths are too long for the display. Execute the following command: itdtinst<version><OS> 4. During the initial program startup. Download itdtinst<version><OS> to a directory of your choice. HP-UX Operating Systems Verify that the following patches are installed before starting ITDT-SE: v PA-Risc: At least these patches: – ld and linker tools cumulative patch – libc cumulative patch v Itanium/IA-64: All regular patches and the following patches: – – – – VxVM 3. Start ITDT. 262 IBM Tape Device Drivers Installation and User’s Guide .014 Kernel Cumulative Patch Aries cumulative patch linker + fdp cumulative 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). 1. v itdtinst<version>Aix is for AIX operating systems v itdtinst<version>LinuxX86 is for Linux operating systems on Intel hardware v itdtinst<version>LinuxPPC is for Linux operating systems on pSeries v itdtinst<version>LinuxS390X is for Linux operating systems on zSeries v itdtinst<version>Hpux is for HP-UX operating systems. Perform the following command to make itdtinst<version><OS> executable: chmod 700 itdtinst<version><OS> 3. Standard Edition . Allocate the TAPs back to the TAPMLB using option 6. ITDT-SE does not make changes outside the installation directory. Installing ITDT-SE on Other Supported Operating Systems To install ITDT-SE on other supported operating systems. When logged in via telnet.014 Command Patch VxVM 3.5~IA. 2.5~IA. perform the following steps: Note: ITDT-SE can only be used by a user with root access rights.IBM Tape Diagnostic Tool 12.Known Issues and Limitations This section describes the known issues and limitations of the ITDT-SE program. backspace may not be working . vIBM.2. Solaris Operating Systems Rescan may take 6-8 minutes. Modify the /etc/driver_alias file to comment all lines not starting with sgen and containing identification of your drives and changers.01. model ULT3580-HH4) # update_drv -a -i '"scsiclass.vIBM. When this event occurs.08"' sgen (adds sgen alias for all changers attached to the system) 5.vIBM.p3573-TL" (all (IBM (all (IBM tape drives) tape drive model ULT3580-TD4) changers) changer model 3573-TL) 3.5 or later. you may experience a SCSI CMD TIMEOUT when running the [T] option while using the IBM Tape Device Driver.IBM Tape Diagnostic Tool On HP-UX11. an entry with cxx:rmt/y.conf. For SUSE SLES9 on zSeries please ensure that the kernel update SUSE-SA:2007:035 is installed.08. LUN 0-10 If the IBM Tape Device Driver is not installed on Solaris 10. Check that the configured drives are not configured for st driver by entering the following command: # cfgadm -al If the tape drive is claimed by st device driver. tape devices may not be found during scan although they are configured in sgen.pULT3580-TD4" "scsiclass.01" /etc/driver_aliases # egrep "scsiclass. Note: On a SLES9 s390x (64bit) configuration. Add sgen driver aliases with one of the following commands: # update_drv -a -i '"scsiclass.08" /etc/driver_aliases (for drives) (for changers) 2.pULT3580-HH4"' sgen (adds sgen alias for IBM drive. The known scan limitations: SCSI ID 0-255.iV3 systems.01. Examples: #st #st #st #st "scsiclass.08.01"' sgen (adds sgen alias for all drives attached to the system) # update_drv -a -i '"scsiclass. model ULT3581-TA2) # update_drv -a -i '"scsiclass. is displayed. IBM Tape Diagnostic Tool (ITDT) 263 . Check that the drives and changers are now configured with the following command: # cfgadm -al Chapter 10.01" "scsiclass. We recommend to perform repeated [S] Scan operations to make the library reappear in the device list. Check the current driver bindings for IBM Tape drives and changers by entering the following commands: # egrep "scsiclass. for example: c11::rmt/0 tape connected configured unknown 4.08" "scsiclass. tape libraries operated through the drive’s control path (no control path failover) may disappear from the Device List after a [F] Firmware Update on the controlling drive. depending on the numbers of host adapters and devices attached. Linux Operating Systems ITDT-SE on Linux requires glibc 2.pULT3581-TA2"' sgen (adds sgen alias for IBM changer.vIBM. perform the following steps to configure the devices: 1. reboot the system and verify the list of configured devices with the command: # cfgadm -al Windows Operating Systems After a firmware update. ITDT-SE on i5/OS V5R4 requires the following PTF installed: PTF: SI25023 Release: 540 Abstract: OSP-MEDIA-TAPE-THREADS-MSGCEE0200T/QTAHRMGR QTARDCAP FAILS The [U] Tapeutil option is not available for i5/OS with this release as all the underlying operations require the IBM Tape Device Driver to be installed. 264 IBM Tape Device Drivers Installation and User’s Guide . the user interface is corrupted. All Supported Operating Systems This section describes the known issues and limitations of the ITDT-SE program on all other supported operating systems. it does not support autoloaders and libraries. devices may disappear. The Tape Drive must be varied online. when this occurs. the input is ignored after pressing the Enter key. the Library must be varied offline.com/kb/812024/en-us Repeated Scan operations may help to rediscover the device. the cartridge must be imported manually before starting the Device Test.microsoft. the input is ignored after pressing the Enter key. See “Installing ITDT-SE on i5/OS Operating Systems” on page 261 for details. See the Article ID: 812024 at: http://support. If the drives or changers are not listed in the output of 'cfgadm -al'. Media changers and media changer operations are not supported with this release of ITDT-SE. the Encryption Test does not deliver decrypted data in a Library Managed Encryption environment. User Interface Issues If you press the arrow keys on most Unix operating system consoles.IBM Tape Diagnostic Tool 6. If the Tape Drive is operated through a Tape Library. This is a known Windows problem. As the Library is varied offline. When switching applications on Windows while ITDT-SE is running. an extra ESC character may appear on the input line. ensure that you are using the latest Adaptec Host Bus Adapter Drivers instead of the drivers shipped with the Windows operating system. If you are using Adaptec SCSI Host Bus Adapters. When the Tab key is pressed as an input string for field data. To test a tape drive inside a library. i5/OS Operating Systems ITDT-SE on i5/OS supports only tape drives. Chapter 10. IBM Tape Diagnostic Tool (ITDT) 265 a2500231 . Start Screen Menu The following commands are available on the start screen menu: v S .IBM Tape Diagnostic Tool 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. Figure 64. use an underscore character ( _ ) instead of the space character.Tapeutil Opens the screen for the Tapeutil operation commands. These commands are the standardized tapeutil functions with most of the options available that were available with the previous tapeutil functions (refer to “Standard Edition Tapeutil Menu Commands” on page 279). v H . 3494 Tape Library Drives in a 3494 tape library or an STK silo library are supported. only the [T] Test option won’t work due to device-specific restrictions for handling cartridges. 3576/TS3310 Tape Library Library Firmware Update using ITDT-SE is not supported with the 3576/TS3310. Command Timeout There is no instant operation termination upon SCSI command timeout. To avoid this. When a command timeout condition occurs. for example.Help Help starts and displays the available online help. v U .Scan for tape drives Opens the screen for the Scan function (refer to “Standard Edition . when the SCSI cable is unplugged after starting POST A. Standard Edition . ITDT-SE displays the start screen menu. Update the Firmware using the 3576/TS3310 Web User Interface.Scan Menu Commands” on page 266).Start Menu Commands After program startup. ITDT may still continue to perform more operations (like unmounting the cartridge) instead of instantly terminating with a timeout condition. L.“Tape Usage” on page 276 O .“Other” on page 277 266 IBM Tape Device Drivers Installation and User’s Guide a2500232 . Entering the O command displays the second device list screen. E.“Firmware Update” on page 271 E .“Encryption” on page 273 W . the Scan function starts and displays the first device list screen. F. This screen contains the S. and O commands.“Dump” on page 271 F .Scan Menu Commands When using ITDT-SE. Scan Menu The following commands are described in this section: v S . Standard Edition .Quit Quits the function. I. D.IBM Tape Diagnostic Tool v Q . T. after entering S on the start screen. The second screen contains the Y.“Full Write” on page 274 U . W. U.“Test” on page 268 v v v v v v D . and R commands. Figure 65.“Scan” on page 267 v T . a bar in the lower left edge of the screen shows that the scan operation is still in progress.“System Test” on page 277 v L . the scan can take several minutes.Known Issues and Limitations” on page 262 for more details. For example. or if not sure. Before continuing. the first device list screen is displayed. Once the scan is finished. After starting ITDT-SE.IBM Tape Diagnostic Tool Figure 66. stop the entire backup application.“Manual Inspect” on page 278 v R . make sure no other program is accessing the devices used by ITDT-SE. stop the backup jobs that are accessing the devices when using ITDT-SE. More Scan Options v Y . IBM Tape Diagnostic Tool (ITDT) 267 a2500233 . See “Standard Edition .“Library Self-Test” on page 278 v I . During the scan operation. type the S key followed by the Enter key to activate the scan function. Chapter 10.“Return” on page 279 Scan The Scan function [S] is used to discover all supported tape and library devices that are attached to the computer system so that they can be selected for the subsequent ITDT-SE operations. Depending on the operating system and the number of attached drives. The scan function also serves as a connection test that can be used to verify proper attachment of the devices. Only one device can be selected. Note: For fast up (backward) scrolling. ITDT-SE uses the IBM Tape Device Driver for its operations. If you need to bypass the IBM Tape Device Driver for diagnostic purposes.followed by a space and the number of lines to scroll up then press the Enter key. Test The Test function [T] checks if the tape device is defective and outputs a pass/fail result. any Tape Device Driver that is installed is used. Device List Screen The first device list screen shows all detected devices and the connection information (host adapter number. On Microsoft Windows. 268 IBM Tape Device Drivers Installation and User’s Guide a2500232 . To scroll down in the list to access non-displayed entries. To scroll back. For drives that are attached to a library. start ITDT-SE with the following command: itdt -force-generic-dd Once the desired device is displayed.IBM Tape Diagnostic Tool Figure 67. the Changer column shows the serial number of the changer the drive is attached to. SCSI/FCP ID and LUN) along with product data (Model name. type + followed by a space and the number of lines to scroll down then press the Enter key. use . Note: For fast down scrolling. type . bus number. select the device for test. Microcode revision). make sure that: v ITDT-SE is running with administrator/root rights. If no devices appear in the list. v the devices are properly attached and powered on.instead of +. type + and press the Enter key. If no IBM Tape Device Driver is installed. Unit Serial number. the generic device driver for the operating system is used instead. 2. type N followed by the Enter key to stop the test. Start ITDT-SE. 2. If no cartridge is inserted. If you are unsure. 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. Note: If ITDT-SE detects data on the cartridge. 1. Chapter 10. ITDT-SE prompts to insert a cartridge. To test tape drives within a library. Scaled (capacity-reduced) cartridges should not be used to test the device. not on autoloaders or libraries. The test can take from 15 minutes up to 2 hours. Type T followed by the Enter key to activate the test. the Device Test screen displays a message (as shown in Figure 68). Figure 68. During the test.IBM Tape Diagnostic Tool Attention: The test functionality erases user data on the cartridge that is used for the test. the library must be in online mode. Select the device you want to test by entering its number and press the Enter key. then type S and press the Enter key to scan for the devices. To perform the test function. 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 overwritten. The test runs only on tape drives. it is recommended that a new or rarely used cartridge is used. Either insert a cartridge and press the Enter key or stop the test by entering C followed by the Enter key. IBM Tape Diagnostic Tool (ITDT) 269 a2500234 . Notes: 1. [Medium Qualification] – only if the previous step indicated this requirement 3. 7. 6. Mount Medium 2. 5. Load/Unload Cycles ( 2 ) 4. Performance Test Unmount Medium Get FSC Get Logs The test can be stopped by typing A followed by the Enter key at any time except during the POST tests. Figure 70. 8. Test Results 270 IBM Tape Device Drivers Installation and User’s Guide a2500236 a2500235 .IBM Tape Diagnostic Tool 1 2 Figure 69. which are not interruptible. Test Running The test sequence contains the following steps: 1. POST A During POST A stopping the test is not allowed. Note: It may take some time until the test actually stops. a dump file (*. If you want to use other ITDT-SE functions. type Q followed by the Enter key to exit the program. 3. The screen also shows the output files that were generated during the test run. Type D and press the Enter key to start the dump retrieval for the selected device. See “Supported Equipment” on page 258 for a list of supported products.a. The ongoing dump process is performed (it takes less than 1 minute). type R followed by the Enter key to return to the device list. Select the device you want to retrieve a dump from by entering its number and press the Enter key. the Dump function stores one log file in the output folder of the program (*.blz). Figure 71. together with the test result and failure information in the code field. Note: When the Dump function is performed for tape libraries or autoloaders other than the 3584/TS3500. while a Drive or 3584/TS3500 Dump contains much more diagnostic information. then type S and press the Enter key to scan for the devices.IBM Tape Diagnostic Tool When all sub-tests are finished. For the 3584/TS3500. The files may be requested by the IBM Support Center. type R followed by the Enter key to return to the first device list screen. Start ITDT-SE. Chapter 10. ITDT-SE shows a screen that displays the attachment and device information as in the first device list screen. the Log file only contains Log Sense and Mode Sense pages. Firmware Update The Firmware Update [U] upgrades the firmware of tape drives and tape libraries. Dump When the dump process is performed on a tape library or autoloader other than the 3584/TS3500. type Q followed by the Enter key to exit the program. Dump Perform the following to start the Dump [D] process: 1. If you want to use other ITDT-SE functions. IBM Tape Diagnostic Tool (ITDT) 271 a2500237 . otherwise. 2. otherwise.gz) will be stored in the output folder. type C and press the Enter key to continue. type D and press the Enter key to refresh the directory content. 5. type S and press the Enter key to start the firmware update. then type F followed by a space and the fully qualified path to the directory containing the firmware file. 272 IBM Tape Device Drivers Installation and User’s Guide . Type F and press the Enter key to display the Firmware Update screen. v If the correct file is not displayed. It indicates true if the directory exists. Start ITDT-SE. v If the firmware file is stored in a directory other than the one displayed in FW Dir. 4.instead of +. then press the Enter key. v If the displayed directory contains more files than those shown. For fast down scrolling type + followed by a space and the number of lines to scroll down then press the Enter key. false otherwise. 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 Navigator to transfer the file To do a Firmware Update perform the following steps: 1. Before starting the firmware update. 7. For example. type + and press the Enter key to scroll down the list. make sure the file displayed in the FW File field is the correct file. type C and press the Enter key to change the selected firmware file. v If the content of the displayed FW Dir has changed. Go to Step 4.ibm. proceed to the next step. Select the device you want to update by typing the number of the device and pressing the Enter key. then type S and press the Enter key to scan for the devices. After selecting the firmware file. If you decide to run the firmware update. To scroll back. Note: The selected filename is reset to the first item in the list when returning to that dialog from the Start Update dialog.IBM Tape Diagnostic Tool Note: See “3576/TS3310 Tape Library” on page 265 for more information on how to update the firmware on a 3576/TS3310 Tape Library.com/storage/lto Download the files to the ITDT-SE input subdirectory that was created during the installation. 6. The following site is available for the latest firmware files: http://www. 2. 3. v If the correct file is displayed. To select the needed firmware update perform one of the following: v If the firmware file you downloaded is listed in the Content field of the Firmware Update screen. enter the following to change the firmware directory (Unix): f /home/user/firmware v If no files are displayed in the Content field. check the Dir OK field on the right side of the screen. Note: The selected filename is reset to the first item (#0) after using the Refresh function. use . type the corresponding line number and press the Enter key. the Encryption function continues even when a cartridge without encrypted data is used. a firmware update progress screen is displayed. ITDT-SE then switches to the Encryption Verification screen. the Status field on the bottom right side indicates PASSED if the firmware was updated successfully and FAILED otherwise. Select the device you want to test by entering its number and press the Enter key. Before continuing. If you decide not to run the firmware update. 2. Chapter 10. the system requires the entry of the number of the start record and the amount of data (in KB) to be read. the following restrictions exist: ITDT-SE supports only tape drives. Media changers and media changer operations are not supported with this release of ITDT-SE. do not interrupt the firmware update. IBM Tape Diagnostic Tool (ITDT) 273 . 2. Type R and press the Enter key to return to the Device List. If the Encryption function is run on IBM Ultrium 3580 Generation 4 drives. It reads both decrypted and raw data from the cartridge into two separate files on disk. Encryption The Encryption [E] function is used to verify if data on the cartridge was actually written encrypted. but it can take up to 45 minutes for libraries. 3. On this screen. Notes: 1. The Tape Drive must be varied online. the Library must be varied offline. ensure that you use a FIPS-certified firmware to update the drive. ITDT-SE stops the Encryption function when it detects that a cartridge is not encrypted. it displays a warning dialog. it does not support autoloaders and libraries. To test a tape drive inside a library. type R and press the Enter key to return to the Device List. on these drives. Attention: Once started. Type E and press the Enter key to start the encryption. the cartridge must be imported manually before starting the Device Test. For i5/OS. the Encryption function does not deliver decrypted data in a Library Managed Encryption environment. After completion.IBM Tape Diagnostic Tool During the firmware update. The firmware update usually takes 3-5 minutes. Note: If ITDT-SE detects a FIPS-certified drive firmware. If the Tape Drive is operated through a Tape Library. On 3592/TS1120/TS1130 drives. ITDT-SE on i5/OS V5R4 requires the following PTF installed: PTF: SI25023 Release: 540 Abstract: OSP-MEDIA-TAPE-THREADSMSGCEE0200-T/QTAHRMGR QTARDCAP FAILS 1. ensure that an encrypted cartridge is used before starting this operation. 8. The user can then verify that the data differs to ensure that encryption worked. After starting ITDT-SE. As the Library is varied offline. The Encryption function is only supported on encryption enabled drives and requires an encryption infrastructure including the Encryption Key Manager (EKM) to be properly set up. See “Installing ITDT-SE on i5/OS Operating Systems” on page 261 for details. type S followed by the Enter key to activate the device scan. The Encryption function can be stopped by typing A followed by the Enter key at any time. The Full Write function runs only on tape drives. type Q followed by the Enter key to exit the program. Type L followed by a blank and the data length. During the encryption. press the Enter key to start the encryption. Type S followed by a space and the start record number. 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. Definitions of Abort Codes ABORT CODE LOCATE FAILED MEDIUM NOT ENCRYPTED NO DRIVER SPECIAL FILE ROOT CAUSE Start position as requested by the user could not be reached Mode Sense detected medium as non-encrypted System-Managed environment. 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. 5. The Full Write test can be used to: 274 IBM Tape Device Drivers Installation and User’s Guide .IBM Tape Diagnostic Tool 4. Table 30. If all encryption operations are finished. less time for compressible data. If you entered the values correctly. The Full Write function takes approximately 2 hours when writing incompressible data. then press the Enter key to enter the start record number. not on autoloaders or libraries. then press the Enter key to enter the data length. type R followed by the Enter key to return to the device list. Full Write The Full Write [F] function writes the entire cartridge with a given block size either with compressible or incompressible data and output performance data. but generic device file is used instead of IBM device driver special file DRIVE ENCRYPTION DISABLED Mode Sense detected disabled drive encryption UNEXPECTED DATA v Set Raw read mode failed v One of the commands failed END OF MEDIUM END OF DATA End of medium encountered before the given amount of data could be read End of data encountered before the given amount of data could be read If you want to use other ITDT-SE functions. Note: It may take some time until the Encryption function actually stops. Attention: The Full Write function erases data on the cartridge that is used for the test. Notes: 1. 2. otherwise. Table 30 defines the abort codes. data is only written partially. When run with compressible data.IBM Tape Diagnostic Tool v Demonstrate that the drive is capable of writing the full amount of data on a cartridge. This is a check for the type of supported block size is performed. either: [C] Compressible or [I] Incompressible. Note: If ITDT-SE detects data on the cartridge. 2. type R followed by the Enter key to return to option 4 the device list. 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. 1. If no cartridge is inserted. type S followed by the Enter key to activate the device scan. type Q followed by the Enter key to exit the program. After starting ITDT-SE.0 but the system does not appear to be able to compress data on the cartridge. Enter the appropriate values for your system. If all write operations are finished. then check the device driver and software settings to see if they disable compression. the output shows the compression rate. 3. v Identify system issues with compression. Select the type of data to write. 4. it shows the Full Write screen. Drive data compression is always switched on during the full write. Chapter 10. Either insert a cartridge and press the Enter key or stop the test by typing C followed by the Enter key. If you are unsure. If an error occurred during the full write. The system prompts for entry of a transfer size between 16 KB and the maximum block size supported by the system (maximum possible value is 512 KB) . the program shows a progress indicator in form of a bar of hash marks (#) that shows the progress of the full write. ITDT-SE then switches to the Full Write screen. Select the device you want to write to by entering its number and press the Enter key. ITDT-SE prompts to insert a cartridge. If the compression rate is higher than 1. and displays the following message: Cartridge not empty! Overwrite data? Type Y followed by the Enter key to continue the test if you are absolutely sure that data on the cartridge can be overwritten. Note: It may take some time until the full write actually stops. If you want to use other ITDT-SE functions. IBM Tape Diagnostic Tool (ITDT) 275 . otherwise. The full write can be stopped by typing A followed by the Enter key at any time. During the full write. type N followed by the Enter key to stop the test. Type W and press the Enter key to start the full write. 3. Select the device you want to test by entering its number and press the Enter key. ITDT-SE then switches to the tape usage screen.IBM Tape Diagnostic Tool 2 1 Figure 72. 276 IBM Tape Device Drivers Installation and User’s Guide a2500244 . Tape Usage Screen 1. 2. Type U followed by the Enter key to start the tape usage log retrieval. ITDT-SE prompts to insert a cartridge. a2500243 Figure 73. type S followed by the Enter key to activate the device scan. Full Write Results Tape Usage The Tape Usage [U] function retrieves statistical data and error counters from a cartridge. If no cartridge is inserted. Either insert a cartridge and press the Enter key or stop the test by entering C followed by the Enter key. After starting ITDT-SE. 128. IBM Tape Diagnostic Tool (ITDT) 277 . If you are unsure. ITDT-SE then switches to the System Test screen. 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. System Test writes BytesToWrite with all supported block sizes in powers of two down to 16kB (at maximum 512. b. it shows the System Test screen. type N followed by the Enter key to stop the test. If no cartridge is inserted. ITDT-SE shows a Tape Usage completion screen. 32. 1. the library must be in online mode. then with incompressible data. Other Other [O] . 256. The System Test is performed as follows: a. Start ITDT-SE. Type O and press the Enter key to display the second device list screen. If all sub-operations are finished. Chapter 10. On the second device list screen. To perform a System Test on tape drives within a library. and then displays performance data and progress screen. At the end of the test. 3. not on autoloaders or libraries. Either insert a cartridge and press the Enter key or stop the test by typing C followed by the Enter key.type O followed by the Enter key to display a screen with the following commands: v “System Test” v “Library Self-Test” on page 278 v “Manual Inspect” on page 278 v “Return” on page 279 System Test The System Test [Y] is a short test that performs the following: v Reveals system performance bottlenecks. The System Test only runs on tape drives. Compressible data throughput values can reveal bandwidth limitations caused by the system or cabling or HBA. 16). 64. a summary screen is displayed. c. then type S and press the Enter key to scan for the devices. ITDT-SE prompts to insert a cartridge. v Measures performance variations across the different block sizes to find the ideal block size for the system configuration. type Y and press the Enter key to start the System Test. The Status field on the bottom right side indicates PASSED if the log retrieval completed successfully and ABORTED otherwise. first with compressible. 2. Note: If ITDT-SE detects data on the cartridge. and displays the following message: Cartridge not empty! Overwrite data? Type Y followed by the Enter key to continue the test if you are absolutely sure that data on the cartridge can be overwritten. System Test determines the amount of data to write for each supported blocksize (a percentage of the cartridge is written for each blocksize).IBM Tape Diagnostic Tool During the get logs operation. Manual Inspect Manual Inspect [I] creates a manual inspection record if a device does not appear in the device list. On the second device list screen. If you want to use other ITDT-SE functions. At the end of the test. type L and press the Enter key to start the Library Self-Test. Note: It may take some time until the System Test actually stops. The Library Self-Test can be stopped by typing A followed by the Enter key at any time. A Device Test screen is displayed and a functionality test on the tape library is performed. type R followed by the Enter key to return to the device list. type R followed by the Enter key to return to the device list. This test only runs on libraries and autoloaders.IBM Tape Diagnostic Tool Figure 74. otherwise press Q followed by the Enter key to exit the program. then type S and press the Enter key to scan for the devices. If you want to use other ITDT-SE functions. Library Self-Test The Library Self-Test [L] starts and monitors the library-internal self-test. Note: It may take some time until the Library Self-Test actually stops. Start ITDT-SE. System Test Results The System Test can be stopped by typing A followed by the Enter key at any time. Type O and press the Enter key to display the second device list screen. 3. otherwise press Q followed by the Enter key to exit the program. not on tape drives. This test is intended for devices that are not recognized or have a technical problem which can not be determined by ITDT-SE. 2. 278 IBM Tape Device Drivers Installation and User’s Guide a2500245 . a results screen is displayed. 1. 6. type I and press the Enter key to open the Manual Inspection screen. Start ITDT-SE. type M followed by a space and the model name and press the Enter key.Tapeutil Menu Commands When the user executes the U command on the ITDT-SE start screen. The results of the wrap test can be entered along with some additional inspection information. Note: On any screen. Enter the required information to complete the items in the screen: a. to execute a command. 1. Type T followed by a space and the content of the Message Display and press the Enter key. type A followed by a space and additional information text and press the Enter key. 4. IBM Tape Diagnostic Tool (ITDT) 279 . Optionally. press the shortkey displayed in brackets [ ]. Both files are stored in the ITDT-SE output folder. If you want to use other ITDT-SE functions. Type N followed by a space and the serial number and press the Enter key. c. For example: M ULT3580-TD1 5.type R followed by the Enter key to go back to the first device list screen. On the next screen. 3. then type S and press the Enter key to scan for the devices. 2. The following commands are described in this section: v “[1] Open a Device” on page 280 v “[2] Close a Device” on page 280 v v v v v v v “[3] “[4] “[5] “[6] “[7] “[8] “[9] Inquiry” on page 281) Test Unit Ready” on page 281 Reserve Device” on page 281 Release Device” on page 281 Request Sense” on page 281 Log Sense” on page 281 Mode Sense” on page 281 Chapter 10. the Tapeutil operation screen is displayed. Return Return [R] . On the second device list screen. Type O and press the Enter key to display the second device list screen. otherwise press Q followed by the Enter key to exit the program. After all information has been entered. type S and press the Enter key to save the data. The result are saved into binary and text output files that have the same format as the output files generated by the test. The system prompts for the user to run the SCSI/FC Wrap test for the drive (see the service manual for the drive).IBM Tape Diagnostic Tool If a tape drive cannot be identified using a device scan. b. type R followed by the Enter key to return to the first device list screen. The information is stored in a binary file (which can be used for further analysis). and in a human-readable text file. Standard Edition . the user can manually create a test record for the drive. followed by the Enter key. 4. ITDT closes the device. You are prompted for a device special file name. [2] Close a Device When you select the Close a Device command [2]: 1. 3. ITDT checks if the device is already closed. You are prompted for an open mode (rw. 2. Path (Test Encryption Key Path/Setup)” on page 285 v v v v v v v v v v v v “[50] “[51] “[52] “[53] “[54] “[55] “[56] “[55] “[58] “[59] “[70] “[71] Element Information” on page 285 Position to Element” on page 285 Element Inventory” on page 285 Exchange Medium” on page 285 Move Medium” on page 285 Initialize Element Status” on page 285 Prevent/Allow Medium Removal” on page 286 Initialize Element Status” on page 285 Read Device IDs” on page 286 Read Cartridge Location” on page 286 Dump/Force Dump/Dump” on page 286 Firmware Update” on page 286 [1] Open a Device When you select the Open a Device command [1]: 1. ro. ITDT opens the device you selected. (Version)” on page 281 “[11] Display All Paths” on page 281 “[20] Rewind” on page 282) “[21] Forward Space File Marks” on page 282 “[24] Backward Space Records” on page 282 “[23] “[22] “[25] “[26] “[27] “[28] “[29] “[30] “[31] “[32] “[33] “[34] “[35] Forward Space Records” on page 282 Backward Space File Marks” on page 282 Space to End of Data” on page 282 Read and Write Tests” on page 282 Read or Write Files” on page 282 Erase” on page 283 Load Tape” on page 283 Unload Tape” on page 283 Write File Marks” on page 283 Synchronize Buffers” on page 283 Query/Set Parameter” on page 283 Query/Set Tape Position” on page 284 Query Encryption Status” on page 284 v “[36] Display Message” on page 284 v “[37] Report Density Supp (Support)” on page 284 v “[38] Test Encryp. 2. wo. append). 280 IBM Tape Device Drivers Installation and User’s Guide .IBM Tape Diagnostic Tool v v v v v v v v v v v v v v v v v v “[10] Query Driver Ver. ITDT checks if a device is already opened. ITDT then displays a decoded format of hexadecimal dump sense data and prints hexadecimal dump sense data. You are prompted for page code. ITDT issues an ioctl command. (Version) When you select the Query Driver Version command [10]: 1. You are prompted for Log Sense Page. Chapter 10. [8] Log Sense When you select the Log Sense command [8]: 1. 3. [5] Reserve Device When you select the Reserve Device command [5]. 2. IBM Tape Diagnostic Tool (ITDT) 281 . [11] Display All Paths When you select the Display All Paths command [11]: 1. ITDT then displays a decoded format of a hexadecimal dump and prints a hexadecimal dump of the inquiry data. 2. 2. [10] Query Driver Ver. ITDT outputs decoded path information for all paths. 3. ITDT prints driver version. [4] Test Unit Ready When you select the Test Unit Ready (TUR) command [4]. ITDT issues the required command to get driver version. ITDT issues mode sense command. 2. [9] Mode Sense When you select the Mode Sense command [9]: 1. ITDT issues a reserve command for the device. [6] Release Device When you select the Release Device command [6]. ITDT issues a release command for the device. ITDT issues a Request Sense command. ITDT performs a hexadecimal dump page. You are prompted for Mode Sense Page. [7] Request Sense When you select the Request Sense command [7]: 1. 2. ITDT issues the Test Unit Ready ioctl command. 2. ITDT performs a hexadecimal dump page.IBM Tape Diagnostic Tool [3] Inquiry When you select the Inquiry command [3]: 1. ITDT issues a mode sense command. [23] Forward Space Records When you select the Forward Space Records command [23]: 1. v You are prompted for the number of blocks per read/write (If you just press Enter. You are prompted for the number of records to space backward. ITDT issues (extrinsic) ioctl command. [22] Backward Space File Marks When you select the Backward Space File Marks command [22]: 1. 2. [26] Read and Write Tests When you select the Read and Write Tests command [26]: v You are prompted for block size (If you just press Enter. and the total bytes transferred. the default block size is 10240). [25] Space to End of Data When you select the Space to End of Data (EOD) command [25]. 2. You are prompted for the number of file marks. ITDT issues the (extrinsic) ioctl command. ITDT issues the ioctl rewind command for the device. [27] Read or Write Files When you select the Read or Write Files command [27]: 282 IBM Tape Device Drivers Installation and User’s Guide . v You are prompted for the number of repetitions (If you just press Enter. You can then select one of the following options: v Read data from tape (to run Read only test) v Write data to tape (to run Write only test) v 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. ITDT issues (extrinsic) ioctl command. the default number of repetitions is 1). 2. [21] Forward Space File Marks When you select the Forward Space File Marks command [21]: 1.IBM Tape Diagnostic Tool [20] Rewind When you select the Rewind command [20]. the number of records read/written. You are prompted for the number of file marks to space forward. 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 forward. ITDT issues (extrinsic) ioctl command. 2. the default number of blocks is 20). You are prompted for parameter to change. ITDT issues the ioctl command. You are prompted for the number of file marks to write. Note: The list of changeable parameters is operating system specific. IBM Tape Diagnostic Tool (ITDT) 283 . [30] Unload Tape When you select the Unload Tape command [30]. Chapter 10. ITDT displays the number of records read/written. ITDT issues the load tape command. 3. 4. You can then select one of the following options: v Read File from Tape: ITDT reads a file from tape and stores data into a file with the given filename. [29] Load Tape When you select the Load Tape command [29]. [33] Query/Set Parameter When you select the Query/Set Parameter command [33]: 1. 2. [31] Write File Marks When you select the Write File Marks command [31]: 1. ITDT issues the unload tape command.IBM Tape Diagnostic Tool v You are prompted to specify the filename of the source file (for Write test) or the destination file (for Read test). 2. [32] Synchronize Buffers When you select the Synchronize Buffers command [32]. ITDT requests prompt for parameter value (if required). Note: The list of non-changeable parameters is operating system specific. v You are prompted for the number of records to be read. ITDT issues the (extrinsic) ioctl command. v Write File to Tape: ITDT reads data from file with the given filename and writes data to tape. ITDT displays non-changeable parameters. ITDT requests safety prompt (if required). ITDT issues the ioctl command. ITDT issues the (extrinsic) ioctl command. 5. the transfer size and the total bytes transferred. [28] Erase When you select the Erase command [28]. ITDT displays changeable parameters. 6. 3. ITDT prints report data in a decoded way. Encryption Method. 4. ITDT issues Report Density Support ioctl command to retrieve current media 6. ITDT displays encryption settings (Encryption capability. flash0. ITDT issues Get Encryption State ioctl command. 284 IBM Tape Device Drivers Installation and User’s Guide . Scroll the screen to print each one of the following: v Density name v Assigning organization v Description v Primary density code v Secondary density code v Write OK v Duplicate v Default v Bits per MM v Media Width v Tracks v Capacity (megabytes). You are prompted for the text of message 0 (8 characters or less). ITDT issues the Display Message ioctl command. You are prompted for the text of message 1 (8 characters or less) 3. The 3592 drive 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. ITDT issues Report Density Support ioctl command to retrieve all supported media. You are prompted for a new position to set. ITDT prints all requested reports. [37] Report Density Supp (Support) When you select the Report Density Support command [37]: 1. Data is printed in a decoded way. [35] Query Encryption Status When you select the Query Encryption Status command [35]: 1. ITDT displays the current position 2. 2. You are prompted for message type (msg0. Not all drives have a display. 3. 4. [36] Display Message When you select the Display Message command [36]: 1. ITDT issues the Set Position ioctl command. Eight is the limit of the characters on a display screen. 2. msg1. Encryption state). ITDT prints report status text for all supported media. ITDT prints report status text for current media 5. 2. alt). flash1.IBM Tape Diagnostic Tool [34] Query/Set Tape Position When you select the Query/Set Tape Position command [34]: 1. number of i/e elements. 4. 3. [51] Position to Element When you select the Position to Element command [51]: 1. You are prompted for second destination address. first element address. ITDT issues the Element Inventory ioctl command. [52] Element Inventory When you select the Element Inventory command [52]: 1. Full Encryption Diag completion code or error message. You are prompted for destination address. type n followed by return to show next page of information. You are prompted for source address. 3. ITDT issues the ioctl command 2. Chapter 10. 2. ITDT issues the ioctl command. You are prompted for source address. IBM Tape Diagnostic Tool (ITDT) 285 . 2. [54] Move Medium When you select the Move Medium command [54]: 1. ITDT issues the ioctl command. first drive address. 2. You are prompted for first destination address. 7. ITDT ITDT ITDT ITDT ITDT ITDT ITDT prints issues prints issues prints issues prints status message that server configuration and connections are tested the Encryption Diagnostics ioctl command. 2. first robot address. 6. ITDT displays number of robots. 5. 3. first slot address. ITDT prints command summary. 1. You are prompted for destination address 2. ITDT displays decoded element inventory info. Ping Diag number of servers available or error message the Encryption Diagnostics ioctl command. [55] Initialize Element Status When you select the Initialize Element Status command [55]: 1. Basic Encryption Diag completion code or error message the Encryption Diagnostics ioctl command. ITDT issues the Element Info ioctl command. ITDT issues the ioctl command. [50] Element Information When you select the Element Information command [50]: 1.IBM Tape Diagnostic Tool [38] Test Encryp. 4. [53] Exchange Medium When you select the Exchange Medium command [53]: 1. 3. 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. number of slots. number of drives. ITDT issues the ioctl command. ITDT retrieves the device ID information for all available drives and displays the information. ITDT verifies that the given address range is valid. You are prompted for the first slot address. 3. 7. v ITDT displays name of stored dump files and the output directory where they are stored. v ITDT issues Force Dump command. or to press Enter to keep the standard ITDT directory. otherwise print error message and exit. [59] Read Cartridge Location When you select the Read Cartridge Location command [59]: 1. Type n followed by Enter to show next page. ITDT issues the ioctl command. You are prompted for number of elements. or (0) for Allow Removal. [56] Prevent/Allow Medium Removal When you select the Prevent/Allow Medium Removal command [56]: 1. The dump filenames start with the serial number of the device. [58] Read Device IDs When you select the Read Device IDs command [58]. 9. 5. ITDT issues the READ_CARTRIDGE_LOCATION ioctl command. You are prompted for the address of the first slot. [57] Initialize Element Status Range When you select the Initialize Element Status Range command [57]: 1. v ITDT retrieves second dump. [70] Dump/Force Dump/Dump When you select the Dump/Force Dump/Dump command [70]: v ITDT retrieves dump. If no slots are found in Element Info data. Type n followed by Enter to show the next page. You are prompted to select (1) for Prevent Removal. 2. The following are examples of the directory: v Example input directory (Windows): c:\itdt\input v Example input directory (Unix): /home/user/itdt/input 2. print error message and exit. ITDT issues the Element Info ioctl command. You are prompted for the number of slots. otherwise prints error message and exit. You are prompted to specify a different input directory if required. 3. [71] Firmware Update When you select the Firmware Update command [71]: 1. 286 IBM Tape Device Drivers Installation and User’s Guide . 4. 2. 8. ITDT displays the default input directory where the firmware files should be stored.IBM Tape Diagnostic Tool 2. ITDT verifies that the address range is valid. ITDT issues the READ_CARTRIDGE_LOCATION ioctl command. ITDT prints decoded storage element information. 6. Graphical Edition . RHEL5 and other Linux systems where none of the supported JREs is available in the path do the following: Chapter 10. Note: The JRE delivered with Red Hat Enterprise Linux 4 and 5 (RHEL4.5 SR6 or higher. The supported Windows operating systems for ITDT-GE are: v Microsoft Windows XP v Microsoft Windows Server 2003 v Microsoft Windows Server 2008 (IX86. RHEL5) is not supported. Install one of the following supported JREs before launching the ITDT Installer: v Java 1.bin to a directory of your choice. ITDT performs firmware update and displays progress status and result. Note: See “3576/TS3310 Tape Library” on page 265 for more information on how to update the firmware on a 3576/TS3310 Tape Library. 4.Installation Windows To install ITDT-GE on Windows. download the executable file install_ITDT_GE_<version>.2 SR3 by IBM Corporation and higher v Java 1.IBM Tape Diagnostic Tool 3. download the executable file install_ITDT_GE_<version>. Install one of the following: v Java 1.com/storage/lto.bin needs to be run by a user with root access rights.4. You are prompted to specify the firmware file name and press Enter to start. ITDT-GE installer automatically uninstalls any previous version before installing the current one.exe on a directory of your choice. The following site is available for the latest firmware files: http://www. For the graphical user interface (GUI) a minimum screen resolution of 1024*768 pixels is required.4. Double-click the downloaded file to launch the installer application. ITDT-GE requires a 32-bit Java Runtime Environment (JRE) to be installed. install_ITDT_GE_<version>.4.2 SR3 by IBM Corporation and higher v Java 1.5 on a Microsoft Windows system is used. ITDT-GE requires a 32-bit Java Runtime Environment (JRE) to be installed. 32-bit) Linux To install ITDT-GE on Linux.ibm.2_10 by Sun Microsystems and higher Note: If IBM Java 1.2_10 by Sun Microsystems and higher On RHEL4. IBM Tape Diagnostic Tool (ITDT) 287 .4. ensure that it is Java 1. Command Timeout There is no instant operation termination upon SCSI command timeout. Devices Disappear After Firmware Update After a firmware update. When a command timeout condition occurs. The ITDT-GE installer automatically uninstalls any previous version before installing the current one. The supported Linux operating systems for ITDT-GE are: v Linux Distributions with glibc 2. when the SCSI cable is unplugged after starting POST A. Create a symbolic link to the JRE to ensure that ITDT finds the right JRE before starting ITDT-GE. only the [T] Test option won’t work due to device-specific restrictions for handling cartridges./install_ITDT_GE_<version>. Add your Java directory to the path before starting the installer: The following are examples of how to extend the search path (replace <version> with the version that is in use). This is a known Windows problem. 32-bit) Graphical Edition . 288 IBM Tape Device Drivers Installation and User’s Guide .2_09 /opt/ibm/itdt-ge/jre Note: In the above examples.2_09/bin:$PATH $ . 3576/TS3310 Tape Library Library Firmware Update using ITDT-GE is not supported with the 3576/TS3310 tape library. 3494 Tape Library Drives in a 3494 tape library or an STK silo library are supported. ITDT may still continue to perform more operations (like unmounting the cartridge) instead of instantly terminating with a timeout condition.bin v For Sun Microsystems Java Runtime Environment: $ export PATH=/usr/java/j2re1.IBM Tape Diagnostic Tool 1. replace the directory names with your JRE directories. Update the Firmware using the 3576/TS3310 Web User Interface. For the graphical user interface (GUI) a minimum screen resolution of 1024*768 pixels is required. 2.4. for example.bin Note: In the above examples. devices may disappear. v For IBM Java Runtime Environment: $ ln -sf /opt/IBMJava2-142/jre /opt/ibm/itdt-ge/jre v For Sun Microsystems Java Runtime Environment: $ ln -sf /usr/java/j2re1.2.5 and higher (IX86. v For IBM Java Runtime Environment: $ export PATH=/opt/IBMJava2-142/jre/bin:$PATH $ .4. replace the directory names with your JRE directories./install_ITDT_GE_<version>.Known Issues and Limitations This section describes the known issues and limitations of ITDT-GE. When switching applications on Windows while ITDT-SE is running. It is strongly recommended that this information be provided to allow for further analysis of test results.IBM Tape Diagnostic Tool See the Article ID: 812024 at: http://support. an extra ESC character may appear on the input line and the input is ignored after you press the Enter key. The Log Level should not be changed unless requested to do so by the IBM Support Center. Click OK to save the settings and close the dialog. IBM Tape Diagnostic Tool (ITDT) 289 a2500238 .microsoft. Graphical Edition .Known Issues and Limitations” on page 262 section. Graphical Edition User Interface To start ITDT-GE on Windows click the shortcut created by the installation process. On Linux. company name. Start ITDT-GE by opening a Terminal window. It is strongly recommend that this information be provided to allow for further analysis of test results. output path and log level. ensure that you are using the latest Adaptec Host Bus Adapter Drivers instead of the drivers shipped with the Windows operating system. then switch to root user: $ su - finally start ITDT-GE with $ /opt/ibm/itdt-ge/itdt-ge The User Settings dialog appears the first time the program is run.com/kb/812024/en-us Repeated Scan operations may help to rediscover the device. Performance Issues Note: This section only applies to Windows and content also appears in the “Standard Edition . The Output Path defines the location where the test reports and dumps are saved. Chapter 10.User Interface Description Figure 75. If you are using Adaptec SCSI Host Bus Adapters. no start menu entry is generated. allowing the entry of user specifications: user name. v Test Lab ( 3 ) .Scan. v Dump Click the arrow next to the Dump menu item to select additional log options.Located on left side (Device operations . Dump. For each device on which the operation has been started.Located below the Test Lab (Contains summary results of tests) The Control Center is the primary section the ITDT-GE operations. Help) v Control Center ( 2 ) . v Update Click the Update menu item to start the firmware update. and Update) Additional device operations are available using drop down arrows. When the scan is complete. Choose one of the following available operations: v Click the Scan menu item in the Control Center to display the list of tape devices found.Located from center to right side (Contains running and previously run tests) v Status Information ( 4 ) . Test. v Test Click the arrow next to the Test menu item to select an extended test.IBM Tape Diagnostic Tool 1 2 3 4 a2500239 Figure 76. a separate tab is opened. The benefit in using tabs even for the single operation mode is that you get a history of operations as for each consecutive operation. a tab appears on the right panel (Test Lab area). 290 IBM Tape Device Drivers Installation and User’s Guide .Located in upper left (File. Graphical Edition Pre-scan Interface The ITDT-GE interface contains the following: v Main Menu ( 1 ). The tab contains the operation information and status. Window. Only one operation can be run at a time with ITDT-GE. select one device in the Test Lab by clicking the corresponding checkbox. the device list is displayed. IBM Tape Diagnostic Tool (ITDT) 291 a2500240 . Once the desired device is displayed. in the Control Center area. Note: When pressing the Scan button for the first time. that warns the user to stop all backup jobs. a dialog box is displayed.IBM Tape Diagnostic Tool Graphical Edition . The scan function also serves as a connection test that can be used to verify proper attachment of the devices. Chapter 10. A scroll bar is available to display all the devices. Only one device can be selected. select the device for test. Scan Function The scan function is used to discover all supported tape and library devices that are attached to the computer system so that they can be selected for the subsequent ITDT-GE operations. Once the scan is finished.Scan Menu Commands The following commands are described in this section: v “Scan” v “Test” on page 292 v “Dump” on page 294 v v v v v v “Firmware Update” on page 295 “Encryption” on page 296 “Full Write” on page 297 “Tape Usage” on page 299 “System Test” on page 299 “Library Diagnostic Self-Test” on page 300 Scan Figure 77. Scaled (capacity-reduced) cartridges should not be used to test the device. 2. not on autoloaders or libraries. The Test function can be stopped by clicking the Abort button. Note: It may take some time until the Test function actually stops. 292 IBM Tape Device Drivers Installation and User’s Guide a2500241 . The test can take from 15 minutes up to 2 hours. To perform the Test function. After selecting the device you want to test. Test Menu The test function checks if the tape device is defective and outputs a pass/fail result. The test runs only on tape drives. To test tape drives within a library. Attention: The test functionality erases user data on the cartridge that is used for the test. it is recommended that a new or rarely used cartridge is used. the library must be in online mode. Notes: 1.IBM Tape Diagnostic Tool Test Figure 78. start the Test function selecting the Test menu item. 6. See the log file section ( 1 ). 5.IBM Tape Diagnostic Tool 1 Figure 79. Performance Test Unmount Medium Get FSC Get Logs Chapter 10. POST A During POST A stopping the test is not allowed. 8.txt/. 7. Test Results Note: Information can be found in the .blz files. [Medium Qualification] – only if the previous step indicated this requirement 3. Mount Medium 2. Load/Unload Cycles 4. The test sequence contains the following steps: 1. IBM Tape Diagnostic Tool (ITDT) 293 a2500242 . When the dump process is performed on a tape library or autoloader other than the 3584/TS3500. Both files start with the serial number of the device ( 1 ). For the 3584/TS3500. a dump file (*.gz) will be stored in the output folder. start the Dump function by selecting Dump -> Dump from the actions toolbar.blz). Dump Menu After selecting the device you want to dump. the Dump function stores one log file in the output folder of the program (*. 1 a2500224 2 Figure 81.a.IBM Tape Diagnostic Tool Dump Figure 80. Dump Results 294 IBM Tape Device Drivers Installation and User’s Guide a2500225 . 3. See “Supported Equipment” on page 258 for a list of supported products. Select the device you want to update. Note: See “3576/TS3310 Tape Library” on page 265 for more information on how to update the firmware on a 3576/TS3310 Tape Library.IBM Tape Diagnostic Tool Note: When the Dump function is performed for tape libraries or autoloaders other than the 3584/TS3500. During the firmware update. The following site is available for the latest firmware files: http://www. IBM Tape Diagnostic Tool (ITDT) 295 . Note: If ITDT-GE detects a FIPS-certified drive firmware. it displays a warning dialog. Chapter 10. but it can take up to 45 minutes for libraries. The firmware update usually takes 3-5 minutes. A standard file dialog opens to select the path of where the firmware update is located. indicating the progress of the update. do not interrupt the firmware update. 2. Before continuing.com/storage/lto To do a Firmware Update perform the following steps: 1. 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 device. the Log file only contains Log Sense and Mode Sense pages. while a Drive or 3584/TS3500 Dump contains much more diagnostic information. ( 2 ) Firmware Update The Firmware Update upgrades the firmware of tape drives and tape libraries. Select the Update menu item. Attention: Once started. a firmware update progress screen is displayed. ensure that you use a FIPS-certified firmware to update the drive.ibm. After selecting the device you want to test. The Encryption function can be stopped by clicking the Abort button. On 3592/TS1120/TS1130 drives. Encryption Function Note: Note that the test shown on the graphic above was run on a non-encrypted device and is showing a failure. Enter the required values and click OK to start the encryption.IBM Tape Diagnostic Tool Encryption Figure 82. It reads both decrypted and raw data from the cartridge into two separate files on disk. 1. The Encryption function is used to verify if data on the cartridge was actually written encrypted. ensure that an encrypted cartridge is used before starting this operation. the system requires the entry of the number of the start record and the amount of data (in KB) to be read. Notes: 1. The Encryption function is only supported on encryption enabled drives and requires an encryption infrastructure including the Encryption Key Manager (EKM) to be properly set up. 296 IBM Tape Device Drivers Installation and User’s Guide a2500226 . If the Encryption function is run on IBM Ultrium 3580 Generation 4 drives. ITDT-GE stops the Encryption function when it detects that a cartridge is not encrypted. the Encryption function continues even when a cartridge without encrypted data is used. on these drives. ITDT-GE then displays the Encryption Verification screen. start the encryption function by selecting Test -> Encryption Verification from the actions toolbar. 2. 3. On this screen. The user can then verify that the data differs to ensure that encryption worked. Click OK to start the full write. 2. Table 30 on page 274 defines the abort codes. IBM Tape Diagnostic Tool (ITDT) 297 . check your device driver and software settings to see if they disable compression. Note: If ITDT-GE detects data on the cartridge. 2. If no difference in overall performance is observed. The Full Write function runs only on tape drives. the library must be in online mode. Full Write firsts runs the test with incompressible data first. less time for compressible data. not on autoloaders or libraries. The Full Write test can be used to: v Demonstrate that the drive is capable of writing the full amount of data on a cartridge. v Reveal system performance bottlenecks. the output shows the compression rate. Attention: The Full Write function erases data on the cartridge that is used for the test.0 but your system does not appear to be able to compress data on the cartridge. then runs the test with compressible data. then probably there is a bandwidth limitation caused by the system or cabling or HBA. ITDT-GE prompts to insert a cartridge. start the Full Write function by selecting Test -> Full Write from the actions toolbar. If no cartridge is inserted. If that is higher than 1. Notes: 1. To perform a full write on tape drives within a library. When run with compressible data. v Identify system issues with compression. The Full Write function takes approximately 2 hours when writing incompressible data. Either insert a cartridge and click OK or stop by clicking the Abort button. it displays the following message (Figure 83 on page 298): Chapter 10.IBM Tape Diagnostic Tool Note: It may take some time until the Encryption function actually stops. ITDT-GE then displays the Full Write screen. Compression is always switched on during the full write. After selecting the device you want to write to. 1. Full Write The Full Write function writes the entire cartridge with a given block size either with compressible or incompressible data and output performance data. If you are unsure. in the Status Information area. 3. This is a check for the type of supported block size is performed. Overwrite Data Click Yes to continue the test if you are absolutely sure that data on the cartridge can be overwritten. either: [C] Compressible or [I] Incompressible. If an error occurred during the full write. data is only written partially. ITDT-GE displays the performance statistics for every block size written on the cartridge. Select the type of data to write. Note: It may take some time until the full write actually stops. Enter the appropriate values for your system. Figure 84. Transfer Size 4. If all write operations are finished. The system prompts for entry of a transfer size between 16 KB and the maximum block size supported by the system (maximum possible value is 512 KB) .IBM Tape Diagnostic Tool Figure 83. click No to stop the test. 298 IBM Tape Device Drivers Installation and User’s Guide a2500228 a2500227 . The full write can be stopped by clicking the Abort button. v Measures performance variations across the different block sizes to find the ideal block size for the system configuration. Tape Usage The Tape Usage function retrieves statistical data and error counters from a cartridge.IBM Tape Diagnostic Tool Tape Usage Figure 85. 2. IBM Tape Diagnostic Tool (ITDT) 299 a2500229 . System Test The System Test is a short test that performs the following: v Reveals system performance bottlenecks. ITDT-GE then displays the tape usage screen. Note: If ITDT-GE detects data on the cartridge. start the System Test function by selecting Test -> System Test from the actions toolbar. start the Tape Usage function by selecting Dump -> Tape Usage Log from the actions toolbar. The System Test only runs on tape drives. ITDT-GE prompts to insert a cartridge. 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. it displays the following message: Chapter 10. After selecting the device you want to test. If no cartridge is inserted. Either insert a cartridge and click OK or stop by clicking the Abort button. 1. not on autoloaders or libraries. After selecting the device you want to test. the library must be in online mode. Compressible data throughput values can reveal bandwidth limitations caused by the system or cabling or HBA. To perform a System Test on tape drives within a library. 32. not on tape drives. Library Diagnostic Self-Test The Library Self-Test starts and monitors the library-internal self-test. 2. If you are unsure. start the Library Self-Test function by selecting Test -> Library Diagnostic Self-Test from the actions toolbar. System Test The System Test is performed as follows: 1. This test only runs on libraries and autoloaders.IBM Tape Diagnostic Tool Cartridge not empty! Overwrite data? Click Yes to continue the test if you are absolutely sure that data on the cartridge can be overwritten. then with incompressible data. click No to stop the test. System Test determines the amount of data to write for each supported blocksize (a percentage of the cartridge is written for each blocksize). 128. 256. Figure 86. 16). a summary information is displayed. the results are displayed in the Status Information area. 3. first with compressible. After selecting the device you want to test. 300 IBM Tape Device Drivers Installation and User’s Guide a2500230 . At the end of the test. and then displays a data and progress screen. 64. At the end of the test. System Test writes BytesToWrite with all supported block sizes in powers of two down to 16kB (at maximum 512. ibm. Obtain them by accessing the following URL: ftp://ftp. Device and Library Drivers for each supported platform can be found beneath /storage/devdrvr/ in the following directories: AIX/ HPUX/ Linux/ SGI/ Solaris/ Tru64/ Windows/ For the most-current information for the device driver you are using. 2007.4.software.Appendix A. consult the README file. The IBM_Tape_Driver_IUG. you may access this information using anonymous FTP.) /storage/devdrvr IBM provides Postscript. that is.com 207. as follows: FTP site: IP Address: User ID: Password: Directory: ftp.26/storage/devdrvr Or.com/storage/devdrvr ftp://207.25.bin.ibm.ibm.html This web page has links to the device driver download web pages.com/systems/support/storage/config/hba/index.4.ibm. 2009 301 .pdf file contains the current version of the IBM Tape Device Drivers: Installation and User’s Guide.0. Postscript documents are gzip-ed.pdf file contains the current version of the IBM Tape Device Drivers: Programming Reference.and PDF-formatted versions of its documentation in the /storage/devdrvr/Doc directory.com/storage/devdrvr/tapedrivers. a higher numeric sequence is assigned.wss You may also browse the FTP site and download drivers using one of the following URLs: ftp://ftp. There are numeric sequence numbers in each level of device and library driver. For example. consult the README files in the directory pertaining to your device driver.0.253. firmware and BIOS levels can be obtained from the following URL: http://www-03.253.software. © Copyright IBM Corp. for information on exploiting the capacity scaling feature of your IBM TotalStorage Enterprise Tape Subsystem 3592.26 anonymous (Use your current e-mail address. Information concerning supported fibre channel host bus adapters (HBAs) and associated HBA device drivers. As newer levels of a driver are released.software.25. AIX/Atape. The IBM_Tape_Driver_PROGREF. Accessing Documentation and Software Online IBM maintains the latest levels of TotalStorage tape drive and library device drivers and documentation on the Internet. n.n.x64.tar Windows/ibmatl/ibmmatl.i64_nnnn.rpm.bin Linux/lin_tape_source-lin_taped/IBMtapeutil/ IBMtapeutil.n.n.bin Linux/lin_tape_source-lin_taped/lin_tape-x.n.exe Windows/Win2000/Latest/IBMTape.i64.n. ia64.x.zip Windows/Win2008/Latest/IBMTape.zip Windows/Win2008Latest//IBMTape.rpm.n.bin HPUX/. or n. 2.n.n.n.tar.bin Linux/lin_tape_source-lin_taped/lin_taped-x. dist indicates a Linux distribution.n.n.x-x.hpux.n.bin SGI/ibmatl.n. arch indicates a machine architecture (for example.bin AIX/atldd.n.n strings are replaced with digits on the FTP site to reflect the version of each driver.zip Windows/Win2003Latest//IBMTape.x-dist.arch.exe Windows/ibmatl/ibmatl. 302 IBM Tape Device Drivers Installation and User’s Guide .zip Windows/Win2003/Latest/IBMTape.n.n.n.n.exe Windows/ibmatl/ibmalt.n.x86_w08_nnnn.n.n.zip Description AIX Device Driver (Atape) AIX 3494 Enterprise Tape Library Driver HP-UX Device Driver HP-UX 3494 Enterprise Library Driver Linux 3494 Enterprise Library Driver Linux Device Driver (lin_tape) source code Linux lin_taped daemon program Linux Tape Utility (IBMtapeutil) SGI/IRIX Enterprise Library Driver Solaris Device Driver (IBMtape) Solaris 3494 Enterprise Library Driver Tru64 Enterprise Library Driver 32-bit Windows 3494 Enterprise Library Service 32-bit Windows 3494 Enterprise Library Service 64-bit Windows 3494 Library Service for IA64 64-bit Windows 3494 Library Service for AMD64 and EM64T Windows Server 2000 Device Driver on x86 Windows Server 2003 32-bit Device Driver on x86 Windows Server 2003 64-bit Device Driver on IA64 Windows Server 2003 64-bit Device Driver on AMD64 and EM64T Windows Server 2008 32-bit Device Driver on x86 Windows Server 2008 64-bit Device Driver on IA64 Windows Server 2008 64-bit Device Driver on AMD64 and EM64T Notes: 1.zip Windows/Win2008/Latest/IBMTape.n.n.n.n.n.kit.bin Linux/ibmatl/ibmatl.n.x86_nnnn.n.x86. Driver Descriptions Driver AIX/Atape.bin Tru64/ibmatl.n.n.tru64.n..n.n.x.n.n.x.exe Windows/ibmalt/ibmalt.n. The n.n./atdd. s390).n.x86_nnnn.n.n.bin HPUX/lmcpd/lmcpd.src.n. i386.rpm.n.Accessing Documentation and Software Online Table 31 documents each driver by name and description: Table 31.n.n.arch.n.tardist Solaris/IBMtape.x64_w08_nnnn.n.bin Solaris/lmcpd.n.n.i64_w08_nnnn.n.n.n..arch.zip Windows/Win2003/Latest/IBMTape.n.n.x64_nnnn.n.n.n.n.n. and install or enable the drivers documented in this manual. disable the other device drivers. you may want to verify that the hardware. 6. Before you can do this. 2.Appendix B. 2007. 3. If there are device drivers being used by your device other than the ones documented in this manual. and device drivers are working together properly. or if you encounter difficulties with your devices. Attach your hardware to the host system as indicated in the appropriate hardware manuals and as indicated in the appropriate chapters from this manual. Verifying Proper Attachment of Your Devices Before you start to use your devices for production work with your applications. you must do the following: 1. Log into the operating system as Administrator. 7. Start your operating system as indicated in the appropriate chapters from this manual. connections. 5. Power On your hardware and verify that the hardware is functioning properly by executing commands from the front panel. 4. Follow the subsequent instructions for your host system. © Copyright IBM Corp. Install your hardware as indicated in the appropriate hardware manuals. 2009 303 . use the appropriate hardware manual to verify that the information is reasonable. . This concludes a very basic test of the device. 6. press Enter after following the instruction. SCSI connection.? message is displayed or when you are told to enter information. 2. When the utility displays information. and the device driver. Enter 30 (Read and Write Tests). Specify 0 when prompted for an inquiry page. 4. 1. 11. Enter 1 (Read/Write). . When the Hit <Enter> to Continue . Enter 1 (Read/Write). Enter 1 (Open a Device). SCSI connection. and the device driver. 1. The procedure assumes that your device is attached at /dev/rmt0. 304 IBM Tape Device Drivers Installation and User’s Guide . 4. The procedure assumes that your device is attached at /dev/rmt0 and that there is no cartridge in the drive. 8. Enter 3 (Device Info). 7. Medium Changer Device Attachment Test The following procedure tests the attachment of a medium changer device to an AIX system. 9. You also need a cartridge in at least one of the slots. use the appropriate hardware manual to verify that the information is reasonable.AIX .Verifying Proper Attachment of Your Devices AIX System Tape Device Attachment Test The following procedure tests the attachment of a tape device to an AIX system. press Enter after following the instruction. Enter 31 (Unload Tape). Enter tapeutil. Enter 1 (Open a Device). 12. Enter /dev/rmt0 when prompted for the device name. Enter 5 (Inquiry). Open an AIX window. Enter /dev/rmt0 when prompted for the device name. Enter Q (Quit Program). When the Hit <Enter> to Continue . 13. . Enter 2 (Close a Device). Open an AIX window. 2. You may stop the test here or continue to perform a more complete test. Enter 3 (Device Info). 10. . Enter 22 (Rewind). 5. A menu is displayed. 14. You may stop the test here or continue to perform a more complete test. Enter tapeutil. A menu is displayed. 6. 7. Enter 5 (Inquiry). When the utility displays information. 3. 5. This concludes a very basic test of the device. Enter 1 (Read/Write). 3. Specify 0 when prompted for an inquiry page. Press the Enter key three times to accept the defaults and run the test. Enter 6 (Test Unit Ready) until no error occurs. ? message is displayed or when you are told to enter information. Enter 16 (Move Medium). 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to an AIX system. From the output of the previous step. then supply the address of the cartridge followed by the address of the unoccupied slot.Verifying Proper Attachment of Your Devices 8. Enter Q (Quit Program). Also. 15. 2. Verifying Proper Attachment of Your Devices 305 . 12. Verify that the cartridge moved. 1. select a writable. Enter 2 (Close a Device). The procedure assumes that your device is defined as /dev/lmcp0. Enter 6 (Test Unit Ready) until no error occurs. 13. 10. 11. scratch cartridge and determine its element ID. 9. Verify that the inventory was updated properly. 14. Open an AIX window. Enter 14 (Element Inventory). Enter mtlib -l /dev/lmcp0-qI 3.AIX . select the element ID of an unoccupied slot. Enter 14 (Element Inventory). Enter mtlib -l /dev/lmcp0 -qL Appendix B. Enter 18 (Initialize Element Status). Enter 5 (Inquiry). When the utility displays information. From the output in the previous step. Enter D (Device Info). 306 IBM Tape Device Drivers Installation and User’s Guide . When you are told to enter information. Enter tapeutil. Enter Element Inventory option. 4. 3. Enter Inquiry Option (Inquiry). 2. You also need a cartridge in at least one of the slots. press the Enter key after following the instruction. The procedure assumes that your device is attached at /dev/rmt/0chng and that the ACF is in Random mode. Enter 1 (Read/Write). scratch cartridge and determine its element ID. use the appropriate hardware manual to verify that the information is reasonable. A menu is displayed. Enter 1 (Open a Device). select the element ID of an unoccupied slot. Enter Test Unit Ready option until no error occurs. Enter 1 (Open a Device). 9. 8. 5. 1. Enter D (Device Info).Verifying Proper Attachment of Your Devices HP-UX System Tape Device Attachment Test The following procedure tests the attachment of a tape device to an HP-UX system. Enter 1 (Read/Write).HP-UX . 4. Enter Q to quit tapeutil. Verify that the inventory was updated properly. Enter Q (Quit Program). A menu is displayed. Also. and the device driver. select a writable. Autochanger Device Attachment Test The following procedure tests the attachment of an autochanger device to an HP-UX system. 11. 8. then supply the address of the cartridge and the address of the unoccupied slot. SCSI connection. When you are told to enter information. 6. Enter /dev/rmt/0m when prompted for the device name. Enter Element Inventory option. press Enter after following the instruction. 7. use the appropriate hardware manual to verify that the information is reasonable. 2. Enter /dev/rmt/0chng when prompted for the device name. Verify that the cartridge moved. Enter tapeutil. Bring up a shell prompt. You may stop the test here or continue to perform a more complete test. 5. When the utility displays information. 13. The procedure assumes that your device is attached at /dev/rmt/0m. 7. 3. This concludes a very basic test of the device. Enter Move Medium option. Enter 2 (Close a Device). 14. 1. 12. Bring up a shell prompt. 10. 6. Verifying Proper Attachment of Your Devices 307 . Bring up a shell prompt. Enter mtlib -l L3494 -qI 3. 1. The procedure assumes that your device is defined in /etc/ibmatl.conf as L3494.Verifying Proper Attachment of Your Devices 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to an HP-UX system.HP-UX . Enter mtlib -l L3494 -qL Appendix B. 2. 2. SCSI connection. This concludes a very basic test of the device. follow the ″Medium Changer Device Attachment Test″ in the next section to mount a writable scratch cartridge. Enter IBMtapeutil. 2. 4. 308 IBM Tape Device Drivers Installation and User’s Guide . use the appropriate hardware manual to verify that the information is reasonable. Tape Device Attachment Test The following procedure tests the attachment of a tape device to a Linux system. Enter 1 (Open a Device). 6. Enter 1 (Read/Write).. message is displayed or when you are told to enter information. Press the Enter key three times to accept the defaults and run the test. or. When the Hit<Enter>to Continue. 13. You also need a cartridge in at least one of the slots. and the device driver. 9. Enter Q (Quit Program). Open a Linux window. Enter 28 (Read and Write Tests). When the utility displays information. Enter IBMtapeutil. The procedure assumes that your device is attached at /dev/IBMchanger0. 5.. press Enter after following the instructions.. use the appropriate hardware manual to verify that the information is reasonable. message is displayed or when you are told to enter information. Enter /dev/IBMtape0 when prompted for the device name.. 7. Enter 20 (Rewind). When the Hit <Enter> to Continue . Enter 4 (Test Unit Ready) until no error occurs. 12. mount a writable scratch cartridge manually into the driver. 3. press Enter after following the instruction. 10. Enter 3 (Inquiry). A menu is displayed. A menu is displayed. Enter 2 (Close a Device). if your device has an autoloader attached. Enter 38 (Unload Tape). The procedure assumes that your device is attached at /dev/IBMtape0 and that there is no cartridge in the drive. Specify 0 when prompted for an inquiry page. When the utility displays information.Linux . 1. You may stop the test here or continue to perform a more complete test as follows: 8. Medium Changer Device Attachment Test The following procedure tests the attachment of a medium changer device to a Linux system. 11. 1. If you want to perform a more complete test. Open a Linux window. Enter 1 (Read/Write).Verifying Proper Attachment of Your Devices Linux System Issue the following command to verify if your host system has recognized all the attached IBM tape and medium changer devices after you installed the lin_tape device driver: cat /proc/scsi/scsi You can follow the instructions below to test the attachment. 14. The procedure assumes that your device is defined in /etc/ibmatl. Enter 62 (Element Inventory). Verifying Proper Attachment of Your Devices 309 . 12. Enter 64 (Move Medium). Enter 1 (Open a Device). 2. 13. then supply the address of the cartridge. 4. Enter 2 (Close a Device). Verify that the cartridge moved. select the element ID of an unoccupied slot.Verifying Proper Attachment of Your Devices 3. Specify 0 when prompted for an inquiry page. 10. Enter mtlib -l L3494 -qL Appendix B. You may stop the test here or continue to perform a more complete test as follows: Enter 4 (Test Unit Ready). SCSI connection. Enter 62 (Element Inventory). Enter Q (Quit Program). Bring up a shell prompt. 9. scratch cartridge and determine its element ID. 1. 11. Enter /dev/IBMchanger0 when prompted for the device name.conf as L3494. 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Linux system. 6. Enter 60 (Element Information). Enter mtlib -l L3494 -ql 3. and the device driver. 8. select a writable. From the output of the previous step. 5. followed by the address of the unoccupied slot. Also.Linux . Verify that the inventory was updated correctly. 7. This concludes a very basic test of the device. Enter 3 (Inquiry). Enter 1 (Open a device). Enter 1 (Open a Device). scratch cartridge and determine its element ID. Bring up a shell prompt. then supply the address of the cartridge and the address of the unoccupied slot. press Enter after following the instruction. 310 IBM Tape Device Drivers Installation and User’s Guide . Autochanger Device Attachment Test The following procedure tests the attachment of an autochanger device to a Sun Solaris system. Enter Q (Quit Program). 10.Solaris . 3. Verify that the cartridge moved. 5. Enter tapeutil. Enter /dev/rmt/0smc when prompted for the device name. 3. 12. When you are told to enter information. use the appropriate hardware manual to verify that the information is reasonable. D (Device Info). A menu is displayed. You may stop the test here or continue to perform a more complete test. When the utility displays information. 5. When you are told to enter information. Enter 6 (Test Unit Ready) until no error occurs. use the appropriate hardware manual to verify that the information is reasonable. Enter 2 (Close a Device). 13. Enter 17 (Element Inventory). Enter 14 (Move Medium). 11. You also need a cartridge in at least one of the slots. 8. press Enter after following the instruction.Verifying Proper Attachment of Your Devices Solaris System Tape Device Attachment Test The following procedure tests the attachment of a tape device to a Sun Solaris system. Enter 1 (Read/Write). 2. 6. When the utility displays information. 1. 7. 7. 4. 10 (Inquiry). 15. Enter D (Device Info). SCSI connection. Enter tapeutil. 6. 8. 14. Verify that the inventory was updated properly. A menu is displayed. From the output in the previous step. Enter /dev/rmt/0st when prompted for the device name. 1. select the element ID of an unoccupied slot. Enter Enter Enter Enter 1 (Read/Write). This concludes a very basic test of the device. and the device driver. 4. The procedure assumes that your device is attached at /dev/rmt/0smc and that the ACF is in Random mode. select a writable. 9. Enter 5 (Inquiry). Enter 17 (Element Inventory). Q to quit tapeutil. Bring up a shell prompt. Also. 2. The procedure assumes that your device is attached at /dev/rmt/0st. Verifying Proper Attachment of Your Devices 311 . Enter mtlib -l L3494 -qI 3.Verifying Proper Attachment of Your Devices 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Sun Solaris system. 1. Bring up a shell prompt. Enter mtlib -l L3494 -qL Appendix B. 2.Solaris .conf as L3494. The procedure assumes that your device is defined in /etc/ibmatl. Enter 21 (close). The procedure assumes that your device is attached at tape0 and that there is no cartridge in the drive. 10. 14. 12.Windows NT Only” on page 312 to mount a writable scratch cartridge in the drive. Select 1 (Manual test). 11.0. Enter 49 (inquiry).Windows NT Only The following procedure tests the attachment of an autochanger device to a Windows NT system. 1. Enter 99 (return to main menu).0. You also need a cartridge in at least one of the slots. 3. Enter 33 (unload). 15. Each time you are prompted with a Drive=0. 4. Enter 20 (open). All devices detected by adapters (that were attached and powered-On at system start time) should be displayed. Enter ntutil. and the device driver. select the element ID of a drive rather than the unoccupied slot ID. The procedure assumes that your device is attached at lb1.1 and that the tape device is attached at tape0. Autochanger Device Attachment Test . When the message Return to continue: message is displayed or when you are told to enter information. 9. use the instructions in “Autochanger Device Attachment Test . Enter 87 (Read/Write Test). adapter connection. mount a writable scratch cartridge manually into the drive. When the utility displays information. For Windows NT users. press Enter after following the instruction. 2. 6. Enter 1 (Read/Write). reply with 0 (zero).Windows . Enter 39 (test unit ready) until no error occurs. If you want to perform a more complete test and your device does not have an autoloader. Note: See Microsoft Windows System for information on the ntutil application. 312 IBM Tape Device Drivers Installation and User’s Guide . Library=1 prompt. Enter 50 (poll registered devices). 8. 13. 5. This is accomplished by following the steps in the procedure. Enter 31 (rewind). except that in steps 11 and 12. Library=1 prompt. Enter 9 (Exit ntutil). Open a Windows command shell window. Reply with 0 (zero) to the Drive=0.Verifying Proper Attachment of Your Devices Microsoft Windows System Tape Device Attachment Test The following procedure tests the attachment of a tape device to a Microsoft Windows system. if you want to perform a more complete test and your device has an autoloader. Enter Y in response to the confirmation message. You may stop the test here or continue to perform a more complete test. use the appropriate hardware manual to verify that the information is reasonable. 7. This step concludes a very basic test of the device. The procedure assumes that your device is defined in c:\winnt\ibmatl. 4. 7. 1. Verify that the inventory was updated properly. 17. 12. Also. 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Windows system. scratch cartridge and determine its element ID. You may stop the test here or continue to perform a more complete test. Enter 11 (ioctl move medium). adapter connection. Library=1 prompt.Verifying Proper Attachment of Your Devices When the Return to continue: message is displayed or when you are told to enter information. Enter 10 (ioctl return library inventory). 14. Note: See Microsoft Windows System for information on the ntutil application.0. All devices detected by adapters (that were attached and powered-On at system start time) should be displayed. Select 1 (Manual test).conf as L3494. This step concludes a very basic test of the device. press Enter after following the instruction. Enter 50 (poll registered devices). Enter 49 (inquiry). 2. use the appropriate hardware manual to verify that the information is reasonable. 6. select the element ID of an unoccupied slot. 9. Enter ntutil. 8. Enter 12 (ioctl initialize element status). select a writable. 13. Verify that the cartridge moved. 11. Enter 21 (close). When the utility displays information. 5. Enter 9 (Exit ntutil). Verifying Proper Attachment of Your Devices 313 . 15. From the output in the previous step. 2.0. 1. Enter 39 (test unit ready) until no error occurs. 3. Enter 8 (Library Mode). Enter 20 (open).Windows .1 in the list of found devices. Enter mtlib -l L3494 -qI 3. You should see lb1. Enter 99 (return to main menu). reply with 1 (zero). Open a Windows command shell window. then supply the address of the cartridge and the address of the unoccupied slot. 10. Library=1 prompt. Enter 1 (Read/Write). and the device driver. Each time you are prompted with a Drive=0. Enter 10 (ioctl return library inventory). Open a Windows NT command shell window. 16. Enter mtlib -l L3494 -qL Appendix B. Reply with 0 (zero) to the Drive=0. Enter /sbin/scu-f/dev/ntape/tape0 (Open the Tape Device). 3. or use the su command to gain superuser privileges. 5. and the device driver. 6. Bring up a shell prompt. Enter quit to quit scu. Enter /sbin/scu -f /dev/changer/mc0 (Open the medium changer device). 314 IBM Tape Device Drivers Installation and User’s Guide . Medium Changer Device Attachment Test The following procedure tests the attachment of a medium changer device to a Tru64 system. The procedure assumes that your device is attached at /dev/ntape/tape0. When the utility displays information. Logon to the system as root. Logon to the system as root. You also need a cartridge in at least one of the slots.Tru64 . The procedure assumes that your device is attached at /dev/changer/mc0. 1. Enter tur (Test Unit Ready) Enter Show Inquiry (Inquiry data). 2. 9. When you are asked to enter information. Enter show element (Element Inventory) to verify that the inventory was updated properly. From the output in the previous step. 4. Enter show element (Element Inventory). scratch cartridge and determine its element address. When you are asked to enter information. Also select the element address of an unoccupied slot.Verifying Proper Attachment of Your Devices Tru64 System Tape Device Attachment Test The following procedure tests the attachment of a tape device to a Tru64 system. 4. This concludes a very basic test of the device. 2. When the utility displays information. Verify that the cartridge moved. SCSI connection. 10. or use the su command to gain superuser privileges. use the appropriate hardware manual to verify that the information is reasonable. Enter tur (Test Unit Ready) until no error occurs. press the Enter key after following the instructions. 3. 5. Enter quit (Quit scu). 7. Enter move medium source Source_address destination Destination_address to move the cartridge from the source element address to the destination element address. You may stop the test here or continue to perform a more complete test. Bring up a shell prompt. Enter show inquiry (Inquiry Data). 1. 8. 6. select a writable. press the Enter key after following the instructions. use the appropriate hardware manual to verify that the information is reasonable. Verifying Proper Attachment of Your Devices 315 .Tru64 . Enter mtlib -l L3494 -qI 3.Verifying Proper Attachment of Your Devices 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a Tru64 system.conf as L3494. Enter mtlib -l L3494 -qL Appendix B. 1. The procedure assumes that your device is defined in /etc/ibmatl. 2. Open a window. Enter mtlib -l L3494 -qI 3. Bring up a shell prompt.Verifying Proper Attachment of Your Devices SGI/IRIX System 3494 Enterprise Tape Library Attachment Test The following procedure tests the attachment of a 3494 Enterprise Tape Library to a SGI/IRIX system. The procedure assumes that your device is defined in /etc/ibmatl.SGI/IRIX . 1. Enter mtlib -l L3494 -qL 316 IBM Tape Device Drivers Installation and User’s Guide . 2.conf as L3494. and ready.” on page 255 or a operating system specific tapeutil command. then press Enter. The unit must be powered On. “IBM Tape Diagnostic Tool (ITDT). 7. Ensure that the tape drive is connected to a host system and that the tape device driver is powered-On and configured properly with no tape cartridge in the drive. 2007. a microcode load was installed and shipped with your device. 4. press F10 (Exit) to return to tapeutil. configured properly. When your tape device or library hardware was manufactured. Managing the Microcode on the IBM Tape Drive Microcode is computer software that is stored in nonvolatile storage on your tape device or library hardware. 2. If your device is connected to a host system that has device or library support. Specify the special file from where the microcode image is to be read and press F7 (Commit) to load the microcode onto the drive. 2009 317 . It controls the operation of your hardware. Select Microcode Load. For additional information. “Verifying Proper Attachment of Your Devices. Follow the instructions in Appendix B. Select the device special file identifier for the device on which to load the microcode. You can query the current level of microcode by issuing commands on the front panel of your hardware. Consult the appropriate hardware reference manual for specific instructions on querying your microcode level. They will provide you with updated microcode.Appendix C. 3. they may instruct you to install a newer level of microcode on your hardware. IBM service personnel will ask what level of microcode you have on your hardware. Enter 4 (Tape Drive Service Aids). 2. A menu is displayed. Open an AIX window. If they believe you need a new level of microcode. AIX System 1. © Copyright IBM Corp. you can also query the last four digits of the current level of microcode using software. If you are having trouble with your hardware. Enter Q (Quit Program).” on page 303 to ensure that the drive is configured properly and ready. refer to Chapter 10. 5. Enter tapeutil. The following instructions are a guide to install another version of microcode on a tape drive: 1. Follow the platform-specific instructions. When the loading is complete. 6. refer to the appropriate chapter in this document (based on the operating system/platform) for details on how to have the device ready. Change to the c:\mydata directory. 1. Enter tapeutil. Specify the file name from which the microcode image is to be read. then press the Enter key. 3. 2. Linux System This procedure assumes that the /dev/IBMtape0 tape device is being updated. Enter tapeutil. The name of the file containing the microcode must have the fmr extension. then press the Enter key. 3. 5. 4. Enter 1 (Open a Device). 8. 2. A menu is displayed. 4. Solaris System This procedure assumes that the /dev/rmt/0st tape device is being updated. 6. Bring up a shell prompt. 2. 1. Enter /dev/rmt/0st when prompted for the device name. Open a Windows command shell window. Specify the special file from where the microcode image is to be read. A menu is displayed. Enter 1 (Open a Device). Enter 1 (Open a Device). 6. 4. Enter /dev/IBMtape0 when prompted for the device name. Select 7 (Download Microcode). Select 1 (Manual test). 1. Enter ntutil. 1. Open a Linux window. Enter 1 (Read/Write). 7. Enter Q (Quit Program). Select Download Microcode option. 5. Enter IBMtapeutil. Bring up a shell prompt. Enter Q (Quit Program). Enter /dev/rmt/0m when prompted for the device name. 4. Specify the special file from where the microcode image is to be read. 3. 7. 8. Enter 1 (Read/Write). 3. Enter 1 (Read/Write). 318 IBM Tape Device Drivers Installation and User’s Guide . 2. 7.fmr and that the drive at tape0 is being updated.Managing Microcode on the IBM Tape Drive HP-UX System This procedure assumes that the /dev/rmt/0m device is being updated. 6. Enter Q (Quit Program). 8. Microsoft Windows System This procedure assumes that the new microcode is stored in c:\mydata\ d0i9_430. A menu is displayed. Select 72 (Load Ucode). 5. then press the Enter key. Bring up a shell prompt. It prompts you to enter a device filename. Tru64 System 1. Enter 2 (Update Microcode). 3. 2. then press the Enter key. 10. Enter 21 (close). 4. 6. 6 (test unit ready) until no error occurs. 8. 7. 12. Enter 3 (Quit). Enter /dev/device name when prompted. Enter 99 (return to main menu). Enter IBMrasutil. 82 (Update Code). Enter Enter Enter Enter Enter 20 (open). 11. Specify the special file from which the microcode image is to be read. Managing the Microcode on the IBM Tape Drive 319 . Appendix C. 1 (Read/Write). Enter 9 (Exit ntutil). d0i9_430. 5.Managing Microcode on the IBM Tape Drive 5. Note: See Microsoft Windows System for information on the ntutil application. 6. 9. Managing Microcode on the IBM Tape Drive 320 IBM Tape Device Drivers Installation and User’s Guide . Appendix D. The tape utility program also performs basic tape and medium changer operations. Note: The functions and capabilities of the tape utility program are now performed by the IBM Tape Diagnostic Tool (ITDT).See “Solaris System .See “Microsoft Windows System . Tape Utility Programs Installed with the device driver is a tape utility program.Tape Utility Program (tapeutil)” on page 357 ntutil .See “Linux System . that exercises or tests the functions of the tape device and the device driver.Utility Program (ntutil)” on page 366 © Copyright IBM Corp.See “HP-UX System .See “AIX System . 2009 321 . 2007. Table 32.Tape Utility Program (IBMtapeutil)” on page 345 tapeutil -f drive -o qmc -v .Tape Utility Program (tapeutil)” on page 335 IBMtapeutil –f drive inquiry . ITDT does not support the Tru64 operating system.Tape Utility Program (tapeutil)” on page 322 tapeutil -f drive -o qmc -v . Tape Utility Program Documentation Operating System AIX HP-UX Linux Solaris Microsoft Windows Tape Utility Program Command and Location tapeutil . AIX - Tape Utility Program (tapeutil) AIX System - Tape Utility Program (tapeutil) Installed with the device driver is a tape utility program, tapeutil, that exercises or tests the functions of the tape device and the device driver. It also performs basic tape and medium changer operations. The tape utility program provides two versions (the interactive interface and the AIX command-line interface) with syntax similar to the tctl and mt commands. The C source code for the tapeutil.c program can be found in the /usr/lpp/Atape/samples directory. The program contains a sample of the interface to the device driver and the ioctl commands supported. Note: This utility program does not support the data path for the IBM 7331, 7336, and 7337 library devices. It can be used only for the medium changer functions on the IBM 7331, 7336, and 7337. The data path is supported by the AIX base device driver and utilities, such as tctl and mt. Interactive Interface The interactive interface of the tape utility program can be called from the AIX command-line using the tapeutil command. A list of general subcommands, medium changer subcommands, and tape subcommands is displayed. You must open a device before using these commands and operations (except for the tape drive service aids). To open a device: 1. Select Open a Device from General Commands. 2. Enter the name of the device special file. Use any special file that exists for the device, for example, /dev/rmt0, /dev/rmt0.1, /dev/rmt1.smc, or /dev/smc0. 3. Enter the Read/Write, Read Only, Write Only, or Append mode to open a device. These modes apply only to the tape devices. After you open a device, select a command using the appropriate number for the command from the interface. Some commands require additional information after they are selected. If an error occurs, then the error number, the error text, and the device sense data (if applicable) are displayed. Command-Line Interface The command-line interface of the tapeutil has a syntax similar to the AIX tctl and mt commands and provides the same basic tape commands. The program also supports tape device, device driver, SCSI, and medium changer subcommands that use the additional functions of the tape device and device driver. Call the tapeutil command from the AIX command-line or from within a shell script. If you enter the tapeutil command without any arguments, the interactive interface is called. The syntax for the command-line interface of the tape utility program is: tapeutil -f Device Subcommand [Subcommand ...] Notes: 1. Device is the name of the device special file (for example, /dev/rmt0). 2. Subcommand is any valid command for the device. 322 IBM Tape Device Drivers Installation and User’s Guide AIX - Tape Utility Program (tapeutil) Multiple subcommands can be combined in a single command to perform more than one operation. The subcommands are processed one at a time in the order specified on the command-line. For a list of subcommands and syntax, enter the tapeutil ? command on the AIX command line. General Subcommands The following general subcommands are available for the tape and medium changer devices. checkpath: This subcommand issues a SCSI Inquiry command to the device on all configured paths to determine the status of each path and sets the path to enabled if successful or disabled if unsuccessful. The status of the primary and alternate path is displayed when the subcommand completes. The output is the same as the qrypath and resetpath subcommands. If more than two paths are configured for the device, run the pathsubcommand also. Examples: # Check the status of paths and display results tapeutil -f/dev/rmt0 checkpath # Check the status of more than 2 paths and display results tapeutil -f/dev/rmt0 checkpath path devinfo: This subcommand displays the device information returned from the IOCINFO ioctl command. disable path Primary|Alternate: This subcommand is used to disable the device driver from using either the primary SCSI path or the alternate SCSI path to a device. This subcommand is valid only if the device has both a primary and alternate path enabled. fuser: This subcommand is similar to the AIX fusercommand. If the device special file is currently open, the process ID is displayed. Otherwise, it indicates the device special file is not currently open. inquiry [Page]: This subcommand issues the SCSI Inquiry command to the device for either standard inquiry data, with no page parameter, or for specified page data, and displays the inquiry data. The page parameter must be specified as a hexidecimal value. Examples: # Get standard inquiry data tapeutil -f/dev/rmt0 inquiry # get inquiry page x'83' tapeutil -f/dev/rmt0 inquiry 83 kill: This subcommand kills a currently active process on a device. This subcommand should be used when the standard Ctrl-C or AIX kill command methods cannot terminate the process. For example: # Kill any active process on rmt0 tapeutil -f/dev/rmt0 kill logpage Page: This subcommand issues the SCSI Log Sense command to the device for the specified page and displays the log sense data. The page parameter must be specified as a hexidecimal value. For example: # Get log page x'31' tapeutil -f/dev/rmt0 logpage 31 Appendix D. Tape Utility Programs 323 AIX - Tape Utility Program (tapeutil) loop [Count]: This subcommand loops all subsequent subcommands continuously or a number of times if the Count parameter is specified. Also refer to the sleep subcommand. Examples: # Continuously loop inquiry commands with a 2-second delay tapeutil -f/dev/rmt0 loop inquiry sleep 2 # Issue 3 Test Unit Ready commands tapeutil -f/dev/rmt0 loop 3 tur modepage Page: This subcommand issues the SCSI Mode Sense command to the device for the specified page and displays the mode sense data. The page parameter must be specified as a hexidecimal value. For example: # Get mode page x'1D' tapeutil -f/dev/rmt0 modepage 1d Note: Issuing this subcommand for page x’3F’ all pages is not supported. passthru: This subcommand opens the device special file using the SC_PASSTHRU mode. This mode bypasses normal open/close processing and no SCSI commands are issued to the device during open or close. path: This subcommand displays information about the device 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. The output from this subcommand is similar to the qrypath subcommand, except more than one alternate path is supported by this subcommand. For example: # Display path information tapeutil -f/dev/rmt0 path preempt: This subcommand will clear all persistent reservations and keys on the device registered from the same host or other hosts. print ″Text″: This subcommand prints the associated text to standard output. It can be used at any time to display the progress of the subcommands. For example: # Set volume id, erase current tape and backup myfile.tar tapeutil -f/dev/rmt0 volid "My Volume" \ rewind \ erase \ print "Writing myfile.tar" \ write -s myfile.tar qrypath: This subcommand displays information about the device and SCSI paths, such as logical parent, SCSI IDs, and status of the SCSI paths. release: This subcommand explicitly releases a device and makes it available for other hosts. Refer to “Reserve and Release Commands” on page 333 for more information. reqsense: This subcommand issues the SCSI Request Sense command to the device and displays the sense data. reserve: This subcommand explicitly reserves a device. Refer to “Reserve and Release Commands” on page 333 for more information. reset: This subcommand opens the device special file using SC_FORCED_OPEN mode and causes a bus device reset to be sent to the device. 324 IBM Tape Device Drivers Installation and User’s Guide AIX - Tape Utility Program (tapeutil) resetpath: This subcommand is used to enable the device driver to use both the primary SCSI path or the alternate SCSI path after one path has been disabled with the disablepath subcommand. sleep Seconds: This subcommand causes the tapeutil program to sleep the specified seconds before executing the next subcommand. Also refer to the loop subcommand. Examples: # Issue 2 inquiry commands with a 1-second delay between commands tapeutil -f/dev/rmt0 inquiry sleep 1 inquiry # Loop inquiry commands with a 2-second delay between commands tapeutil -f/dev/rmt0 loop inquiry sleep 2 tur: This subcommand issues the SCSI Test Unit Ready command to the device. vpd: This subcommand obtains the vital product data (VPD) from a SCSI tape device. It opens the device special file in SC_DIAGNOSTIC mode and uses the SCSI pass-through ioctl command to obtain the inquiry data from the device. Medium Changer Subcommands The following medium changer subcommands are available for the integrated and independent medium changer devices. allow: This subcommand allows medium removal by an operator. It is normally used after the prevent subcommand to restore the device to the default state. audit [Address[Count]]: This subcommand with no parameters issues the SCSI Initialize Element Status command to the device. Using the optional parameters Address and Count issues the SCSI Initialize Element Status With Range command to the device. 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. For example: # Initialize all elements tapeutil -f/dev/smc0 audit # Initialize element 32 tapeutil -f/dev/smc0 audit 32 # Initialize elements 36 to 40 tapeutil -f/dev/smc0 audit 36 5 cartridgelocation [Slot[Count]]: This subcommand with no parameters issues the SCSI Read Element Status command to the device to report all slots with the cartridge location information. Using the optional parameters Slot and Count issues the SCSI Read Element Status to the device 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. For example: # Return cartridge locations for all slot elements tapeutil -f/dev/smc0 cartridgelocation # Return cartridge location for slot 1024 tapeutil -f/dev/smc0 cartidgelocation 1024 # Return cartridge locations for starting slot 1024 and 10 slots tapeutil -f/dev/smc0 cartridgelocation 1024 10 Appendix D. Tape Utility Programs 325 AIX - Tape Utility Program (tapeutil) devids: This subcommand issues the SCSI Read Element Status command to the device with the read device id option for all drive elements and displays the element status information, which includes the device id field. elementinfo: This subcommand displays the information returned from the SMCIOC_ELEMENT_INFO ioctl command that contains the number and address of each element type. exchange ″Source″ ″Dest1″ ″Dest2″: This subcommand issues the SCSI Exchange Medium command to the device using the Source, Dest1, and Dest2 addresses specified. This command performs the equivalent function of two Move Medium commands. The first moves the cartridge from the element address specified by the Dest1 parameter to the element address specified by the Dest2 parameter. The second moves the cartridge from the element address specified by the source parameter to the element address specified by the Dest1 parameter. For example: # Exchange cartridge in slot 34 with cartridge in drive address 16 # and return that cartridge to slot 40 (drive must be unloaded first) tapeutil -f/dev/smc0 exchange 34 16 40 # Use move medium commands to perform exchange tapeutil -f/dev/smc0 move 16 40 move 34 16 inventory [-i | -v Volid]: 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 element status information is returned. If the optional -v parameter is used, then only the element status information for the specified Volid if found is returned. mount [Slot]: This subcommand mounts a tape from the specified slot into the drive or from the first full slot into the drive if the slot is omitted. For example: # Mount cartridge from slot 3 tapeutil -f/dev/smc0 mount 3 # Mount cartridge from first full slot tapeutil -f/dev/smc0 mount move ″Source″ ″Destination″: This subcommand issues the SCSI Move Medium command using the source and destination addresses specified. The element addresses can be obtained using the elementinfo subcommand. For example: # Get slot and drive addresses tapeutil -f/dev/smc0 elementinfo # Move cartridge in slot 20 to drive at address 16 tapeutil -f/dev/smc0 move 20 16 position ″Destination″: This subcommand issues the SCSI Position to Element command using the destination specified. For example: # Position to slot at address 20 tapeutil -f/dev/smc0 position 20 prevent: This subcommand prevents medium removal by an operator until the allow subcommand is issued or the device is reset. unmount [Slot]: This subcommand moves a tape from the drive to the specified slot or the first empty one if the slot is omitted. The tape is rewound and unloaded automatically from the drive first when this command is issued to the tape device special file. For example: 326 IBM Tape Device Drivers Installation and User’s Guide AIX - Tape Utility Program (tapeutil) # Move tape from drive to slot 4 (tape is already unloaded) tapeutil -f/dev/rmt0.smc unmount 4 # Unload tape and move to the first empty slot tapeutil -f/dev/rmt0 unmount Tape Subcommands The following tape subcommands are available for the tape devices. allow: This subcommand issues the SCSI Prevent Allow Medium Removal command to the device to allow medium removal by an operator. It is normally used after the prevent subcommand to restore the device to the default state. append: This subcommand opens the device in append mode and allows the appending of data to the end of the current tape. The subcommand can be used with a No Rewind on Close special file to set the tape position after the last file that was written. # Append myfile.tar to the end of tape using dd subcommand tapeutil -f/dev/rmt0.1 append dd if=myfile.tar of=dev/rmt0 autoload: This subcommand turns on the autoload feature only for subsequent subcommands. For example: # Backup large.tar (requires multiple tapes) using autoload feature tapeutil -f/dev/rmt0 autoload write -s large.tar bsf [Count]: This subcommand backward spaces the filemarks. An optional count can be specified. The default is 1. bsr [Count]: This subcommand backward spaces the records. An optional count can be specified. The default is 1. cancelerase: This subcommand cancels an erase immediate command in progress. chgpart Number [Blockid]: This subcommand changes the current active tape partition to a new partition specified by Number. Optionally, a Blockid can also be specified. If Blockid is omitted, the tape is positioned at the start of the new partition, otherwise, the tape is positioned at the Blockid specified. For example: # Change to beginning of partition 16 tapeutil -f/dev/rmt0 chgpart 16 # Change to partition 0, block number 25 tapeutil -f/dev/rmt0 chgpart 0 25 compress and nocompress: These subcommands turn On and Off compression only for subsequent subcommands. density: This subcommand issues the SCSI Report Density command for all supported media and for the current media loaded in the drive, and displays the results. If the drive is not loaded, the current media density is not reported and a Drive Not Ready error is returned. display ″Message″: This subcommand displays a message on the display panel of the tape device. 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. For example: # Display "Test 1" and "Running" messages tapeutil -f/dev/rmt0 display "Test 1 Running" Appendix D. Tape Utility Programs 327 AIX - Tape Utility Program (tapeutil) eof [Count] and weof [Count]: These subcommands write the filemarks. An optional count can be specified. The default is 1. erase: This subcommand erases the tape. erg: This subcommand performs an erase record gap operation. fsf [Count]: This subcommand forward spaces the filemarks. An optional count can be specified. The default is 1. fsr [Count]: This subcommand forward spaces the records. An optional count can be specified. The default is 1. idp: This subcommand creates an IDP partition on tape. For example: # Create IDP partition tapeutil -f/dev/rmt0 idp list: This subcommand displays the content of a tape. The output lists filemarks and the size of each record found on the tape until the end of data is reached. The output generated from this subcommand can be large depending on the amount of data on the tape and should usually be directed to a file. For example: # List tape contents to file tapeutil -f/dev/rmt0 list > tape.list load: This subcommand issues the SCSI Load command to load the next tape. logsense: This subcommand issues the STIOC_LOG_SENSE ioctl command and displays the data. If volume logging is active, then the log sense data is also saved in the log file. mtdevice: This subcommand issues the MTDEVICE ioctl command and displays the library sequence number. Refer to the MTLIB command -D flag in Figure 37 on page 195. noautoload: This subcommand turns off the autoload feature only for subsequent subcommands. For example: # Make sure autoload feature is off before writing file to tape tapeutil -f/dev/rmt0 noautoload write -s myfile.tar nosili: This subcommand turns off the Suppress Incorrect Length Indication (SILI) bit in variable length SCSI Read commands for all subsequent subcommands, such as rtest, rwtest, and read. offline, rewoffl, and unload: These subcommands rewind and unload the tape. parms and status: These subcommands issue the STIOCQRYP ioctl command and display the current tape drive, media, and device driver parameters. prevent: This subcommand issues the SCSI Prevent Allow Medium Removal command to the device to prevent medium removal by an operator until the allow subcommand is issued or the device is reset. qrypart: This subcommand queries and displays tape partitioning information. 328 IBM Tape Device Drivers Installation and User’s Guide AIX - Tape Utility Program (tapeutil) qrypos: This subcommand issues the STIOCQRYPOS ioctl command for the logical and physical tape positions and displays the data. In addition, the current tape position is saved and can be restored using a subsequent setpos subcommand. For example: # Append myfile.tar to the end of tape and then read back tapeutil -f/dev/rmt0.1 append \ qrypos \ write -s myfile.tar \ setpos \ read -d temp.tar # Verify myfile.tar was written correctly diff myfile.tar temp.tar read -d Destination [-c Count]: 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. For example: # Restore myfile.tar from tape tapeutil -f/dev/rmt0 read -d myfile.tar # Read 3 records from the tape into myfile tapeutil -f/dev/rmt0 read -d myfile -c3 rewind and retension: These subcommands rewind the tape. rtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a read test by reading a random data pattern from the tape and verifying that it matches the written data. The rtest subcommand can be used after the wtest subcommand to verify the data. An optional block size, count, and repetition can be specified with the -b, -c, and -r flags, respectively. 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 (variable), then the count 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. For example: # R/W test using 256 KB blocks, 5 megabytes per write, 100 times tapeutil -f/dev/rmt0 rewind \ wtest -b 262144 -c 20 -r 100 \ rewind \ rtest -b 262144 -c 20 -r 100 rwtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a read and write test by writing a random data pattern on the tape, reading it, and verifying that it matches the written data. An optional block size, count, and repetition can be specified with the -b, -c, and -r flags, respectively. 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 (variable), 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. For example: # R/W test using 256 KB blocks, 5 megabytes per write, 10 times tapeutil -f/dev/rmt0 rwtest -b 262144 -c 20 -r 10 sdp Number: This subcommand creates the specified Number of SDP partitions on tape. For example: Appendix D. Tape Utility Programs 329 count. 5 megabytes per write. setpos [Blockid]: This subcommand issues the SCSI Locate command to the device to set the tape position. the tape position is set to the last position saved using the qrypos subcommand. The device driver stores up to three dump files in this 330 IBM Tape Device Drivers Installation and User’s Guide . if the Blockid parameter is omitted. If the block size is zero (variable). dump [Filename]: This subcommand forces a dump on the tape device and stores the dump in the specified Filename or.tar # Set tape position to block 32 and leave positioned on close tapeutil -f/dev/rmt0.tar # Verify myfile. The default is a block size of 10240.tar temp.tar to tape tapeutil -f/dev/rmt0 write -s myfile. sync: This subcommand synchronizes or flushes the tape buffers to tape. rwtest. such as rtest.tar \ setpos \ read -d temp.tar wtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a write test by writing a random data pattern on the tape.1 append \ qrypos \ write -s myfile. in the system /var/adm/ras directory. respectively. The rtest subcommand can be used after the wtest subcommand to verify the data that was written. then the count specifies the number of bytes to write on each repetition. write -s Source: This subcommand writes the source file specified with the -s flag on the tape. a count of 20 blocks. For example: # Backup myfile. if Filename is omitted. and -r flags. If the optional Blockid parameter is specified.tar was written correctly diff myfile. For example: # R/W test using 256 KB blocks. Otherwise.1 setpos x20 sili: This subcommand turns on the SILI bit in variable length SCSI Read commands for all subsequent subcommands. and repetition can be specified with the -b. If the block size is fixed. then the count specifies the number of blocks to write on each repetition. Refer to “Volume ID for Logging” on page 32 and “Volume ID for Logging” on page 334.tar to the end of tape and then read back tapeutil -f/dev/rmt0.1 setpos 32 # Set tape position to block 32 and leave positioned on close tapeutil -f/dev/rmt0. the tape position is set to the Blockid. -c. and a repetition of 1. with a leading x. volid ″Name″: This subcommand sets the volume ID for logging. An optional block size. The Blockid can be specified in decimal or in hexidecimal.AIX . 100 times tapeutil -f/dev/rmt0 rewind \ wtest -b 262144 -c 20 -r 100 \ rewind \ rtest -b 262144 -c 20 -r 100 Service Aid Subcommands The following service aid subcommands are available for the tape devices.Tape Utility Program (tapeutil) # Create 32 SDP partitions and then query partitioning tapeutil -f/dev/rmt0 sdp 32 qrypart seod: This subcommand spaces to the end of data on the tape. For example: # Append myfile. and read. The first dump file is named Atape. It performs the same function as the dump subcommand above without forcing a dump first. Configuration Parameters The configuration parameters can be queried using either the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands or using the command-line interface and issuing the parms or status subcommand. After a third dump file is created. the ACF mode can be queried using either the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands or using the command-line interface and issuing the parms or status subcommand. such as /dev/rfd0. displays it to standard out. forcedump: This subcommand issues a Send Diagnostic SCSI command to force a dump on the tape drive. where: x is the device number (for example. Tape Utility Programs 331 .dump1.ucode Automatic Cartridge Facility Mode If the device is the IBM TotalStorage Enterprise Tape System 3590 with an Automatic Cartridge Facility (ACF) or the IBM Magstar MP 3570 library. The configuration parameters can be changed temporarily using the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands. Block Size and SCSI Transfer Size The minimum and maximum block sizes for the tape device and the maximum SCSI transfer size can be queried using either the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands or using the command-line interface and issuing the parms or status subcommand. rmt0).rmtx. Appendix D. ucode ″Name″: This subcommand downloads microcode to the device. The Name parameter can specify a diskette drive. the next dump starts at dump1 again and overlays the previous dump file. respectively. The second and third dump files are named dump2 and dump3. readbufferid ″id″ [Filename]: This subcommand reads a specific buffer id from the device and stores the data in the specified Filename or if Filename is omitted. resetdrive: This subcommand issues a Send Diagnostic SCSI command to reset the device. or a microcode file on the RISC machine. readdump [Filename]: This subcommand reads and stores a tape drive dump in the specified filename or. The tape is created using the loaded functional microcode in the device when the command is issued. The dump can be read using the readdump subcommand.AIX .Tape Utility Program (tapeutil) directory. in the system /var/adm/ras directory. For example: # download microcode from diskette tapeutil -f/dev/rmt0 ucode /dev/rfd0 # download microcode from RISC file tapeutil -f/dev/rmt0 ucode /etc/microcode/device. if filename is omitted. fmrtape: This subcommand issues a Send Diagnostic SCSI command to the device to create a field microcode replacement (FMR) cartridge tape. . SCSI IDs. Encryption settings: Drive Encryption Capable.. Querying Tape Drive Encryption Settings There is a tape diagnostic and utility function available for encryption to query tape drive encryption settings.. The current tape drive encryption settings can be queried using the tapeutil menu option 38 “Get Drive Encryption Settings” or the command line tapeutil –f/dev/name encryption. such as the logical name of the device..AIX .. you can easily determine how many physical devices are configured with path failover support. System Encryption State. Following is an example of a correct tape drive configuration with wrt_encryption set to on... >tapeutil -f/dev/rmt1 encryption Getting drive encryption settings. then the tape drive “Encryption State” is Off. and how many paths are configured for the device. If the wrt_encryption attribute is set to no.. the current enabled status.. All other logical devices configured after the first device are labeled as alternate devices....... Run the following command: lsdev -Cc tape | grep P For example. Yes Encryption Method.Tape Utility Program (tapeutil) Note: The changes are effective only while the current device is open.. All configuration parameters are reset to their current default values when the device is closed. Querying Primary and Alternate Path Configurations You can display the primary and alternate path configuration for all devices with the lsdev command. but the first device configured is labeled the primary device...... There can be two or more logical devices configured for a single physical device.. Capacity Scaling The capacity scaling of the current tape can be queried or set using the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands. On 332 IBM Tape Device Drivers Installation and User’s Guide ... To see this. You can display the primary and alternate path configuration for any device by running: tapeutil -f/dev/smcx path (where smcx is the logical name of any device) This command shows specific information for the primary path and all alternate paths. Logical Write Protect The logical write protect of the current tape can be queried or set using the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands... run the lsdev -Cc tape command and look at the location field in the data. .Tape Utility Program (tapeutil)” on page 322 for information on the tapeutil application. In these cases. In other situations.. Test complete. This is done by explicitly reserving the device. Use SMIT to set Appendix D.Tape Utility Program (tapeutil) Reserve and Release Commands The device driver reserves the device automatically on the open call and releases the device on the close call. Perform the following recommended problem determination steps to resolve the problem: 1. the reservation must be retained between the close call and the next open call.. The first test checks the server configuration defined in the ibmekm.conf file server entries and test tape drive to server connectivity operations. After all work is completed on the device. completion code 0 > If the first server test fails with one of the following errors. then the remaining tests are not run. The third test runs an enhanced diagnostic that checks a key operation between the tape drive and server then reports success or fail. Test complete. run tar. /dev/rmt0 . This test can be run using the tapeutil menu option 40 “Data Encryption Test” or the command line “tapeutil –f/dev/name ekmtest”.conf file and then communication to the configured servers. However.System encryption is not configured for the tape drive in the device driver. For example. Testing Data Encryption Configuration and Connectivity There is a tapeutil command available to validate the ibmekm.. completion code 0 Running full drive to server encryption test. The second test runs a basic diagnostic that checks the tape drive to server communication and reports success or fail.. servers available 2 Running basic drive to server encryption test. even if the device is deconfigured and reconfigured. Test complete.. there may be situations when the reserve should be maintained after the close call.. “Invalid argument or Operation not supported on device” . a device is shared by multiple initiators or hosts. some backup programs such as tar can open and close the device multiple times. For example: # Reserve device. and then release device tapeutil -f/dev/rmt0 reserve tar ... Following is an example of a successful test: > tapeutil –f /dev/rmt2 ekmtest Testing server configuration and connections. This test reports back the number of servers available. Tape Utility Programs 333 . tapeutil -f/dev/rmt0 release After the reserve command is used. This prevents other applications and hosts from accessing the device. the device driver retains the reservation until a release command is issued.. A device can be reserved and released explicitly using either the interactive interface of the tape utility program and selecting Reserve or Release under General Commands or using the command-line interface and issuing the reserve and release subcommands.AIX . the user will explicitly release the device. Note: See “AIX System . AIX .Tape Utility Program (tapeutil) system encryption to “yes” for the tape drive. 3. and set volume id tapeutil -f /dev/rmt0 unload load volid "VOLSER001" 334 IBM Tape Device Drivers Installation and User’s Guide . For example: # Unload tape.Either the ibmekm. Volume ID for Logging The volume ID used in the log entry when volume logging is active can be set using either the interactive interface of the tape utility program and selecting Query/Set Parameters under Tape Commands or using the command-line interface and issuing the volid subcommand. Check all servers configured in the ibmekm.conf file are currently running on the server IP address and configured correctly.conf file is missing or is invalid. If system encryption can not be set then the tape drive is not encryption capable. load next tape. 2. Check and correct.conf file are not available. “Network is down” – All configured servers in the ibmekm. “Can’t assign requested address” . After observing the preview output.7. Command Sequence Information Take note of the following facts about the command sequences described in this section: v In some of the examples. If you are using the ATDD version 3.Tape Utility Program (tapeutil) This chapter describes how to install.1 or later.x. check the associated log file.hpux.x v HP PCI Bus . Analysis. “Install tapeutil” on page 336 Copy the Software to the Software Depot Copy the software from its location to the Software Depot. # swcopy -p -s /tapeutil_location/tapeutil. reissue the command without the -p flag to perform the actual operation.x.versions of this program are identified by levels tapeutil. The steps are typically Selection. Each step may produce useful information and error messages. uninstall and use the IBM HP-UX Tape Utility Program.x. “Review the tapeutil README File” on page 336 3.x.2 or later.0. v All the software distributor commands (for example.HP-UX 10. Product Requirements The following hardware and software components are required and supported by IBM and are necessary for implementation of the tapeutil.x.0. use tapeutil.hpux. If you run into unexpected results during the installation.4. Hardware Requirements Refer to “Hardware Requirements” on page 54.x tapeutil (preview option) # swcopy -s /tapeutil_location/tapeutil.4. Tape Utility Programs 335 .hpux.Tape Utility Program (tapeutil) HP-UX System .x. so it is a good idea to carefully observe the results of the installation process as it occurs.3.7. on HP-UX 11.x. filenames given on the command-line must be referenced with an absolute path. use tapeutil.3.0.x.x.0.0 or later. v The software distributor commands are moderately complex scripts that frequently require several steps. use tapeutil level tapeutil.0.hpux. on HP-UX 11i. “Copy the Software to the Software Depot” on page 335 2. Install tapeutil Installing the product manually requires the three steps detailed in the following sections: 1. and Execution.0 or later.0.hpux. Otherwise.20 and 11. tapeutil.hpux.00 .x.x.x tapeutil Appendix D.00.If you are using the ATDD version 1.HP-UX . swinstall or swcopy) can first be run with the -p flag to preview the command. Tapeutil Implementation The tapeutil program contains utility program implementations for operation in the following HP-UX platform environments: v HP Precision Bus . Using ’pwd’/filename to reference to a file instead of filename ensures this. enter: # swremove -p tapeutil (preview option) # swremove tapeutil Other Administrative Tasks To determine the version of tapeutil currently installed on the default root file system: # swlist -a state tapeutil To determine the version of tapeutil stored in the default depot: 336 IBM Tape Device Drivers Installation and User’s Guide . It is best to use the swremove command. the tapeutil software can be installed to the root file system using the HP-UX swinstall command. Review it before proceeding with the software installation. including required system software patches and required tape related firmware versions. Install tapeutil When the software is in the depot. The file also documents any changes in the installation. and administration of the software that occurred after this documentation was completed.Tape Utility Program (tapeutil) Use swlist to verify that the tapeutil software is in the depot: # swlist -d tapeutil Review the tapeutil README File After copying the tapeutil software to the depot. To remove the tapeutil software from the root file system. The following commands install tapeutil from the depot to the default root file system: # swinstall -p tapeutil (preview option) # swinstall tapeutil You can use swlist to list the software installed on the default root file system as follows: # swlist tapeutil You can verify correct installation to the default root file system with the swverify command: # swverify tapeutil Uninstalling tapeutil Attention: Do not try to uninstall the ATDD software by simply deleting the files that make up the ATDD fileset. use.HP-UX . use the swlist command to view the README file in the directory /opt/tapeutil: # swlist -d -a readme tapeutil The README file lists the system configuration requirements. This causes a number of inconsistencies on the system. Interactive Mode The tapeutil program provides both an interactive mode and a command-line mode. This source code is commented and demonstrates calls to all the supported device driver entry points and ioctl commands. convenient for use in shell scripts. the tapeutil program provides a command-line interface. or it is closed automatically when the Quit option is selected. Tape Utility Programs 337 . If the tapeutil program is called with no command-line parameters. the menu is not displayed again automatically after each command but instead is refreshed only after the M (menu refresh) command is entered. the interactive mode version is started.HP-UX . The user is prompted for additional information if required for the specific options selected. The menu is displayed once automatically when the program is first called. giving the application developer a starting point for interfacing to the HP-UX device driver. The device can be closed using option 2.Tape Utility Program (tapeutil) # swlist -d state tapeutil To view the set of files installed with tapeutil: # swlist -l file tapeutil To remove tapeutil from the depot: # swremove -d tapeutil Using the tapeutil Program A Tape and Medium Changer Utility Program called tapeutil is provided with the IBM Tape and Medium Changer Device Driver for HP-UX and installed in the /usr/bin directory. Other options may then be selected. The results of a command are displayed after it is executed. v The source code for the tapeutil program is provided for example purposes and is installed in the /opt/tapeutil directory during the tapeutil package installation. In the interactive mode. the device to be operated on should first be opened using option 1. The tapeutil program fulfills several purposes: v The program provides the following service aids for IBM tape systems: – Query Device Type/Verify Device Attachment – Query Device Serial Number – Query Device Microcode Level – Force Device Diagnostic Dump – Store Device Diagnostic Dump – Download Device Microcode v The program provides a menu driven test tool for exercising or testing IBM tape and medium changer devices with a full suite of supported operations: – Reading/Writing Data – Tape Motion Commands – Setting/Displaying Device Information/Status – Mounting/Demounting Cartridges – Cartridge Inventory v In addition to the menu driven front end. If an error occurs for the command. To prevent unnecessary scrolling of the screen. Appendix D. error information and device sense data are displayed. Tape Utility Program (tapeutil) These commands can issue the MTIOCTOP ioctl with the MT opcodes defined in /usr/include/sys/mtio. For detailed information. The program can be invoked from within a shell script if desired. or issue the STIOC_TAPE_OP ioctl with the ST_OP opcodes defined in /usr/include/sys/st. When in command-line mode.HP-UX . GA32-0566. A completion code.h.h (ST mode).h (MT mode). Service Commands Query Serial Number Query Microcode Level Force Dump Store Dump Download Microcode Query Device Type tapeutil -f f -o qsn [-w w] [-v] tapeutil -f f -o qmc [-w w] [-v] tapeutil -f f -o fdp [-w w] [-v] tapeutil -f f -o sdp [-w w] [-v] -z z tapeutil -f f -o dmc [-w w] [-v] -z z tapeutil -f f -o chk [-w w] [-v] Basic SCSI Commands Test Unit Ready Inquiry/Inquiry Page Request Sense Log Sense Page tapeutil -f f -o tur [-w w] [-v] tapeutil -f f -o inq [-w w] [-v] [-t t] [-x x] tapeutil -f f -o req [-w w] [-v] tapeutil -f f -o log [-w w] [-v] [-x x] 338 IBM Tape Device Drivers Installation and User’s Guide . The device special file and the operation are required. No information is displayed when not in verbose mode. /dev/rmt/1m) and operation is one of the values listed below. The following commands run in the two modes: v Write File Mark v Erase Tape v Rewind v Offline v Forward/Backward Space File v Forward/Backward Space Record v Locate End of Data Command-Line Interface If command-line parameters are provided when the program is started. Parameters enclosed in square brackets are optional. as defined in /usr/include/sys/errno. is always returned from the program upon exit (in both verbose and quiet mode). the device is first opened. The specific options associated with a particular operation are indicated below. Toggle between the MT or ST mode by using option 8. This is particularly useful for quiet shell script implementations. refer to the MTIOCTOP and STIOC_TAPE_OP sections in the IBM Tape Device Drivers Programming Reference. for the operation requested. All others are required. The usage of the tapeutil program in command-line mode is as follows: tapeutil -f device -o operation [options] Where: device is the name of the tape device special file (for example. and the device is then closed. Results of the operation are displayed only when executed in verbose mode. the program runs in command-line mode. the specific command is issued. The default for tapeutil is the ST mode. Tape Utility Program (tapeutil) Mode Page Reserve on Close Reserve Release tapeutil -f f -o mod [-w w] [-v] -x x tapeutil -f f -o mod [-w w] [-v] -x x tapeutil -f f -o res [-w w] [-v] tapeutil -f f -o rel [-w w] [-v] Prevent/Allow Medium Removal tapeutil -f f -o rem [-w w] [-v]-x x Medium Changer Commands Move Medium tapeutil -f f -o mov [-w w] [-v] -s s -d d Position To Element tapeutil -f f -o pos [-w w] [-v] -s s Element Information tapeutil -f f -o ele [-w w] [-v] Read Element Status with Drive ID tapeutil -f f -o dvc[-w w] [-v] Inventory tapeutil -f f -o inv [-w w] [-v] To Output the Inventory Data into a File tapeutil -f f -o inv -t 1 [-w w] [-v] > filename Audit tapeutil -f f -o aud [-w w] [-v] Lock/Unlock Door tapeutil -f f -o lck [-w w] [-v] -x x Note: Exchange Medium and Initial Element Status Range commands are not supported by IBM TotalStorage and System Storage tape devices. Tape Utility Programs 339 . CPF Commands Display Paths Enable Path Disable Path tapeutil -f f -o phs[-v] tapeutil -f f -o ena -p path [-v] tapeutil -f f -o dis -p path [-v] Tape Drive Commands Read Write tapeutil -f f -o rea [-w w] [-v] -b b -n n -m m tapeutil -f f -o wri [-w w] [-v] -b b -n n -m m [-r r] [-z z] tapeutil -f f -o eof [-w w] [-v] -c c tapeutil -f f -o era [-w w] [-v] tapeutil -f f -o rew [-w w] [-v] tapeutil -f f -o ret [-w w] [-v] tapeutil -f f -o off [-w w] [-v] tapeutil -f f -o lod [-w w] [-v] -x x tapeutil -f f -o fsf [-w w] [-v] -c c tapeutil -f f -o bsf [-w w] [-v] -c c tapeutil -f f -o fsr [-w w] [-v] -c c Write File Mark Erase Tape Rewind Retension Offline Load/Unload Tape Forward Space File Backward Space File Forward Space Record Appendix D.HP-UX . wri) {0–2097152} Blocking Factor (rea. and their acceptable ranges are as follows: -? -b Usage Help (stand-alone flag) {no value required} Block Size (rea. wri) {0 < (block size x blocking factor) < 2097152} -c -d Operation Count (eof. their associated operations. srs) {0–65535} Destination Address (mov) {device specific.y1 Note: Invoking the tapeutil program with the -h flag (for example.HP-UX . determine range from Element Info} -t Type of Parameter Value 340 IBM Tape Device Drivers Installation and User’s Guide . fsf. tapeutil -?) displays the usage help information. Flag Description The supported flags. bsr. pos) {device specific. bsf. their meanings.Tape Utility Program (tapeutil) Backward Space Record Locate End of Data Report Tape Density Check Device Type Get Record Size Set Record Size Get Device Status Get Device Information Get Media Information Get Position Set Position Get Parameter Set Parameter Sync Buffer Display Message tapeutil -f f -o bsr [-w w] [-v] -c c tapeutil -f f -o eod [-w w] [-v] tapeutil -f f -o den [-w w] [-v] tapeutil -f f -o chk [-w w] [-v] tapeutil -f f -o grs [-w w] [-v] tapeutil -f f -o srs [-w w] [-v] -c c tapeutil -f f -o gds [-w w] [-v] tapeutil -f f -o gdi [-w w] [-v] tapeutil -f f -o gmi [-w w] [-v] tapeutil -f f -o gpo [-w w] [-v] -t t tapeutil -f f -o spo [-w w] [-v] -t t -x x tapeutil -f f -o gpa [-w w] [-v] -t t tapeutil -f f -o spa [-w w] [-v] -t t -x x tapeutil -f f -o syn [-w w] [-v] tapeutil -f f -o msg [-w w] [-v] -t t -y y1. determine range from Element Info} -f Device Special File Name (always required) {/dev/rmt/1st or similar} -h -m -n Usage Help (stand alone flag) {no value required} Multiples to Read or Write (rea. fsr. wri) {0 > (block size x blocking factor) < 2097152} -o -p -r -s Operation (always required) {refer to the previous list} The path that is enabled or disabled Random Seed (wri) {0–65535} Source Address (mov. tapeutil -h) or -? flag (for example. 2=compression. Attempting to set capacity scaling that is not supported by a device or the current media loaded returns a failure. 2=display msg1. 5=trailer. the size of one buffer of data transferred during a single SCSI read or write command is determined by the product of the Block Size value and the Blocking Factor value. If the current microcode on a tape drive is FIPS (Federal Information Processing Standard) code. 1=st mode} -v Verbose Mode (optional for all commands. For further information on the Get Parameter (gpa) and Set Parameter (spa) operations. 2. 7=acf mode.message2} Input/Output File Name v (sdp) {path and name of the file in which to store dump} v (dmc) {path and name of the microcode image file} v (wri) {path and name of the file containing write data pattern} Notes: 1. 6=write protect. then a window opens and displays the following: Appendix D. The actual total number of bytes transferred is then (Block Size) x (Blocking Factor) x (Multiplier). 9=sili} v (msg) {1=display msg0. 8=capacity. 4.HP-UX . 2=unload} v (spo) {0–65535} v v v v v -y -z (spa) {0–65535} (inq) {0x0–0xFF} (log) {0x00–0xFF} (mod) {0x00–0xFF} (rem) {1=prevent. 6=write protect. the product of Block Size and Blocking Factor must be a multiple of the device block size setting. 3=write only. For read and write operations. 2=physical block} v (gpa) {1=block size. stand-alone flag) {no value required. 3=buffering. If the device is set to fixed block mode (block size not equal to zero). 2=compression. absence of flag means quiet mode} -w Open Mode (optional for all commands) {1=read/write. Tape Utility Programs 341 . The number of these buffers transferred is determined by Multiplier value. 4=immediate. refer to the STIOC_GET_PARM and STIOC_SET_PARM ioctl commands in the IBM Tape Device Drivers Programming Reference. 3=buffering. 5=trailer. 2=read only (default). 9=sili} v (spa) {1=block size. GA32-0566. 4=immediate. 2=allow} Messages (msg) {message1. 2=unlock} v (lod) {1=load. 2=physical block} v (spo) {1=logical block. 4=flash msg1. 4=append} -x Parameter Value v (lck) {1=lock. 3=flash msg0. All media types for the 3590 tape drive support capacity scaling.Tape Utility Program (tapeutil) v (gpo) {1=logical block. 1=page code} v {0=mt mode. 5=alternate msg1/msg2} v (inq) {0=standard data. Capacity scaling is only supported for the standard 300 GB re-writable Data Cartridge for the 3592 tape drive. 3. 8=capacity. v To query the serial number of the device: tapeutil -f /dev/rmt/0m -o qsn -v v To request inquiry data from the device: tapeutil -f /dev/rmt/0m -o inq -v v To request inquiry page data from the device: tapeutil -f /dev/rmt/0m -o inq -t 1 -x 0x03 -v v To request log sense page from the device: tapeutil -f /dev/rmt/0m -o log -x 0x00 -v v To request mode page from the device: tapeutil -f /dev/rmt/0m -o mod -x 0x02 -v v To move a cartridge from cell 32 to the tape drive (16) for TotalStorage 3590: tapeutil -f /dev/rmt/4chng -o mo -s 32 -d 16 -v v To write one hundred 64K blocks of data to the tape device: tapeutil -f /dev/rmt/0mn -w 1 -o wri -b 65535 -n 1 -m 100 -v v To write two file marks to the tape device: tapeutil -f /dev/rmt/0mn -w 1 -o eof -c 2 -v v To rewind the tape device: tapeutil -f /dev/rmt/0mn -o rew -v v To read one hundred 64K blocks of data from the tape device: tapeutil -f /dev/rmt/0mn -o rea -b 65535 -n 1 -m 100 -v v To report the tape density: tapeutil -f /dev/rmt/0mn -o den -v v To prevent tape removal from the tape drive: tapeutil -f /dev/rmt/0mn -o rem -x 1 -v v To allow tape removal from the tape drive: tapeutil -f /dev/rmt/0mn -o rem -x 2 -v v To read the element status with the drive ID: tapeutil -f /dev/rmt/4chng -o dvc -v v To output the inventory information into a file: tapeutil -f /dev/rmt/4chng -o inv -t 1 > inv.HP-UX .Tape Utility Program (tapeutil) Warning: The drive is currently using FIPS code.txt Querying Primary and Alternate Path Configurations (Control Path Failover) You can display the primary and alternate path configuration for all devices by running the ioscan command. otherwise. You can also display the primary and alternate paths configuration for any device by running the following command: # tapeutil -f /dev/rmt/Xchng -o phs -v 342 IBM Tape Device Drivers Installation and User’s Guide . substitute the actual value of the special file associated with the target device. as explained in section “Determine the Device Hardware Path for IBM Tape Drives” on page 58. The following examples should help to demonstrate and clarify the command-line usage of the tapeutil program. For all examples. Do you want to continue with downloading new drive code? [y/n]: Enter n to exit without downloading new code. enter y to continue with the download code procedure. such as the logical name of the device. Querying Primary and Alternate Path Configuration (Data Path Failover) You can display the primary and alternate path configuration for all devices by running ioscan. the logical unit number under the target. by default. run commands to disable and then later enable the primary and alternate paths. you can run the following command: # tapeutil -f /dev/rmt/Xchng -o ena -p /dev/rmt/Xchng -v This command enables the path. then run the following commands: 1. as explained in section “Primary and Alternate Paths” on page 82. the target id. This command disables the path: # tapeutil -f /dev/rmt/Xchng -o dis -p /dev/rmt/Xchng -v This command ensures that the path is labeled as ″disabled. all the available paths for a physical device are enabled. the target ID. the current enabled status. the attached host bus adapter. and the number of paths configured for the device. the logical unit number under the target. and how many paths are configured for the device. by default. the current enabled status. all the available paths for a physical device are enabled. To disable the path: Appendix D.Tape Utility Program (tapeutil) Where: Xchng is the logical name of any device. such as the logical name of the device. This command shows specific information for the primary path and all alternate paths. Tape Utility Programs 343 .″ To enable a path from a disabled state. Disable and Enable Primary and Alternate Paths (Control Path Failover) When you load the ATDD device driver with the alternate_pathing parameter set to ON. the attached host bus adapter. You can also display the primary and alternate path configuration for any device by running the following command: # tapeutil -f /dev/rmt/Xm -o phs -v Where: Xm is the logical name of any device This command shows specific information for the primary path and all alternate paths. the channel ID. Where the -f flag is for the primary path and the -p flag is for the path that you want to enable or disable. If for some maintenance reason you need to disable a path and do not want to fail over to this path. Disable and Enable Primary and Alternate Paths (Data Path Failover) Once you load the ATDD device driver with the alternate_pathing parameter set to ON. If it is necessary to disable a path and not perform path fail over (for example due to maintenance).HP-UX . the channel id. HP-UX . To make sure the path is labeled as ″disabled″ # tapeutil -f /dev/rmt/Xm -o phs -v The string /dev/rmt/Xm is the primary path and /dev/rmt/Xm.altpath -o dis -v 2.altpath is the alternate path you want to disable. To enable a path from a disabled state. run the following command: # tapeutil -f /dev/rmt/Xm -p /dev/rmt/Xm.Tape Utility Program (tapeutil) # tapeutil -f /dev/rmt/Xm -p /dev/rmt/Xm.altpath -o ena -v 344 IBM Tape Device Drivers Installation and User’s Guide . x. Enter the Read/Write.Tape Utility Program (IBMtapeutil) Linux System . the interactive mode is invoked. for example. 2. Enter the name of the device special file.x. IBMtapeutil.. Device is the name of the device special file (for example. 3. If you enter the IBMtapeutil command without any arguments.] Note: 1. Interactive Mode The interactive mode for the tape utility program can be invoked from the command line using the IBMtapeutil command. the error number. 2. /dev/IBMtape0n. The subcommands are processed one at a time in the order specified on the command line. or /dev/IBMchanger0.com/storage/devdrvr/Linux/. Multiple subcommands can be combined in a single command to perform more than one operation. After you open a device. You must open a device before using these commands and operations.x.Tape Utility Program (IBMtapeutil) Installed with the device driver is a tape utility program (IBMtapeutil) that exercises or tests the functions of the tape device and the device driver. Some commands require additional information after they are selected from the window. The tape utility program can be used in either the interactive or the command-line mode. It also performs basic tape and medium changer operations. Use any special file that exists for the device. A list of general subcommands. To open a device: 1. medium changer subcommands. Write Only. Select Open a Device from General Commands. Command-Line Mode The command-line mode for the tape utility program (IBMtapeutil) provides the same basic tape and changer commands as the interactive mode. Appendix D. If an error occurs running the command. enter the IBMtapeutil ? command on the Linux command line. Read Only. The syntax for the command-line mode of the tape utility program is: IBMtapeutil -f Device Subcommand [Subcommand . The C source code for the IBMtapeutil program contains a sample of the interface to the device driver and the ioctl commands supported by the device driver. the error text. and the device sense data (if applicable) are displayed.ibm. /dev/IBMtape0.c may be found in the tar file IBMtapeutil. /dev/IBMtape0). and service aid subcommands is displayed.. These modes apply only to the tape devices. or Append mode to open a device. tape subcommands. Tape Utility Programs 345 .software. Figure 87 on page 346 is an example of the help information that is displayed.Linux . select a command using the appropriate number for the command from the window. Append mode uses Write Only for file access permission. Invoke the IBMtapeutil command from the Linux command line or within a shell script. For help information about the subcommands and their syntax. Subcommand is any valid command for the device.tar on the device driver down load ftp site: ftp://ftp. version 1. If there is only one path available and you attempt to disable it. on libraries that have the Control Path Failover feature enabled.Linux . This subcommand is only available in IBMtapeutil version 1. version 1. the primary path is enabled. If a numeric value is specified. that specific path is disabled. This subcommand is only available in IBMtapeutil version 1. If ″primary″ is specified. and the lin_tape device driver.4.4. If you attempt to disable a data path (to the tape drive).0 or higher. enablepath ″primary″ | number: The enablepath subcommand is used to enable a path to a medium changer that has been previously disabled with the disablepath subcommand. a ″function not implemented″ error is returned. If a numeric value is specified. but this subcommand can be used to disable a path. and the lin_tape device driver. Use the path command to obtain a list of the paths. that specific path is enabled. for example [Page]. IBM recommends that you leave all paths enabled.1 or higher.Tape Utility Program (IBMtapeutil) General Subcommands: tur reserve qryversion Tape Subcommands: bsf [Count] fsf [Count] fsfm [Count] compress nocompress load unload qrypos setpos [Blockid] offline rewoffl prevent allow qryinquiry bsr [Count] fsr [Count] bsfm [Count] tell rewind erase retension seod status parms list lock unlock qrysense eof [Count] weof [Count] asf [Count] seek [Count] sync display "Message" read -d Destination [-c Count] write -s Source rtest [-b Blocksize] [-c Count] [-r Repetition] wtest [-b Blocksize] [-c Count] [-r Repetition] rwtest [-b Blocksize] [-c Count] [-r Repetition] setblk [Count] density append mtdevice encryption inquiry [Page] release logpage "Page" print "Text" reqsense modepage "Page" Medium Changer Subcommands: allow inventory elementinfo devids prevent mount [Slot] unmount [Slot] exchange "Source" audit [Address [Count]] position "Destination" move "Source" "Destination" "Dest1" "Dest2" Service Aid Subcommands: dump [Filename] forcedump ucode "Name" resetdrive Figure 87. Linux Command Line Help Display General Subcommands The following general subcommands are available for the tape and medium changer devices. Items shown enclosed in square brackets.2. If ″primary″ is specified. the primary path is disabled. 346 IBM Tape Device Drivers Installation and User’s Guide . a ″function not implemented″ error is returned.2. disablepath ″primary″ | number: The disablepath subcommand is used to disable a path to a medium changer. this subcommand fails with an illegal argument. If you attempt to enable a data path (to a tape drive). Use the path command to obtain a list of the paths. are optional.1 or higher. on libraries that have the Control Path Failover feature enabled.0 or higher. It prints out the current version of the lin_tape driver. reserve: This subcommand explicitly reserves a device by issuing the SCSI Reserve command.0 or higher. version 1. release: This subcommand explicitly releases a device and makes it available for other hosts by issuing the SCSI Release command.0 or higher.2.1 or higher. erase current tape and backup myfile. on libraries that have the Control Path Failover feature enabled. reqsense: This subcommand issues the SCSI Request Sense command and prints out the sense data. For example: # Rewind.4. qryversion: This subcommand issues the QUERY_DRIVER_VERSION ioctl command. This subcommand is only available in IBMtapeutil version 1. Appendix D. or for a specific inquiry page.tar IBMtapeutil -f /dev/IBMtape0 rewind \ erase \ print "Writing myfile. The page parameter must be specified as a hexidecimal value. and the lin_tape device driver.1 or higher. print ″Text″: This subcommand prints the associated text to standard output.Linux . For example: # Get standard inquiry data IBMtapeutil -f /dev/IBMtape0 inquiry # Get inquiry page x'83' IBMtapeutil -f /dev/IBMtape0 inquiry 83 logpage ″Page″: This subcommand issues the SCSI Log Sense Page command to the device for the specified page and displays the log sense data. tur: This subcommand issues the SCSI Test Unit Ready command to the device. The page parameter must be specified as a hexidecimal value.tar" \ write -s myfile.Tape Utility Program (IBMtapeutil) inquiry [Page]: This subcommand issues the SCSI Inquiry command to the device for either standard inquiry data. version 1. For example: # Get log page x'31' IBMtapeutil -f /dev/IBMtape0 logpage 31 modepage ″Page″: This subcommand issues the SCSI Mode Sense Page command to the device for the specified page and displays the mode sense data. It can be used at any time to display the progress of the subcommands. on libraries that have the Control Path Failover feature enabled. For example: # Get mode page x'1D' IBMtapeutil -f /dev/IBMtape0 modepage 1d path: This subcommand shows all the available paths to a medium changer. when no page parameter is specified. and the lin_tape device driver. This subcommand is only available in IBMtapeutil version 1. Tape Utility Programs 347 . The page parameter must be specified as a hexidecimal value.4. Tape Subcommands The following tape subcommands are available for the tape devices.2.tar qrypath: This subcommand shows the primary path and the first alternate path for a medium changer. density: This subcommand issues the SCSI Report Density Support command for all supported media and for the current media loaded in the drive. The default count is 1. An optional count can be specified. An optional count can be specified. The default is 1. Up to 16 characters can be used for the message. The default is 1. The default is 1. For example: # Display "Test 1" and "Running" messages IBMtapeutil -f /dev/IBMtape0 display "Test 1 Running" encryption: This subcommand displays the encryption state of the drive. fsfm [Count]: This subcommand forward spaces count filemarks. An optional count can be specified. the current media density is not reported. erase: This subcommand erases the tape from the current position through the physical end of the tape. fsr [Count]: This subcommand forward spaces count records. Positioning is done by first rewinding the tape and then spacing forward over count filemarks. append: This subcommand opens the device in Append mode. The file access permission is set to Write Only. bsfm [Count]: This subcommand backward spaces count filemarks then positions the tape on the end of tape (EOT) side of the filemark. asf [Count]: This subcommand places the tape at the beginning block of count files from the beginning of the tape. The default is 1. then positions the tape on the beginning of tape (BOT) side of the filemark. The default is 1. bsf [Count]: This subcommand backward spaces count filemarks. and displays the results. compress and nocompress: These subcommands turn the hardware compression On or Off. An optional count can be specified. the display alternates between the first eight characters and the remainder of the message.Linux . bsr [Count]: This subcommand backward spaces count records. eof [Count] and weof [Count]: These subcommands write count filemarks. The default is 1. It is normally used after the prevent subcommand to restore the device to the default state. The tape is positioned on the last block of the previous file. If the message is longer than eight characters. The tape is positioned on the beginning of the last block of the previous file. An optional count can be specified. The default is 1. display ″Message″: This subcommand displays a message on the display panel of the tape device. An optional count can be specified. An optional count can be specified.Tape Utility Program (IBMtapeutil) allow: This subcommand issues the SCSI Allow Medium Removal command to the device to allow medium removal by an operator. If the drive is not loaded. fsf [Count]: This subcommand forward spaces count filemarks. 348 IBM Tape Device Drivers Installation and User’s Guide . The tape is positioned on the first block of the next file. lock: This subcommand locks the tape drive door. and device driver parameters.Linux . Tape Utility Programs 349 . For example: # Append myfile. parms: This subcommand issues the STIOCQRYP ioctl command and displays the current tape drive. The device number is only valid when an Enterprise Tape System 3590 is installed in a 3494 Enterprise Tape Library. and in most cases should be directed to a file.tar temp. the current tape position is saved and can be restored using a subsequent setpos subcommand. qryinquiry: This subcommand issues the STIOCQRYINQUIRY ioctl command and displays the output. all records up to the next filemark on tape are read. If the count parameter is not used. depending on the amount of data on the tape. and issues the STIOCSETP ioctl command to do so. and unload: These subcommands rewind and unload the tape. 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. For example: # List tape contents to file IBMtapeutil -f /dev/IBMtape0 list > tape. read -d Destination [-c Count]: This subcommand reads a file or a specified number of records from the current position on the tape to the destination file name specified with the -d flag. prevent: This subcommand issues the SCSI Prevent Medium Removal command to the device to prevent medium removal by an operator until the allow subcommand is issued or the device is reset.tar \ setpos \ read -d temp. qrypos: This subcommand issues the STIOCQRYPOS ioctl command for the current logical and physical tape position and displays the data.tar to the end of tape and then read back IBMtapeutil -f /dev/IBMtape0 append \ qrypos \ write -s myfile. The output generated from this subcommand can be large. mtdevice: This subcommand issues the MTDEVICE ioctl command and displays the library device number. media. the tape is at end of data. For example: Appendix D.tar # Verify myfile. Then the subcommand prompts users to set parameters to new values. rewoffl.list load: This subcommand issues the SCSI Load command to load a tape.tar qrysense: This subcommand issues the STIOCQRYSENSE ioctl command to obtain new sense data. When the command completes. In addition.Tape Utility Program (IBMtapeutil) list: This subcommand rewinds the tape to the beginning of tape and displays the contents.tar was written correctly diff myfile. The output lists filemarks and the size of each record found on the tape until the end of data is reached. The device number consists of the control unit serial number with a 1 digit logical unit number appended to it. If a record is larger than 256 KB. offline. a read error is returned. Both the control unit serial number and the 1 digit logical unit number are hexadecimal. setblk [Block Size]: This subcommand sets the block size of the drive to block size bytes per record. and repetition can be specified with the -b. and -r flags. an error message is printed and errno is set to 999. a count of 20 blocks. and a repetition of 1. For example: # R/W test using 256K blocks. reading it. 5 megabytes per write. an error message is printed and errno is set to 999. For example: # R/W test using 256K blocks.tar # Read 3 records from the tape into myfile IBMtapeutil -f /dev/IBMtape0 read -d myfile -c 3 rewind and retension: These subcommands rewind the tape to the beginning of the tape (BOT).tar from tape IBMtapeutil -f /dev/IBMtape0 read -d myfile. or there is a data mismatch.Tape Utility Program (IBMtapeutil) # Restore myfile. rtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a read test by reading a random data pattern from the tape and verifying that it matches the written data. seod: This subcommand spaces to the end of data on the tape. and a repetition of 1. the tape position is set to the last position saved using the tell subcommand. For example: 350 IBM Tape Device Drivers Installation and User’s Guide . 100 times IBMtapeutil -f /dev/IBMtape0 rewind \ wtest -b 262144 -c 20 -r 100 \ rewind \ rtest -b 262144 -c 20 -r 100 Note: If the number of bytes read is not equal to the number of bytes specified. the countspecifies the number of bytes to read on each repetition. -c. count. If the block size is fixed. if the count parameter is omitted. The Blockid can be specified in decimal or in hexidecimal (with a leading ″x″). 10 times IBMtapeutil -f /dev/IBMtapeutil rwtest -b 262144 -c 20 -r 10 Note: If the number of bytes written/read is not equal to the number of bytes specified. and -r flags. An optional block size. An optional block size. If the block size is fixed. -c. seek [Count]: If the optional count parameter is specified.Linux . if the Blockid parameter is omitted. the tape position is set to the last position saved using the qrypos subcommand. If the block size is zero (variable). respectively. The count can be specified in decimal or in hexidecimal (with a leading ″x″). and verifying that it matches the written data. Otherwise. 5 megabytes per write. the count specifies the number of bytes to write on each repetition. and repetition can be specified with the -b. a count of 20 blocks. count. The rtest subcommand can be used after the wtest subcommand to verify the data. the count specifies the number of blocks to read on each repetition. the tape position is set to the block whose ID is count. the count specifies the number of blocks to write on each repetition. or there is a data mismatch while reading. respectively. If the optional Blockid parameter is specified. If the block size is zero (variable). A block size of zero sets the drive to variable block mode. setpos [Blockid]: This subcommand issues the SCSI Locate command to the device to set the tape position. If no block size is specified. the block is set to variable block mode. The default is a block size of 10240. rwtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a read and write test by writing a random data pattern on the tape. the tape position is set to the Blockid. The default is a block size of 10240. Otherwise. tar # Verify myfile. Medium Changer Subcommands The following medium changer subcommands are available for the integrated and independent medium changer devices.tar to the end of tape and then read back IBMtapeutil -f /dev/IBMtape0n append \ qrypos \ write -s myfile. An optional block size. If the block size is fixed. a count of 20 blocks. 100 times IBMtapeutil -f /dev/lin_tape rewind \ wtest -b 262144 -c 20 -r 100 \ rewind \ rtest -b 262144 -c 20 -r 100 Note: If the number of bytes written is not equal to the number of bytes specified.tar \ setpos \ read -d temp. and a repetition of 1. If the block size is zero (variable). For example: # backup myfile. an error message is printed and errno set to 999.tar wtest [-b Blocksize] [-c Count] [-r Repetition]: This subcommand performs a write test by writing a random data pattern on the tape. tell: This subcommand reports the current block position on the tape and saves the position for use by a subsequent seek subcommand. respectively.Linux . sync: This subcommand synchronizes or flushes the tape buffers to tape. # Initialize all elements IBMtapeutil -f /dev/IBMtape0 audit Appendix D. 5 megabytes per write. Tape Utility Programs 351 .tar to tape IBMtapeutil -f /dev/IBMtape0 write -s myfile. For example: # R/W test using 256K blocks. write -s Source: This subcommand writes the source file specified with the -s flag on the tape.tar # Set tape position to block 32 and leave positioned on close IBMtapeutil -f /dev/IBMtape0n setpos 32 # Set tape position to block 32 and leave positioned on close IBMtapeutil -f /dev/IBMtape0n setpos x20 status: This subcommand issues the MTIOCGET command and prints out status information about the tape unit. the count specifies the number of blocks to write on each repetition. audit [Address[Count]] This subcommand with no parameters issues the SCSI Initialize Element Status command to the device. allow This subcommand is not supported for TotalStorage medium changer devices. the count specifies the number of bytes to write on each repetition. The Address and Count parameters are not supported for IBM TotalStorage devices.Tape Utility Program (IBMtapeutil) # Append myfile. The rtest subcommand can be used after the wtest subcommand to verify the data that was written. and -r flags. unlock: This subcommand unlocks the tape drive door. The default is a block size of 10240. count. -c.tar temp. and repetition can be specified with the -b.tar was written correctly diff myfile. elementinfo This subcommand displays the information returned from the SMCIOC_ELEMENT_INFO ioctl command that contains the number of and the address of the first of each element type. exchange Source Dest1 Dest2 This subcommand is not supported for TotalStorage devices. The element addresses can be obtained using the elementinfo subcommand. mount [Slot] This subcommand mounts a tape from the specified slot address into the drive or from the first full slot into the drive if the slot is omitted. For example: # Get slot and drive addresses IBMtapeutil -f /dev/IBMchanger0 elementinfo # Move cartridge in slot 20 to drive at address 16 IBMtapeutil -f /dev/IBMchanger0 move 20 16 position Destination This subcommand issues the SCSI Position to Element command using the destination specified.Linux . unmount [Slot] This subcommand moves a tape from the drive to the specified slot address or the first empty one if slot is omitted. For example: # Position to slot at address 20 IBMtapeutil -f /dev/IBMchanger0 position 20 prevent This subcommand is not supported for TotalStorage medium changer devices. inventory This subcommand issues the SCSI Read Element Status command for each element type and displays the element status information.Tape Utility Program (IBMtapeutil) devids This subcommand issues the SCSI Read Element Status command to the device with the DVCID option for all drive elements and displays the element status information. For example: # Mount cartridge from slot 3 IBMtapeutil -f /dev/IBMchanger0 mount 3 # Mount cartridge from first full slot IBMtapeutil -f /dev/IBMchanger0 mount move Source Destination This subcommand issues the SCSI Move Medium command using the source and destination addresses specified. For example: # Move tape from drive to slot address 4 (tape is already unloaded) IBMtapeutil -f /dev/IBMchanger0 unmount 4 # Unload tape and move to the first empty slot IBMtapeutil -f /dev/IBMchanger0 unmount Service Aid Subcommands The following service aid subcommands are available for the devices. No device identifier information is obtained. 352 IBM Tape Device Drivers Installation and User’s Guide . For example: # Force a dump and then stores the dump into file /tmp/dump1. or by issuing the parms subcommand when in command-line mode. this operation fails and errno is set to 999. Note: All configuration parameters are reset to their default values whenever the lin_tape device driver is reinstalled.Linux . It is usually followed by the dump subcommand. or the returned status from SCSI Pass Through is not correct. in dump0001. This parameter is currently not supported for IBM Ultrium devices. ucode [Filename] This subcommand is implemented using SCSI Pass Through ioctl. the ACF mode can be queried by the IBMtapeutil application using the Query/Set Parameters option in the window.dmp IBMtapeutil -f /dev/IBMtape0 forcedump dump /tmp/dump1.ucode Note: If the device is not supported. However. this operation fails and errno is set to 999. For example: # download microcode IBMtapeutil -f /dev/IBMchanger0 ucode /temp/device. Reserve and Release Commands The device driver reserves the device automatically on the open call and releases the device on the close call. This prevents other applications and hosts from accessing the device. It forces a dump on a tape device. Tape Utility Programs 353 . there may be situations when the reserve should be Appendix D. It should follow a forcedump subcommand. Some of the parameters can be changed using the interactive mode of the tape utility program and selecting Query/Set Parameters under lin_tape Commands. Configuration Parameters The configuration parameters can be queried using either the interactive mode of the tape utility program and selecting Query/Set Parameters under Tape Commands. Filename is a file that contains the ucode. or the returned status from SCSI Pass Through is not correct. resetdrive This subcommand issues a STIOC_RESET_DRIVE ioctl command to reset the device.Tape Utility Program (IBMtapeutil) dump [Filename] This subcommand is implemented using SCSI Pass Through ioctl. It stores the dump in the specified Filename or. It downloads microcode to the device. forcedump This subcommand is implemented using SCSI Pass Through ioctl.dmp Note: If the device is not supported. or by issuing the parms subcommand when in command-line mode.dmp in the current directory. Block Size and SCSI Transfer Size The minimum and maximum block sizes for the tape device and the maximum SCSI transfer size can be queried using either the interactive mode of the tape utility program and selecting Query/Set Parameters under Tape Commands. Automatic Cartridge Facility (ACF) Mode If the Enterprise Tape System 3590 tape subsystem has an ACF installed. if Filename is omitted. assuming this utility program has been installed.You can also display the primary and alternate path configuration for any device by running the following command: IBMtapeutil -f /dev/IBMchangerx path (IBMchangerx is the logical name of any device) 354 IBM Tape Device Drivers Installation and User’s Guide .f /dev/IBMtape0 reserve tar .Tape Utility Program (IBMtapeutil) maintained after the close call. Querying Primary and Alternate Path Configuration (Control Path Failover) IBMtapeutil -f /dev/IBMchangerx path (Where: IBMchangerx is the logical name of any device). or a device may be shared by multiple initiators or hosts.com/systems/storage/index/tape... the logical unit number under the target. IBMtapeutil -f /dev/IBMtape0 release After the reserve command is used.ibm. the reservation must be retained between the close call and the next open call. The command lin_tapeconfig can also be used directly from the Linux command line. some backup programs (such as tar) can open and close the device multiple times. This command shows specific information for the primary path and all alternate paths. Tape Drive Service Aids The service aids described here are accessible through both the interactive and command-line mode of the IBMtapeutil command. run tar. In these cases. /dev/IBMtape0 . For example. the attached host bus adapter. For information on using tape drive service aids with the IBM Virtualization Engine TS7510. and then release device IBMtapeutil . the device driver retains the reservation until a release command is issued. You can display the primary and alternate path configuration for all devices by reading the /proc/scsi/IBMchanger file. For example: # Reserve device. A device can be reserved and released explicitly using either the interactive mode of the tape utility program and selecting reserve or release under General Commands. for more information refer to “Service Aid Subcommands” on page 352. It invokes a command. the user explicitly releases the device.Linux . Create Special Files The interactive mode of the tape utility program provides a selection to create special files based on attached devices.. the channel id. the target id. This is done by explicitly reserving the device. to remove current /dev/lin_tape and /dev/IBMchanger files and generate new ones. Note: Running lin_tapeconfig requires root authority. such as the logical name of the device. please refer to the IBM System Storage Virtualization Engine TS7510 Installation and Planning Guide at: http://www-03. After all work is completed on the device.html.. lin_tapeconfig. the current enabled status. and how many paths are configured for the device. or by issuing reserve and release commands when in command-line mode. the logical unit number under the target. all the available paths for a physical device are enabled. the target id. in the /proc/scsi/IBMchanger file. Tape Utility Programs 355 . and how many paths are configured for the device. in the /proc/scsi/IBMchanger file. the channel id. you can run the following command: v IBMtapeutil -f /dev/IBMchangerx enablepath number (where: number is the number of the path you want to enable) Appendix D. If for some maintenance reason you need to disable a path and do not want to fail over to this path. Once you load the lin_tape device driver with the alternate_pathing parameter to be ON. by default. If for some maintenance reason you need to disable a path and do not want to fail over to this path. you can run the following command: v IBMtapeutil -f /dev/IBMchangerx enablepath number (where: number is the number of the path you want to enable) Querying Primary and Alternate Path Configuration (Data Path Failover) You can display the primary and alternate path configuration for all devices by reading the /proc/scsi/IBMtape file. the attached host bus adapter. by default.You can also display the primary and alternate path configuration for any device by running the following command: >IBMtapeutil -f /dev/IBMtapex path (IBMtapex is the logical name of any device) This command shows specific information for the primary path and all alternate paths. the disabled path is listed as ″Disabled″ under the ″FO Path″ column. you can run the following commands: v IBMtapeutil -f /dev/IBMchangerx path (to know what number of this path is) v IBMtapeutil -f /dev/IBMchangerx disablepath number (where: number is the number of the path you want to disable) v IBMtapeutil -f /dev/IBMchangerx path (to make sure the path is labeled as ″disabled″) Correspondingly. all the available paths for a physical device are enabled.Linux . you can run the following commands: v IBMtapeutil -f /dev/IBMchangerx path (to know what number of this path is) v IBMtapeutil -f /dev/IBMchangerx disablepath number (where: number is the number of the path you want to disable) v IBMtapeutil -f /dev/IBMchangerx path (to make sure the path is labeled as ″disabled″) Correspondingly. the current enabled status. the disabled path is listed as ″Disabled″ under the ″FO Path″ column.Tape Utility Program (IBMtapeutil) Disable and Enable Primary and Alternate Paths (Control Path Failover) Once you load the lin_tape device driver with the alternate_pathing parameter to be ON. such as the logical name of the device. To enable a path from a disabled state. To enable a path from a disabled state. in the /proc/scsi/IBMtape file. To enable a path from a disabled state. you may run the following commands: >IBMtapeutil -f /dev/IBMtapex path (to know what number of this path is) >IBMtapeutil -f /dev/IBMtapex disablepath number ("number" will be the number of the path you want to disable) >IBMtapeutil -f /dev/IBMtapex path (to make sure the path is labeled as "disabled") Correspondingly.Linux .Tape Utility Program (IBMtapeutil) Disable and Enable Primary and Alternate Paths (Data Path Failover) Once you load the lin_tape device driver with the alternate_pathing parameter to be ON. If for some maintenance reason you need to disable a path and do not want to fail over to this path. all the available paths for a physical device are enabled. by default. the disabled path is listed as ″Disabled″ under the ″FO Path″ column. you may run the following command: >IBMtapeutil -f /dev/IBMtapex enablepath number ("number" will be the number of the path you want to enable) 356 IBM Tape Device Drivers Installation and User’s Guide . For each command-line execution of the program. the interactive mode is started. or it is closed automatically when the Quit option is selected. thus giving the application developer a starting point for interfacing to the IBMtape device driver. the device to be operated on should first be opened using option 1. Note: When using the command-line calls to the tapeutil program. The tapeutil program provides both an interactive mode and a command-line mode. Other options may then be selected. If the tapeutil program is called with no command-line parameters. Configuration parameters that are changed in one call to the tapeutil program are returned to default values when the device is closed. The user is prompted for additional information if required for the specific options selected. This source code is commented and demonstrates calls to all of the supported device driver entry points and ioctl commands. The device can be closed using option 2. Appendix D.Tape Utility Program (tapeutil) Solaris System . To prevent unnecessary scrolling of the screen. If command-line parameters are provided when the program is called.Solaris . the tapeutil program provides a command-line mode that is convenient for use in shell scripts. the command-line mode is started. In the interactive mode. the menu is not displayed automatically again after each command but instead is refreshed only after the M (menu refresh) command is entered. Interactive Mode The program provides a menu driven test tool for exercising or testing IBM tape and medium changer devices with a full suite of supported operations. Tape Utility Programs 357 . The program provides the following service aids for IBM tape subsystems.Tape Utility Program (tapeutil) A SCSI Tape and Medium Changer Utility Program called tapeutil is provided with the IBM SCSI Tape and Medium Changer Device Driver for Solaris and is installed in the /opt/IBMtape directory as part of the IBMtape package. the tape device is opened and closed for each invocation. The results of a command are displayed after it is executed. The menu is displayed automatically one time when the program is first called. v Cartridge Inventory v Mounting/Demounting Cartridges v Reading/Writing Data v Setting/Displaying Device Information/Status v Tape Motion Commands Command-Line Mode In addition to the menu driven front end. If an error occurs for the command. error information and device sense data is displayed. v Download Device Microcode v Force Device Diagnostic Dump v v v v Query Device Microcode Level Query Device Serial Number Query Device Type/Verify Device Attachment Store Device Diagnostic Dump The source code for the tapeutil program is provided for example purposes and is installed in the /opt/IBMtape directory during the IBMtape package installation. for the operation requested is always returned from the program upon exit (in both verbose and quiet mode). Parameters enclosed in square brackets are optional.Tape Utility Program (tapeutil) the device is first opened. and the device is then closed.h. A completion code. All others are required.Solaris . Results of the operation are displayed only when executed in verbose mode. The program can be driven from within a shell script if desired. The specific options associated with a particular operation are indicated. No information is displayed when not in verbose mode. This is particularly useful for quiet shell script implementations. the specific command is issued. Service Commands Query Serial Number Query Microcode Level Force Dump Store Dump Download Microcode Format Cartridge Query Device Type tapeutil -f f -o qsn [-w w] [-v] tapeutil -f f -o qmc [-w w] [-v] tapeutil -f f -o fdp [-w w] [-v] tapeutil -f f -o sdp [-w w] [-v] -z z tapeutil -f f -o dmc [-w w] [-v] -z z tapeutil -f f -o fmt [-w w] [-v] tapeutil -f f -o chk [-w w] [-v] Basic SCSI Commands Test Unit Ready Inquiry Request Sense Reserve Release tapeutil -f f -o tur [-w w] [-v] tapeutil -f f -o inq [-w w] [-v] tapeutil -f f -o req [-w w] [-v] tapeutil -f f -o res [-w w] [-v] tapeutil -f f -o rel [-w w] [-v] Medium Changer Commands Move Medium Position To Element Element Information Inventory Audit Lock/Unlock Door tapeutil -f f -o mov [-w w] [-v] -s s -d d tapeutil -f f -o pos [-w w] [-v] -s s tapeutil -f f -o ele [-w w] [-v] tapeutil -f f -o inv [-w w] [-v] tapeutil -f f -o aud [-w w] [-v] tapeutil -f f -o lck [-w w] [-v] -x x Tape Drive Commands Read Write tapeutil -f f -o rea [-w w] [-v] -b b -n n -m m tapeutil -f f -o wri [-w w] [-v] -b b -n n -m m [-r r] [-z z] tapeutil -f f -o eof [-w w] [-v] -c c tapeutil -f f -o era [-w w] [-v] Write File Mark Erase Tape 358 IBM Tape Device Drivers Installation and User’s Guide . as defined in /usr/include/sys/errno. The device special file and the operation are required. The usage of the tapeutil program in command-line mode is as follows: tapeutil -f device -o operation [options] Where: device is the name of the tape device special file (for example: /dev/rmt/1st) and operation is one of the following values. Solaris . fsf. Tape Utility Programs 359 . their associated operations. wri) {0 < (block size x blocking factor) < 2097152} -c -d Operation Count (eof. wri) {0–2097152} Blocking Factor (rea. tapeutil -?) displays the usage help information. bsf. their meanings. and their acceptable ranges are as follows: -? -b Usage Help (stand alone flag) {no value required} Block Size (rea. bsr) {0–65535} Destination Address (mov) {device specific. tapeutil -h) or or -? flag (for example. fsr. determine range from Element Info} -f Device Special File Name (always required) {/dev/rmt/1st or similar} -h -m -n Usage Help (stand alone flag) {no value required} Multiples to Read or Write (rea.Tape Utility Program (tapeutil) Rewind Retension Offline Load/Unload Tape Forward Space File Backward Space File Forward Space Record Backward Space Record Locate End of Data Get Record Size Set Record Size Get Device Status Get Device Information Get Media Information Get Position Set Position Get Parameter Set Parameter Sync Buffer Display Message tapeutil -f f -o rew [-w w] [-v] tapeutil -f f -o ret [-w w] [-v] tapeutil -f f -o off [-w w] [-v] tapeutil -f f -o lod [-w w] [-v] -t t tapeutil -f f -o fsf [-w w] [-v] -c c tapeutil -f f -o bsf [-w w] [-v] -c c tapeutil -f f -o fsr [-w w] [-v] -c c tapeutil -f f -o bsr [-w w] [-v] -c c tapeutil -f f -o eod [-w w] [-v] tapeutil -f f -o grs [-w w] [-v] tapeutil -f f -o srs [-w w] [-v] -x x tapeutil -f f -o gds [-w w] [-v] tapeutil -f f -o gdi [-w w] [-v] tapeutil -f f -o gmi [-w w] [-v] tapeutil -f f -o gpo [-w w] [-v] -t t tapeutil -f f -o spo [-w w] [-v] -t t -x x tapeutil -f f -o gpa [-w w] [-v] -t t tapeutil -f f -o spa [-w w] [-v] -t t -x x tapeutil -f f -o syn [-w w] [-v] tapeutil -f f -o msg [-w w] [-v] -t t -y y1.y1 Note: Invoking the tapeutil program with the -h flag (for example. Flag Description The supported flags. wri) {0 > (block size x blocking factor) < 2097152} -o Operation (always required) {refer to the previous list} Appendix D. 2=read only (default). refer to the STIOC_GET_PARM and STIOC_SET_PARM ioctl commands described in the IBM Tape Device Drivers: Programming Reference. For read and write operations. v To query the serial number of the device: /opt/IBMtape/tapeutil -f /dev/rmt/0st -o qsn -v v To request inquiry data from the device: 360 IBM Tape Device Drivers Installation and User’s Guide . If the device is set to fixed block mode (block size not equal to zero). substitute the actual value of the special file associated with the target device. determine range from Element Info} -t Type of Parameter Value v (gpo) {1=logical block. 2=physical block} v (gpa) {1=block size. 2=physical block} v (spo) {1=logical block. 2. The number of these buffers transferred is determined by the Multiplier value. 8=capacity. pos) {device specific. GA32-0566. absence of flag means quiet mode} -w Open Mode (optional for all commands) {1=read/write. 2=unload} -v Verbose Mode (optional for all commands.message2} Input/Output File Name v (sdp) {path and name of the file in which to store dump} v (dmc) {path and name of the microcode image file} v (wri) {path and name of the file containing write data pattern} Notes: 1.Tape Utility Program (tapeutil) -r -s Random Seed (wri) {0–65535} Source Address (mov. 9=sili} v (spa) {1=block size. 5=trailer. 4=immediate. 2=compression. The actual total number of bytes transferred is then Block Size x Blocking Factor x Multiplier. 3=flash msg0. 3=buffering. The following examples should help demonstrate and clarify the command-line usage of the tapeutil program. 6=write protect. 4=immediate. For further information about the Get Parameter (gpa) and Set Parameter (spa) operations. 8=capacity. 6=write protect. For all examples. 4=flash msg1. 3=buffering. 9=sili} v (msg) {1=display msg0.Solaris . the size of one buffer of data transferred during a single SCSI read or write command is determined by the product of the Block Size value and the Blocking Factor value. 2=compression. 4=append} -x Parameter Value v (lck) {1=lock. 3=write only. stand alone flag) {no value required. 7=acf mode. 2=unlock} v (srs) {0–65536} v (spo) {0–65535} v (spa) {0–65535} -y -z Messages (msg) {message1. 5=trailer. 5=alternate msg1/msg2} v (lod) {1=load. 2=display msg1. the product of Block Size and Blocking Factor must be a multiple of the device block size setting. substituting file with the actual path and filename of the microcode image file and substituting n with the actual value from the device special file associated with the destination device: /opt/IBMtape/tapeutil -f /dev/rmt/nst -o dmc -z file -v Notes: 1. followed by option 4 to query the current device microcode level. then a window opens and displays the following: Warning: The drive is currently using FIPS code. For 3592 Media types.file). v Enter the following command.Tape Utility Program (tapeutil) /opt/IBMtape/tapeutil -f /dev/rmt/0st -o inq -v v To move a cartridge from cell 32 to the tape drive (16): /opt/IBMtape/tapeutil -f /dev/rmt/0smc -o mov -s 32 -d 16 -v v To set the block size of the device to 64K: /opt/IBMtape/tapeutil -f /dev/rmt/0st -o spa -t 1 -x 65535 -v v To write one hundred 64K blocks of data to the tape device: /opt/IBMtape/tapeutil -f /dev/rmt/0stn -w 1 -o wri -b 65535 -n 1 -m 100 -v v To write two filemarks to the tape device: /opt/IBMtape/tapeutil -f /dev/rmt/0stn -w 1 -o eof -c 2 -v v To rewind the tape device: /opt/IBMtape/tapeutil -f /dev/rmt/0stn -o rew -v v To read one hundred 64K blocks of data from the tape device: /opt/IBMtape/tapeutil -f /dev/rmt/0stn -o rea -b 65535 -n 1 -m 100 -v 3. enter the following command. such as /vol/dev/aliases/floppy0 or host file. v Verify that the tape drive does not have a tape cartridge currently loaded. To download microcode to these devices. The microcode download procedure may also be performed using the interactive mode of the tapeutil program. continue with downloading new drive code? [y/n]: Do you want to Appendix D. Downloading Device Microcode The IBM tape drives support downloading a new microcode image from the host system by way of the SCSI bus. For example. Tape Utility Programs 361 . diskette. perform the following steps: v Verify that the IBM tape system is powered On and online. then click option 1 to open the device. To call the tapeutil program in this format. capacity scaling is only supported for the standard 300 GB rewritable data cartridge. the 60GB (Economy Data) cartridge for the IBM 3592 cannot be capacity scaled and is always 100%. such as /tmp/ucode_image. v Determine the current version of microcode present on the device by entering the following command. and option 7 to download new microcode: /opt/IBMtape/tapeutil 2. If the current microcode on a tape drive is FIPS (Federal Information Processing Standard) code.Solaris . Attempting to set capacity scaling that is not supported by a device or the current media loaded always returns 100% and cannot be changed. 4. substituting n with the actual value from the device special file associated with the target device: /opt/IBMtape/tapeutil -f /dev/rmt/nst -o qmc -v v Determine the source of the new microcode image file (that is. ............. For example: Path list in the device: Path 0 Path 1 Path 2 Current active path: Path 0 Enter path number or <enter> for all of the paths: Instance Number .. Verify that the IBM tape system is powered On and online. otherwise enter y to continue with the download code procedure..... Determine the location for the dump to be stored (that is..... Note: The diagnostic dump procedure may also be performed using the interactive mode of the tapeutil program.file)... 1 Serial Number .... Enter the following command... 4. 4 SCSI LUN ...Primary Path . N/A Path World Wide PN ..... 231 SCSI Target ................ You can also display the primary and alternate path configuration for any device running the tapeutil utility and selecting option 54 Query Device Paths... The dump may also be written to a tape cartridge mounted in the dump device using tapedrive for file............ Enter the following to force the dump.............. Forcing and Storing Device Diagnostic Dump The IBM tape drives support forcing a diagnostic dump and storing that dump to a mounted tape cartridge or to a host system file through the SCSI bus..... such as /tmp/diag_dump...... 1 362 IBM Tape Device Drivers Installation and User’s Guide . then click option 1 to open the device and option 6 to store the dump: /opt/IBMtape/tapeutil Querying Primary and Alternate Path Configuration (Control Path Failover) You can display the primary and alternate path configuration for all devices with the tapelist utility.... diskette........ substituting file with the actual path and filename of the dump destination file and substituting n with the actual value from the device special file associated with the dump device: /opt/IBMtape/tapeutil -f /dev/rmt/nst -o sdp -z file -v 5.......... 2...... /devices/pci@1f...... 000001301084 Ucode Level .. 227B Path World Wide NN . To call the tapeutil program in this format......2000/scsi@1/IBMtape@4..... substituting n with the actual value from the device special file associated with the target device: /opt/IBMtape/tapeutil -f /dev/rmt/nst/-o sdp -z file -v 3........ 3 SCSI LUN .....Solaris ...1 Instance Number ........Enable Device Physical Path ............... 201 SCSI Target . enter the following command... N/A Path Type . perform the following steps: 1..........Tape Utility Program (tapeutil) Enter n to exit without downloading new code........ such as /vol/dev/aliases/floppy0 or host file..... To store a diagnostic dump on these devices............. . Ucode Level .... Serial Number .......... Path Type ...... Path ... Path World Wide NN .......... If for some maintenance reason you need to disable a path and do not want to fail over to this path.....Solaris .......1 293 2 1 000001301084 227B N/A N/A Alt_path_2 Enable /devices/pci@6...... Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 3... Device Physical Path .. Path Type ................. SCSI LUN ....... Instance Number ..... Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 3...... Tape Utility Programs 363 .... all the available paths for a physical device are enabled. Remove the parameter of failover=0 in the path entry in IBMtape.. Turn the failover parameter to off in the path entry in the IBMtape....... by default... Path World Wide PN .. name="IBMtape" class="scsi" target=3 lun=1" 2..1 This option shows specific information for each path.....................Tape Utility Program (tapeutil) Serial Number ....... 2..... name="IBMtape" class="scsi" target=3 lun=1 failover=0. Disable and Enable Primary and Alternate Paths (Control Path Failover) Once you install the IBMtape device driver.. path type and so on.... Path World Wide PN ... you can run the following steps: 1.... Device Physical Path .... It also indicates how many paths are configured for the device.. the logical unit number....conf file. Path World Wide NN ... and which path is active currently........ For example.... such as the instance number for the logical device..... Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd To enable a path from a disabled state...... the target id......... 000001301084 227B N/A N/A Alt_path_1 Enable /devices/pci@4.... Ucode Level . Path ........... SCSI Target ...2000/pci@1/fibre-channel@4/IBMtape@3.. you can run the following steps: 1..... Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd Appendix D.......... For example.. device serial number.......................conf file.............4000/lpfc@4/IBMtape@2.... the current enabled status...... . SCSI LUN ...... Path World Wide PN .. such as the instance number for the logical device............. the logical unit number.... SCSI Target ..............Solaris ............. Serial Number ..................... Device Physical Path ..Tape Utility Program (tapeutil) Querying Primary and Alternate Path Configuration (Data Path Failover) You can display the primary and alternate path configuration for all devices with the tapelist utility................. Serial Number ..................... SCSI LUN ..FCR@2/IBMtape@3................. Device Physical Path ........................................... Instance Number ................FCR@2/IBMtape@1........... Path .......... Ucode Level ................. Ucode Level ............. Path World Wide PN ......................................... path type and so on.0 697 7 0 000001300168 04CE 5005076302000127 5005076302800127 Alt_path_1 Enable /devices/pci@1f... It also indicates how many paths are configured for the device.2000/QLGC...... Path Type .... SCSI LUN .. Ucode Level .... Path World Wide PN ....... Path ........... SCSI Target ..................... 685 1 0 000001300168 04CE 5005076302000127 5005076302400127 Primary Enable /devices/pci@1f........ Path World Wide NN ..0 This option shows specific information for each path.... the target id..................... SCSI Target ....... Path ........ Path Type .. SCSI LUN ..............4000/JNI.......... 364 IBM Tape Device Drivers Installation and User’s Guide ........ SCSI Target ............ Ucode Level .................................. Path World Wide NN .........qla@1/IBMtape@1......... Path World Wide NN ............................... You can also display the primary and alternate path configuration for any device running the tapeutil utility and selecting option 54 Query Device Paths............ For example: Path list in the device: Path 0 Path 1 Path 2 Path 3 Current active path: Path 0 Enter path number or <enter> for all of the paths: Instance Number ................ device serial number..................... Instance Number ...... Device Physical Path . the current enabled status............. Path Type . Serial Number ..........2000/QLGC............. Instance Number ...................................................4000/JNI............0 670 3 0 000001300168 04CE 5005076302000127 5005076302400127 Alt_path_3 Enable /devices/
[email protected] 666 1 0 000001300168 04CE 5005076302000127 5005076302800127 Alt_path_2 Enable /devices/pci@1f..... and which path is the current active path.............. Path .................. Path World Wide PN . Serial Number ............ Device Physical Path .qla@1/IBMtape@7........ Path World Wide NN ..................................... Path Type ....... Add the parameter of ″dpf_support″ and turn it off in the path entry in IBMtape. 2. all the available paths for a physical device are enabled. If for some maintenance reason you need to disable a path and do not want to fail over to this path. For example.conf file. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd To enable a path from a disabled state.Solaris . Tape Utility Programs 365 . name="IBMtape" class="scsi" target=3 lun=0. Reload the IBMtape driver module in the kernel and start the daemon: # /usr/sbin/add_drv -m ' 0666 bin bin' IBMtape # /opt/IBMtape/tmd Appendix D. For example.Tape Utility Program (tapeutil) Disable and Enable Primary and Alternate Paths (Data Path Failover) Once you enter the parameter dpf_support in the IBMtape.conf file and install the IBMtape device driver.conf file. name="IBMtape" class="scsi" target=3 lun=0 dpf_support=0. you may run the following steps: 1. you may run the following steps: 1. 2. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 3. Remove the parameter dpf_support=0 from the path entry in IBMtape. Stop the TMD (tape monitor daemon) running on the system and unload the IBMtape driver module from the current kernel: # /opt/IBMtape/tmd -s # /usr/sbin/rem_drv IBMtape 3. Note: If no parameters are specified. The default for this file is ntutil. but the default input file ntutil. Calling ntutil The ntutil program can be called as a command from the command line or from within a shell script: ntutil <-f input-file> <-o output-file> <-t tape-path-special-file-name> <-c changer-path-special-file-name> <-l > <-d > The options are: -f input-file Specifies the input file for batch mode. Changer0 for Windows 200x) to substitute when executing an open (for both batch and interactive mode). If a file is specified. -o output-file -t tape-special-file-name Specifies the tape device special file value (for example.1.OUT.Utility Program (ntutil) Microsoft Windows System . In interactive mode. The results of that command are then presented.Windows . Used only for tool debugging. which are presented to ntutil one by one. lb0.3 for Windows NT. Begins ntutil in batch mode (same as -f. is specified. In batch mode. -c changer-special-file-name Specifies the changer device special file value (for example. tape0) to substitute when executing an open (for both batch and interactive mode).in is used. ntutil operates in interactive mode. you use an editor to create a file that contains ntutil commands.2.in. The special value def_lun_1 specifies that an open uses the default lun 1 associated with the tape-special-file-name.Utility Program (ntutil) The Windows Utility Program (ntutil) allows easy operation of your TotalStorage or Magstar devices and changers. Specifies the output file for batch mode. The default for this file is ntutil. Turns on internal tracing printouts in the output. ntutil will execute in batch mode and read input from this file. a menu is presented to issue one command at a time. The ntutil program can be used for the following purposes: v Help determine if there are hardware or connection problems v Determine which devices are recognized by the device and changer drivers v Force a drive dump v Load new microcode on your drive or changer device v Send SCSI commands to drives and changers v Receive the status of SCSI commands v Obtain sense data for SCSI commands that encounter errors The ntutil program can be run in interactive mode or batch mode. 366 IBM Tape Device Drivers Installation and User’s Guide . It is supported only with the IBM-supplied device drivers. -l -d -b Specifies that an open will open both the tape path special file and the changer path special file (for both batch and interactive mode). ntutil displays a menu of functions that can be used. There are two modes available in interactive mode: v Base mode (LUN0) commands. write v Library mode (LUN0 and LUN1) supports open. Base mode (for example. and write. When in interactive mode. plus medium changer commands such as read element status and move media. Appendix D. close. library functions are available if the Removable Storage Management component of Microsoft Windows 200x is stopped. Note: On Microsoft Windows 200x platforms. read.Windows . it defaults to interactive (or manual) mode. only LUN 0 of the device specified by the tape-path-special-file-name tape0 is accessed) is shown in Figure 88 on page 368. Tape Utility Programs 367 . close. read.Utility Program (ntutil) Interactive Mode When ntutil is called without the -f flag. such as open. The other TotalStorage or Magstar devices must be in Random mode both when started and to operate ntutil in Library mode. This mode allows a developer to interactively issue the operations to be performed. x | Variable settings | ==================== BASE MODE ========================================| tape-special-file-name: tape0 | gp->fd0=-1 gp->fd1=-1 block size=1024 block count=1 | hex block id = 0000000000000000 | return_error_when_fail 1 exit_on_unexpected_result 0 trace_flag 0 | | manual test menu: | =======================================================================| 1: set device special file 2: display symbols | 3: set block size R/W (now !0 fixed) | 5: set return error when fail 6: set/reset trace | 7: set exit on unexpected result 8: Library Mode | =======================================================================| 20: open 21: close | 22: read 23: write | 24: read and display block 25: flush (buffer->media) | 26: read block id 27: erase | 28: locate block id 29: display block data | =======================================================================| 30: write filemark(s) 31: rewind | 32: forward space filemark(s) 33: unload | 34: reverse space filemark(s) 35: load | 36: forward space record(s) 37: return error | 38: reverse space record(s) 39: test unit ready | 43: set media parms (block size) 44: set dev parms (compression)| 46: get device information 47: restore data | 48: get medium information 49: inquiry | 50: poll registered devices | 53: space EOD 54: display message | =======================================================================| 70: system command | =======================================================================| 80: Force Dump 81: Read Dump | 82: Update MicroCode 83: Log Sense | 84: Get Last Sense 85: Get Version | 86: Associative/Persistent WProtect 87: Read/Write Test | 88: List registered devices 89: Get MTDevice info | =======================================================================| 99: return to main menu | =======================================================================| enter selection: | Figure 88.3. tape0. 368 IBM Tape Device Drivers Installation and User’s Guide .x. and LUN 1 specified by the changer-path-special-file-name. Example of Base Mode Library mode (LUN 0 specified by the tape-path-special-file-name. for example. for example.Windows .x.Utility Program (ntutil) Test tool version x.2.1. are accessed) is shown in Figure 89 on page 369. lb0. If the device driver is stopped. if there is one tape device defined on the Windows system. that device is named tape0 when the device driver is started the first time. changer-special-file-name: lb0.Windows . then restarted. the name is tape1.x.Utility Program (ntutil) Test tool version x. Rather. where N is a digit. the next unused name in the operating system is used.2.3 | gp->fd0=-1 gp->fd1=-1 block size=1024 block count=1 | hex block id = 0000000000000000 | return_error_when_fail 1 exit_on_unexpected_result 0 trace_flag 0 | | manual test menu: | =======================================================================| 1: set device special file 2: display symbols | 3: set block size R/W (now !0 fixed) | 5: set return error when fail 6: set/reset trace | 7: set exit on unexpected result 8: Base Mode | =======================================================================| 10: ioctl return library inventory 11: ioctl move medium | 12: ioctl initialize element status 13: ioctl get changer params | =======================================================================| 20: open 21: close | 22: read 23: write | 24: read and display block 25: flush (buffer->media) | 26: read block id 27: erase | 28: locate block id 29: display block data | =======================================================================| 30: write filemark(s) 31: rewind | 32: forward space filemark(s) 33: unload | 34: reverse space filemark(s) 35: load (3590 System Mode) | 36: forward space record(s) 37: return error | 38: reverse space record(s) 39: test unit ready | 43: set media parms (block size) 44: set dev parms (compression)| 46: get device information 47: restore data | 48: get medium information 49: inquiry | 50: poll registered devices | 53: space EOD 54: display message | =======================================================================| 70: system command | =======================================================================| 80: Force Dump 81: Read Dump | 82: Update MicroCode 83: Log Sense | 84: Get Last Sense 85: Get Version | 86: Associative/Persistent WProtect 87: Read/Write Test | 88: List registered devices 89: Get MTDevice info | =======================================================================| 99: return to main menu | =======================================================================| enter selection: | Figure 89. and so on. The device names can be obtained using command 88 (List registered devices) also shown previously. the device must be open. If the device driver is stopped. Example of Library Mode To issue SCSI commands. This behavior continues until the system is restarted. Tape device names have the format tapeN. and then restarted without a reboot.x | Variable settings | ==================== LIBRARY MODE =====================================| tape-special-file-name: tape0. the name is not the same as it was previously. Tape Utility Programs 369 .1.x. Open a SCSI device by issuing option 20 (Open) from library mode as shown previously. For example. such as 0. Batch Mode Batch input files can contain these kinds of statements: v Command v Comment v Delay Appendix D. 1. described in the Microsoft Software Development Kit (SDK). The RC is always 1. Command Device driver function is exercised by command entries in the input file. close: SYNTAX: close for example. close FUNCTION Tested: This command calls the device driver CloseHandle entry point and closes the tape device special file opened previously. device_info FUNCTION Tested: This command calls the device driver GetTapeParameters entry point with an operation of GET_TAPE_DRIVE_INFORMATION.Windows .Utility Program (ntutil) v v v v v Exit Pause Set Symbols System v Type Each type of statement is described in the following section. display_block FUNCTION Tested: 370 IBM Tape Device Drivers Installation and User’s Guide . If the command is successful. This includes information such as ECC. The information is formatted and printed. but leading or embedded blanks are ignored. Supported Command Text Fields The command text specifies the tape operation to perform. and features. The command and command text is case sensitive. default block size. the information returned is in a TAPE_GET_DRIVE_PARAMETERS structure. display_block (data): SYNTAX: display_block for example. compression. Lines that start with a pound sign (#) or a space and blank lines are comments and are ignored. The following sections describe the possible values for these fields. Command statements must be on a single line of the input file. device_info: SYNTAX: device_info for example. command command-text <result-text> Comment This statement is used to execute a tape command and to test the command completion status for an expected result. and block_count for Variable mode. display_message: SYNTAX: display_message for example. the RC shows the total number of bytes transferred. It attempts to erase. find_devices: SYNTAX: find_devices for example. This command transfers n records. It attempts to read from the tape device special file opened previously. Tape Utility Programs 371 . display_message FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of input/output control IOCTL_SCSI_PASS_THROUGH and a CDB[0] of 0xC0 (Display Message). the message is displayed on the operator panel. block_count=2 and records=3. find_devices FUNCTION Tested: This command (which corresponds to the List registered devices command on the interactive menu) searches the following registry key and looks for tape and medium changer device identifiers: "HARDWARE\\DEVICEMAP\\Scsi\\Scsi Port W\\Scsi Bus X\\Target Id Y\\Logical Unit Id Z" Appendix D.Windows . The message alternates between TESTMSG and T E S T unless the Manual mode display message was used previously. If the operation is successful. The amount of data to be read depends on the current settings of the block_size and block_count variables and on the number of records specified. then leave at load point. dump_blocks (read and display blocks): SYNTAX: dump_blocks dump_blocks records = n for example. A record has a length of block_size*block_count for Fixed-Block mode. if block_size=1024. the tape device special file opened previously. The first 16 bytes of each record are printed. erase FUNCTION Tested: This command calls the device driver EraseTape entry point with an operation of TAPE_ERASE_LONG. then three 2048 transfers are done. dump_blocks records = 2 FUNCTION Tested: This command calls the device driver ReadFile entry point. erase: SYNTAX: erase for example. For example. If the operation succeeds. in which case that data is displayed.Utility Program (ntutil) This command displays the data buffer contents for the last read or write transfer. Utility Program (ntutil) It then prints a list of those devices supported by the Windows tape and medium changer device drivers. forward_filemark: SYNTAX: forward_filemark n for example. It attempts to forward space n files on the cartridge in the tape device special file opened previously. forward_record 2 FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_SPACE_RELATIVE_BLOCKS and a count of n.Windows . 372 IBM Tape Device Drivers Installation and User’s Guide . This forces a microcode dump. flush FUNCTION Tested: This command calls the device driver WriteTapemark entry point with an operation of TAPE_FILEMARKS and a count of 0. force_dump FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB[0] of SCSIOP_SEND_DIAGNOSTIC. It attempts to forward space n records on the cartridge in the tape device special file opened previously. flush (buffer to media): SYNTAX: flush for example. get_last_sense FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of OBTAIN_SENSE. This writes the data buffer contents to the tape media of the tape device special file opened previously. This displays the last sense data returned by a sense command. get_last_sense: SYNTAX: get_last_sense for example. force_dump: SYNTAX: force_dump for example. forward_record: SYNTAX: forward_record n for example. forward_filemark 2 FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_SPACE_FILEMARKS and a count of n. If the command is successful. load FUNCTION Tested: This command calls the device driver PrepareTape entry point with an operation of TAPE_LOAD. Tape Utility Programs 373 . inquiry 0 FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB of SCSIOP_INQUIRY. This displays the library device number (in hexadecimal).Utility Program (ntutil) get_mtdevice: SYNTAX: get_mtdevice for example. Specify n=0 to obtain inquiry information from the drive. init_element_status: SYNTAX: init_element_status for example. the information returned is displayed. FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of OBTAIN_MTDEVICE. Only Inquiry page 0 is supported. It attempts to load the tape media into the drive of the tape device special file opened previously. get_version FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of OBTAIN_VERSION. Appendix D. This displays the Windows Device Drivers Version ID string. inquiry: SYNTAX: inquiry n for example. load (3590 System Mode and Ultrium devices): SYNTAX: load for example.Windows . This issues an Initialize Element Status command to the device. get_version: SYNTAX: get_version for example. Specify n=1 to obtain inquiry information from the changer. init_element_status FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an opcode of LIBRARY_AUDIT. get_mtdevice This command is valid for 3590 devices in an automated library only. the information returned is in the TAPE_GET_MEDIA_PARAMETERS structure described in the Microsoft SDK.Windows 2000 and Windows Server 2003 and Windows Server 2008: move_medium stype = n saddr = n dtype = n daddr = n where stype = decimal source address type 2=SE(ChangerSlot). The page_code (xx) is two hexidecimal characters that specify the log sense page to be read.Windows . This reads the log sense page specified by the page code and displays the data. The information is formatted and printed. medium_info FUNCTION Tested: This command calls the device driver GetTapeParameters entry point with an operation of GET_TAPE_MEDIA_INFORMATION. locate_block_id FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_LOGICAL_BLOCK. medium_info: SYNTAX: medium_info for example. move_medium: SYNTAX . 3=IEE (ChangerIEPort).Utility Program (ntutil) locate_block_id: SYNTAX: locate_block_id for example.Windows NT: move_medium saddr = n daddr = n where saddr = decimal source address (moving from) daddr = decimal destination address (moving to) for example. log_sense page_code = 00 FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB[0] of SCSIOP_LOG_SENSE. It attempts to position to the last read_block_id value for the cartridge in the tape device special file opened previously or the block ID set by the set block_id function. log_sense (page_code): SYNTAX: log_sense page_code = xx for example. and write protect. partition count. If the command is successful. move_medium saddr = 11 daddr = 13 SYNTAX . move_medium stype = 2 saddr = 1 dtype = 4 daddr = 0 374 IBM Tape Device Drivers Installation and User’s Guide . 4=DTE (ChangerDrive) saddr = decimal source address (moving from) dtype = decimal target address type (see stype for supported values) daddr = decimal destination address (moving to) for example. The information returned is block_size. y. and Windows Server 2008. Issue a return_lib_inventory_all command to obtain the mapping. FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an opcode of MOVE_MEDIUM.x. If this command is successful.y. It attempts to open a tape device special file for LUN0 and LUN1.x. open: SYNTAX: open <tape-special-file-name> <changer-special-file-name> RW RO where RW means read/write RO means read only The tape-special-file-name is in the form of tapen.x. w is the device SCSI ID. This may also contain the value def_lun_1 in which case the utility will open LUN 1 associated with the tape-special-file-name. the value is assigned by the device driver during the boot process and can be found using the interactive modes option 50 poll registered devices. The mode will be RW.z. the information returned is displayed. and z is the port number where the SCSI adapter resides. The mode will be RW.z. it is in the form Changerx. and so on. the addresses are remapped such that the first element of each type is mapped to 0. y is the adapter SCSI bus (usually 0). supported on Windows NT. FUNCTION Tested: This command calls the device driver CreateFile entry point.. In Windows NT.Windows .z. Windows Server 2003.y. This attempts to move a data cartridge from a source element location to a destination element location inside the library. The changer-special-file-name. and Windows Server 2008.x. Windows Server 2003. x is the changer device LUN (usually 1). and n is a numeric value from 0.Utility Program (ntutil) In Windows 200x. the tape-special-file-name must be specified. The -t and -c options will override tapex and lbw. This value may be specified explicitly in the open statement or overridden using the command-line -t option.x. usually starting with 0. open tapex RW open tapex lbw.z. and so on. This value may be specified explicitly in the open statement or overridden using the command-line -c option. Tape Utility Programs 375 . The -t and -c options will override tapex and lbw. the addresses are remapped such that the first element of each type is mapped to 0. If this value is specified. the second element is mapped to 1. On Windows 2000. These values are assigned during the boot process and can be found using the interactive modes option 50 poll registered devices.x.. where x is a numeric value.z RW means open tapex and if in library mode the changer special file lbw. Issue a return_lib_inventory_all command to obtain the mapping. poll_devices: Appendix D.y. the second element is mapped to 1. is in the form of lbw. In Windows 2000. For example: open RW means open the default tape-special-file-name and changer-special-file-name if in library mode or those special file names specified by the -t and -c options means open tapex and if in library mode the default changer-special-file-name. the source and destination addresses are the decimal equivalents of the hexidecimal Element Addresses described in the appropriate hardware manuals.y. This reads the dump data and writes it to a file specified by dump_name or to a dump0000. read_block_id: SYNTAX: read_block_id for example. FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB[0] of SCSIOP_READ_DATA_BUFF.Utility Program (ntutil) SYNTAX: poll_devices for example. read_dump dump_name = fsc0000 device = 0. poll_devices FUNCTION Tested: This command searches the following registry key: HARDWARE\\DEVICEMAP\\Scsi\\Scsi Port W\\Scsi Bus X\\Target Id Y\\ Logical Unit Id Z for devices supported by the Windows tape and medium changer device drivers. read: SYNTAX: read read records = n for example. if block_size=1024. then three 2048 transfers are done. For example. This command transfers n records. block_count=2 and records=3. read_dump: SYNTAX: read_dump read_dump dump_name=string device=devnum where string is eight characters or less and devnum=0 (for tape) or 1 (for changer) For example. and block_count for Variable mode. Executing this command closes all currently open devices. read records = 2 FUNCTION Tested: This command calls the device driver ReadFile entry point. this command will not be able to query the status of that device.Windows . read_block_id FUNCTION Tested: This command calls the device driver GetTapePosition entry point with an operation of TAPE_LOCICAL_POSITION. If the operation succeeds. It attempts to read from the tape device special file opened previously. The status of all the devices is printed on the screen. It attempts to read the current block ID value for the cartridge in the tape device special file opened previously. The amount of data to be read depends on the current settings of the block_size and block_count variables and on the number of records specified. If another application is using the device. A record has have a length of block_size*block_count for Fixed-Block mode. Dump_name must be 376 IBM Tape Device Drivers Installation and User’s Guide . the RC shows the total number of bytes transferred. This command then attempts to open each of the devices found and issue INQUIRY and TEST UNIT READY SCSI commands to each open device.dmp default file. 3. the information returned is displayed.dmp extension automatically. It attempts to perform 64 KB variable block read operations on the tape device special file until either a filemark or an end of data is detected. return_error_state FUNCTION Tested: This command calls GetLastError. and no data is saved. Rewind the tape. If there is no data on the tape. regardless of error. Set Media Parameters to fixed block 32K. is saved in the file specified. read_write FUNCTION Tested: This command performs the following test on the cartridge in the tape device special file opened previously: 1. 4. There is no RC for this function. It attempts to return information about all the hardware components in a library. Tape Utility Programs 377 .Utility Program (ntutil) eight characters or less. Rewind the tape. 2. return_error: SYNTAX: return_error_state for example. Ntutil adds the . Read the block and compare the data to the data written in step 3. The dump is written into the directory where ntutil was started. Appendix D. If this command is successful. The RC should be ignored in most cases. Write a 32K random data block on tape. because this operation always ends with an error (either filemark detected or end of data detected). the information returned is displayed. If the command is successful. read_write (test): SYNTAX: read_write for example.Windows . refer to the appropriate hardware manuals for a description of the information returned by a read element status command. 5. All the data read. return_lib_inventory_all FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an opcode of LIBRARY_INVENTORY. the command fails. restore_data: SYNTAX: restore_data restore_data file_name=string for example. return_lib_inventory_all: SYNTAX : return_lib_inventory_all for example. For Windows NT. read_data file_name=fsc0000 FUNCTION Tested: This command calls the device driver ReadFile entry point. or DTE (ChangerDrive). v hexidecimal value is a hexadecimal value that indicates the mapped address of the item. blank if not.Utility Program (ntutil) For Microsoft Windows 2000.Windows . It attempts to backward space n files on the cartridge in the tape device special file opened previously. rewind: SYNTAX: rewind for example. v Empty or Full indicates if the element is occupied. Potential values for this field are documented in the ELEMENT_STATUS_abc constants in ntddchgr. the flags field for the element is displayed after the element address. Status is presented when the rewind is complete. reverse_filemark: SYNTAX: reverse_filemark n for example. and Windows Server 2008. and Windows Server 2008. reverse_filemark 2 FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_SPACE_FILEMARKS and a count of n. Note that if a cartridge is in the drive.h. It attempts to backward space n records on the cartridge in the tape device special file opened previously. or IEE (ChangerIEPort). Empty or Full. reverse_record: SYNTAX: reverse_record n for example. reverse_record 2 FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_SPACE_RELATIVE_BLOCKS and a count of n. which is different from using the actual hardware element addresses on Windows NT. It attempts to rewind the tape device special file opened previously. v n is 2. 3. Empty is returned. If tracing is enabled. A remapped inventory is returned where one element is returned per line. rewind FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_REWIND. the RSM must be stopped to issue this command. Windows Server 2003. which indicates SE (ChangerSlot). Addr: hexidecimal value. Each line has the following format: Type: n. or 4. respectively. Windows Server 2003. set_device_parameters (compression): 378 IBM Tape Device Drivers Installation and User’s Guide . This mapped address is used for medium operations on Microsoft Windows 2000. access type on a new line. v access type is set to Access if the element is accessible. a CDB[0] of MODE_SELECT (0x55). set_media_parameters block_size = 0 FUNCTION Tested: This command calls the device driver SetTapeParameters entry point with an operation of SET_TAPE_MEDIA_INFORMATION.device compression On or Off (0 for Off.device block size setting (0 for variable). The block_size value is a required parameter with the command. test_unit_ready: SYNTAX: test_unit_ready n for example. set_device_parameters compression = 0 FUNCTION Tested: This command calls the device driver SetTapeParameters entry point with an operation of SET_TAPE_DRIVE_INFORMATION.Windows . block_size . space_eod FUNCTION Tested: This command calls the device driver SetTapePosition entry point with an operation of TAPE_SPACE_END_OF_DATA. and a mode page of 0x23. compression . The write protect value on the mode page is updated based on the wp parameter. Tape Utility Programs 379 . set_media_parameters (block size): SYNTAX: set_media_parameters block_size = n for example. test_unit_ready 1 FUNCTION Tested: Appendix D.Utility Program (ntutil) SYNTAX: set_device_parameters compression = n for example. The compression value is a required parameter with the command. Refer to the appropriate hardware reference manual for details on Associative and Persistent Write Protect. set_reset_write_protect wp = 1 FUNCTION Tested: This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH. It attempts to space to the end of data on the cartridge in the tape device special file opened previously. any other value On). where wp is: 1 2 3 4 8 0 Set Associative Write Protect Set Persistent Write Protect Set Both Reset Associative Reset Persistent Reset Both space_eod: SYNTAX: space_eod for example. set_reset_write_protect: SYNTAX: set_reset_write_protect wp = x for example. result data=888. If the operation is unsuccessful. This value can be checked on a read command by specifying. unload: SYNTAX: unload for example. 380 IBM Tape Device Drivers Installation and User’s Guide . block_count=2 and records=3. A record has a length of block_size*block_count for Fixed-Block mode. This can be overridden by specifying data=. Specify 1 to send the command to the changer. It attempts to write to the tape device special file opened previously. For example. update_code: SYNTAX: update_code image_name = string for example. the identifier is a unique sequential counter. then three 2048 transfers are done. If the operation succeeds. the default is 1. Each record written has random bytes preceded by an integer identifier.Windows . and block_count for Variable mode. write: SYNTAX: write write records = n write records = n data = m for example. If the data attribute is not specified. If data is specified. If the records attribute is not specified. The amount of data to be written depends on the current settings of the block_size and block_count variables and on the number of records specified.fmr for the file.Utility Program (ntutil) This command calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB[0] of SCSIOP_TEST_UNIT_READY. the record count must be specified. for example. It attempts to rewind and unload the tape device special file opened previously. The file extent must be . if block_size=1024. Specify 0 to send the command to the drive. The filename portion of the image name must be specified and is read from the directory where ntutil was started. write records = 3 data = 888 FUNCTION Tested: This command calls the device driver WriteFile entry point. the RC shows the total number of bytes transferred. unload FUNCTION Tested: This command calls the device driver PrepareTape entry point with an operation of TAPE_UNLOAD. the sense data is displayed. This command transfers n records. update_code image_name = d0i9_430 FUNCTION Tested: This command updates the microcode and calls the device driver DeviceIoControl entry point with an operation of IOCTL_SCSI_PASS_THROUGH and a CDB[0] of SCSIOP_WRITE_DATA_BUFF. Data can be a decimal value from 0–4294967295. A setting of true means ntutil ends by returning an error at the end of the test if any command does not produce a correct expected result as specified in result text. It attempts to write n filemarks on the tape media. n> <err < > <= >= == != n> <cc < > <= >= == != n> set: This statement allows setting of variables that affect how tests are executed. In the case of rc. consider this statement in the input file: command write 1 result rc == -1 err == WRITE_PROTECT This means we will try to write one record to tape and we expect this to fail with return code -1.Windows . The syntax for result text is: < rc < > <= >= == != where: rc = return code from the last command. the command is treated as successful. These can be set using a set statement. write_filemark 2 (write 2 file marks) FUNCTION Tested: This command calls the device driver WriteTapemark entry point with an operation of TAPE_FILEMARKS and a count of n. Further execution of a test case is affected by the current settings of the return_error_when_fail and exit_on_unexpected_result variables. err WRITE_PROTECT. a failure returns -1. set return_error_when_fail = 1 Here are the variables that can be set: return_error_when_fail Can be set to 1 (true) or 0 (false). For example. the operation succeeded. Note: Symbolic values or integers can be used for err. The syntax for a set statement is: set variable = value for example. Tape Utility Programs 381 . data = expected record identifier for a read command. See the appendix on symbolic values for a list of those recognized. If no result text is specified. except as noted in the command section. err = Operating System GetLastError () value for the last command.Utility Program (ntutil) write_filemark: SYNTAX: write_filemark n for example. Supported Result Text Fields The result text on a command statement is used to test completion status for an expected result. Otherwise. Appendix D. 382 IBM Tape Device Drivers Installation and User’s Guide .Utility Program (ntutil) exit_on_unexpected_result Can be set to 1 (true) or 0 (false). type tell operator it's lunch time pause The test stops until a character is typed at the terminal. The syntax for the system statement is: system operation for example. The syntax for the delay statement is: delay value for example. delay 1 system Text following the word system is passed to the system for execution. block_id Can be set to a four byte hexidecimal value (for example. This can be used to show the progress of the test or to prompt for a subsequent pause statement. This value is used on a locate_block_id command. No further lines are read from the input file. writing or set_mode. system dir symbols This statement prints the symbol list that may be used in result text fields. 0001aa03). exit This statement causes immediate termination of the batch test. Can be set to 0 to indicate Variable Block mode. type string for example. the first occurrence of an unexpected result terminates the test. This allows for tests that require delay for mechanical completion before continuing. This allows for tests that require manual intervention. If set to true. block_count Number of blocks or bytes (Variable mode) to transfer on an individual data transfer command.Windows . delay The test stops for n seconds. type Text following the word type is typed on the terminal. Symbolic Values Figure 90 on page 383 shows the values (symbolic error or error number) that can be used for err. block_size Block size to be used for reading. Windows . Tape Utility Programs 383 .Utility Program (ntutil) --------------------------------------------------------------------------------------| Symbolic Error | NT/Win2000| Symbolic Error |NT/Win2000 | | | Error # | | Error # | |-----------------------------|---------------------------------------------|-----------| | ERROR_SUCCESS | 0 | DD_CLEANER_INST | 316 | | ERROR_INVALID_FUNCTION | 1 | DD_MEDIA_NOT_EJECTED | 317 | | ERROR_FILE_NOT_FOUND | 2 | DD_IOPORT_NOT_CONFIG | 318 | | ERROR_PATH_NOT_FOUND | 3 | DD_FIRST_DEST_EMPTY | 319 | | ERROR_TOO_MANY_OPEN_FILES | 4 | DD_END_PHYSICAL_MEDIA | 400 | | ERROR_ACCESS_DENIED | 5 | DD_MEDIA_BLANK | 401 | | ERROR_INVALID_HANDLE | 6 | DD_MEDIA_CORRUPTED | 402 | | ERROR_NOT_ENOUGH_MEMORY | 8 | DD_MEDIA_FAILURE | 403 | | ERROR_BAD_FORMAT | 9 | DD_MEDIA_INCOMPATIBILITY | 404 | | ERROR_INVALID_BLOCK | 10 | DD_SECTOR_RELOCATION | 405 | | ERROR_BAD_ENVIRONMENT | 11 | DD_SECTOR_OUT_OF_RANGE | 406 | | ERROR_INVALID_ACCESS | 12 | DD_WRITE_PROTECT | 407 | | ERROR_INVALID_DATA | 13 | DD_CLEAN_MEDIA | 408 | | ERROR_OUTOFMEMORY | 14 | DD_MEDIA_FAULT | 409 | | ERROR_INVALID_DRIVE | 15 | DD_CLEANING_COMPLETE | 410 | | ERROR_WRITE_PROTECT | 19 | DD_LOGICAL_END_OF_MEDIA | 411 | | ERROR_BAD_UNIT | 20 | DD_MEDIA_NOT_PRESENT | 412 | | ERROR_NOT_READY | 21 | DD_BEGINNING_OF_MEDIA | 413 | | ERROR_BAD_COMMAND | 22 | DD_ERASE_FAILURE | 414 | | ERROR_CRC | 23 | DD_WRITE_TO_WRITTEN_WORM | 415 | | ERROR_HANDLE_EOF | 38 | DD_WRONG_LENGTH_BLOCK | 416 | | ERROR_NOT_SUPPORTED | 50 | ERROR_IO_INCOMPLETE | 996 | | ERROR_DEV_NOT_EXIST | 55 | ERROR_IO_PENDING | 997 | | ERROR_ALREADY_ASSIGNED | 85 | ERROR_NOACCESS | 998 | | ERROR_INVALID_PARAMETER | 87 | ERROR_CANTOPEN | 1011 | | ERROR_OPEN_FAILED | 110 | ERROR_CANTOPEN | 1011 | | ERROR_INSUFFICIENT_BUFFER | 122 | ERROR_CANTREAD | 1012 | | ERROR_INVALID_NAME | 123 | ERROR_CANTWRITE | 1013 | | ERROR_BUSY_DRIVE | 142 | ERROR_END_OF_MEDIA | 1100 | | DD_NO_SENSE | 200 | ERROR_FILEMARK_DETECTED | 1101 | | DD_DEVICE_DRIVER_FAILURE | 201 | ERROR_BEGINNING_OF_MEDIA | 1102 | ERROR_SETMARK_DETECTED | 1103 | | DD_EEPROM_FAILURE | 202 | | DD_MANUAL_INTERVENTION | 203 | ERROR_NO_DATA_DETECTED | 1104 | | DD_RECOVERED_ERROR | 204 | ERROR_PARTITION_FAILURE | 1105 | | DD_SCSI_ADAPTER_ERROR | 205 | ERROR_INVALID_BLOCK_LENGTH | 1106 | | DD_SCSI_ERROR | 206 | ERROR_DEVICE_NOT_PARTITIONED | 1107 | | DD_SCSI_BUSY | 211 | ERROR_UNABLE_TO_LOCK_MEDIA | 1108 | | DD_ILLEGAL_REQUEST | 207 | ERROR_UNABLE_TO_UNLOAD_MEDIA | 1109 | | DD_COMMAND_ABORTED | 208 | ERROR_MEDIA_CHANGED | 1110 | | DD_HARDWARE_MICROCODE | 209 | ERROR_BUS_RESET | 1111 | | DD_UNIT_ATTENTION | 210 | ERROR_NO_MEDIA_IN_DRIVE | 1112 | | ERROR_MORE_DATA | 234 | ERROR_IO_DEVICE | 1117 | | DD_CARTRIDGE_ENTRY_FAILURE | 300 | ERROR_TOO_MANY_LINKS | 1142 | | DD_CARTRIDGE_LOAD_FAILURE | 301 | | | | DD_CARTRIDGE_IN_FAILED_DRIV| 302 | | | | DD_CAROUSEL_NOT_LOADED | 303 | | | | DD_CHANGER_FAILURE | 304 | | | | DD_DRIVE_FAILURE | 305 | | | | DD_DRIVE_OR_MEDIA_FAILURE | 306 | | | | DD_ENTRY_EXIT_FAILURE | 307 | | | | DD_ENTRY_EXIT_NOT_PRESENT | 308 | | | | DD_LIBRARY_AUDIT | 309 | | | | DD_LIBRARY_FULL | 310 | | | | DD_MEDIA_EXPORT | 311 | | | | DD_SLOT_FAILURE | 312 | | | | DD_SLOT_OR_MEDIA_FAILURE | 313 | | | | DD_SOURCE_EMPTY | 314 | | | | DD_DESTINATION_FULL | 315 | | | ---------------------------------------------------------------------------------------- Figure 90. Symbolic Values Appendix D. 01 YES PRIMARY Changer0 0000000T003904E5 YES 03. you may use the Windows utility program ntutil.05. One of them is marked as “Primary”.00 03. For Changer0. choose option “get tape bus info”.01.04.00 03.01. The other Tape0s that are not marked as Primary are alternate paths for Tape0. Open a tape library from ntutil library mode. Tape2 does not have failover enabled. The other Changer0s that are not marked as Primary are alternate paths for Changer0.01. and 3 have failover enabled. Tape0. The path with the SCSI address 03.01.01.01. Changer0 and Changer1 have failover enabled. There are one path for Changer1 and two paths for Changer0.00 03.01 YES Changer2 0000000T00361234 NO 03. choose option “get changer bus info”. If you have multiple paths configured for Changer0.01.05. lists of multiple Tape0s are output.00. The following is an example of the output of “get changer bus info” option from ntutil.03. Tape3 has two paths configured.08. the path with SCSI address 03.07.01 is the primary path.07.00 03.02. DEVICE NAME SERIAL FAILOVER SCSI ADDRESS ACTIVE PRIMARY ------------------------------------------------------------------------Changer1 0000000T00390401 YES 03. and Changer2 does not have failover enabled. you may use the Windows utility program ntutil. lists of multiple Changer0s are output. DEVICE NAME SERIAL FAILOVER SCSI ADDRESS ACTIVE PRIMARY ------------------------------------------------------------------------Tape1 Tape2 Tape3 Tape3 Tape0 000001300486 1200019801 000001350051 000001350051 000001365066 YES NO YES YES YES 03.01. If you have multiple paths configured for Tape0.01.01.Utility Program (ntutil) Querying Primary and Alternate Path Configuration (Control Path Failover) To check if the control path failover has been enabled in the device driver and display the primary and alternate paths. and the path with SCSI address 03. Each one is associated with a different bus address.01.01 is an alternate path.01.00 is an alternate path.01 YES PRIMARY Querying Primary and Alternate Path Configuration (Data Path Failover) To check if the data path failover has been enabled in the device driver and display the primary and alternate paths. and the path with SCSI address 03.00. The following is an example of the output of this option from ntutil.00. Each one is associated with a different bus address. Open a tape library from ntutil base mode. 1.01.01.00 YES YES YES YES YES PRIMARY PRIMARY PRIMARY PRIMARY 384 IBM Tape Device Drivers Installation and User’s Guide .03.01 YES PRIMARY Changer0 0000000T003904E5 YES 03.00 is the primary path. One of them is marked as “Primary”.Windows . ibm.tar setld -l RasUtil. Query Procedure You can determine if the IBM RAS Utility Program kit is installed on the system by using the following command.kit.Tru64 . remove the old version first.x.x.com/storage/devdrvr/Tru64 After you have downloaded the RasUtil kit from the FTP site. issue: IBMrasutil -h Uninstalling The IBM RAS Utility Program can be uninstalled by using the setld command: setld -d IBMRASxxx Update Procedure To update the RasUtil kit to a newer version.x. Tape Utility Programs 385 . 3581 and 3583 Tape Libraries v IBM TotalStorage Enterprise 3590 Tape Drive Models E11 or H11 (Rack Mount with ACF) v IBM TotalStorage Enterprise 3590 Tape Drive Models E1A or H1A (3494 Tape Library Models) Installation Procedure from the Device Driver FTP Site If you want to download the RasUtil kit from the FTP site. setld -i|grep IBMRAS To display the RasUtil product kit’s fileset and the located directory.x. The following IBM devices are supported: v IBM Ultrium LTO1 tape drive inIBM System Storage TS3500. setld -v IBMRASxxx Appendix D. enter this FTP address: ftp://ftp.x. enter: setld -i IBMRASxxx Verify Procedure Use this command to verify the existence of the installed RasUtil program. untar the kit first and then run the setld command to install: tar -xvf RasUtil.x.RAS Utility Program (IBMrasutil) IBMrasutil is a RAS utility program which allows the operator to obtain device dumps from IBM tape and medium changer devices for diagnostic purposes.software. The setld -v command executes any V phase processing included in the subset control program except during installation.RAS utility program (IBMrasutil) Tru64 System . use vi or some other text editor to edit the . setld -d IBMRASxxx then follow the above installation steps to install the new version. To find more information on how to execute the IBM RAS utility program. It is also used to update microcode on the IBM tape and medium changer devices.kit After installing the IBM RAS utility program.profile file to add the /usr/opt/RASUTIL/bin to the search path. Invoke the IBMrasutil command from the Tru64 command line or from within a shell script. For example: IBMrasutil -f /dev/ntape/tape7 -M 2360. Device is the name of the device special file (for example. The program prompts you to enter a device special file name. /dev/ntape/tape7) 2. You must open a device before you can issue any RAS utility subcommands. 4. If only the -f option is issued. the interactive mode is invoked.Tru64 . Command-Line Options -D filename Read device dump information and output it into a file specified by the filename. If the -f option is not issued. The syntax for the command-line mode of the RAS utility program is: IBMrasutil -f Device -Option Filename Note: 1. the program queries and displays the Model Name.bin 386 IBM Tape Device Drivers Installation and User’s Guide . For example: IBMrasutil -f /dev/ntape/tape7 -D DriveDump.log -M filename Load the microcode from the specified file to the device.RAS utility program (IBMrasutil) Interactive Mode The interactive mode for the RAS utility program can be invoked from the command line by using the IBMrasutil command. Command-Line Mode The command-line mode for the RAS utility program (IBMrasutil) provides the same basic RAS utility commands as the interactive mode. Filename for input or output operations 3. the interactive mode is invoked. Serial Number and the Firmware level of the device. If you enter the IBMrasutil command without any arguments. A.Notices References in this publication to IBM products. Evaluation and verification of operation in conjunction with other products. in writing. except those expressly designed by IBM. NY 10504-1785 U. This information could include technical inaccuracies or typographical errors. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. is the user’s responsibility. IBM may have patents or pending patent applications covering subject matter in this document. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. MERCHANTABILITY. BUT NOT LIMITED TO. these changes are incorporated in new editions of the publication. Any references to an IBM program or other IBM product in this publication is not intended to state or imply that only IBM’s program or other product may be used. or services do not imply that IBM intends to make these available in all countries (or regions) in which IBM operates. or both: AIX AIX 5L FICON HyperFactor i5/OS © Copyright IBM Corp. EITHER EXPRESS OR IMPLIED. OR FITNESS FOR A PARTICULAR PURPOSE. The following paragraph does not apply to the United Kingdom or any other country (or region) where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND. programs. Changes are periodically made to the information herein. Any functionally equivalent program that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM product. 2009 IBMLink Magstar Micro Channel Netfinity POWER5 RS/6000 S/390 StorageSmart System i® System p System z Tivoli TotalStorage Virtualization Engine xSeries 387 . You can send license inquiries. INCLUDING. IBM may make improvements and/or changes in the product(s) and/or program(s) described in this publication at any time without notice. Some states (or regions) do not allow disclaimer of express or implied warranties in certain transactions. The furnishing of this document does not give you any license to these patents.S. other countries (or regions). 2007. therefore. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. this statement may not apply to you. product. and service names may be trademarks or service marks of others. other countries (or regions).iSeries IBM ProtecTIER pSeries System Storage System x z9 zSeries Adobe and Acrobat are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. and/or other countries. UNIX is a registered trademark of The Open Group in the United States and other countries (or regions). other countries (or regions). and Windows 2000 are trademarks of Microsoft Corporation in the United States. or both. Linux is a registered trademark of Linus Torvalds in the United States. Itanium. Java and all Java-based trademarks are trademarks of Sun Microsystems. or both. Other company. in the United States. other countries. Intel. and Pentium are trademarks of Intel Corporation in the United States. Inc. Microsoft. Windows. Windows NT. or both. other countries. 388 IBM Tape Device Drivers Installation and User’s Guide . or both. and Device Driver Parameters 26 AIX 3494 Enterprise Tape Library Installation Instructions 209 Configuring Library Manager Control Point 211 configuring the 3490E or Enterprise Tape System 3590 tape drive 210 configuring the serial port 210 Connecting the TotalStorage Enterprise Tape Library 209 deconfiguring the Library Manager Control Point 215 defining tape libraries to the daemon 210 installation procedure 209 loading the daemon 214 uninstall procedure 215 Problem Determination 215 daemon trace facility 216 device driver trace facility 216 error logging 215 Product Requirements data flow 208 hardware requirements 209 software requirements 209 Special Files 215 AIX 3494 Enterprise Tape Library Driver Library Driver Information TotalStorage Virtual Tape Server Subsystem Attachment 208 AIX device parameters 50 AIX microcode 317 AIX System testing 304 3494 Enterprise tape library attachment test 305 A about data encryption 15 AIX 39 Device and Volume Information Logging 41 log file 42 tape log utility 42 Dynamic Load Balancing 14 Installation and Configuration Instructions deconfiguring the 3490E. 2009 389 . 22 Purpose 9. 3590. 7331.Index Numerics 3494 Enterprise Tape Library Driver Library Driver Information 201 driver message queue 202 Library Manager event notification 201 operation complete notification 202 software interface 201 synchronous and asynchronous operations 202 TotalStorage Virtual Tape Server Subsystem Attachment 203 unsolicited notification 202 volume categories 202 3494 Enterprise Tape Library Support mtlib command 190 Programs MTEVENT program 201 MTLIB 190 Tape Library Support Programs 189 AIX (continued) Problem Determination (continued) error log templates 43 error logging 43 trace facility 45 Special Files 32 Special Files for 3490E. Magstar MP. 3590. Media. or 7337 medium changer devices 33 System-Managed Encryption 39 Tape Drive Service Aids 46 create an FMR tape 49 Detailed Description 47 error log analysis 48 force microcode dump 47 microcode load 48 read dump 47 reset drive 49 Tape Drive. Magstar MP. 7336. 21 Software Requirements 24 Performance Considerations 49 Before Calling Support 50 common utilities 50 data path 49 Tape Drive. or 7332 tape devices 32 Special Files for 3575. 7331. 7334. 7336. or 7332 tape device 26 deconfiguring the 3575. 7334. or 7337 medium changer device 26 installation procedure 25 preinstallation considerations 25 uninstall procedure 26 path failover and Failover Support configuring and unconfiguring primary and alternate devices 39 querying primary and alternate path configuration 39 path failover Support 37 primary and alternate paths 38 Path Failover Support configuring and unconfiguring path failover support 38 Persistent Naming Support 34 Problem Determination 41 ATRC utility 46 automatic dump facility for 3590 and Magstar MP tape drives 45 detail data 44 error labels 43 © Copyright IBM Corp. and Device Driver Parameters alternate pathing 27 autoloading 27 Automatic Cartridge Facility Mode 32 block size 28 buffered mode 29 capacity scaling 31 compression 29 configuration parameters 27 emulate autoloader 28 fail degraded media 29 logging 29 logical write protect 31 maximum size of log file 29 media parameters 31 new logical name 30 read error recovery time 30 record space mode 30 rewind immediate 30 trailer labels 30 volume ID for logging 32 Tape Utility (tapeutil) Program 321 Automatic Cartridge Facility (ACF) Mode 331 Block Size and SCSI Transfer Size 331 Capacity Scaling 332 command-line interface 322 Configuration Parameters 331 General Subcommands 323 interactive interface 322 Logical Write Protect 332 Medium Changer Subcommands 325 Reserve and Release Commands 333 Service Aid Subcommands 330 Tape Subcommands 327 AIX (continued) Tape Utility (tapeutil) Program (continued) Volume ID for Logging 334 Using Dump Support 41 dump device commands 41 AIX (Atape) Installation and Configuration Instructions 24 configuring tape and medium changer devices 25 Installation Procedure 25 Introduction and Product Requirements 21 Data Flow 22 Hardware Requirements 22 Product Requirements 9. Media. 2007. or 7337 tape medium changer 8 Magstar MP 3570 7 Magstar MP 3575 tape library 7 drive dump 40 E EKM server logs 40 emulation 205 Encryption 9 encryption key manage configuration file 18 error logging 40 F failover 19 field support 40 G general information 15 H HP-UX Installation and Configuration Instructions 56 HP-UX (ATDD) Configuration Parameter Definitions 73 device-specific parameters 73 driver-specific parameters 75 Install. 7336. 7334.AIX System testing (continued) medium changer device attachment test 304 tape device attachment test 304 AIX System-Managed Encryption System-Managed Encryption 39 Application-Managed Tape Encryption 15 Application-Managed Tape Encryption Setup Tasks 17 B bulk rekey 20 C Checklist 16 Comments xiv configuration 17. 40. Uninstall. 333 connectivity 40. and Configuration create hardware path entry 69 determine drive hardware path for 3581 68 determine drive hardware paths for 3580 and 3583 with fibre channel attachment 68 determine drive hardware paths for 3583/3584 Tape Libraries with SCSI attachment 68 Installation and Configuration for DLKM PCI Drivers 56 Installation and Configuration for PCI Drivers 60 command sequence information 57 copy software to software depot 60 create device-specific configuration entries (optional) 59 create drive configuration file. 333 CPF commands 339 D Data Path Failover 9 device driver configuration 39 device drivers Attachment to open systems servers 1 Device drivers Attachment to open systems servers 3490E tape subsystem 7 7331. if required 57 create hardware path entry 58 determine device hardware path for IBM tape drives 58 install driver manually 60 install the ATDD software 60 Overview of the Installation Process 56 power off tape drives 59 Preinstallation considerations 57 Installation and Configuration for Precision Bus Drivers 64 adding a tape device using currently installed ATDD 72 copy software to software depot 70 create configuration file 65 create device-specific configuration entries (optional) 69 create hardware path entry 69 determine device hardware path for 3590 65 determine device hardware path for Magstar MP 3570 tape subsystem 66 determine device hardware path for Magstar MP 3575 tape libraries 67 install the ATDD software 71 other administrative tasks 73 power off tape drives 70 Preinstallation Considerations 64 review ATDD README file 71 Persistent Naming Support 78 Product Requirements 53 ATDD implementation 54 data flow 53 hardware requirements 54 software interface to device driver 56 software requirements 55 HP-UX (ATDD) (continued) Special Files 76 Supported Configurations 73 modifying configuration parameters 75 Tape Utility Program (tapeutil) copy software to software depot 335 hardware requirements 335 install manually 335 install the product 336 other administrative tasks 336 review tapeutil README file 336 tapeutil command-line interface 338 tapeutil implementation 335 tapeutil interactive interface 337 uninstalling the software 336 Using tapeutil 337 tapeutil service commands 338 Troubleshooting 83 Atdd_d log daemon 85 error logging 83 Problems and Solutions 87 Support_info script 84 tracing facility 84 HP-UX (ATDD) basic SCSI commands 338 HP-UX (ATDD) flag description 340 HP-UX (ATDD) medium changer commands 339 HP-UX (ATDD) tape drive commands 339 HP-UX 3494 Enterprise Tape Library Product Requirements Compatibility 218 data flow 217 hardware requirements 218 software compatibility 219 software requirements 218 HP-UX 3494 Enterprise Tape Library Driver Installation Instructions 219 adding or deleting entries in the library device 222 command sequence information 219 connecting the TotalStorage Enterprise tape library 221 copy software to depot 220 defining the library device to lmcpd 221 install manually 220 install the product 220 installation overview 219 other administrative tasks 222 uninstall procedure 222 Problem Determination 222 daemon trace facility 223 error logging 223 HP-UX microcode 318. 335 HP-UX System testing 306 3494 Enterprise tape library attachment test 307 autochanger device attachment test 306 tape device attachment test 306 390 IBM Tape Device Drivers Installation and User’s Guide . 93 software requirements 94 Special Files 105 Special Files for medium changer device 105 Special Files for tape device 105 Tape Drive Service Aids 119 Detailed Description 119 force drive dump 119 load microcode 119 read dump 119 reset drive 119 Tape Drive.I Introduction 1 ITDT Accessing 257 Introduction and Product Requirements Purpose 256 Purpose 255 L library requirements 15 Library-Managed Tape Encryption 16 libsmc extension 205 Linux 111 System-Managed Encryption 111 Linux (lin_tape) Installation and Configuration Instructions 94 components created during installation 95 Configuring Tape and Medium Changer Devices 97 conventions used 94 installation procedure 95 querying installed package 96 uninstall procedure 100 update procedure 96 verifying/updating installation 97 Introduction and Product Requirements 91 Product Requirements Data Flow 91 hardware requirements 92. 332 R Related Information ix 3447 and 7337 Digital Linear Tape Library xiii 3490E Tape Subsystem xii 3592 Tape System ix Additional Information xiv AIX xi HP-UX xi IBM 7331 8mm Tape Library xiii IBM 7332 4mm DDS-2 Tape Cartridge Autoloader xiii IBM 7332 Model 220 External 4mm Tape Autoloader xiii IBM 7334 8mm Tape Library xiii IBM 7336 4mm Tape Library xiii IBM TotalStorage Enterprise Tape System 3590 xiii IBM TotalStorage UltraScalable Tape Library 3584 x IBM TotalStorage Ultrium External Tape Drive 3580 xi IBM TotalStorage Ultrium Scalable Tape Library 3583 xii IBM TotalStorage Ultrium Tape Autoloader 3581 xi IBM TotalStorage Ultrium Tape Library 3582 xii Linux xi Magstar MP 3570 Tape Subsystem xii Magstar MP 3575 Tape Subsystem xii Microsoft Windows xi SGI (Silicon Graphics) xiv Solaris xi TotalStorage Enterprise Automated Tape Library 3494 xii Tru64 xiv requirements library 15 tape 15 M managing encryption 15 Managing Microcode on the Tape Drive 317 Microsoft Windows microcode 318 Microsoft Windows System testing 312 3494 Enterprise tape library attachment test 313 autochanger device attachment test Windows NT only 312 tape device attachment test 312 S sample configuration file 18 sense data 40 server logs 40 SGI IRIX 3494 Enterprise Tape Library Installation Instructions 251 configuring the serial port 252 connecting the Enterprise tape library 252 defining the library device to LMCPD 253 installation procedure 251 problem determination 254 starting the Enterprise tape library daemon 254 uninstall procedure 251 Index N Notices 387 O Online access 301 P Path Failover 9 Automatic Failover 13 Load Balancing 13 391 . Media. and Device Driver Parameters 100 changeable parameters 102 configuration parameters 100 nonchangeable parameters 101 Tape Utility Program (IBMtapeutil) 345 Automatic Cartridge Facility (ACF) Mode 353 Block Size and SCSI Transfer Size 353 command-line mode 345 Configuration Parameters 353 Create Special Files 354 General Subcommands 346 interactive mode 345 Medium Changer Subcommands 351 Reserve and Release Commands 353 Linux (lin_tape) (continued) Tape Utility Program (IBMtapeutil) (continued) Service Aid Subcommands 352 Tape Drive Service Aids 354 Tape Subcommands 347 Linux 3494 Enterprise Tape Library Installation Instructions 226 adding or deleting entries in the library device 228 connecting TotalStorage Enterprise 3494 tape library 226 defining the library device to atldd 227 installation procedure 226 uninstall procedure 228 Problem Determination 229 daemon trace facility 229 error logging 229 Product Requirements data flow 224 hardware requirements 225 software requirements 225 Linux Enterprise Installation Instructions querying the installed package 228 updating procedure 228 verifying the install/update 228 Linux microcode 318 Linux System-Managed Encryption System-Managed Encryption 111 Linux verification testing 308 3494 Enterprise tape library attachment test 309 medium changer device attachment test 308 tape device attachment test 308 path failover support library control path failover 78 Q querying drive configuration 40. and Configuration Configuration Parameters 136 preinstallation considerations 125 Introduction and Product Requirements 121 Persistent Naming Support 145 Product Requirements and Compatibility 122 Data Flow 121 hardware requirements 122 software requirements 124 Service and Diagnostic Aids 152 Basic SCSI Commands 358 downloading device microcode 361 forcing and storing device diagnostic dump 362 functional verification 152 Medium Changer Commands 358 problem determination 153 Service Commands 358 setting the IBM_trace level 156 Tape Drive Commands 358 tape/medium changer utility program 357 tracing facility 154 Special Files 142 device behaviors 143 file naming conventions 144 Solaris 3494 Enterprise Tape Library Installation Instructions 232 adding or deleting entries in the library 234 configuring the serial port 233 connecting the Enterprise tape library 233 defining the symbolic name to the lmcpd 233 preinstallation considerations 232 uninstall procedure 235 Problem Determination 235 daemon trace facility 235 error logging 235 Product Requirements data flow 230 Solaris 3494 Enterprise Tape Library (continued) Product Requirements (continued) hardware requirements 231 software compatibility 232 software requirements 232 Solaris flag description 359 Solaris System testing 310 3494 Enterprise tape library attachment test 311 autochanger device attachment test 310 tape device attachment test 310 Solaris System-Managed Encryption System-Managed Encryption 150 StorageSmart by IBM Ultrium device drivers Attachment to open systems servers Ultrium Products 6 Sun Solaris microcode 318 Supported Hardware 9 System-Managed Encryption 39. 180 system-managed encryption configuration 17 System-Managed Tape Encryption 16 Tru64 3494 Enterprise Tape Library (continued) Installation Instructions (continued) uninstall procedure 247 Problem Determination 247 daemon trace facility 248 error logging 248 Product Requirements data flow 243 hardware requirements 244 software requirements 244 Tru64 Enterprise Installation Instructions querying the installed package 247 updating procedure 246 verifying the install/update 247 Tru64 System testing 314 3494 Enterprise tape library attachment test 315 medium changer device attachment test 314 tape device attachment test 314 U Ultrium device drivers Attachment to open systems servers 3580 Ultrium Tape Drive 6 3581 Ultrium Tape 2U Autoloader 6 3581 Ultrium Tape Autoloader 6 3582 Ultrium Tape Library 5 3583 Ultrium Scalable Tape Library 5 3584 UltraScalable Tape Library 5 T Tape Utility (tapeutil) Program 321 testing data encryption configuration 40.SGI IRIX 3494 Enterprise Tape Library (continued) Introduction data flow 249 hardware requirements 250 software requirements 250 SGI/IRIX System testing 316 3494 Enterprise tape library attachment test 316 SMIT panels 39 Solaris 150 System-Managed Encryption 150 Solaris (IBMtape) Installation and Configuration Instructions 124 Adding or Removing Devices 139 installing and updating IBMtape 125 preventing conflicts with other device drivers 125 removing IBMtape 139 Installation. 333 timeout value 19 TotalStorage device drivers Attachment to open systems servers 3494 Tape Library 6 3590 TotalStorage tape drive 7 Virtual Tape Server 7 Trademarks 387 Tru64 Installation and Configuration Instructions 385 Command-Line mode 386 Command-Line options 386 Installation procedure from the device driver ftp site 385 Interactive mode 386 Query procedure 385 uninstall procedure 385 Update procedure 385 Verify procedure 385 Introduction and Product Requirements 185 Hardware Requirements 185 Product Requirements 185 Purpose 185 Setting up the environment 185 Software Requirements 185 Tru64 3494 Enterprise Tape Library Installation Instructions 245 adding or deleting entries in the library device 246 connecting TotalStorage Enterprise Tape Library 3494 245 defining the library device to atldd 245 installation procedure 245 V Verifying device attachment 303 W Windows 180 System-Managed Encryption 180 Utility Program (ntutil) 366 batch mode 369 calling ntutil 366 command 370 comment 370 interactive mode 367 supported command text fields 370 supported result text fields 381 symbolic values 382 Windows 3494 Enterprise Tape Library Installation Instructions 238 adding or deleting library on the service 240 connecting the 3494 Enterprise tape library 239 defining the symbolic name to the service 240 installation procedure 238 uninstall procedure 241 392 IBM Tape Device Drivers Installation and User’s Guide . 111. 150. Removal. Windows 3494 Enterprise Tape Library (continued) Problem Determination daemon trace facility 242 Product Requirements data flow 236 hardware requirements 237 software requirements 237 Windows Device Driver Device Driver Management 173 disable procedure 177 installation overview 174 installation procedures 174 removal procedure 177 uninstalling the device drivers 177 Introduction and Product Requirements 159 Product Requirements software requirements 161 Windows NT Device Driver Management installation overview 161 installation procedure 162 manual starting and stopping procedures 172 removal procedure 168 Installation and Configuration Instructions Adding or Removing Devices 161 Product Requirements 161 Windows System-Managed Encryption System-Managed Encryption 180 Windows Utility Program (ntutil) Batch Mode poll_devices 375 Utility Program (ntutil) 366 Index 393 . 394 IBM Tape Device Drivers Installation and User’s Guide . GC27-2130-07 We appreciate your comments about this publication. organization. or your authorized remarketer. please contact your IBM branch office.Readers’ Comments — We’d Like to Hear from You IBM Tape Device Drivers Installation and User’s Guide Publication No. you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. When you send comments to IBM. Send your comments to the address on the reverse side of this form. accuracy. For technical questions and information about products and prices. Comments: Thank you for your support. your IBM business partner. subject matter. please fill in the following information: Name Company or Organization Phone No. If you would like a response from IBM. Please comment on specific errors or omissions. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. Address E-mail address . IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. or completeness of this book. ___________________________________________________________________________________________________ Readers’ Comments — We’d Like to Hear from You GC27-2130-07 Cut or Fold Along Line Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 40 ARMONK. NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE International Business Machines Corporation Information Development Department GZW 9000 South Rita Road Tucson. Arizona 85775-4401 _________________________________________________________________________________________ Fold and Tape Please do not staple Fold and Tape GC27-2130-07 Cut or Fold Along Line . . Printed in USA GC27-2130-07 . Spine information: IBM Tape Device Drivers IBM Tape Device Drivers Installation and User’s Guide . Documents Similar To IBM_Tape_Driver_IUGSkip carouselcarousel previouscarousel nextNVM Express SCSI Translation Reference 1 1 GoldSpeech Recognition Server-GlenayreIBM Tape Device DriversVsp 41 Upgrade Guide10.1.1.60Chapter 7 - v2.208 - Cool Blue - Brand ManagerExamReal.IBM.000-451.v20131011.80q.pdfConfiguring MPIOYotta Mini Hardware V1_1Appendix DIBM Storwize V7000 UnifiedComputer Hardware Servicing Lecturest11 Scsi Device Discovery ProcedureBio Rad Fluor-s ManualSathaye College,FybmsIs ComponentsHyundai LCD-TFT Q74A_SERVICE_MANUALmapreduceReplOpenvms Cluster_c Abb Pcm600 Fact Sheet 0.3InfoIRJET-Paper on Customer Care Unit For Shopping Mallhard diskComputer System ArchitectureSg ChainingHowto Dynamically Add a New LUN to SDD Multipath 460562ReportTogaGrade 7 - Activity Sheet.docxBest Books About Computer HardwareProgramming Arduino with LabVIEWby Marco Schwartz8051 Microcontroller: An Applications Based Introductionby David Calcutt, Frederick Cowan, and Hassan ParchizadehStudents' Guide to Information Technologyby Roger CarterArduino Essentialsby Francis PereaInternet of Things with Arduino Blueprintsby Pradeeka SeneviratneRaspberry Pi For Dummiesby Sean McManus and Mike CookFooter MenuBack To TopAboutAbout ScribdPressOur blogJoin our team!Contact UsJoin todayInvite FriendsGiftsLegalTermsPrivacyCopyrightSupportHelp / FAQAccessibilityPurchase helpAdChoicesPublishersSocial MediaCopyright © 2018 Scribd Inc. .Browse Books.Site Directory.Site Language: English中文EspañolالعربيةPortuguês日本語DeutschFrançaisTurkceРусский языкTiếng việtJęzyk polskiBahasa indonesiaSign up to vote on this titleUsefulNot usefulYou're Reading a Free PreviewDownloadClose DialogAre you sure?This action might not be possible to undo. Are you sure you want to continue?CANCELOK