HP LTO Ultrium 5 tape drives UNIX, Linux and OpenVMS configuration guide Part number: n/a First edition: January 2010
Legal and notice information © Copyright 2010 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 ....................................................................................... 6 Purpose of this manual ................................................................................................................ LTO Ultrium drives in a library ................................................................................................ SAS drives ..........................................................................................................................
HP-data values ......................................................................................................................... 28 7 Verifying the installation .................................................................... 31 Verifying the installation of the drive (UNIX) .................................................................................. 31 To verify the installation: ......................................................................................................
Figures 1 SAM GUI ............................................................................................................... 10 2 SAM text-based interface ......................................................................................... 10 3 SMH web-based interface (HP-UX11i v3) ................................................................... 11 4 Adding estape driver to the kernel .............................................................................
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.
Fibre Channel drives have a slightly different format in ioscan output, similar to the following segment: For 11i v3 (Agile I/O tree view) Enter the command: % ioscan -m lun The output should look similar to the following1 which includes an LTO 5 SAS drive. Fibre Channel tape drives have a similar format in this type of ioscan output: 1 Note that device files (such as /dev/rtape/tape9_BEST) may or may not be in place initially.
For a given SAS device the SAS address can be obtained from the Lun H/W Path. For example: The lunpath hardware path for the above tape drive is “0/2/0/0/0/ 0.0x500110a0013091b8.0x0”. • The SAS bus ID is “0/2/0/0/0/0” (including all the numbers separated by “/”). From the remaining “0x500110a0013091b8.
Figure 1 SAM GUI . Figure 2 SAM text-based interface . 1. Enter sam at the command line. % sam 2. Select the following: Kernel Configuration > Kernel Configuration (character mode) > Modules 3. Highlight the stape driver. If the driver has not been added to the kernel, both Current State and Planned State will read “unused”. 4. Type “m to modify the stape driver and “s” to set it to “static”. The Planned State will now read “static”. 5. The stape driver is now added to the kernel. 6.
7. Reboot the system. For HP-UX 11iv3 (11.31) 1. Start up the SMH web-based interface. % smh –w This will attempt to launch a web browser. Mozilla browser2 is the default when HP-UX 11i v3 is installed. 2. From the SMH Tools page, select Modules from the Kernel Configuration section: Figure 3 SMH web-based interface (HP-UX11i v3) . 3. In the Search box on the Kernel Configuration page, type stape and execute the search. The search results list will include both estape and stape modules.
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.
2. Select the following: Peripheral Devices > Tape Drives sam will then scan the system for any tape drives connected. For example, when an HP LTO Ultrium 5 drive is found, for example, it will be displayed as something like: Hardware Path Driver Description =========================================================== 8/0/2/0.3.0 stape HP Ultrium 5-SCSI 3.
Figure 5 Selecting a tape device to create its device files (Agile View) . 4. From the right-hand panel on the HP-UX Peripheral Device Tool page, click on Reinstall Device Files. At the next page, click the Reinstall button. When the browser returns to the HP-UX Peripheral Device Tool page, click the Refresh button one or more times until the list of device files appears under the Properties header.
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.
HP (OpenVMS) servers and workstations
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.
. mptsas 37321 0 If a particular driver module is not listed as above use the modprobe utility to load it. For example if the st driver is missing, execute: modprobe st NOTE: Loading of the st driver should happen naturally if your system is rebooted after attaching the drive.
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... A list of tape device files gets created automatically when the st driver module and the correct HBA driver have been added.
Linux servers and workstations
5 IBM (AIX) servers and workstations For supported versions of AIX, see http://www.hp.com/go/connect.
3. A pop-up window is displayed: 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.
2. The following is displayed: Select “change/show characteristics of a tape drive” 3. A pop-up window is displayed: Select the tape drive you wish to change. The example above shows an LTO FC tape drive as available for selection. 4.
Device filenames under AIX Use device filenames as listed below for the combination of Rewind on Close, Retension on Open, and Compression that you want: Filename Rewind on Close Retension on Open Compression /dev/rmtn Yes No enabled /dev/rmtn.1 No No enabled /dev/rmtn.2 Yes Yes enabled /dev/rmtn.3 No Yes enabled /dev/rmtn.4 Yes No disabled /dev/rmtn.5 No No disabled /dev/rmtn.6 Yes Yes disabled /dev/rmtn.
6 Sun (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 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.
% cfgadm -al |grep tape This produces output lines with a format similar to the following: c9::rmt/0 tape connected configured unknown The rmt/K entry indicates the tape device file, where K is the instance number. In the above example, rmt/0 indicates a set of device file options for one tape drive, such as /dev/rmt/0cb, /dev/rmt/ 0cbn, and so on.
1. In the file /kernel/drv/st.conf, after these lines: ######## # # Copyright 2004 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # #pragma ident "@(#)st.conf 1.
3. You should now be able to use the drive. • Use /dev/rmt/Kcb if you require a compression rewind device file, where K is the relevant device file instance. • Use /dev/rmt/Kcbn 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. “Verifying the installation” on page 31 provides instructions on backing up and restoring a sample file to test your installation.
Parameter Value Meaning 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, variable records not limited to 64 KB, auto-density over-ride and MODE SELECT compression.
Sun (Solaris) servers and workstations
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 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.
2. Write a sample file to tape, using ‘tar’: % cd /% tar cvf The options to tar have the following meanings: c Create a new archive (backup file) on the device. v Operate in verbose mode. f Specify the device file explicitly. 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.
2. Change directory to root: % cd / nl 3. Back up /stand/vmunix to tape: % tar cvf /dev/rmt/c4t3d0BESTnb ./stand/vmunix nl Note the prefix of ‘.’ to the filename. 4. Change to the temporary directory: % cd /tmp nl 5. Extract the file from the tape: % tar xvf /dev/rmt/c4t3d0BESTnb nl 6. Compare the original with the restored version: % cmp /stand/vmunix /tmp/stand/vmunix nl Note that the original filename is not prefixed with ‘.’.
Verifying the installation
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.
Support and other resources
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.
groups. On the other hand, infinite flush means that data can remain in the buffer for very long periods of time, and could be lost in the event of a power failure. LUN Logical Unit Number, by which different logical units within a particular device can be addressed individually. Each logical unit contains a device server. The drive provides a SSC device server, typically at LUN 0, and an ADC device server, typically at LUN 7.
Index A AIX, 21 ANSI, 35 AT&T mode, 37 B Berkeley mode, 37 BOT, 37 buffered mode, 37 C ISO, 35 L Linux, 17 LUN, 38 M mode AT&T, 37 Berkeley, 37 immediate, 37 compression, 37 confirming installation, 31 O D OpenVMS servers, 15 OpenVMS servers and workstations determining attached devices, 15 device files AIX, 24 IBM (AIX), 21 direct access, 38 documents, related, 35 E ECMA, 35 F fibre channel, 37 filemarks, 37 filenames under AIX, 24 H HP-UX systems, 7 I IBM (AIX), 21 device files, 21 immediate
W workstations OpenVMS, 15 40
