koopa79 wrote:
Have you tried logging a call with vmware as well?
Yes, VMware says everything OK from their side.
ESX keeps trying to connect through the paths of the primary storage, but receives "Target Busy" states, eventually they come back as ok in the end.
According to VMW engineer "busy state" (see SCSI sense codes 2nd post from "Wed Jul 19, 2017 11:18" further up this thread) can be caused not only by the target (storage) itself, but because of the HBA too.
Currently it looks as if it works
fine with
qLogic HBAs but
fails with
Emulex HBAs.
FW & drivers are in accordance with the VMware and HPE certified versions.
Thanks for efforts so far though.