IS0054602-00 B
7-1
7
Troubleshooting
Problems can occur when installing and using SANsurfer iSCSI HBA Manager.
This section provides information that will help you troubleshoot these problems,
including the following:
“Troubleshooting Tools” on page 7-1
“Troubleshooting Problems and Solutions” on page 7-2
“Verifying That the HBA Driver is Installed” on page 7-12
“Verifying That iqlremote is Installed and Running” on page 7-13
“Using Debug to Trace User Interface and Agent Activity” on page 7-14
(as
directed by your authorized service provider)
“Retrieving Records” on page 7-22
Troubleshooting Tools
The following sections explain how to use the Windows event log and SANsurfer
iSCSI HBA Manager to solve hardware problems.
Windows Event Log
The Windows event log is the main source of information for device driver
problems and events. Device drivers usually indicate only status by logging
events in the system event log. SANsurfer iSCSI HBA Manager agents also use
the event log to report service errors and other problems.
The miniport driver logs events for significant driver errors. Due to a limitation of
the Windows miniport driver interface, the miniport can log only two 32-bit values
for any event. Information about interpreting these event codes is in the
eventlog.txt
file, which is shipped with the miniport driver.
NOTE:
The iqlremote agent refers to the SANsurfer iSCSI HBA Manager server
agent (SANsurfer iSCSI Windows Agent, SANsurfer iSCSI Linux Agent,
SANsurfer iSCSI Solaris Agent, or SANsurfer iSCSI NetWare 5/6.
x
Agent
with which the SANsurfer iSCSI HBA Manager user interface (client)
connects to manage QLogic QLA2
xxx
iSCSI HBAs.