NVMe over TCP storage targets not detected on ESXi host - VMware vSphere ESXi
search cancel

NVMe over TCP storage targets not detected on ESXi host - VMware vSphere ESXi

book

Article ID: 449699

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

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.

  • Running esxcli storage core adapter list shows the NVMe adapter as online, but no devices or paths are visible.

  • Storage targets are detected on other hosts in the cluster but not the impacted host.



  • The VMkernel adapter (vmk) used for NVMe traffic has no physical uplinks listed in the configuration.

Environment

VMware vSphere ESXi

Cause

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.

Resolution

Review the VMkernel and physical uplink configuration to ensure the network path is active.

  1. Log in to the vSphere Client. Select the impacted ESXi host and navigate to Configure > Networking > VMkernel adapters.

  2. Identify the VMkernel adapter (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.

    Note: Navigate to Networking > Virtual Switches. If the physical adapter (vmnic) is assigned to another switch/port group and it is unused, remove it from the switch/port group.

  3. Edit the port group settings associated with the NVMe VMkernel adapter.

  4. In the Teaming and failover section, move the physical 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 .

  5. Confirm that the VMkernel adapter now shows the physical link as active.

  6. Perform a storage rescan by navigating to Storage Adapters > Rescan Storage. Verify that the device paths are now populated under the NVMe over TCP adapter

Additional Information

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 .