We are working on a new FC multipath storage and encounter the ESXi 6.5 FC multipath issue.
Description:
When connecting the storage to ESXi 6.5, "Failing registration of device 'naa.60xxxx'" errors are reported and the Lun is not available. The issue occurs only to ESXi 6.5, the identical storage and multipath configuration are working fine with ESXi 6.0 and 5.5.
(ESXi 6.5 vmkernel.log("failed_register_device_vmkernel.log)") is attached.)
Steps to reproduce:
The storage supports ALUA, the multipath TPG state is:
Multipath:
Lun 0: (Primary)
ALUA supported
Implicit TPGS
Path: Optimized/Active
Prefer bit: True
Lun 254: (Passive)
ALUA supported
Implicit TPGS
Path: Standby/Active
Prefer bit: False
1. Rescan storage controller HBA.
2. "Paths" view does display multiple path information, but "Devices" view is empty.
3. "Failing registration of device 'naa.60xxxx...'" errors are dumped in vmkernel.log.
4. If remove the "Lun 254" path, edit the Lun to a different Lun number(e.g. 253), rescan storage HBA again, both "Paths" and "Devices" view now can display correct information and the multipath Lun is working correctly.
Details:
Detailed information includes the SCSI command response of INQUIRY VPD 0x80, 0x83 and MAINTENANCE_IN is attached("details.log")
Questions:
1. As the identical storage and multipath configuration can work fine with ESXi 6.0 and 5.5, what is the related changes in ESXi 6.5 regarding FC multipath and ALUA support?
2. Is the asymmetric Lun number of multipath the major cause of the issue? According to vSphere document, Understanding Storage Device Naming, device Path-based identifier is determined by Inquiry VPD 0x83 if available. It's assumed Lun number is not included in the device identifier.
Thank you.