
Configuring Robotic Controls
If the devices do not exist, you can create device files by using the mknod command as
follows. See the scsi_ctl(7) man page.
mkdir /dev/sctl
cd /dev/sctl
/usr/sbin/mknod c
CONTROLLER
t
TARGET
l
LUN
c 203 0x
IITL
00
Where:
◆ CONTROLLER is the Instance number of the controlling bus. The Instance value is
displayed in ioscan -f output under column I of the controller entry (ext_bus in
the Class column).
◆ TARGET is the SCSI ID of the robotic control.
◆ LUN is the SCSI logical unit number.
◆ II are two hexadecimal digits that identify the controlling bus interface card by its
Instance number (same as controller).
◆ T is one hexadecimal digit representing the SCSI ID.
◆ L is one hexadecimal digit representing the SCSI LUN.
Using ioscan With sctl Robots
If the robotic control has its own SCSI ID, it has an entry similar to the following:
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
unknown -1 2/0/1.1.0 unknown UNCLAIMED UNKNOWN LAGO SYSLS-340L
The Class, I, and Driver columns may also have invalid information. In these instances
the robotics are correct, but ioscan returns invalid information.
Chapter 4, Hewlett-Packard HP-UX 57
Comentários a estes Manuais