Detailed instructions for use are in the 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 Solutions, LLC. All rights reserved Seagate and the Seagate logo are trademarks of Seagate Technology, LLC. Viper is a trademark of Seagate Removable Storage Systems, LLC. Other product names are trademarks or registered trademarks of their owners. Seagate reserves the right to change, without notice, product offerings or specifications. No part of this publication may be reproduced in any form without written permission from Seagate Removable Storage Solutions, LLC.
T-010, Rev. B
November 13, 2001
9LSHU 81,;&203$7,%,/,7<*8,'(
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
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
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 Fast Wide SCSI Wide Ultra SCSI Wide Ultra2 SCSI Ultra 3 SCSI Maximum Transfer rate 20 Mbytes per second 40 Mbytes per second 80 Mbytes per second 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,'(
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
Configuring for the DEC/Compaq Unix Environment
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.
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,'(
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
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)
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 sd34 st21 st22 at at at at ithps0: ithps0: ithps1: ithps1: target target target target 2 4 0 1 lun 0 lun 0 lun 0 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
9LSHU 81,;&203$7,%,/,7<*8,'(
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
200 not be attached to esp controllers. This controller is not fast enough to work with the Viper 200. The minimum recommended controller would be a glm controller which is a Ultra Wide controller. We recommend Ultra2 SCSI capable controllers capable of 80MB/s data transfer. Ultra 3 controllers supporting 160MB/s transfer rates can also be used.
Configuring the device file st.conf
To configure Solaris 2.4 and above to use the Viper 200 correctly, add the following lines to the file st.conf in the directory /kernel/drv.
tape-config-list= "SEAGATE ULTRIUM06242-XXX","Seagate LTO","SEAGATE_LTO"; SEAGATE_LTO = 1,0x36,0,0x1d639,4,0x00,0x00,0x00,0x00,1;
Note: The inquiry string above contains one space between SEAGATE and ULTRIUM. The value 0x1d639 equates to the manner in which the Viper 200 will be configured to operate in the Solaris environment. This value enables the Viper 200 to: · · · · · · · · ·
T-010, Rev. B
Support variable length records (variable length block size) Backspace over files (same as `mt bsf' command to backspace over filemarks) Backspace over records (same as `mt bsr', backspace over individual tape blocks) Long timeout for long erase function (it is not recommended to try and erase the entire tape) Viper 200 knows when end of data has been encountered Device driver is unloadable Long timeouts ( 5 times longer than normal) Buffered writes supported Variable record size not limited to 64k
November 13, 2001
9LSHU 81,;&203$7,%,/,7<*8,'(
·
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
Uses Mode Select Page 10h to enable/disable compression
Once st.conf has been modified, the kernel must be reconfigured by booting the system using the boot -r command. If you are replacing a tape device with the same SCSI ID you may want to delete the st devices from the /dev/rmt directory (recommended). When using commands that require a blocking factor such as tar, ufsdump, ect., we suggest a minimum factor of 64. The preferred factor is 128. For commands that use density and tape size settings the tape density is 124,000 bpi and the tape length is 1800 feet. We suggest using the ufsdump/ufsrestore commands. These commands automatically detect end of tape without the need of the density and tape length settings. To enable the st driver to turn on data compression when writing data to tape use the `c' option. For example, tar cf /dev/rmt/0c would cause the Seagate Ultrium tape drive to compress the data before writing the data to tape.
Configuring for the IBM AIX Environment (AIX Version 4.1.x and later)
Finding existing SCSI controllers and devices
Enter the following command: lsdev ÂCs scsi. This will show all of the SCSI target id's known to the system. Note the SCSI target id's and choose a SCSI id for the Viper 200 that will not conflict with the id's shown from the lsdev command. 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. See figure 1 to view how to set the SCSI ID address jumpers for the Viper 200.
Configuring the Viper 200 using SMIT
The Seagate Viper 200 tape drive can be configured to work with AIX Versions 4.1.x and later by using the SMIT "Other SCSI Tape Drive" option. NOTE: Record the SCSI ID of the tape drive before installing it. To configure AIX using the SMIT utility, use the following procedure: 1. Enter SMIT at the Tape Drive menu by typing "smit tape"
T-010, Rev. B November 13, 2001
9LSHU 81,;&203$7,%,/,7<*8,'(
2. Select "Add a tape Drive"
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
3. Select the type of tape drive you will be adding. Use the "Other SCSI Tape Drive" option. 4. Select the Parent SCSI Adapter from the available list 5. The Add a tape Drive "Entry Fields" now appear. Some of the standard options need can be changed to maximize drive performance and functionality: 1. Set the Connection Address with the Drives Target and Lun ( always use Lun 0 ). In the list, the Target is the first number and the Lun is the second. For example, if the drive is ID 5, choose 5,0 2. Set the "BLOCK size" to 0 3. Set "Use DEVICE BUFFERS during writes" to yes. 4. Set "RETURN error on ape change or reset" to no 5. Set "Use EXTENDED file marks" to yes. 6. Set "RESERVE/RELEASE support" to yes 7. Set "BLOCK SIZE for variable length support(Num.)" to 0 8. Set "Density 1" to 0 Leave the "Set delay. . ." and "Set timeout. . ." lines at the default value. Click on OK and the drive will be installed in the system database, and devices created. There is no need to reboot the system. Now exit SMIT Notes: We suggest using the AIX commands `backup' and `restore' when transferring data to and from the Viper 200. These commands transfer data more quickly than other commands such as tar and cpio. For cpio we suggest a blocking factor of 128. For tar we suggest using the ÂN option and a factor of 128. Some older systems with poor video controllers may experience a reduction in performance when using the Âv option which prints the path names
T-010, Rev. B November 13, 2001
9LSHU 81,;&203$7,%,/,7<*8,'(
6HDJDWH 7DSH 2SHUDWLRQV &RVWD 0HVD &$
on the standard console during the backup. Unless there is a real need to see the filenames as they are backed up we suggest not using the Âv option. For commands that use density and tape size settings the tape density is 124,000 bpi and the tape length is 1800 feet.
Configuring for SCO Open Server 5.0.x
Finding existing SCSI controllers and devices
The files /usr/adm/hwconfig and /var/adm/messages list the devices found during boot up of Open Server. The current SCSI controllers can be found using the command:
grep adapter /usr/adm/hwconfig
which will produce and out similar to:
%adapter 0x6400 Â 0x64FF fts=st0. 11 type=alad ha=0 bus=0 id=7
The current tape drives can be found using the command:
grep tape /usr/adm/hwconfig
which will produce and out similar to:
%tape type=S ha=0 id=6 lun=0 bus=0 ht=alad
The information above shows that an Adaptec SCSI controller is installed (alad) and a SCSI tape drive (type=S) is installed as target id 6. SCSI ID #7 is almost always dedicated to the SCSI controller. Never configure your target device for ID 7 unless you are absolutely sure th ...
