Troubleshooting and Maintenance Manual
Page 9
•
Verify that driver settings are set correctly.
Defaults are optimized for normal operation, and
Emulex recommends default settings in most cases. By default, all Emulex drivers perform
automatic mapping of FC nodes to target IDs (SCSI IDs). If SAN changes occur, the target
mapping may not stay consistent for each FC node between reboots of the OS. Use persistent
binding or target mapping to insure target IDs do not change between server reboots.
•
Configure the driver using instructions in the driver and application manuals
. Manual links
are available on the same page as the driver download. The driver manuals have parameter lists
with minimum and maximum values for each setting. If a parameter can be changed with tools
other than the OneCommand Manager or HBAnyware application, parameter information is in
the driver manual. Review this parameter list before you perform changes to ensure that values
are not out of range or invalid. If changes require a reboot, schedule downtime for performing
the changes.
Tools to Collect Data
Emulex provides tools to collect data about a problem or behavior with Emulex products. Sometimes,
more importantly, these tools provide information about general SAN operation, even if the problem
appears to be outside of Emulex's domain.
Driver Tools - Event Logging
All Emulex OS device drivers can log additional events beyond critical errors. This can be useful in
troubleshooting. By default, Emulex drivers log only severe errors, but can be configured to log more
events. Examples of events: FC timer expiration, RSCN reception, SCSI errors (such as Check
Condition errors, Busy or Queue Full), and FC errors (to detect bad cables or transceivers). Emulex
considers this type of event logging a powerful troubleshooting tool.
Instructions for enabling the various levels of event logging in each of the Emulex drivers can be found in
the documentation for those drivers on the Emulex Web site. Emulex driver event logging can be
enabled dynamically (which means without a system reboot). The documentation for each of the drivers
includes information on how to interpret and/or decode the event log information.
The OneCommand Manager and HBAnyware Applications
•
OneCommand Manager and HBAnyware applications GUI
. The OneCommand Manager and
HBAnyware applications can show all targets and LUNs an adapter port has detected on the
SAN. Problems such as fabric zoning and array configuration can be detected. Detect persistent
binding problems: if the target shows in the OneCommand Manager and HBAnyware application
and is not seen in the OS storage management tool, the persistent binding entries should be
checked.
Note:
For SAN disk drives (storage arrays) on Windows, persistent binding is not
necessary. Windows uses the drive signature on each drive to determine the correct
drive letter. Persistent binding is necessary for SAN tape devices on Windows.
Caution:
Do not make configuration changes to a production server unless downtime
has been scheduled. These changes can cause issues with access to the
SAN storage, thereby causing unexpected server downtime.
Note: Drivers for Linux only:
Emulex's provides a "grab" tool to collect pertinent adapter,
driver and system information for processing by Emulex and stores it in a tarball file.
This tarball file is available for download from the Support section of the Emulex Web
site.
