Emulex Adapters - Manual (Page 9)

Troubleshooting and Maintenance Manual Page 6
Web site and in Emulex documentation) the version of Microsoft's STORPORT.SYS that
is required for a particular version of Emulex's Storport Miniport driver, ELXSTOR.SYS.
• Path management software
• Unsupported configuration. An unsupported configuration or incorrect SAN zoning and/
or configuration can result in unexpected behavior.
• Unsupported adapter driver. An unsupported driver can result in software that does not
operate properly. Tight integration between software and drivers is critical. The correct
version of the driver must be used for proper operation.
• Unsupported adapter driver configuration. Unsupported driver settings can result in
failovers that take too long or can be triggered unnecessarily (these problems can be
caused by incorrectly configured timers in the adapter driver). Correct settings in the
adapter driver specified by the path management software provider must be used.
Checklists
Connectivity Checklist
After setting up a new SAN or reconfiguring an existing SAN, connectivity problems occasionally occur.
Storage volumes (devices) may not appear in the OS, although the storage management tool is ready
for use. The devices could be marked offline or not present at all. Below is a checklist that can be used
to help solve connectivity problems.
• Check for a good FC link. Verify that there is a good link at the desired speed. Most Emulex
adapters have LED lights that provide the link status and current speed of each port. The LED
states for each adapter are documented in each adapter's user manual. If the LEDs are not
visible, use the OneCommand Manager or HBAnyware application to show link status, or use
the remote port's utility to examine the link state. For example, if the Emulex adapter is
connected to a switch port, use the switch's utility tools to see the link state.
• Check switch zoning. Large switched fabrics are complicated to set up and maintain. Zoning is
a key element of a good configuration, and it is one of the most complicated to manage. An
improperly zoned fabric can cause a variety of problems that are not always directly attributable
to zoning. For example, a small disturbance on a large fabric with no zoning can cause
connectivity problems because all the devices on the fabric will be trying to resolve the
disturbance at the same time which overloads the switch. It is important to verify that the device
that is not being discovered is properly zoned.
• Verify device discovery. Use the OneCommand Manager or HBAnyware application to
examine devices discovered by the adapter and driver. In nearly all OSs, the device driver for
the FC adapter is responsible for discovering all the devices in a SAN. These devices must then
be assigned SCSI target IDs and mapped to the OS. The OneCommand Manager or
HBAnyware application provides the unique ability to see all the devices on the SAN that the
device driver discovered, regardless of whether the devices where mapped to the OS. This
provides a way to determine whether the device that is having problems is visible on the SAN.
• Check that the Automap driver parameter is on or there are valid persistent binding
entries. In order for the OS to communicate with all of the expected devices, its storage
management tool must be mapped to SCSI target IDs. As previously mentioned, the device
driver performs the mapping function that assigns a remote FC device to a SCSI target ID so the
OS can communicate with the device. Few OSs know how to directly communicate with an FC
device. They must use the SCSI target ID to communicate across the SAN. Emulex device
drivers have several options on how this mapping is performed:
• Automapping - Emulex device drivers can be configured to automatically map the FC
devices to SCSI target IDs.