Troubleshooting and Maintenance Manual
Page 7
•
Persistent Binding - Emulex device drivers can be configured to map certain FC devices
to corresponding SCSI target IDs to maintain a known configuration of SCSI target
devices. This manual mapping process is done using the OneCommand Manager or
HBAnyware application, and it typically links an FC world wide name value to a SCSI
target ID value. This is called persistent binding.
The device driver must have correct persistent binding information, or the Automap configura-
tion parameter must be enabled to allot the device driver to map the devices.
•
Check storage configuration.
When storage devices are presented in the OS storage
management tool, they are typically described as volumes or disks. The adapter device driver
maps discovered storage ports on a SAN as SCSI targets and the LUNs are discovered and
managed by the OS, not the adapter driver. If LUNs are configured on a particular storage
controller port and the port is not discovered by the adapter, all the LUNs associated with that
port will not be available for use.
Many storage systems provide security by requiring that each storage controller port be
configured with the host server world wide names that will communicate with that storage port.
The storage controller will not allow a server with unknown World Wide Names to communicate
with LUNs on the storage system. Further, some storage systems allow LUNs to be allocated to
particular servers based on world wide name. If the storage controller with this security and LUN
mapping feature is not properly configured, the controller will allow the server adapter port to
login and communicate with the storage controller, however, the storage controller will not
present any LUNs to the server. This means that the adapter driver will complete its discovery
and map the targets to the OS, but the OS will not find LUNs with which to communicate.
Installation Checklist
This checklist covers installation of drivers and applications. In addition to this checklist, verify with your
storage and system providers for any specific instruction they may provide. Some OEM vendors will
repackage drivers and utilities.
•
Verify recommended driver, firmware, and boot versions from your storage and system
providers.
Many storage and system providers qualify specific adapter models, driver, and
firmware releases. Using qualified storage and system provider solutions will ensure you have a
supported SAN configuration.
•
Verify releases for storage and system providers that have a page on the Emulex Web
site.
If the storage or system provider is not listed, contact them to verify their preferred driver
releases. If the storage and system provider does not have preference, Emulex recommends
the latest driver and firmware releases. Latest releases ensure the latest enhancements and
bug fixes. For latest driver and utilities, refer to the Emulex Web site.
•
Review the prerequisites section in the driver user manual.
This will ensure that you meet
the minimal requirements for each driver you are installing. The driver user manual may also
contain other information regarding tested SAN environments.
•
Follow the installation instructions in the Emulex driver and utilities manuals.
The manual
has step-by-step instructions that can be followed for easy installation of the driver. It is available
at the above URL and on the same page as the driver download. Utilities are packaged with the
driver kits or listed separately on the driver page. Use the same utilities bundled with the driver
kit. Running older applications with newer drivers can render some utility features inoperative.
