An Administrator observes that there are storage paths to a single HBA but not the other HBA. Rebooting the ESXi host does not make paths visible to that HBA.
ESXi (All versions)
Storage array
Upon boot/reboot of the ESXi host, the HBA driver is able to successfully perform a login to the array targets:
/var/log/boot:2025-06-09T18:32:59.437Z cpu44:2098172)ql_fcoe:vmhba3:GPN_FTCallback:2812:Info: 0x43159a96be90 0: 20:01:1a:20:03:10:##:## 0a0b04 0 <--- HBA itself2025-06-09T18:32:59.437Z cpu44:2098172)ql_fcoe:vmhba3:GPN_FTCallback:2812:Info: 0x43159a96be90 1: 50:00:09:73:b0:10:##:## 0a2900 0 <--- Array target2025-06-09T18:32:59.437Z cpu44:2098172)ql_fcoe:vmhba3:GPN_FTCallback:2812:Info: 0x43159a96be90 2: 50:00:09:73:b0:10:##:## 0a3840 80 <--- Array target
However, the HBA itself is reporting that no LUNs are being presented to it from the array side for both targets:/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a
Target Information:
TGT ID[0]:
No. of LUNS:0
WWNN=0x50000973b010####:a2900WWPN=0x50000973b010####:a2900Internal State: OFFLOADEDTransport State: OFFLOADEDactive i/o: 0, free sqes: 1024(0)Flush in progress: 0
TGT ID[1]:
No. of LUNS:0
WWNN=0x50000973b010####:a3840WWPN=0x50000973b010####:a3840Internal State: OFFLOADEDTransport State: OFFLOADEDactive i/o: 0, free sqes: 1024(0)Flush in progress: 0
In this instance, the HBA is successfully logged into the target but the array target itself is not presenting any LUNs to this initiator. Contact the array vendor to validate that the WWPN for the HBA has LUNs presented to it.