ATTO Technology Celerity FC-41EL Troubleshooting Manual

ATTO Celerity FC Troubleshooting Guide for Linux
This document describes troubleshooting techniques that can be used to identify
and resolve issues associated with the ATTO Celerity Fibre Channel host
adapter. Some of these techniques may seem simplistic or overly obvious, but
these are the ones that are commonly overlooked and can take several hours of
frustration to find. It is important to only try one technique at a time. While
changing multiple variables may seem to be a time saver, it usually complicates
the troubleshooting process.
A.) Linux Operating Systems
The host adapter driver was loaded properly and everything was working, but
the devices do not show up after the computer was rebooted. On some Red Hat
Linux distributions, the driver may not automatically load when the system is
booted.
To enable driver autoload in Red Hat Enterprise Linux 3, 4, and 5, add the
following line to /etc/rc.modules after installing the driver:
modprobe celerityfc <Enter>
(Note: you may need to create /etc/rc.modules and make it executable with
'chmod +x /etc/rc.modules')
The host adapter can detect the target device at LUN 0 but not the devices at
LUN 1 or higher in Red Hat Linux version 3 with kernel 2.4.
When using version 2.4 of the Linux kernel (eg. Red Hat 3), devices on LUN 1 or
higher may not be detected automatically when the driver is loaded. This is a
known issue with the 2.4 kernel. To manually detect such devices, issue the
following command:
$ echo "scsi add-single-device <h> <b> <t> <l>" > /proc/scsi/scsi
Where <h> is the host, <b> is the port (always 0 for ATTO drivers), <t> is the
target, and <l> is the LUN. You can confirm that the device has been detected
by checking for it in /proc/scsi/scsi.
(Note: To automate the above "echo" command, write a script that executes at
boot time. You need to include a line for each LUN. One possibility is add these
lines to /etc/rc.d/rc.local for RedHat or to /etc/rc.d/boot.local for Suse.)
Page 1 of 5 Atto Technology, Inc. April 9, 2007