
Configuring Robotic Controls
Examples of Creating Device Files
Example 1
In this example the robotic control for a ADIC Scalar 100 library is on a SCSI bus with a
instance number of 7 (ext_bus entry, I column), SCSI ID 2 and LUN 0. The robotic control
for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0.
Use the following procedure to create the robotic device files:
1. Use the ioscan -f command to get information on the SCSI bus and the robotic
control.
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 7 0/7/0/1 c720 CLAIMED INTERFACE SCSI C896 Fast
Wide LVD
target 10 0/7/0/1.0 tgt CLAIMED DEVICE
tape 65 0/7/0/1.0.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 11 0/7/0/1.1 tgt CLAIMED DEVICE
tape 66 0/7/0/1.1.0 stape CLAIMED DEVICE QUANTUM SuperDLT1
target 12 0/7/0/1.2 tgt CLAIMED DEVICE
autoch 14 0/7/0/1.2.0 schgr CLAIMED DEVICE ADIC Scalar 100
target 13 0/7/0/1.3 tgt CLAIMED DEVICE
autoch 19 0/7/0/1.3.0 schgr CLAIMED DEVICE IBM ULT3583-TL
target 14 0/7/0/1.4 tgt CLAIMED DEVICE
tape 21 0/7/0/1.4.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
target 15 0/7/0/1.5 tgt CLAIMED DEVICE
tape 19 0/7/0/1.5.0 atdd CLAIMED DEVICE IBM ULT3580-TD1
2. The commands to create the device files follow. See the “Command Summary” on
page 70 for the mknod command format or see the scsi_ctl(7) man page.
cd /dev/sctl
/usr/sbin/mknod c7t2l0 c 203 0x072000
/usr/sbin/mknod c7t3l0 c 203 0x073000
This creates the following device files, which you specify to Media Manager during
configuration of the ADIC robotic control and IBM robotic control respectively:
/dev/sctl/c7t2l0
/dev/sctl/c7t3l0
Note It is important to also create the passthru driver device files for tape drives. See
“Configuring Tape Drives” on page 62.
58 NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
Kommentare zu diesen Handbüchern