HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module Technical Reference Manual
Generation 2 scsi and fc drives, volume 5: unix configuration guide
Hide thumbs
Also See for 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module:
- User manual (73 pages) ,
- Getting started manual (56 pages)
Table of Contents
Advertisement
Quick Links
Download this manual
See also:
User Manual
Advertisement
Table of Contents
Related Manuals for HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module
Summary of Contents for HP 330834-B21 - StorageWorks Ultrium 460 Tape Library Drive Module
- Page 1 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...
-
Page 2: Revision History
All rights reserved. No part of this document may be Hewlett-Packard makes no photocopied, reproduced or warranty of any kind with regard translated to another language to this material, including, but not... -
Page 3: Related Documents
Related Documents The following documents provide additional information: Documents Specific to HP Ultrium Drives Software Integration Guide, volume 2 of the HP Ultrium Technical Reference Manual The SCSI Interface, volume 3 of the HP Ultrium Technical Reference Manual Specifications, volume 4 of the HP Ultrium Technical Reference Manual HP Ultrium Configuration Guide, volume 5 of the HP Ultrium Technical Reference Manual Background to Ultrium Drives, volume 6 of the HP Ultrium Technical... - Page 4 SCSI Drives FC Drives Determining the configuration SW Integration: ch. 2 SW Integration: ch. 2 External drives (SCSI only) HW Integration: ch. 5 In Libraries HW Integration: ch. 1 In Servers (SCSI only) HW Integration: ch. 4 In Tape Arrays (SCSI only) HW Integration: ch.
-
Page 5: Maintenance And Troubleshooting
SCSI Drives FC Drives Mode pages SCSI: ch. 4 —see the MODE SENSE command Pre-execution checks SCSI: ch. 3 Responding to Sense Keys and ASC/Q SW Integration: ch. 6 Sense Keys and ASC/Q SCSI: ch. 4 —see REQUEST SENSE command Maintenance and Troubleshooting SCSI Drives FC Drives... -
Page 6: General Documents And Standardization
SCSI Drives FC Drives Cartridge Memory (LTO-CM)s 1 HW Integration: ch. 2 SW Integration: ch. 5 HW Integration: ch. 5 Data Compression, how it works Background: ch. 5 Data Compression, managing SW Integration: ch. 5 Design principles Background: ch. 1 OBDR and CD-ROM emulation Background: ch. - Page 7 114 Rue du Rhône Tel: +41 22 849 6000 ECMA CH-1204 Geneva Web URL: http://www.ecma.ch Switzerland 2805 McGaw Tel: 800 854 7179 or 714 261 1455 Global Engineering Documents Irvine, CA 92714...
-
Page 9: Table Of Contents
contents Contents Related Documents 3 Documents Specific to HP Ultrium Drives 3 Documentation Map 3 General Documents and Standardization 6 1 1 1 1 Introduction 11 The Purpose of this Manual 11 Ultrium Drives in a Library 11 Backup Applications 12 2 2 2 2 HP-UX Systems 13 HP Servers and Workstations—HP-UX 11.x 13... - Page 10 Configuring on Linux Systems 25 Using the Seek and Tell Features of mt 27 What Next? 27 6 6 6 6 Sun Systems, Solaris (SunOS 5.x) 29 Determining the SCSI ID 29 Configuring the Device Files 30 HP-Data Values 32 7 7 7 7 Verifying the Installation 35 Verifying the Installation of the Drive (UNIX) 35...
-
Page 11: Introduction
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: HP UNIX systems (HP-UX) (Chapter HP (Compaq) Tru64 UNIX... -
Page 12: Backup Applications
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. -
Page 13: Hp-Ux Systems
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. - Page 14 target 1 8/16/5.5 CLAIMED DEVICE disk 0 8/16/5.5.0 sdisk CLAIMED DEVICE SEAGATE ST34573N target 2 8/16/5.7 CLAIMED DEVICE 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.
-
Page 15: Creating The Device Files
Actions Create a New Kernel driver will now be added to the kernel and then the system will stape 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... - Page 16 where: Device File Description where is the instance number of the drive <I> AT&T encoding, rewind driver <I>m AT&T encoding, non-rewind driver <I>mn Berkeley encoding, rewind driver <I>mb Berkeley encoding, rewind driver <I>mnb where is the card number <X> is the target number <Y>...
- Page 17 Argument Description Specifies Berkeley mode; absence of this parameter indicates AT&T mode. [-u] Berkeley and AT&T modes differ in their read-only close behavior: In Berkeley mode, the tape position will remain unchanged by a device close operation. In 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).
-
Page 18: What Next
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):... -
Page 19: Hp (Compaq) Tru64 Unix
HP (Compaq) Tru64 UNIX HP (Compaq) Tru64 UNIX 5. Add the following entry to your file: /dev/ddr.dbase SCSIDEVICE Type = tape Name = “HP” “Ultrium” PARAMETERS: TypeSubClass = lto # Linear Tape Open BlockSize = 262144 TagQueueDepth MaxTransferSize = 0xffffff # 16Mb - 1 ReadyTimeSeconds = 120... -
Page 20: What Next
Data.UBYTE[2] = 0x01 Data.UBYTE[3] = 0x00 Rebuild the kernel by running , then reboot the /sbin/ddr_config system with the tape drive attached. The device files for the Ultrium drive will be generated in when you reboot. /dev/tape and /dev/ntape The names of the device files can be interpreted as follows: Devices in the directory are “no-rewind”... -
Page 21: Ibm (Aix)
IBM (AIX) Determining the SCSI ID Before you configure your system to support your 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... -
Page 22: Device Filenames Under Aix
If you are using a non-graphics terminal, at the command line type: % smit -C tape If no device has been configured at this address before, select “ add a ” to set up the address. From the pop-up window, select tape drive “... - Page 23 in 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. Normally, the drive repositions the tape to BOT (Beginning of Tape) when the Rewind on Close device file is closed.
- Page 24 IBM (AIX)
-
Page 25: Linux
Linux Determining the SCSI ID (Linux) Look at the output of to find out what SCSI channel number is used for dmesg each connection. To find out the SCSI IDs in use on each channel, type: cat /proc/scsi/scsi This will produce output similar to the following for each device: Attached Devices Host: SCSI0 Channel: 00 Id:00 Lun:00 Vendor: HP Model ------------... - Page 26 The lines of interest here are: This is the tape driver. Its presence in the output of the lsmod command shows that the tape driver is loaded. This is a SCSI chipset driver for the LSI Logic family of HBAs ncr53c8xx (amongst others).
-
Page 27: Using The Seek And Tell Features Of Mt
In order to enable large transfers under Linux (>64 KB per write), edit the file and change the /usr/src/linux/drivers/scsi/st_options.h definition of ST_BUFFER_BLOCKS If you want requests to space to end of data to be faster, you should also enable in the same file. After changing this file, rebuild the ST_FAST_MTEOM modules and install the new binary. - Page 28 Linux...
-
Page 29: Sun Systems, Solaris (Sunos 5.X)
Sun Systems, Solaris x x x x ) (SunOS 5. Determining the SCSI ID Before you configure your system to support an HP Ultrium drive, you need to determine which SCSI ID to use. IDs must be unique for each device on attached to the SCSI bus. -
Page 30: Configuring The Device Files
For example, for an ESP-based adapter: % dmesg | egrep ".*esp.*target" | sort | uniq This produces a list similar to: sd0 at esp0: target 0 lun 0 sd6 at esp0: target 6 lun 0 This indicates that SCSI IDs 0 and 6 are used for existing devices. SCSI ID 7 is generally used for the adapter itself. - Page 31 name="st" class="scsi" target=X lun=0; for Solaris 9: tape-config-list = "HP Ultrium 1", "HP Ultrium LTO 1", "HP_LTO_GEN_1", HP_LTO_GEN_1 =,0x3B,0,0x18659,4,0x40,0x40,0x40,0x40,3,60,300,600,1200,600,600,18000; "HP Ultrium 2","HP Ultrium LTO 2","HP_LTO_GEN_2"; HP_LTO_GEN_2 = ,0x3B,0,0x18659,4,0x42,0x42,0x42,0x42,3,60,300,600,1200,600,600,18000; name="st" class="scsi" target=X lun=0; where is the SCSI target address of the device you have attached. “HP-Data Values”...
-
Page 32: Hp-Data Values
HP-Data Values The values for , which provide normal LTO mode, HP_LTO_GEN_n name have the following meanings: The syntax for on Solaris 8 or earlier HP_LTO_GEN_1 HP_LTO_GEN_2 <drive type> = <version>, <type>, <bsize>, <options>, <no. of densities>, <density 0>, <density 1>, <density 2>,<density 3>, <default density>... - Page 33 Parameter Value Meaning Device knows when end of data has been reached. 0x0200 Device driver is unloadable. 0x0400 Time-outs five times longer than normal. 0x1000 Driver buffers write requests and pre-acknowledges success to 0x4000 application. Variable record size not limited to 64 KB. 0x8000 Solaris 9 only: Device determines which of the two mode pages...
- Page 34 Sun Systems, Solaris (SunOS 5.x)
-
Page 35: Verifying The Installation
Verifying the Installation Verifying the Installation of the Drive (UNIX) As part of the installation process, you will have installed the appropriate device driver for your UNIX system, and created device files to communicate with the tape drive. This section describes how you can verify that the installation has been performed correctly. - Page 36 Write a sample file to tape, using ‘ ’: % cd / % tar cvf <device file> <file> The options to have the following meanings: Create a new archive (backup file) on the device. Operate in verbose mode. Specify the device file explicitly. The arguments follow the options in the command line.
- Page 37 Example: Suppose you are verifying the installation of an HP Ultrium tape drive on an HP-UX 10.X system. The procedure would be as follows.: Change directory to root: % cd / Back up to tape: /stand/vmunix % tar cvf /dev/rmt/0m ./stand/vmunix Note the prefix of ‘...
- Page 38 Verifying the Installation...
-
Page 39: Glossary
glossary Glossary AT&T mode Berkeley and AT&T functional modes differ in “read-only” close functionality. In AT&T mode, a device close operation will cause the tape to be repositioned just after next filemark on the tape (the start of the next file). Berkeley mode Berkeley and AT&T functional modes differ in “read-only”... - Page 40 synchronous data transfer, the initiator and target work in synchronization, allowing transmission of a packet of data to start before acknowledgment of the previous transmission. wide (16-bit) data transfer, two bytes are transferred at the same time instead of a single byte. HP Ultrium drives support asynchronous, synchronous and narrow (8-bit) wide transfers.
- Page 41 Storage Area Network. A dedicated, high-speed network that establishes a direct connection between storage elements and servers. The hardware that connects workstations and servers to storage devices in a SAN is referred to as a fabric. The SAN fabric enables any-server-to-any-storage device connectivity through the use of Fibre Channel switching technology.
- Page 42 Ultra SCSI supports both SE and LVD interfaces. Ultra2 SCSI supports LVD interfaces only. In normal situations, slower devices can coexist with faster devices, and narrow devices can be used on the same SCSI bus as wide devices using a suitable adapter. HP’s Ultrium drives are Ultra2, wide SCSI-3 compatible devices.
-
Page 43: Index
index Index Index Index Index A A A A H H H H HP (Compaq) Tru64 ANSI HP-UX systems asynchronous data transfer determining SCSI-ID AT&T mode device files B B B B I I I I Berkeley mode IBM (AIX) determining SCSI ID buffered mode device files... - Page 44 S S S S 3, 41 SCSI SCSI ID, determining HP-UX IBM (AIX) Linux Sun workstations sequential access single-ended SCSI Solaris storage area network Sun workstations data values determining SCSI ID device files synchronous data transfer systems HP-UX Linux T T T T Tru64 U U U U ultra SCSI...