NVMe over TCP storage targets are not detected or listed under specific storage adapters (e.g., vmhba64 or vmhba65) on an ESXi host, even though the adapter status shows as online. This issue typically occurs when the logical VMkernel interface lacks a properly associated and active physical uplink.
esxcli storage core adapter list shows the NVMe adapter as online, but no devices or paths are visible.vmk) used for NVMe traffic has no physical uplinks listed in the configuration.VMware vSphere ESXi
The physical network adapter (vmnic) intended for the software NVMe adapter is incorrectly assigned to a Distributed Switch (DVS) or is set to an 'unused' state in the port group, preventing the VMkernel interface from establishing a physical link to the storage network.
Review the VMkernel and physical uplink configuration to ensure the network path is active.
e.g., vmk1) assigned to the NVMe over TCP service and verify if it has an associated physical uplink. If there is no uplink, proceed to next step.vmnic) is assigned to another switch/port group and it is unused, remove it from the switch/port group.vmnic from Unused adapters to Active adapters. For instructions, refer - Teaming and Failover policy on Standard Switch and Teaming and Failover policy on Distributed Switch .For further troubleshooting of NVMe over TCP connectivity, see Unable to configure NVMe over TCP storage for New Site .
To configure NVMe over TCP on ESXi .