HP Ultrium tape drives Technical reference manual Generation 3 drives Volume 5—Unix configuration guide Part number: Q1538–90925 Volume 5 Edition 6.
Legal and notice information © Copyright 2004—Hewlett-Packard Development Company, L.P. 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.
The purpose of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documents specific to HP Ultrium drives . . . . . . . . . . . . . . . . . . . . . . . Documentation map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General documents and standardization . . . . . . . . . . . . . . . . . . . . . . ... ... ... ... ... ... ... ... ... ... .... .... .... .
7 Verifying the Installation Verifying the Installation of the Drive (UNIX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 To verify the installation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Index . .
The purpose of this manual This is one of six volumes that document HP Ultrium drives. This volume provides background information for driver and application developers. The following products are covered. Capacities are when the drive is using data compression with a compression ratio of 2:1, where applicable: • HP Ultrium Generation 3 Full-Height SCSI Internal Drive • HP Ultrium Generation 3 Full-Height FC Internal Drive NOTE: Throughout this manual frequent reference is made to SCSI commands.
Drives—general SCSI Drives Connectors Controller architecture Front Panel LEDs Mechanism and hardware FC Drives 1 HW Integration: ch. 7 1 HW Integration: ch. 4 6 Background: ch. 4 1 HW Integration: ch. 6 1 HW Integration: ch. 3 6 Background: ch. 3 Specifications 4 Specs Installation and configuration SCSI Drives FC Drives Connectors 1 HW Integration: ch. 7 1 HW Integration: ch. 4 Determining the configuration 2 SW Integration: ch. 2 2 SW Integration: ch.
SCSI Drives FC Drives Features 6 HW Integration: ch. 5 Managing the use of cartridges 2 SW Integration: ch. 1 Use of cartridges 2 SW Integration: ch. 3 Interface SCSI Drives FC Drives SCSI Guide 3 SCSI Commands 3 SCSI: ch. 4 Error codes 1 HW Integration: ch. 10 1 HW Integration: ch. 6 Implementation 3 SCSI: ch. 1 Interpreting sense data 2 SW Integration: ch. 3 Messages 3 SCSI: ch. 2 Mode pages —see the MODE SENSE command 3 SCSI: ch. 4 Pre-execution checks 3 SCSI: ch.
SCSI Drives Handling errors How error correction works FC Drives 2 SW Integration: ch. 5 6 Background: ch. 4 Logs—see the LOG SENSE command 3 SCSI: ch. 4 Recovering from write and read errors 2 SW Integration: ch. 7 Software response to error correction 2 SW Integration: ch. 3 Software response to logs 2 SW Integration: ch. 3 TapeAlert log 2 SW Integration: ch. 7 Ultrium features SCSI Drives Adaptive Tape Speed (ATS) FC Drives 6 Background: ch. 1 Autoload 1 HW Integration: ch.
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 Global Engineering Documents 2805 McGaw Irvine, CA 92714 USA Tel: +41 22 849 6000 Web URL: http://www.ecma.
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.
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 HP-UX AIX Sun, Solaris Linux Omniback1 yes yes yes yes Legato Networker yes yes yes yes Veritas NetBackup yes yes yes yes2 HP 1. Cell Manager is only available on HP-UX or Windows 2.
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.
For an HP Ultrium drive, execute the following: % /sbin/ioscan -f | grep "Ultrium" The new lines should look similar to the following, where the 4 in the I field represents the instance of the SCSI tape driver, not the SCSI ID: tape 4 2/0/1.5.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI 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.
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 Generation 3 drive is found, it will be displayed as: Hardware Path Driver Description =========================================================== 8/0/2/0.3.0 stape HP Ultrium 3-SCSI 3.
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 [-n] [-u] /dev/rmt/X where: Argument Description -d stape Specifies the SCSI tape driver -I 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.
• A hardware address specified by instance 5 (-I 5) • No rewind (-n) • Berkeley mode tape positioning on close (-u) • A filename of 4mnb, where 4 is 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 This should produce the following output to show that the device file now exists: stape card instance 0 SCSI target 6
HP-UX Systems
3 HP Alpha UNIX HP Alpha UNIX 5.x x 1. Add the following entry to your /dev/ddr.
Data.UBYTE[0] = 0x3D # Vendor Unique Page Code 3D Data.UBYTE[1] = 0x02 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.
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.
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.
5 Linux Determining the SCSI ID (Linux) Look at the output of dmesg to find out what SCSI channel number is used for 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 ------------ Linux Type: Direct-Access ANSI SCSI Revision 02 Look at the ID information to establish which IDs are in use.
sym53c8xx This is a SCSI chipset driver for the LSI Logic family of HBAs (amongst others). aic7xxx This is a SCSI chipset driver for the Adaptec 7xxx chipset family (such as Adaptec 29160LP). Latest SCSI controller drivers for Linux will be available from the manufacturer’s web site. In order to communicate with a tape device, the operating system needs to have drivers for the tape and the underlying transport mechanism (the host bus adaptor) loaded.
If you want requests to space to end of data to be faster, you should also enable ST_FAST_MTEOM in the same file. After changing this file, rebuild the modules and install the new binary. At the very least, this requires: make modules make modules_install from the /usr/src/linux directory. See your kernel documentation. Using the Seek and Tell Features of mt In order to use the seek and tell features of mt, you must tell the st driver that HP Ultrium drives use logical block addressing.
Linux
6 Sun Systems, Solaris 8, 9, 10 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. 1.
Configuring the Device Files Determine the device file by typing: % ls -l /dev/rmt/*m | grep "st@X" where X is the SCSI ID. Identify the line for the tape drive. For example, if the drive was at SCSI ID 2, look for the line containing “st@2,0”. This might be as follows (but on a single line): lrwxrwxrwx 1 root root 63 Mar 1 00:00 /dev/rmt/0m ../../devices/sbus@1f,0/espdma@e,8400000/esp@e, 8800000/st@2,0:m Here you could use /dev/rmt/0m (shown underlined above) as the device file.
2. If you are replacing an existing tape device on the same SCSI ID, remove the contents of the /dev/rmt directory as follows: % cd /dev/rmt % rm * 3. Do a reconfigure boot: % cd / % touch /reconfigure % sync;halt 4. When the system is down, reboot: % boot -r Make sure you include the -r switch, so that the device directory is reconfigured using the new data. 5. You should now be able to use the drive.
Parameter Value 0 Meaning Indicates variable block size. 0xd639 or This value is derived from constants provided in /usr/include/sys/ 0x18659 scsi/targets/stdef.h. The value determines which operations the driver can perform with the attached device by using a unique value for each feature and then adding them together to form the options value. Supported features will vary with OS revision, and may include the following: 0x001 Device supports variable length records.
7 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. In outline, the procedure is as follows: 1. Check the tape drive responds to a rewind command. 2. Write test data to a tape. 3. Read the test data from the tape. 4.
Specify the device file explicitly. f The arguments follow the cvf options in the command line. Their values depend on the operating system; suggested values are given the appropriate operating system chapter.The arguments are as follows: The name of the device file for the drive. Example: /dev/rmt/0m The name of the file to archive, prefixed with ‘./’. Example: ./stand/vmunix NOTE: Make sure you prefix the file name with ‘.’ when you back it up to tape.
3. Change to the temporary directory: % cd /tmp 4. Extract the file from the tape: % tar xvf /dev/rmt/0m 5. Compare the original with the restored version: % cmp /stand/vmunix /tmp/stand/vmunix Verifying the Installation Note that the original filename is not prefixed with ‘.’.
Verifying the Installation
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” close functionality. In Berkeley mode the tape position will remain unchanged by a device close operation. BOT Beginning Of Tape. The first point on the tape that can be accessed by the drive.
fibre channel Fibre Channel provides an inexpensive yet expendable means of quickly transferring data between workstations, mainframes, supercomputers, desktop computers, storage devices, displays and other peripherals. Although it is called Fibre Channel, its architecture represents neither a channel nor a real network topology. It allows for an active intelligent interconnection scheme, called a fabric, to connect devices.
Single-Ended and Low Voltage Differential SCSI These terms define how the signals are transmitted along the cable. With single-ended (SE) SCSI, each signal travels over a single wire and each signal’s value is determined by comparing the signal to a paired ground wire. Signal quality tends to decrease over longer cable lengths or at increased signal speed.
sequential access 38 Glossary Sequential access devices store data sequentially in the order in which it is received. Tape devices are the most common sequential access devices. Devices such as disk drives are direct access devices, where data is stored in blocks, not necessarily sequentially. Direct access allows for speed of retrieval, but is significantly more costly.
A I AIX 21 ANSI 5 asynchronous data transfer 35 AT&T mode 35 IBM (AIX) 21 determining SCSI ID 21 device files 21 immediate mode 36 infinite flush 36 installation, verifying 31 B Berkeley mode 35 BOT 35 buffered mode 35 L C Linux 23 determining SCSI ID 23 LUN 36 LVD SCSI 37 compression 35 confirming installation 31 M D data transfer 35 device files AIX 22 HP-UX 14 IBM (AIX) 21 Sun workstations 28 direct access 38 documents, related 5 F fast SCSI 37 fibre channel 36 filemarks 36 filenames under AIX
Index
