User`s guide

2 – System Overview
Troubleshooting
2-12 FS0054601-00 E
Q
2.5
Troubleshooting
This section lists troubleshooting tools to help identify the source of a problem in
hardware or software. This section also contains a list of known issues related to
certain configurations.
2.5.1
Troubleshooting Tools
The following sections explain how to use the Windows event log and SANblade
Manager to solve hardware problems.
2.5.1.1
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. SANblade Manager agents also use the application event log to
report service errors, etc. For more information, see section 8.1.
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.
In addition, the miniport driver can be configured to perform extended event logging
for an adapter, which causes it to log all loop transitions and many minor events.
Extended event logging uses extra overhead and is enabled only in troubleshooting
situations. The extended event logging flag is stored in the adapter NVRAM and
can be modified using Fast!UTIL or SANblade Manager.
The QLdirect driver logs events for significant driver errors, and for failover and
failback of a device. QLdirect logs full text messages for each event. These event
messages can be parsed and displayed on any system where QLdirect is installed.
These messages usually are self-explanatory.
QLdirect can also be configured for extended event logging, which causes it to log
every retry and many minor events. Extended event logging uses extra overhead
and is enabled only in troubleshooting situations. The extended event logging flag
for QLdirect is different from the extended event logging flag for the miniport driver;
either or both can be enabled. QLdirect extended event logging is enabled by setting
the following registry parameter to 1 and rebooting:
HKLM\System\CurrentControlSet\Services\qldirect\flags