The troubleshooting sections that follow provide tips for dealing with problems that might occur when you are running the FC protocol with the Host Utilities.
(FC) Linux hosts with QLogic initiators fail to detect LUNs
A Linux host with QLogic initiators fails to detect LUNs mapped to it when configured to autonegotiate port topology and speed. This can cause the host to miss a few LUNs during the HBA scan. This behavior persists even after rebooting the host.
(FC) Poor performance due to misalignment of partitioned LUNs
If you experience poor performance on some or all FC LUNs that have partitions, it might be due to an alignment mismatch between the LUN block boundaries and the underlying WAFL boundaries.
(FC) sanlun command displays error when HBA libHBAAPI.so is missing
The sanlun command uses the HBAAPI software provided by both the host operating system and the HBA vendor's API plugins to gather information about the HBAs, including their WWPNs. If this software is not available, the sanlun command returns an error message.
(FC) LUNs are unavailable after a storage system failover or giveback
The host requires specific driver, HBA, and FC switch zoning settings to maintain LUN access across a storage system takeover, giveback, and reboot. You should confirm that you have set the required driver and HBA settings. Also, verify that you have correctly zoned your FC switches.
(FC) SCSI rescan issues on SUSE Linux Enterprise Server hosts
On a SUSE Linux Enterprise Server host connected to a storage controller, the presence of dummy LUNs causes issues during a SCSI rescan. This issue is not yet resolved in SUSE Linux Enterprise Server 9 and SUSE Linux Enterprise Server 10.
