Seagate ST11200N Technical Information PDF herunterladen (Seite 49)

Configuring Robotic Controls

Note Note that the smc device file only exists for IBM robots using the Atape driver. If

smc0 device files exist for SCSI-connected IBM silos, remove the smc0 device files

to allow for the use of ovpass0 files. See the VERITAS support site for a tech note

with instructions for removing the smc0 files. The headline of the tech note is

“Install_ovpass script does not appear to work upon AIX reboot”.

6. Display the newly created logical identifier for the device by using one of the

following commands:

/usr/sbin/lsdev -C -s scsi

/usr/sbin/lsdev -C -s fcp

In the following example output, ovpass0 is a SCSI robotic control device file:

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

The path name for these types of device files has the following form, where ovpass_id

is the logical identifier assigned to the device.

/dev/

ovpass_id

In this example, you would use the following device file path:

/dev/ovpass0

Examples of SCSI Robotic Control Device Files

Example 1

For this example, assume this robot is a LUN 0 controlled robot. The ovpass driver has

been installed and the desired SCSI robotic controller is controller 1 at SCSI ID 5, but the

device files do not exist.

1. Determine the logical identifier for the SCSI controller as follows:

/usr/sbin/lsdev -C -c adapter | grep 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

Chapter 3, IBM AIX 35

1 2 ... 44 45 46 47 48 49 50 51 52 53 54 ... 112 113

Keine Kommentare

Seagate ST11200N Technical Information Seite 49