User`s guide

12 – Troubleshooting
Troubleshooting Problems and Solutions
FS0054601-00 E 12-7
Q
SANblade Manager
GUI crashes
Cause: SANblade Manager GUI lost communication with the
qlremote agent, another application caused a conflict with
SANblade Manager, or an operating system driver lost
communication with the adapter or device.
Solution:
Verify that the qlremote agent is installed and running:
For Windows NT/2000, 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 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
Verify that no other application is causing SANblade Manager
to crash.
Verify that the operating system driver detects the adapter or
device.
Host keeps
disconnecting from and
connecting to the HBA
tree
Cause: Fibre Channel protocol activity caused the qlremote
agent to rescan the configuration.
Solution: If SANblade Manager is managing several hosts and
a remote host reboots or there is activity in the SAN, the qlremote
agent and SANblade Manager refresh the configuration to make
certain that no adapter or device was disconnected.
Functional
Unable to create
failover configuration
Cause: An incorrect version of SANblade Manager is installed
or SANblade 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.
Table 12-1. Troubleshooting Problems and Solutions (Continued)
Problem Cause and Solution