Page 1
HP LTO Ultrium tape drives technical reference manual LTO 4 FC, SCSI and SAS drives volume 5: UNIX, Linux and OpenVMS configuration guide Edition 1, May 2007...
Contents Related documents ............3 Documents specific to HP LTO Ultrium drives .
Page 4
If you are using a graphics terminal running X-Windows ......27 If you are using a non-graphics terminal ........29 Device filenames under AIX .
Related documents The following documents provide additional information: Documents specific to HP LTO Ultrium drives Hardware Integration Guide, volume 1 of the HP LTO Ultrium Technical Reference Manual • • Software Integration Guide, volume 2 of the HP LTO Ultrium Technical Reference Manual Host Interface Guide, volume 3 of the HP LTO Ultrium Technical Reference Manual •...
General documents and standardization http://www.t10.org/t10_main.htm for INCITS SCSI Primary Commands—3 (SPC-3) and other specifications Copies of documents of other standards bodies can be obtained from: INCITS 11 West 42nd Street New York, NY 10036-8002 CP 56 CH-1211 Geneva 20 Switzerland 114 Rue du Rhône Tel: +41 22 849 6000 ECMA...
Introduction Purpose of this manual This manual provides basic information on configuring the drives with various operating systems. See the top-level release notes that accompany the drive for expected functionality and features. LTO Ultrium drives are supported on the following platforms: •...
HP (HP-UX) servers and workstations This chapter covers: HP servers and workstations: HP-UX 11i v1 (11.11), 11i v2 (11.23) • HP servers: HP-UX 11i v3 (11.31) • Before you install your tape drive, log on to the HP web site, www.hp.com, and download the latest hardware enablement (HWE) patch bundle for your operating system.
Page 12
ext_bus 0/0/2/0.1 side CLAIMED INTERFACE IDE Secondary Channel CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783) ext_bus 0/1/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD target 0/1/1/0.0 CLAIMED DEVICE disk 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC ext_bus 0/1/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD 0/1/2/0...
Page 13
For 11i v3 (Agile I/O tree view) Enter the command: % ioscan -m lun The output should look similar to the following (SCSI interface drives are shown in this example) Class Lun H/W Path Driver S/W State H/W Type Health Description ===================================================================================== disk...
The lunpath hardware path for the above tape drive is “0/4/1/0.0x50060b0000b7f3c8.0x0”. • The FC bus ID is “0/4/1/0” (including all the numbers separated by “/”). From the remaining “0x50060b0000b7f3c8.0x0” portion: Tape drive WWN (hexadecimal) = 0x50060b0000b7f3c8 • • Tape drive SCSI LUN = 0x0 (hexadecimal SCSI-3 64-bit LUN identifier) Adding stape and schgr (autoloader driver) to the kernel For HP-UX 11i v1, 11i v2 If your tape drive or autoloader does not appear in ioscan listing or is listed with H/W Type...
Page 15
Figure 2 SAM text-based interface For HP-UX 11i v1 (11.11) Enter sam at the command line. % sam Select the following: Kernel Configuration Drivers Highlight the stape driver. If the driver has not been added to the kernel, both Current State and Pending State will read “Out”.
Page 16
Highlight the stape driver. If the driver has not been added to the kernel, both Current State and Planned State will read “unused”. Type “m” to modify the stape driver and “s” to set it to “static”. The Planned State will now read “static”.
Select the module radio button. Its details will appear in a panel below the modules estape list. From the right hand panel on the web page, click the Modify Module link. On the Modify Kernel Module: estape page, for Next Boot State, select the “static” radio button. Check the box entitled Backup to create a backup copy of the existing kernel (see Figure Figure 4...
Page 18
Peripheral Devices Tape Drives will then scan the system for any tape drives connected. For example, when an HP LTO Ultrium 4 drive is found, it will be displayed as something like: Hardware Path Driver Description =========================================================== 8/0/2/0.3.0 stape HP Ultrium 4-SCSI Highlight the drive and select the following from the tool bar: Actions Create Device Files...
Select from the Class drop down box on the HP-UX Peripheral Device Tool page. Select the tape tape device (radio button) requiring device files from the resulting list. If device files are not already present this will be indicated under the Properties header (see Figure Selecting a tape device to create its device files (Agile View) Figure 5...
HP (OpenVMS) servers and workstations NOTE: Only SCSI drives are supported on Alpha Server systems. Determining attached devices After connecting the tape drive to your system, boot OpenVMS and check for the presence of the new tape device. Execute the following commands. $ sho dev mk Device Device...
HP (Tru64 5.1x) servers and workstations NOTE: Only SCSI drives are supported on Alpha Server systems. Determining attached devices After connecting the tape drive to your system, boot TRU64 and check for the presence of the new tape device. Execute the following commands # hwmgr -scan scsi hwmgr: Scan request successfully initiated # hwmgr -v d...
Page 24
HP (Tru64 5.1x) servers and workstations...
Linux (kernel 2.6.x) servers and workstations Determining the SCSI ID 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...
NOTE: To add drivers to the statically built kernel you need the Linux source code available on disk and knowledge of how to use the kernel building tools that ship with various Linux distributions. This should not be attempted by novice users. In order to determine if the drive has been detected by the tape driver at module load time, execute: dmesg | grep "st"...
What next? Once device files have been created, you should confirm that your new tape drive is working properly. Chapter 8 on page 37 provides instructions on backing up and restoring a sample file to test your installation. HP LTO Ultrium 4 drives technical reference manual, volume 5: UNIX, Linux and OpenVMS configuration guide...
Page 28
Linux (kernel 2.6.x) servers and workstations...
IBM (AIX) servers and workstations Determining the SCSI ID Before you configure your system to support LTO Ultrium drives, determine which SCSI ID to use. IDs must be unique for each device attached to the SCSI bus. To list existing devices, use the following: % lsdev -C |grep SCSI This produces output similar to: scsi0 Available 00-00-0S Standard SCSI I/O Controller...
Page 30
A pop-up window is displayed: Select “ost” or “Other SCSI tape drive” as the tape drive you wish to change. If no device has been configured at this address before, choose connection addresses as appropriate. The following details are displayed: Check the following values and change them if necessary: •...
If you are using a non-graphics terminal At the command line type: % smit -C tape The following is displayed: If no device has been configured at this address before, select “add a tape drive” to set up the address. Otherwise, select “change/show characteristics of a tape drive”...
HP LTO Ultrium drives will work with tar, cpio, backup, restore and dd. Once device files have been created, you should confirm that your new tape drive is working properly. Chapter 8 on page 37 provides instructions on backing up and restoring a sample file to test your installation.
Sun (Solaris 8, 9, 10) servers and workstations Fibre Channel drives Before configuring your system to support an HP LTO Ultrium drive, ensure that the drive is visible to the Sun system HBA by correctly zoning the fabric switch (if one is being used). Configuring the device files Before configuring FC-attached drives, ensure the operating system is updated with the latest recommended patches.
This produces output similar to the following: 106 780a0000 102b3 glm (GLM SCSI HBA Driver) 110 780b4000 1272c qus (isp10160 HBA Driver) For the adapter to which the new tape drive is attached, you need to determine what SCSI IDs are already used.
Page 35
If for some reason you cannot upgrade to the minimum patch level, you can make the following file modifications to enhance performance: In the file /kernel/drv/st.conf, after these lines: ######## # Copyright (c) 1992, by Sun Microsystems, Inc. #ident "@(#)st.conf 93/05/03 SMI"...
You should now be able to use the drive. • Use /dev/rmt/Xcb if you require a compression rewind device file, where X is the relevant device address. • Use /dev/rmt/Xcbn when you require a compression non-rewind device. Once the device files have been created, you should confirm that your new tape drive is working properly.
Page 37
Parameter Value Meaning 0x1000 Time-outs five times longer than normal. 0x4000 Driver buffers write requests and pre-acknowledges success to application. 0x8000 Variable record size not limited to 64 KB. 0x10000 Device determines which of the two mode pages the device supports for selecting or deselecting compression. So 0xd639 indicates variable record length, bsf and bsr enabled, long timeouts for erase, EOD recognition, Unloadable device driver, 5 x longer timeouts, buffer writes and pre-acknowledge success,...
Page 38
Sun (Solaris 8, 9, 10) servers and workstations...
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 the installation has been performed correctly. In outline, the procedure is as follows: Check the tape drive responds to a rewind command.
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: <device file> The name of the device file for the drive. Example: /dev/rmt/c4t3d0BESTnb The name of the file to archive, prefixed with ‘./’.
Page 41
Compare the original with the restored version: % cmp /stand/vmunix /tmp/stand/vmunix Note that the original filename is not prefixed with ‘.’. HP LTO Ultrium 4 drives technical reference manual, volume 5: UNIX, Linux and OpenVMS configuration guide...
Glossary Berkeley and AT&T functional modes differ in “read-only” close functionality. In AT&T AT&T mode 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 44
Fibre Channel Fibre Channel provides an inexpensive yet expandable 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.