User`s guide

12 – Troubleshooting
Troubleshooting Problems and Solutions
FS0054603-00 C 12-5
Q
SANsurfer FC HBA
Manager GUI does not
find/display any
devices
Cause: The operating system driver did not find devices during
the initial load.
Solution: Verify that the operating system driver detects the
devices. If the operating driver does not detect devices, neither
does SANsurfer FC HBA Manager. Check agent logs for any
problems while querying information (see section 12.2.2).
SANsurfer FC HBA
Manager GUI reports
that the HBA device
driver is invalid or
incorrect
Cause: An incorrect or unsupported operating system driver is
installed.
Solution: Refer to the readme.txt file for a list of supported
operating system drivers.
Unable to find
SANsurfer FC HBA
Manager GUI online
help
Cause: The path to the browser is not correctly specified.
Solution: In the SANsurfer FC HBA Manager main window Help
menu, select Set Browser Location to specify the path (see
section 6.4.2). See section 4.2 for supported browsers.
SANsurfer FC HBA
Manager GUI does not
automatically refresh
Cause: There is a disconnect with the qlremote agent or network
communication has stopped.
Solution:
■ Verify that the qlremote agent is installed and running:
■ For Windows 2000/Windows Server 2003, open the
Services window and verify that the QLogic Management
Suite Java agent service is running.
■ For NetWare, at the server command prompt type the
following and then press ENTER. Verify that qlremote.nlm
is loaded.
modules q*
■ For Red Hat/SuSE Linux and Solaris SPARC, change to
the following directory:
cd/ usr/local/bin
Type the following command and then press ENTER.
Verify that the appropriate network protocol is running.
./qlremote -v
■ For network requirements, see sections 4 and 5.1.
Table 12-1. Troubleshooting Problems and Solutions (Continued)
Problem Cause and Solution