HP C7401A - SureStore Ultrium 230 Tape Drive Technical Reference Manual

Generation 1 scsi drives volume 5: unix configuration guide
Hide thumbs Also See for C7401A - SureStore Ultrium 230 Tape Drive:
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
Table of Contents
loading

Summary of Contents for HP C7401A - SureStore Ultrium 230 Tape Drive

  • Page 1 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...
  • 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: Maintenance And Troubleshooting

    In Servers HW Integration: ch. 3 Modes of Usage HW Integration: ch. 6 Optimizing performance HW Integration: ch. 6 SW Integration: ch. 4 UNIX configuration UNIX Config Operation In Libraries HW Integration: ch. 1 In Servers HW Integration: ch. 3 Cartridges Cartridge Memory (LTO-CM) SW Integration: ch.
  • Page 5: General Documents And Standardization

    Monitoring drive and tape condition SW Integration: ch. 7 Software troubleshooting techniques SW Integration: ch. 1 Dealing with Errors Error Codes HW Integration: ch. 8 Handling errors SW Integration: ch. 5 How error correction works Background: ch. 4 Logs—see the LOG SENSE command SCSI: ch.
  • Page 6 Small Computer System Interface (SCSI-1), ANSI X3.131-1986. This is the ANSI authorized standard for SCSI implementation, available through ANSI Enhanced Small Computer System Interface (SCSI-2), ANSI X3T9.2-1993 Rev. 10L, available through ANSI Information Technology — SCSI Parallel Interface-3 (SPI-3), T10 Project 1302D, Working Draft Revision 14 Copies of General Documents can be obtained from: 11 West 42nd Street...
  • Page 7: Table Of Contents

    contents Contents Related Documents 3 Documents Specific to HP Ultrium Drives 3 Documentation Map 3 General Documents and Standardization 5 1 1 1 1 Introduction 9 The Purpose of this Manual 9 Ultrium Drives in a Library 9 2 2 2 2 HP-UX Systems 11 HP Servers and Workstations HP-UX 10.x and 11.x 11...
  • Page 8 5 5 5 5 Sun Systems, Solaris (SunOS 5.x) 25 Determining the SCSI ID 25 Configuring the Device Files 26 HP-Data Values 27 6 6 6 6 Verifying the Installation 31 Verifying the Installation of the Drive (UNIX) 31 To verify the installation: 31 Glossary 35 Index 39 Contents...
  • Page 9: 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 IBM (AIX)
  • Page 10 Introduction...
  • Page 11: Hp-Ux Systems

    HP-UX Systems HP Servers and Workstations HP-UX 10.x and 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.
  • Page 12 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 13: 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 14 where: Device File Description where is the instance number of the drive AT&T encoding, rewind driver m AT&T encoding, non-rewind driver mn Berkeley encoding, rewind driver mb Berkeley encoding, rewind driver mnb where is the card number is the target number ...
  • Page 15 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 16: 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 17: Ibm (Aix)

    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...
  • Page 18: 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 19 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 20 IBM (AIX)
  • Page 21: 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 22 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 23: 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 24 Linux...
  • Page 25: 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 the 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 26: 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 27: Hp-Data Values

    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; name="st" class="scsi" target=X lun=0; where is the SCSI target address of the device you have attached. “HP-Data Values” on page 27 below for the values of the parameters in these lines.
  • Page 28 The syntax for on Solaris 8 or earlier is: HP_LTO_GEN_1 = , , , , , , , ,, The syntax for on Solaris 9 is: HP_LTO_GEN_1 = , , , ,
  • Page 29 Parameter Value Meaning indicates variable record length, enabled, long 0xd639 timeouts for erase, EOD recognition, Unloadable device driver, 5 x longer timeouts, buffer writes and pre-acknowledge sucess, variable records not limited to 64 KB. There are four densities following in the parameter list.
  • Page 30 Sun Systems, Solaris (SunOS 5.x)
  • Page 31: 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 32 Write a sample file to tape, using ‘ ’: % cd / % tar cvf 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 33 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 34 Verifying the Installation...
  • Page 35: Glossary

    glossary Glossary Berkeley and AT&T functional modes differ in “read-only” close functionality. AT&T mode 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 and AT&T functional modes differ in “read-only”...
  • Page 36 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 37 With low voltage differential (LVD) signaling, signals travel along two wires and the difference in voltage between the wire pairs determines the signal value. This enables faster data rates and longer cabling with less susceptibility to noise than SE signaling and reduced power consumption. Narrow and Wide, Fast, Ultra and Ultra2 SCSI Narrow SCSI devices can transfer data one byte at-a-time (and are...
  • Page 38 Glossary...
  • Page 39: Index

    index Index Index Index Index A A A A device files I I I I ANSI IBM (AIX) asynchronous data transfer determining SCSI ID AT&T mode device files B B B B immediate mode infinite flush Berkeley mode installation, verifying buffered mode L L L L C C C C...
  • Page 40 Linux Sun workstations sequential access single-ended SCSI Solaris Sun workstations data values determining SCSI ID device files synchronous data transfer systems HP-UX Linux U U U U ultra SCSI ultra2 SCSI V V V V verifying installation wide data transfer wide SCSI workstations Index...

Table of Contents