HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive... Product manual

unix
configuration
guide
hp ultrium drives
technical reference manual
generation 2 SCSI and FC drives
volume 5: unix configuration guide
Part Number: C7379–90900 Volume 5
Edition 5.1, July 2003

2
Notice
The information contained in this
document is subject to change
without notice.
Hewlett-Packard makes no
warranty of any kind with regard
to this material, including, but not
limited to, the implied warranties of
merchantability and fitness for a
particular purpose. Hewlett-Packard
shall not be liable for errors
contained herein or direct, indirect,
special, incidental or consequential
damages in connection with the
furnishing, performance, or use of
this document.
Revision History
This document contains proprietary
information which is protected by
copyright. All rights reserved. No
part of this document may be
photocopied, reproduced or
translated to another language
without the prior written consent of
Hewlett-Packard.
© Copyright 2001–2003 by
Hewlett-Packard Limited
Version Date Changed Pages
Edition 1 Feb 2001 All
Edition 2 Mar 2002 Reordering. Removal of pass-through functionality. Changes to HP
chapter (update of ioscan output, use of sam to add stape and device
files), Linux chapter (use of sam to add device files), Sun chapter (using
seek and tell), verification chapter (<archive name> changed to <device
file>
Edition 4 Jun 2002 Updated for Generation 2 Ultrium drives. Now only includes supported
and tested platforms. Extra information added to HP-UX, Sun and Linux
chapters.
Edition 5.1 Jul 2003 Generation 2 SCSI and FC drives only. Support for Silicon Graphics
removed. Other minor changes.
This document is frequently revised and updated. To find out if there is a
later version, please ask your HP OEM Representative.

3
Related Documents
The following documents provide additional information:
Documents Specific to HP Ultrium Drives
3Software Integration Guide, volume 2 of the HP Ultrium Technical
Reference Manual
3The SCSI Interface, volume 3 of the HP Ultrium Technical Reference
Manual
3Specifications, volume 4 of the HP Ultrium Technical Reference Manual
3HP Ultrium Configuration Guide, volume 5 of the HP Ultrium Technical
Reference Manual
3Background to Ultrium Drives, volume 6 of the HP Ultrium Technical
Reference Manual
3HP Ultrium Technology White Paper, which describes the features and
benefits of HP Ultrium drives
Please contact your HP supplier for copies.
Documentation Map
The following will help you locate information in the 6-volume Technical
Reference Manual:
Drives—general
Installation and Configuration
SCSI Drives FC Drives
Connectors 1HW Integration: ch. 7 1HW Integration: ch. 4
Controller architecture 6Background: ch. 4
Front Panel LEDs 1HW Integration: ch. 6 1HW Integration: ch. 3
Mechanism and hardware 6Background: ch. 3
Specifications 4Specs
SCSI Drives FC Drives
Connectors 1HW Integration: ch. 7 1HW Integration: ch. 4

4
Operation
Cartridges
Interface
Determining the configuration 2SW Integration: ch. 2 2SW Integration: ch. 2
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a
Modes of Usage (SCSI only) 1HW Integration: ch. 8n/a
Optimizing performance (SCSI only) 1HW Integration: ch. 8n/a
2SW Integration: ch. 4
UNIX configuration 5UNIX Config
SCSI Drives FC Drives
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a
SCSI Drives FC Drives
Cartridge Memory (LTO-CM) 2SW Integration: ch. 5
6HW Integration: ch. 5
Cartridges 1HW Integration: ch. 9 1HW Integration: ch. 5
Features 6HW Integration: ch. 5
Managing the use of cartridges 2SW Integration: ch. 1
Use of cartridges 2SW Integration: ch. 3
SCSI Drives FC Drives
SCSI Drives FC Drives
SCSI Guide 3SCSI
Commands 3SCSI: ch. 4
Error codes 1HW Integration: ch. 10 1HW Integration: ch. 6
Implementation 3SCSI: ch. 1
Interpreting sense data 2SW Integration: ch. 3
Messages 3SCSI: ch. 2

5
Maintenance and Troubleshooting
Dealing with Errors
Ultrium Features
Mode pages
—see the MODE SENSE command
3SCSI: ch. 4
Pre-execution checks 3SCSI: ch. 3
Responding to Sense Keys and ASC/Q 2SW Integration: ch. 6
Sense Keys and ASC/Q
—see REQUEST SENSE command
3SCSI: ch. 4
SCSI Drives FC Drives
SCSI Drives FC Drives
Cleaning 2SW Integration: ch. 5
2SW Integration: ch. 7
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a
Monitoring drive and tape condition 2SW Integration: ch. 7
Software troubleshooting techniques 2SW Integration: ch. 1
SCSI Drives FC Drives
Error Codes 1HW Integration: ch. 10 1HW Integration: ch. 6
Handling errors 2SW Integration: ch. 5
How error correction works 6Background: ch. 4
Logs—see the LOG SENSE command 3SCSI: ch. 4
Recovering from write and read errors 2SW Integration: ch. 7
Software response to error correction 2SW Integration: ch. 3
Software response to logs 2SW Integration: ch. 3
TapeAlert log 2SW Integration: ch. 7
SCSI Drives FC Drives
Adaptive Tape Speed (ATS) 6Background: ch. 1
Autoload 1 HW Integration: ch. 2
Automation Control Interface (ACI) 1 HW Integration: ch. 2
6 Background: ch. 1

6
General Documents and Standardization
3For a general backgrounder on LTO technology and licensing, go to
http://www.lto-technology.com.
3Small Computer System Interface (SCSI-1), ANSI X3.131-1986. This is the
ANSI authorized standard for SCSI implementation, available through
ANSI
3Enhanced Small Computer System Interface (SCSI-2), ANSI X3T9.2-1993
Rev. 10L, available through ANSI
3Information Technology — SCSI Parallel Interface-3 (SPI-3), T10 Project
1302D, Working Draft Revision 14
Copies of General Documents can be obtained from:
Cartridge Memory (LTO-CM)s 1 HW Integration: ch. 2
2SW Integration: ch. 5
6HW Integration: ch. 5
Data Compression, how it works 6Background: ch. 5
Data Compression, managing 2SW Integration: ch. 5
Design principles 6Background: ch. 1
OBDR and CD-ROM emulation 6Background: ch. 1
2SW Integration: ch. 7
Performance optimization 1HW Integration: ch. 8n/a
2SW Integration: ch. 1
Performance, factors affecting 2SW Integration: ch. 4
Software design 2SW Integration: ch. 1
Supporting Ultrium features 2SW Integration: ch. 5
Ultrium Format 6Background: ch. 2
SCSI Drives FC Drives
ANSI 11 West 42nd Street
New York, NY 10036-8002
USA
ISO CP 56
CH-1211 Geneva 20
Switzerland

7
ECMA 114 Rue du Rhône
CH-1204 Geneva
Switzerland
Tel: [phone]
Web URL: http://www.ecma.ch
Global Engineering Documents 2805 McGaw
Irvine, CA 92714
USA
Tel: [phone] or 714 261 1455

8

Contents 9
Contents Related Documents 3
Documents Specific to HP Ultrium Drives 3
Documentation Map 3
General Documents and Standardization 6
1
11
1Introduction 11
The Purpose of this Manual 11
Ultrium Drives in a Library 11
Backup Applications 12
2
22
2HP-UX Systems 13
HP Servers and Workstations—HP-UX 11.x 13
Introduction 13
Determining the SCSI ID 13
Creating the Device Files 15
What Next? 18
3
33
3HP (Compaq) Tru64 UNIX 19
HP (Compaq) Tru64 UNIX 5.x 19
What Next? 20
4
44
4IBM (AIX) 21
Determining the SCSI ID 21
Configuring the Device Files 21
Device Filenames under AIX 22
5
55
5Linux 25
Determining the SCSI ID (Linux) 25
contents

10 Contents
Configuring on Linux Systems 25
Using the Seek and Tell Features of mt 27
What Next? 27
6
66
6Sun Systems, Solaris (SunOS 5.x) 29
Determining the SCSI ID 29
Configuring the Device Files 30
HP-Data Values 32
7
77
7Verifying the Installation 35
Verifying the Installation of the Drive (UNIX) 35
To verify the installation: 35
Glossary 39
Index 43

Introduction 11
1
Introduction
The Purpose of this Manual
This manual provides basic information on configuring the drives with various
operating systems.
Please see the top-level release notes that accompany the drive for expected
functionality and features.
Ultrium drives are supported on the following platforms:
3HP UNIX systems (HP-UX) (Chapter 2)
3HP (Compaq) Tru64 UNIX (Chapter 3)
3IBM (AIX) (Chapter 4)
3Linux (Chapter 5)
3Sun Systems, Solaris 2 (SunOS 5.x) (Chapter 6)
For platforms not mentioned here, please contact HP because there may be
new connectivity details available that arrived after the release notes were
published.
See Chapter 7 for details of how to verify the installation.
Ultrium Drives in a Library
Ultrium drives may also be used in a library. However, instructions about
installing device drivers for automatic robotics are not included in this
manual.

12 Introduction
Backup Applications
For optimum performance it is important to use a backup application that
supports the drive’s features within your system’s configuration. Please see the
“Getting Started Guide” for more information about usage models.
The following applications are suitable for use within an enterprise
environment and have been tested with Ultrium drives. They use the operating
system’s standard, built-in device drivers, as described in this manual. For
further information about optimizing performance and making full use of the
drive’s functions, please contact the software manufacturer or HP
1. Cell Manager is only available on HP-UX or Windows
2. Redhat Server only (not Caldera, Suse, and so on)
HP-UX AIX Sun, Solaris Linux
HP Omniback1yes yes yes yes
Legato Networker yes yes yes yes
Veritas NetBackup yes yes yes yes2

HP-UX Systems 13
2
HP-UX Systems
HP Servers and Workstations—HP-UX 11.x
Note HP-UX 10.x is only supported by Generation 1 Ultrium drives.
Introduction
Before you install your tape drive log on to the HP web site, www.hp.com,
and download the latest hardware enablement patch bundle for your
operating system. This ensures that you will have the correct device driver for
your tape drive.
Determining the SCSI ID
Before you configure your system to support your new HP Ultrium drive, you
need to determine what SCSI ID to use. The SCSI ID must be unique for each
device attached to the SCSI bus. To list the existing devices, use the following
command:
% /sbin/ioscan -f
The output of this should look similar to the following example:
Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
bc 0 root CLAIMED BUS_NEXUS
bc 1 8 bc CLAIMED BUS_NEXUS Psudo Bus Converter
ba 0 8/0 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge
ext_bus 1 8/0/2/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2 Wide LVD
target 0 8/0/2/0.7 tgt CLAIMED DEVICE
ctl 1 8/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
lan 0 8/0/20/0 btlan3 CLAIMED INTERFACE PCI(10110019) -- Built-in #1
ba 1 8/16 bus_adapter CLAIMED BUS_NEXUS Core I/O Adapter
tty 0 8/16/4 asio0 CLAIMED INTERFACE Built-in RS-232C
ext_bus 2 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI

14 HP-UX Systems
target 1 8/16/5.5 tgt CLAIMED DEVICE
disk 0 8/16/5.5.0 sdisk CLAIMED DEVICE SEAGATE ST34573N
target 2 8/16/5.7 tgt CLAIMED DEVICE
ctl 2 8/16/5.7.0 sctl CLAIMED DEVICE Initiator
processor 0 62 processor CLAIMED PROCESSOR Processor
memory 0 63 memory CLAIMED MEMORY Memory
After you have installed the new tape drive, you can check that it has been
attached successfully. From a shell window (hpterm/xterm), execute
ioscan to display the list of attached devices.
For an HP Ultrium drive, execute the following:
% /sbin/ioscan -f | grep "Ultrium"
The new lines should look similar to the following, where the 4in the Ifield
represents the instance of the SCSI tape driver, not the SCSI ID:
tape 4 2/0/1.5.0 stape CLAIMED DEVICE HP Ultrium
Note If you are installing the drive onto a Storage Area Network
(SAN), the fibre channel/SCSI bridge will also appear in the
list of attached devices.
If you cannot find the Ultrium drive, this may be because the kernel does not
contain the correct driver. Use the System Administration Manager (sam) to
add stape to the kernel:
To add stape to the kernel using sam:
1 % sam
2 Select the following:
Kernel Configuration
Drivers
3 Highlight the stape driver. If the driver has not been added to the kernel,
both Current State and Pending State will read “Out”.
4 Select the following:
Actions
Add Driver to Kernel
The Pending State will now read “In”.
5 To add the new driver to the kernel, select:

HP-UX Systems 15
HP-UX Systems
Actions
Create a New Kernel
6 The stape driver will now be added to the kernel and then the system will
reboot.
Creating the Device Files
Once you have verified the tape drive connection, you will need to create the
appropriate device files for the drive. Normally, you would have rebooted
your system after attaching the tape drive, and this process runs insf.
However, if you have not rebooted your system since attaching the drive, you
can create device files by one of two ways, either through the System
Administration Manager (sam), or by executing the mksf command.
To add device files using sam:
This is the recommended and simplest way to create device files.
1 % sam
This will bring up the graphical user interface for the utility.
2 Select the following:
Peripheral Devices
Tape Drives
sam will then scan the system for any tape drives connected.
When an HP Ultrium drive is found, it will be displayed as:
Hardware Path Driver Description
===========================================================
8/0/2/0.3.0 stape HP Ultrium 1-SCSI
8/0/2/0.4.0 stape HP Ultrium 2-SCSI
3 Highlight the Ultrium drive and select the following from the tool bar:
Actions
Create Device Files
Create Default Device Files
This will create default device files for the drive. To view the device files
that have been created, select:
Actions
Create Device Files
Show Device Files

16 HP-UX Systems
where:
4 When you have exited sam, run ioscan to see the tape drive:
%/sbin/ioscan -C tape -fn
To create device files using mksf:
Note This method is not recommended.
1 Run insf as follows:
% /sbin/insf -C tape
2 Create the device files for the devices using the mksf command as
follows:
% /sbin/mksf -d stape -I <instance> [-n] [-u] /dev/
rmt/X<name>
where:
Device File Description
where <I>
<I>m
<I>mn
<I>mb
<I>mnb
is the instance number of the drive
AT&T encoding, rewind driver
AT&T encoding, non-rewind driver
Berkeley encoding, rewind driver
Berkeley encoding, rewind driver
where <X>
<Y>
<Z>
cXtYbZBEST
cXtYbZBESTb
cXtYbZBESTn
cXtYbZBESTnb
is the card number
is the target number
is the LUN number
Best compression driver, AT&T encoding, with rewind
Best compression driver, Berkeley encoding, with rewind
Best compression driver, AT&T encoding, non-rewind
Best compression driver, Berkeley encoding, non-rewind
Argument Description
-d stape Specifies the SCSI tape driver
-I <instance> Specifies the tape drive’s hardware address via the instance of the SCSI tape
driver. The first instance is 0, the second 1, and so on.
[-n] Specifies no rewind; absence of this parameter indicates rewind mode

HP-UX Systems 17
HP-UX Systems
See the man page (man 1m mksf) for other options of the mksf command.
The stape section covers the SCSI tape driver options. The man page man 7
mt describes the long filenames used in HP-UX 10.xand later.
Example:
To create a device file with the following characteristics:
3A hardware address specified by instance 5 (-I 5)
3No rewind (-n)
3Berkeley mode tape positioning on close (-u)
3A filename of 4mnb, where 4is the tape device identifier (/dev/rmt/
4mnb)
You would execute the following:
% /sbin/mksf -d stape -I 4 -n -u /dev/rmt/4mnb
You can check that the appropriate device file was created using the lssf
command as follows:
% /sbin/lssf /dev/rmt/4mnb
[-u] Specifies Berkeley mode; absence of this parameter indicates AT&T mode.
Berkeley and AT&T modes differ in their read-only close behavior:
3In Berkeley mode, the tape position will remain unchanged by a device
close operation.
3In AT&T mode, a device close operation will cause the tape to be
repositioned just after the next tape filemark (the start of the next file).
In most cases, Berkeley mode should be used.
/dev/rmt/X<name> Specifies the path of the device file, where:
XSpecifies the tape device identifier. Use the next available
identifier. You can examine the contents of /dev/rmt using the ls
command to determine which identifiers have already been used.
<name> Specifies the short name (in HP-UX 9.x-style) of the device file:
mnb No rewind, compression disabled, Berkeley-mode device
hnb No rewind, compression disabled, Berkeley-mode device
mnb No rewind, compression disabled, Berkeley-mode device
hnb No rewind, compression enabled, Berkeley-mode device
Argument Description

18 HP-UX Systems
This should produce the following output to show that the device file now
exists:
stape card instance 0 SCSI target 6 SCSI LUN 0 berkeley no rewind
BEST density at address 2/0/1.6.0 /dev/rmt/4mnb
To create a device file for Ultrium in uncompressed mode, you should use a
command such as:
mksf -H -a -b U_18
and for compressed mode (default):
mksf -H -a -b U_18C
The hardware path can be found from previous ioscan output.
What Next?
Once the device files have been created, you should confirm that your new
tape drive is working properly. Chapter 7, “Verifying the Installation”
provides instructions on backing up and restoring a sample file to test your
installation.

HP (Compaq) Tru64 UNIX 19
3
HP (Compaq) Tru64 UNIX
HP (Compaq) Tru64 UNIX 5. x
1 Add the following entry to your /dev/ddr.dbase file:
SCSIDEVICE
Type = tape
Name = “HP” “Ultrium”
#
PARAMETERS:
TypeSubClass = lto # Linear Tape Open
BlockSize = 262144
TagQueueDepth = 0
MaxTransferSize = 0xffffff # 16Mb - 1
ReadyTimeSeconds = 120 # Seconds
SyncTransfers = enabled
WideTransfers = enabled
InquiryLength = 0x20
DENSITY:
DensityNumber = 0,1,2,3,4,5,6,7
OneFileMarkOnClose = yes
DensityCode = 0x42
Blocking = 0
CompressionCode = 1
Buffered = 1
Speed = 0
MODESELECT:
ModeSelectNumber = 0
SavePage = No
PageFormat = scsi2
BlockDescriptor = yes
TransferLength = 16
Hdr.Tape.BufferMode = 0x1
Hdr.MediumType = 0
Data.UBYTE[0] = 0x3D # Vendor Unique Page Code 3D
Data.UBYTE[1] = 0x02

20 HP (Compaq) Tru64 UNIX
Data.UBYTE[2] = 0x01
Data.UBYTE[3] = 0x00
2 Rebuild the kernel by running /sbin/ddr_config, then reboot the
system with the tape drive attached. The device files for the Ultrium drive
will be generated in /dev/tape and /dev/ntape when you reboot.
3 The names of the device files can be interpreted as follows:
Devices in the /dev/ntape directory are “no-rewind” devices. Those in
/dev/tape will do a rewind on close.
The device files then have the syntax: tapeX_dn
For example, /dev/ntape/tape66_d1 is a device file for device 66,
no-rewind using density number 1. Since all density numbers have the
same parameters it does not matter which density number file is used.
What Next?
Once the device files have been created, you should confirm that your new
tape drive is working properly. Chapter 7, “Verifying the Installation”
provides instructions on backing up and restoring a sample file to test your
installation.