Device connectivity is lost after several closely spaced
path failovers
Symptom
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.
Cause
The current implementation is failure tolerant only and not intended to fix unstable SAN environments.
Action
Locate and repair the SAN faults. When both the active path and the standby path have faults, the driver
is not always able to recover.
The device driver does not connect to the preferred path
Symptom
The device driver does not connect to the preferred path after a system boot or device rescan.
Cause
The current implementation of the Windows driver uses the first path to a device that was successfully
found.
Action
If a particular path is preferred, load the HBA for that path in the lower numbered hardware location.
The device driver does not connect to the highest
performance path
Symptom
The device driver does not connect to the highest performance path after a system boot or device rescan.
Cause
By default, the driver prefers the first path in the hardware scan performed by the operating system. The
driver does not perform speed or performance comparisons of all available paths to a device to select the
best one as a primary.
Device connectivity is lost after several closely spaced path failovers
85
