Troubleshooting
Troubleshooting Problems and Solutions
S
Functional Issues
Table
Table 7-3. Troubleshooting: Functional Issues
Problem | Cause and Solution |
|
|
Unable to create failover con- | Cause: An incorrect version of SANsurfer FC HBA Manager is installed |
figuration. | 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 adapters. |
| 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. |
|
|
Unable to create load bal- | Cause: SANsurfer FC HBA Manager detected an invalid configuration. |
ance configuration. | Solution: To enable load balancing, each storage subsystem must |
| |
| report multiple LUNs. When using a JBOD, you must individually con- |
| figure and manually balance each device. |
|
|
Unable to mask LUNs. | 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). |
|
|
Unable to set device path as | Cause: The SANsurfer FC HBA Manager user interface or qlremote |
visible, hidden, or unconfig- | agent did not detect any devices. |
ured. | Solution: Verify that the SANsurfer FC HBA Manager user interface |
| |
| shows the devices under their adapters in the FC/CNA HBA tree. Each |
| device should show its device port name and its connected LUNs. |
|
|
Unable to set LUN path as | Cause: The LUN path is not configured or the devices were not |
preferred or alternate. | 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 adapters in the FC/CNA HBA tree. Each |
| device should show its device port name and its connected LUNs. |
|
|
Unable to get host Informa- | Cause: The qlremote agent is not running or installed. |
tion. | Solution: Verify that the qlremote agent is installed and running (see |
| |
| “Verifying that qlremote is Installed and Running” on page |
|
|
