
Configuring Robotic Controls
4. Display the FCP SCSI device files that have already been created by using the
following command:
/usr/sbin/lsdev -C -s fcp
5. If device files for the desired robotic control SCSI ID do not exist, create the files using
the following commands.
Note If you get an error (mkdev error code 0514-0520) while trying to configure a FCP
SCSI device, review the topic “Upgrading The SCSI Passthru Driver” on page 31.
mkdev -c media_changer -s scsi -t ovpass -p
controller
-w
id
,
lun
mkdev -c media_changer -s fcp -t ovpass -p
controller
-w
scsi_id
,
lun
Where:
◆ controller is the logical identifier of the drive’s SCSI adaptor, such as scsi0, scsi1 or
vscsi1.
◆ id is the SCSI ID of the robotic connection.
◆ scsi_id is the fibre channel identifier for the N_Port address (D_ID) of the robotic
connection.
◆ lun is the logical unit number of the robotic connection.
Several methods exist for determining the D_ID of the robot as follows:
◆ Inspect the name server for the switch (if available). Each vendor uses a unique
method to make this information available. Consult the documentation for the
switch vendor.
◆ Inspect the bridge for mapping information (if available). Each vendor uses a
unique method to make this information available. Consult the documentation
for the bridge vendor.
Chapter 3, IBM AIX 33
Comentários a estes Manuais