Fibre Channel Guidelines
The following guidelines exist for AMASS running with fibre channel.
HP-UX Fibre
For AMASS users in a
A known error condition exists where the first SCSI
Note | Make sure that if this environment variable is being used to set it in the shell | |
before amassbackup and amassrestore are executed. | ||
|
Solaris Fibre
AMASS supports fibre on the Sun Solaris platform. When installing AMASS, the AMASS juke driver may be unable to attach to fiber attached drives and libraries. If you have this problem, please call ATAC for assistance.
SGI IRIX 6.5 Fibre
AMASS uses symbolic links (/dev/rjuke1, /dev/rj1d1..) that are mapped to system device files.
For example: /dev/rjuke1
However, the AMASS install process may have trouble creating symbolic links for fibre devices attached to a fabric under IRIX 6.5.14 and later. For instance, after entering the desired controller, target, and Logical Unit Number (LUN), you might receive the following error message.
Failed to build a path to the device for you.
Please enter the explicit device path:
To find the explicit device path, use the following steps. You can also use the same steps to determine the explicit device path for other fibre devices. This example tries to determine the device path for the first device listed in Step 1.
Fabric Tape: node 1000006045170ad2 port 2001006045170ad2, lun 2 on SCSI
controller 8: unknown
1Perform an hinv system call.
# hinv grep
Fabric Tape: node 1000006045170ad2 port 2001006045170ad2, lun 2 on SCSI
controller 8: unknown
Fabric Tape: node 1000006045170ad2 port 2001006045170ad2, lun 4 on SCSI
controller 8: unknown
Fabric Tape: node 1000006045170ad2 port 2001006045170ad2, lun 6 on SCSI
controller 8: unknown
Fabric Tape: node 1000006045170ad2 port 2001006045170ad2, lun 8 on SCSI
controller 8: unknown
2Look at the contents of the /dev/scsi or /hw/scsi directories and match the output from the hinv system call for the desired device.
14 | © December 2004, ADIC |