User's Guide

9LSHU
81,;&203$7,%,/,7<*8,'(
T-010, Rev. B November 13, 2001
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:
• 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