User`s guide

2 – System Overview
Troubleshooting
2-6 FS0054603-00 C
Q
2.4.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. SANsurfer FC HBA 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 HBA, 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 HBA NVRAM and can
be modified using Fast!UTIL or SANsurfer FC HBA Manager.
2.4.1.2
Linux Messages File
For Red Hat/SuSE Linux systems, the Linux messages file is the main source of
information for device driver problems and events. Device drivers usually indicate
only status by logging events in the Linux messages file. SANsurfer FC HBA
Manager agents also use the Linux messages file to report service errors, etc. For
more information, see section 8.1.
The Linux agent logs events for significant driver errors. In addition, the Linux agent
can be configured to perform extended event logging for an HBA, 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 HBA NVRAM and can be modified using Fast!UTIL or
SANsurfer FC HBA Manager.
The path for the linux messages file is /var/log/messages.
2.4.1.3
Solaris Messages File
For Solaris SPARC systems, the Solaris messages file is the main source of
information for device driver problems and events. Device drivers usually indicate
only status by logging events in the Solaris messages file. SANsurfer FC HBA
Manager agents also use the Solaris messages file to report service errors, etc. For
more information, see section 8.1.
The Solaris agent logs events for significant driver errors. In addition, the Solaris
agent can be configured to perform extended event logging for an HBA, 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