A
Troubleshooting Troubleshooting Problems and Solutions
Solaris Messages File
For Solaris SPARC/x86 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, and so on. For more information, see the SANsurfer FC HBA Manager Application Help.
The Solaris agent logs events for significant driver errors. In addition, you can configure the Solaris agent to perform extended event logging for an adapter, which causes it to log all loop transitions and many minor events. Extended Application Event Logging uses extra overhead and is enabled only in troubleshooting situations. The extended event logging flag is stored in the adapter parameters, which you can modify using Fast!UTIL (Solaris SPARC), FCode (Solaris x86), or the SANsurfer FC HBA Manager.
The path for the Solaris messages file is /var/adm/messages.
SANsurfer FC HBA Manager
SANsurfer FC HBA Manager lists target devices on an adapter, loop topology information, loop error count information, and so on. SANsurfer FC HBA Manager shows target devices on an adapter and is useful for analyzing system configurations. SANsurfer FC HBA Manager uses a feature of the enhanced miniport driver to find and display information about devices that are not configured on the local host. This feature can display information about all potential target devices on a fabric or all devices on a loop topology, not just those that are configured on the local host.
Troubleshooting Problems and Solutions
This section provides troubleshooting problems and solutions. Refer to the associated readme.txt file for the latest problems and solutions (see “Related Documents” on page
“Installation Issues” on page
“User Interface and Remote Agent Issues” on page
“Functional Issues” on page
