Functional Issues - Qlogic SANsurfer FC HBA Manager User Manual

9 – Troubleshooting
Troubleshooting Problems and Solutions

Functional Issues

Table 9-3
Manager, and provides possible causes and solutions.
Problem
Unable to create failover con-
figuration.
Unable to create load bal-
ance configuration.
Unable to mask LUNs.
Unable to set device path as
visible, hidden, or unconfig-
ured.
Unable to set LUN path as
preferred or alternate.
Unable to get host Informa-
tion.
9-8
lists functional problems that may occur with using SANsurfer FC HBA
Table 9-3. Troubleshooting: Functional Issues
Cause: An incorrect version of SANsurfer FC HBA Manager is installed
or SANsurfer FC HBA Manager detected an invalid configuration.
Solution: To create a failover configuration, the following criteria must
be met:
The host system must contain two or more HBAs.
The storage subsystem must report the same device node name
and separate device port names for each port.
The storage subsystem must report the same total number of LUNs
down each path.
The storage subsystem must report the same LUN numbers for
each port.
Cause: SANsurfer FC HBA Manager detected an invalid configuration.
Solution: To enable load balancing, each storage subsystem must
report multiple LUNs. If a JBOD is used, each device must be individu-
ally configured and manually balanced.
Cause: The LUN path is unconfigured.
Solution: In the Fibre Channel Configuration dialog box, set the device
path to visible (or hidden, if a failover configuration will be saved).
Cause: The SANsurfer FC HBA Manager user interface or qlremote
agent did not detect any devices.
Solution: Verify that the SANsurfer FC HBA Manager user interface
shows the devices under their HBAs in the HBA tree. Each device
should show its device port name and its connected LUNs.
Cause: The LUN path is not configured or the devices were not
detected by the SANsurfer FC HBA Manager user interface or qlremote
agent.
Solution: Verify that the SANsurfer FC HBA Manager user interface
shows the devices under their HBAs in the HBA tree. Each device
should show its device port name and its connected LUNs.
Cause: The qlremote agent is not running or installed.
Solution: Verify that the qlremote agent is installed and running (see
"Verifying that qlremote is Installed and Running" on page
Cause and Solution
S
9-12).
SN0054651-00 B