Manualshelf

User`s guide

ManualsBrandsQlogic ManualsAdapterSANsurfer FC/CNA HBA CLI
12345678910
7.2.5 Warning Messages on Startup
Issue: When launching SANsurfer FC HBA CLI, the following warning messages may appear on the
console:
qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.1: Unable to read SFP data (102/a0/0).
qla2xxx 0000:01:02.0: Unable to read SFP data (102/a0/0).
The driver displays these messages when it is unable to read small form factor pluggable (SFP) data.
You can safely ignore them.
Workaround: None
7.2.6 Manually Starting IOCTL Module on Red Hat 4.x Systems
On Red Hat 4.x systems, an input/output control (IOCTL) module is used to communicate between
SANsurfer and the driver. If you are using an earlier version of SANsurfer (prior to 1.7.1.b26), you
must manually start the IOCTL module. After installing but before starting SANsurfer, execute the
following command:
# modprobe -a qioctlmod
7.3 Solaris
7.3.1 Slow Startup in Interactive Mode with Serial Console Server
Issue: On Solaris, when launching SANsurfer FC HBA CLI in interactive mode from a Telnet session
using a serial console port login, SANsurfer FC HBA CLI takes a long time to start.
Workaround: To resolve the issue, add the int flag to the command used to start the interactive mode.
For example:
# scli int
7.3.2 Stale Semaphore Left Behind
Issue: During normal operation of SANsurfer FC HBA CLI on Solaris, a stale semaphore may be left
behind, causing all tools (SANsurfer FC HBA Manager and SANsurfer FC HBA CLI) to fail on load.
Workaround: Manually remove the following two files:
/var/tmp/.SEMD
/var/tmp/.SEML
7.3.3 FCode/BIOS Update Not Available with Sun-branded 2Gb Adapters
Issue: SANsurfer FC HBA CLI does not support FCode/BIOS update with Sun-branded 2Gb adapters.
Workaround: None
7.4 Mac OS X
7.4.1 Adapter Instance Number Changes at Reboot
Issue: With Mac OS X, the adapter instance number may not be the same as the current number after
the next reboot. SANsurfer FC HBA CLI does not accept the adapter number as a valid input and will
abort the command.
SANsurfer FC/CNA HBA Command Line Interface (CLI) Readme
8 of 10