![]() |
![]() |
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 Atape 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 | Atape |
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 | Atape |
IBM LTO 3581, 3583, 3584 Library | SCSI | |
IBM 3494, 3495 Library | 349X | atldd |
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. You can use SMIT to get the device special file.
When a device configures successfully, a logical file name is
returned. Table 9 specifies the name of the device (or the special file name)
that corresponds to the drive or library. In the examples, x
denotes any number from 0 to 9.
Device | Device Example | Logical File Name |
---|---|---|
Tape drives that are supported by the Tivoli Storage Manager device driver | /dev/mtx | mtx |
SCSI-attached libraries that are supported by the Tivoli Storage Manager device driver | /dev/lbx | lbx |
Optical drives that are supported by the Tivoli Storage Manager device driver | /dev/ropx | opx |
Drives associated with the GENERICTAPE device type | /dev/rmtx | rmtx |
IBM 3570 devices and the Automatic Cartridge Facility feature of the IBM 3590 B11 as a library | /dev/rmtx.smc | rmtx |
IBM 3575, 3581, 3583, 3584 libraries | /dev/smcx | smcx |
IBM 349X libraries | /dev/lmcpx | lmcpx |
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, you receive a message from the system:
rmtx Available
Use the value of x, which is assigned automatically by the system, to complete the Device Name field on the worksheet that applies to your device (see http://www.tivoli.com/support/storage_mgr/tivolimain.html). For example, if the message is rmt0 Available, the special file name for the device is /dev/rmt0. Enter /dev/rmt0 in the Device Name field for the drive on the worksheet. Always use the /dev/ prefix with the name provided by the system.
rmtx Available
or
smcx Available
Note the value of x, which is assigned automatically by the system.
For example, if the message is rmt0 Available, enter /dev/rmt0 in the Device Name field for the drive. Enter /dev/smc0 in the Device Name field on the worksheet for the library's robotics. Always use the /dev/ prefix with the name provided by the system.
For an IBM 3494 or 3495 Tape Library Dataserver, refer to IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide (GC35-0154). After completing the procedure in the manual, you will receive a message (logical filename) of the form:
lmcpx Available
where x is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet. For example, if the message is lmcp0 Available, enter /dev/lmcp0 on the worksheet in the Device Name field for the library. Always use the /dev/ prefix with the name provided by the system.
Use the procedure in this section to configure Tivoli Storage Manager device drivers for autochangers for non-IBM libraries.
Run the SMIT program to configure the device driver for each autochanger or robot:
You will receive a message (logical filename) of the form lbX Available. Note the value of X, which is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.
For example, if the message is lb0 Available, the Device Name field is /dev/lb0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
Use the procedure in this section to configure Tivoli Storage Manager device drivers for non-IBM tape or optical drives.
Attention: Tivoli Storage Manager cannot write over tar or dd tapes, but tar or dd can write over TSM tapes.
Run the SMIT program to configure the device driver for each drive (including drives in libraries) as follows:
For example, if the message is mt0 Available, the Device Name field is /dev/mt0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
For example, if the message is op0 Available, the Device Name field is /dev/rop0 on the worksheet. Always use the /dev/r prefix with the name provided by SMIT.
The Tivoli Storage Manager device definition menus and prompts in SMIT allow for the management of both SCSI and FCP attached devices. The main menu for Tivoli Storage Manager has two options:
FC Port ID:
This is the 24-bit FC Port ID(N(L)_Port or F(L)_Port). This is the address identifier that is unique within the associated topology where the device is connected. In the switch or fabric environments, it is usually determined by the switch, with the upper 2-bytes which are non-zero. In a Private Arbitrated Loop, it is the Arbitrated Loop Physical Address(AL_PA), with the upper 2-bytes being zero. Please consult with your FC vendors to find out how an AL_PA or a Port ID is assigned
Mapped LUN ID
This is from an FC to SCSI bridge (also, called a converter, router, or gateway) box, such as an IBM SAN Data Gateway (SDG) or Crossroads 4200. Please consult with your bridge vendors about how LUNs are mapped. It is recommended that you do not change LUN Mapped IDs.
WW Name
The World Wide Name of the port to which the device is attached . It is the 64-bit unique identifier assigned by vendors of FC components such as bridges or native FC devices. Please consult with your FC vendors to find out a port's WWN
Product ID
The product ID of the device. Please consult with your device vendors to determine the product ID.
To configure an FC SAN-attached device: