Quantum LTO-1 User's Guide

9LSHU
81,;&203$7,%,/,7<*8,'(
6HDJDWH
7DSH 2SHUDWLRQV
&RVWD 0HVD &$
Viper® 200 LTO Tape Drive
Unix Compatibility Guide
Introduction................................................................................................2
Configuring for the DEC/Compaq Unix Environment.............................3
Configuring for the Sun Environment
(Solaris 2.4, 2.5, 2.6, 7, and 8) ...................................................................5
Configuring for the IBM AIX Environment
(AIX Version 4.1.x and later)......................................................................7
Configuring for SCO Open Server 5.0.x...................................................9
Configuring for Linux ..............................................................................11
Configuring for SGI Irix ...........................................................................12
Configuring for HP-UX 11.0.....................................................................14
© 2000-2001 Seagate Removable Storage Solut i ons, LLC. All rights reserved Seagate and the Seagate logo are trademarks of Seagate Technology, LLC. Viper is a tradem ark of Seagate
Removable Storage Syst em s, LLC. Other product names are trademarks or regis tered trademarks of their owners.
Seagate reserves the right t o change, without notice, product offeri ngs or specifications. No part of t hi s publication may be reproduced in any form without written permission from S eagate Removable Storage Solutions, LLC.
T-010, Rev. B November 13, 2001
Introduction
This document describes how to configure various UNIX systems to recognize and obtain optimal performace from the Seagate Viper 200 LTO Ultrium tape drive. It summarizes drive configuration options, as well as changes that may be required at the operating system level.
Note: Seagate makes no Warranty of any kind with regard to this
document. Seagate shall not be liable for any errors contained herein, or indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this document.
A word about SCSI controllers
9LSHU
81,;&203$7,%,/,7<*8,'(
6HDJDWH
7DSH 2SHUDWLRQV
&RVWD 0HVD &$
The Viper 200 is capable of transferring date at 32 Mbytes per second with 2:1 compression of the data. The Viper 200 also supports the SCSI Ultra2 specification and can transfer data at burst rates of up to 80 Mbytes per second . In order to achieve maximum drive performance, it is important to choose high performance disk drives for your system, as well as high performance SCSI controllers. The table below lists the types of SCSI controllers that Seagate recommends, in order of least preferred to most preferred.
Controller type Maximum Transfer rate
Fast Wide SCSI 20 Mbytes per second Wide Ultra SCSI 40 Mbytes per second Wide Ultra2 SCSI 80 Mbytes per second Ultra 3 SCSI 160 Mbytes per second
(For definitions of the terms used above, please refer to SCSI Trade Organization web site: http://www.scsita.org/aboutscsi/index01.html)
T-010, Rev. B November 13, 2001
9LSHU
81,;&203$7,%,/,7<*8,'(
Configuring for the DEC/Compaq Unix Envi ronment
Finding existing SCSI controllers and devices
SCSI ID #7 is almost always dedicated to the SCSI controller. Never configure your target device for ID 7 unless you are absolutely sure that the controller is not addressed for ID 7. Figure 1 shows the locations of the SCSI ID address jumpers for the Viper 200.
6HDJDWH
7DSH 2SHUDWLRQV
&RVWD 0HVD &$
Jumper Settings:
Drive-configuration jumper pins
Default settings:
Pins: Function:
1-2 SCSI ID bit 0 3-4 SCSI ID bit 1 5-6 SCSI ID bit 2 7-8 SCSI ID bit 3
9-10 Reserved
11-12 Termination Power
SCSI ID=0 SCSI ID=1 SCSI ID=2 SCSI ID=3 SCSI ID=4 SCSI ID=5 SCSI ID=6 SCSI ID=7
SCSI ID=8 SCSI ID=9 SCSI ID=10 SCSI ID=11 SCSI ID=12 SCSI ID=13 SCSI ID=14 SCSI ID=15 Term. power
Figure 1: SCSI jumper settings for the Viper 200
T-010, Rev. B November 13, 2001
9LSHU
81,;&203$7,%,/,7<*8,'(
6HDJDWH
7DSH 2SHUDWLRQV
&RVWD 0HVD &$
Digital Unix Version 4.0 and later/Compaq Tru64 Unix 5.x
Use File Manager to open the file /etc/ddr.dbase and create an entry as follows:
SCSIDEVICE # Type = tape Name = "SEAGATE" "ULTRIUM" # PARAMETERS: TypeSubClass = tk TagQueueDepth = 0 MaxTransferSize = 0x0ffffff # (16MB - 1) ReadyTimeSeconds = 180 # seconds
CMD_PreventAllow = supported CMD_ExtReserveRelease = supported BlockSize = 0 PwrMgmt_capable = 0
DENSITY: # DensityNumber = 0,2,3,4,5,6,7 DensityCode = default CompressionCode = 0x0 Buffered = 0x1
DENSITY: # DensityNumber = 1 DensityCode = default CompressionCode = 0x1 Buffered = 0x1
Save the file. Run the following command:
ddr_config -c
ddr_config
will take the default input file, ddr.dbase, and build a new device database. This is effective immediately, and there is no need to rebuild the kernel.
T-010, Rev. B November 13, 2001
9LSHU
81,;&203$7,%,/,7<*8,'(
Note: ddr.dbase is a unix shell script and is not written in C. This means #
is used to signify a comment, not /* and */ or //, as used in C. Make sure any comments included in this file are preceded with the # character.
To enable the tape driver to turn on data compression when writing data to tape use the ‘c’ option.
For commands that use density and tape size settings the tape density is 124,000 bpi and the tape length is 1800 feet. For commands that use a blocking factor we recommend a blocking factor of 64 as a minimum, preferably 128.
Configuring for the Sun Environment (Solaris 2.4, 2.5, 2.6, 7, and 8)
6HDJDWH
7DSH 2SHUDWLRQV
&RVWD 0HVD &$
Use the following for attaching the Viper 200 to Sun Sparc and Intel systems.
Finding current SCSI controllers and targets
In order to properly attach SCSI devices to hosts it is necessary to ensure that each target device has a unique SCSI address. The commands ‘modinfo’ and ‘dmesg’ can be used to find the SCSI controllers in use and the SCSI target devices installed.
For example, the command “dmesg | egrep “target” | sort | uniq” can find all SCSI controllers and SCSI targets. The output may look similar to:
sd32 at ithps0: target 2 lun 0 sd34 at ithps0: target 4 lun 0 st21 at ithps1: target 0 lun 0 st22 at ithps1: target 1 lun0
In this case the Viper 200 could be set for SCSI ID address 2 thru 6 and attached to controller ithps1 (this particular controller also supports SCSI addresses 8 thru 15). See figure 1 to view how to set the SCSI ID address jumpers for the Viper 200.
Types of controllers
You may be able to view the man pages of three types of SCSI controllers for Sun Sparc systems, esp, glm and isp. We recommend that the Viper
T-010, Rev. B November 13, 2001
Loading...
+ 10 hidden pages