HP C7401A - SureStore Ultrium 230 Tape Drive Product manual

unix
configuration
guide
hp ultrium drives
technical reference manual
generation 1 SCSI drives
volume 5: unix configuration guide
Part Number: C7369–90901 Volume 5
Edition 5, February 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 Feb 2003 Support Silicon Graphics and Tru64 removed. Other minor changes.
Generation 1 version.
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
Connectors 1HW Integration: ch. 5
Controller architecture 6Background: ch. 4
Front Panel LEDs 1HW Integration: ch. 4
Mechanism and hardware 6Background: ch. 3
Specifications 4Specs
Connectors 1HW Integration: ch. 5
Determining the configuration 2SW Integration: ch. 2
In Libraries 1HW Integration: ch. 1

4
Operation
Cartridges
Interface
Maintenance and Troubleshooting
In Servers 1HW Integration: ch. 3
Modes of Usage 1HW Integration: ch. 6
Optimizing performance 1HW Integration: ch. 6
2SW Integration: ch. 4
UNIX configuration 5UNIX Config
In Libraries 1HW Integration: ch. 1
In Servers 1HW Integration: ch. 3
Cartridge Memory (LTO-CM) 2SW Integration: ch. 5
6HW Integration: ch. 5
Cartridges 1HW Integration: ch. 7
Features 6HW Integration: ch. 5
Managing the use of cartridges 2SW Integration: ch. 1
Use of cartridges 2SW Integration: ch. 3
SCSI Guide 3SCSI
Commands 3SCSI: ch. 4
Error codes 1HW Integration: ch. 8
Implementation 3SCSI: ch. 1
Interpreting sense data 2SW Integration: ch. 3
Messages 3SCSI: ch. 2
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
Cleaning 2SW Integration: ch. 5
2SW Integration: ch. 7
In Libraries 1HW Integration: ch. 1
In Servers 1HW Integration: ch. 3

5
Dealing with Errors
Ultrium Features
General Documents and Standardization
3For a general backgrounder on LTO technology and licensing, go to
http://www.lto-technology.com.
Monitoring drive and tape condition 2SW Integration: ch. 7
Software troubleshooting techniques 2SW Integration: ch. 1
Error Codes 1HW Integration: ch. 8
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
Adaptive Tape Speed (ATS) 6Background: ch. 1
Autoload 1HW Integration: ch. 2
Automation Control Interface (ACI) 1HW Integration: ch. 2
6Background: ch. 1
Cartridge Memory (LTO-CM)s 1HW 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. 6
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

6
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:
ANSI 11 West 42nd Street
New York, NY 10036-8002
USA
ISO CP 56
CH-1211 Geneva 20
Switzerland
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

Contents 7
Contents Related Documents 3
Documents Specific to HP Ultrium Drives 3
Documentation Map 3
General Documents and Standardization 5
1
11
1Introduction 9
The Purpose of this Manual 9
Ultrium Drives in a Library 9
2
22
2HP-UX Systems 11
HP Servers and Workstations
HP-UX 10.x and 11.x 11
Introduction 11
Determining the SCSI ID 11
Creating the Device Files 13
What Next? 16
3
33
3IBM (AIX) 17
Determining the SCSI ID 17
Configuring the Device Files 17
Device Filenames under AIX 18
4
44
4Linux 21
Determining the SCSI ID (Linux) 21
Configuring on Linux Systems 21
Using the Seek and Tell Features of mt 23
What Next? 23
contents

8Contents
5
55
5Sun Systems, Solaris (SunOS 5.x) 25
Determining the SCSI ID 25
Configuring the Device Files 26
HP-Data Values 27
6
66
6Verifying the Installation 31
Verifying the Installation of the Drive (UNIX) 31
To verify the installation: 31
Glossary 35
Index 39

Introduction 9
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)
3IBM (AIX) (Chapter 3)
3Linux (Chapter 4)
3Sun Systems, Solaris 2 (SunOS 5.x) (Chapter 5)
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 6 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.

10 Introduction

HP-UX Systems 11
2
HP-UX Systems
HP Servers and Workstations
HP-UX 10.xand 11.x
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

12 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 13
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

14 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 15
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

16 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 6, “Verifying the Installation”
provides instructions on backing up and restoring a sample file to test your
installation.

IBM (AIX) 17
3
IBM (AIX)
Determining the SCSI ID
Before you configure your system to support you Ultrium drive, you need to
determine which SCSI ID to use. IDs must be unique for each device attached
to the SCSI bus. To list the existing devices, use the following command:
% lsdev -C |grep SCSI
This will produce output that looks similar to:
scsi0 Available 00-00-0S Standard SCSI I/O Controller
hdisk0 Available 00-00-0S-0 1.0 GB SCSI Disk Drive
rmt1 Defined 00-00-0S-2,0 Other SCSI Tape Drive
The SCSI ID is in the series 00-00-0S-X,0, where Xis the SCSI ID. Review
the list of existing SCSI IDs and choose an available ID to assign to the new
tape drive.
Configuring the Device Files
To install an HP Ultrium drive on an IBM workstation you will need to create
the appropriate device files for the drive.
Note Do not choose the smit option of “4mm2gb” as the Tape
Device Type. This is reserved for Connor drives. If you use it
with HP drives, you will get the error “Device to be
configured does not match the physical device
at the specified connection location”.
To change to variable block mode, use the following procedure:
1 If you are using a graphics terminal running X-Windows, then at a
Windows terminal, type: smit tape

18 IBM (AIX)
If you are using a non-graphics terminal, at the command line type:
% smit -C tape
2 If no device has been configured at this address before, select “add a
tape drive” to set up the address. From the pop-up window, select
“ost” or “Other SCSI tape drive” as the tape drive you wish to
change and choose connection addresses as appropriate.
3 Select from the window: “change/show characteristics of a
tape drive”
4 From the pop-up window, select “ost” or “Other SCSI tape drive”
as the tape drive you wish to change. Do not choose “4mm2gb”.
5 Change the block size field to 0, and click on the “DO” button or press
[Enter] to apply the change.
HP Ultrium drives will work with tar, cpio, backup, restore and dd. For
systems other than the 43P, the drive is also boot-capable, provided a boot
tape is generated using mkszfile and mksysb.
Once the device files have been created, you should confirm that your new
tape drive is working properly. Chapter 6, “Verifying the Installation”
provides instructions on backing up and restoring a sample file to test your
installation.
Device Filenames under AIX
Use device filenames as listed below for the combination of Rewind on Close,
Retension on Open, and Compression that you want:
Filename Rewind on Close Retension on Open Compression
/dev/rmtnYes No enabled
/dev/rmtn.1 No No enabled
/dev/rmtn.2 Yes Yes enabled
/dev/rmtn.3 No Yes enabled
/dev/rmtn.4 Yes No disabled
/dev/rmtn.5 No No disabled
/dev/rmtn.6 Yes Yes disabled
/dev/rmtn.7 No Yes disabled

IBM (AIX) 19
IBM (AIX)
The nin the filename is the instance number assigned to the drive by the
operating system, where 0 is the first device, 1 is the second and so on.
Rewind on Close Normally, the drive repositions the tape to BOT (Beginning of Tape) when the
device file is closed. Using the no rewind option is useful when creating and
reading tapes that contain multiple files.
Retension on Open Retensioning consists of winding to EOT (End of Tape) and then rewinding to
BOT, in order to reduce errors. If this option is selected, the tape is positioned
at BOT as part of the open process.
Compression Compression can be disabled or enabled.

20 IBM (AIX)