![]() |
![]() |
To use a device, you must install the appropriate device driver. Tivoli Storage Manager provides its own device driver for non-IBM devices. The IBM device driver IBMTape is supported for IBM devices. These device drivers are available on the ftp site ftp://ftp.software.ibm.com/storage/devdrvr/. Tivoli Storage Manager also supports third party vendor device drivers if the devices are associated with the GENERICTAPE device class and the hardware vendor also supports that device driver. Using a device class other than GENERICTAPE with a third party vendor device driver is not recommended.
Table 7 and Table 8 list the device drivers needed for Tivoli
Storage Manager drives and libraries.
Table 7. Device Drivers for Tape and Optical Drives
Device | Device Type | Library | Device Driver |
---|---|---|---|
4MM drive | 4MM | External, Manual, SCSI | Tivoli Storage Manager device driver |
8MM drive | 8MM | External, Manual, SCSI | |
DLT drive | DLT | External, Manual, SCSI | |
DTF drive | DTF | External, Manual, SCSI | |
QIC drive | QIC | External, Manual, SCSI | |
STK SD3, 9490, 9840, 9940 drive | ECARTRIDGE | External, Manual, SCSI, ACSLS | |
Optical drive | OPTICAL | External, Manual, SCSI | |
WORM drive | WORM | External, Manual, SCSI | |
IBM 3570 drive | 3570 | External, Manual, SCSI | IBMtape |
IBM 3480, 3490, 3490E drive | CARTRIDGE | External, Manual, SCSI, ACSLS, 349X | |
IBM 3590, 3590E drive | 3590 | External, Manual, SCSI, ACSLS, 349X | |
IBM LTO 3580 drive | LTO | External, Manual, SCSI |
Table 8. Device Drivers for Automated Libraries
Device | Library Type | Device Driver |
---|---|---|
IBM MP 3570, 3575 Library | SCSI | IBMtape |
IBM LTO 3581, 3583, 3584 Library | SCSI | |
IBM 3494, 3495 Library | 349X | lmcpd |
Non-IBM SCSI libraries | SCSI | Tivoli Storage Manager device driver (tsmscsi) |
To work with removable media devices, Tivoli Storage Manager needs the device's special file name. You specify the device special file name when you issue the DEFINE PATH commands for drives and libraries.
For an IBM 349X, the device name is the symbolic name you entered in the configuration file for the library. During configuration of devices other than a 349X, one or more device special file names are created. Table 9 shows the form of the names. In the examples, x denotes a number (0-7).
The special file is a symbolic link into the /devices tree of the file system. The symbolic link destination has the form:
/devices/.../mt@x,0:mt
where x is the SCSI ID of the device.
Description | Device Example | Logical File Name |
---|---|---|
Tape drives that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xmt | xmt |
SCSI-attached libraries that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xlb | xlb |
Optical drives that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xop | xop |
IBM 3490, 3575, 3581, 3583, 3584, and 3590 tape drives, which are supported by the IBMtape device driver | /dev/rmt/xst | xst |
Medium changer of an IBM 3570 or an IBM 3590 B11 with Automatic Cartridge Facility (ACF) feature, which is supported by the IBMtape device driver | /dev/rmt/xsmc | xsmc |
Mount point to use on REMOVABLEFILE device type (CD-ROM) | /dev/cdx | cdx |
File system to use on REMOVABLEFILE device type (zip drive) | /zip | Not applicable |
To install the device drivers for IBM 3490, 3570, 358X, and 3590 devices, see
After completing the procedure in the manual, a set of special file names are available for each device. To see the special file names, use the command
ls -la /dev/rmt
The output shows that the special files are really symbolic links into the /devices tree of the file system.
/dev/rmt/xst
where x is a number. The name may have additional characters (n, b, c) at the end to indicate different operating characteristics. Enter the device name that you select in the Device Name field on the worksheet that applies to your device (see http://www.tivoli.com/support/storage_mgr/tivolimain.html).
The name for the drive typically has the form:
/dev/rmt/xst
where x is a number. The name may have additional characters (n, b, c) to indicate different operating characteristics. Enter the name that you select for the drive in the Device Name field for the drive. For example, to use the compression capability of the drive, enter:
/dev/rmt/1stc
The name for the medium changer has the form:
/dev/rmt/xsmc
where x is a number. The smc stands for SCSI medium changer. Enter this name in the Device Name field for the library's medium changer (robotics). For example:
/dev/rmt/0smc
For an IBM 349X Tape Library Dataserver, refer to IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide (GC35-0154) to install the driver. The driver is the IBM Tape Library Driver, which consists of the lmcpd (a daemon) and other components.
To determine the name to use to define the path for the library, check what you entered in the /etc/ibmatl.conf file for the library's symbolic name. Use this information to complete the Device Name field on your worksheet. For example, if the symbolic name for the library in the /etc/ibmatl.conf file is 3494a, enter that name on the worksheet in the Device Name field for the library.
The drives that are in the library are set up separately. See Installing Device Drivers for IBM SCSI Tape Devices.
If you are configuring a tape library, you must set up the device drivers for both the drives in the library and the library itself.
Attention: Tivoli Storage Manager /mt device drivers do not support the Sun Solaris mt command.
To install the Tivoli Storage Manager device drivers for tape drives and libraries , do the following:
Add one stanza (as shown in the example at the top of the file) for each tape drive SCSI target ID, LUN combination that you want the device driver to probe for supported tape drives and for each autochanger device in the system that you want the server to use.
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt
To add a library, enter the following command:
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
> ls -l /dev/rmt/*mt
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../mt@x,0:mt, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xmt special file names to provide to the server when you issue a DEFINE PATH command.
> ls -l /dev/rmt/*lb
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE PATH command.
If you are configuring an optical library, you must set up the device drivers for both the drives in the library and the library itself.
To install the Tivoli Storage Manager device driver for optical drives and optical libraries, do the following:
Add one stanza (as shown in the example at the top of the file) for each optical drive and optical library in the system that you want the server to use.
/usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/op
To add a library, enter the following command:
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
ls -l /dev/rmt/*op
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../op@x,0:op, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xop special file names to provide to the server when you issue a DEFINE PATH command.
> ls -l /dev/rmt/*lb
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE PATH command.