
Configuring Robotic Controls
The output shows that the device files exist for tape and disk, but not for the SCSI
robotic control at controller 1 (scsi0) and SCSI ID 5 (5,0).
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
3. Create the device files by using the following command:
mkdev -c media_changer -t ovpass -s scsi -p scsi0 -w 5,0
4. Display the device files by issuing the following lsdev command:
/usr/sbin/lsdev -C -s scsi
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive
hdisk1 Available 00-01-00-1,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
ovpass0 Available 00-01-5,0 VERITAS Media Changer
For this example use the following device file path to configure the SCSI robotic
control connected to controller 1 and SCSI ID 5:
/dev/ovpass0
Example 2
For this example, assume this robot is a LUN 1 controlled robot, rather than LUN 0. The
ovpass driver has been installed, but the device files for SCSI robotic control at controller
1 with SCSI ID 3 and logical unit number 1 do not exist.
1. Determine the logical identifier for the SCSI controller:
/usr/sbin/lsdev -C -c adapter | grep -i SCSI
The following output shows that scsi0 is the logical name for SCSI controller 1:
scsi0 Available 00-01 SCSI I/O Controller
2. Check if the device files exist for ovpass at SCSI ID 5.
/usr/sbin/lsdev -C -s scsi
The following output shows that the device files exist for tape and disk, but not for the
SCSI robotic control at controller 1 (scsi0), SCSI ID 3, and logical unit number 1 (3,1):
hdisk0 Available 00-01-00-0,0 400 MB SCSI Disk Drive
rmt0 Available 00-01-00-3,0 Other SCSI Tape Drive
3. The device files can now be created using the following command:
mkdev -c media_changer -t ovpass -s scsi -p scsi0 -w 3,1
36 NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
Kommentare zu diesen Handbüchern