HP StoreEver High Availability Path Failover Windows Driver Release Notes Version 1.0.6.3 (5697-3325, June 2014)

Languages
• International English
Features
This section identifies features for first release of advanced path failover drivers.
• Drivers to be used with HP LTO-6 FC drives and the ESL G3 and MSL6480 tape libraries in which
they are installed.
• Drivers create entries in the Windows system log when they are first started and whenever any
exceptional conditions occur.
• Diagnostic application that is installed with the drivers.
Maintains the state of failover sessions by communicating with the drivers, tape drives, and
libraries.
◦
◦ Displays worldwide port and node names (WWN).
◦ Clears reservations on libraries that had been set up hosts that are now offline.
See the user guide for information about using the diagnostic application.
• Debug (checked) drivers can be installed, which when Windows is configured appropriately, will
save a crash dump in the event of a system crash. Released and debug drivers cannot coexist on
the same host. Installed driver should be uninstalled prior to installing another driver. See the user
guide for additional information.
Fixes
N/A
Issues and workarounds
This section identifies important issues and workarounds for Advanced Path Failover.
Current implementation is failure tolerant only and not intended to fix unstable
SAN environments.
Symptom: Device connectivity lost after several closely spaced path failures. If several closely spaced
path failures occur on all of the available paths the operating system might not detect a path change
and report that to the driver causing a loss of connectivity with the device.
Workaround: Locate and repair the SAN faults. The driver is not always able to recover if both the
active path and the standby path have faults.
Current implementation uses the first path to a device that was successfully found.
Symptom: The device driver does not connect to the preferred path after a system boot or device
rescan.
Workaround: The driver prefers the first path in the hardware scan performed by the operating system.
If a particular path is preferred, load the HBA for that path in the lower numbered hardware location.
Windows driver does not perform speed or performance comparisons of all
available paths to a device in order to select the best one as a primary.
Symptom: The device driver does not connect to the highest performance path after a system boot or
device rescan.
Workaround: The driver prefers the first path in the hardware scan performed by the operating system.
If a particular path is preferred, load the HBA for that path in the lower numbered hardware location.
4 Languages