HP LTO Ultrium 6 Tape Drives UNIX, Linux and OpenVMS Configuration Guide HP Part Number: n/a Published: August 2012 Edition: First
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Windows is a U.S.
Contents 1 Introduction...............................................................................................4 Purpose of this manual..............................................................................................................4 LTO Ultrium drives in a library................................................................................................4 SAS drives.......................................................................................................................
1 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.
2 HP (HP-UX) servers and workstations For supported versions of HP-UX, go to http://www.hp.com/go/connect. Before you install your tape drive, visit the HP web site, www.hp.com, and search to locate IT Resource Center (you may be required to set up a new login). Download the latest hardware enablement (HWE) patch bundle for your operating system. This ensures that you will have the correct device driver for your tape drive.
2-port U320 ext_bus 2-port U320 lan 2-port U320 lan 2-port U320 ba ba slot ext_bus ext_bus target tape processor processor ba ipmi tty acpi_node usbmsvbus ext_bus target disk SCSI/2-port 1000B-T Combo Adapter 1 0/3/1/0/4/1 mpt CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X U320 SCSI SCSI/2-port 1000B-T Combo Adapter 2 0/3/1/0/6/0 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T SCSI/2-port 1000B-T Combo Adapter 3 0/3/1/0/6/1 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T SCSI/2-port 1
If the lunpath hardware path for a giventape 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/estape and eschgr/schgr (media changer driver) to the kernel For HP-UX 11i v2 (11.
1. Enter sam at the command line. % sam 2. Select the following: Kernel Configuration > Kernel Configuration (character mode) > Modules 3. 4. 5. 6. 7. 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”. The stape driver is now added to the kernel.
5. 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: Figure 4 Adding estape driver to the kernel 6. If you wish, type in a Reason for Change, such as “Initial estape installation May 1st 2007” and then select the Modify tab. 7. Click the OK button at the Operation Successful page. Both estape and stape drivers will now be shown with Next Boot State as “static”. 8.
Actions > Create Device Files > Show Device Files 4. When you have exited sam, run ioscan to see the tape drive: %/sbin/ioscan -fnC tape All default device files displayed have compression enabled. NOTE: HP recommends the ‘Berkeley’ device files of most applications: nl cXtYdZBESTnb = Berkeley, no rewind, best available density nl cXtYdZBESTb = Berkeley, with rewind, best available density nl where: nl X = card number nl Y = target number nl Z = LUN number For HP-UX 11i v3 (HP-UX 11.31) 1.
sizes that are no larger than 256 KB. Please check your application documentation to find out how to check or configure block sizes used for transfers to and from tape or VTL devices. This is because, by default, the HP-UX stape driver processes a block size larger than 256 KB by subdividing it into 256 KB blocks for writing to tape (giving a net effect of 256 KB I/O transfers)6. For example a 1 MB block (1048576 bytes) is written to tape as four 256 KB blocks.
3 HP (OpenVMS) servers and workstations NOTE: SAS drives are not 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.
4 Linux servers and workstations TIP: Where convenient, do the original install of the Linux operating system with the tape drive attached to the SAS port, so that the st driver gets loaded with the kernel during boot up. Otherwise, see the guidelines below for cases where the operating system was already installed without the tape drive being available.
lsmod For example, the st driver for tape listing would resemble the entry shown below. Also shown below are three examples of HBA drivers—cciss and hpsa drivers (for HP SmartArray SAS HBAs), and mptsas driver (for LSI SAS HBA): Module st . . cciss . . mptsas . . hlsa Size 38749 Used by 0 68484 3 37321 0 47277 2 If a particular driver module is not listed as above use the modprobe utility to load it.
. . scsi3 : cciss Vendor: HP Model: Ultrium 6-SCSI Rev: ZxxD Type: Sequential-Access ANSI SCSI revision: 06 scsi 3:0:0:0: Attached scsi generic sg0 type 1 st: Version 20050830, fixed bufsize 32768, s/g segs 256 st 3:0:0:0: Attached scsi tape st0 . . The tape drive instance identifies which device files are applicable to the tape drive. For example: • st0 indicates device files /dev/st0 or /dev/nst0 • st1 indicates device files /dev/st1 or /dev/nst1 and so on...
What next? Once device files have been created, you should confirm that your new tape drive is working properly. “Verifying the installation” (page 25) provides instructions on backing up and restoring a sample file to test your installation.
5 IBM (AIX) servers and workstations For supported versions of AIX, see http://www.hp.com/go/connect.
Select the tape drive you wish to change. The example above shows an LTO FC tape drive as available for selection. 4. The following details are displayed: Check the following values and change them if necessary: • BLOCK Size (0=variable length)= 0 • Use EXTENDED file marks = “no” • RESERVE/RELEASE support = “yes” • Set timeout for the READ or WRITE command = 1200 Click on the “OK” button to apply the changes. If you are using a non-graphics terminal 1.
Select the tape drive you wish to change. The example above shows an LTO FC tape drive as available for selection. 4. The following details are displayed: Check the following values and change them if necessary: • BLOCK Size (0=variable length) = 0 • Use EXTENDED file marks = “no” • RESERVE/RELEASE support = “yes” • Set timeout for the READ or WRITE command = 1200 Press the Enter key (“Do”) to apply the changes. Refer to http://www.hp.
The n 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. 20 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.
6 Oracle (Solaris) servers and workstations For supported versions of Solaris, see http://www.hp.com/go/connect. Fibre Channel drives Before configuring your system to support an HP LTO Ultrium drive, ensure that the drive is visible to the Oracle 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.
An output containing, for example, “/devices/pci@0/pci@0/pci@8/pci@0/pci@1/LSILogic,sas@0:scsi::rmt/1” indicates an SAS tape drive connected via an LSI SAS HBA.
b. Unload the kernel module: # modunload -i 96 c. Load the kernel module back in: # modload -p drv/st d. Rebuild the device paths: devfsadm -C devfsadm -i st For further details, see How do you load st.conf changes without rebooting, Oracle support document 18010, on http://support.oracle.com/search/document.do? assetkey=1-9-18010-1&searchclause=18010 This link is valid for registered Oracle users with a valid Oracle Service Plan. 3. You should now be able to use the drive.
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.
7 Verifying the installation 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: 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.
3. Read the file back from tape: % cd /tmp nl % tar xvf The ‘x’ option to tar here means “extract from the archive”. Use the same value for the argument as in step 2. 4. Compare the original with this retrieved file: % cmp /tmp/ This compares the files byte by byte. If they are the same, there should be no output, and this verifies that the installation is correct.
8 Support and other resources Related documents For a general background to LTO technology and licensing, go to http://www.lto-technology.com. See http://www.t10.org/t10_main.
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” 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.
Index A AIX, 17 ANSI, 27 AT&T mode, 28 B Berkeley mode, 28 BOT, 28 buffered mode, 28 C compression, 28 confirming installation, 25 D device files AIX, 19 IBM (AIX), 17 direct access, 28 documents, related, 27 Oracle systems, 21 Oracle workstations data values, 23 identifying attached devices, 21 P PC-based UNIX - Linux, 13 S SAN, 28 sequential access, 28 servers OpenVMS, 12 Solaris, 21 storage area network, 28 systems HP-UX, 5 Linux, 13 V verifying installation, 25 E W ECMA, 27 workstations OpenV
