New vVOL datastores using NVMe over TCP (NVMeoTCP) connectivity becomes inaccessible immediately after creation
search cancel

New vVOL datastores using NVMe over TCP (NVMeoTCP) connectivity becomes inaccessible immediately after creation

book

Article ID: 388238

calendar_today

Updated On:

Products

VMware vSphere ESXi 7.0 VMware vSphere ESXi 8.0

Issue/Introduction

Symptoms:

  • When using the "New Datastore" dialog in the vSphere Client to add a new vVOL datastore, the datastore becomes inaccessible.
  • The Create Virtual Volume Datastore tasks complete successfully on the hosts:



  • The new vVOL datastore is visible in the Datastores/Cluster Tab in the vSphere Client, but is inaccessible:



  • You are able to ping the SAN IP address from the hosts successfully
  • Messages similar to these are found in the vvold.log on the ESXi hosts at the time the new datastore is being created: 

2025-02-05T18:50:23.602Z In(166) VVold[2111861]: [Originator@6876 sub=Default OpId=Session] StorageArray::CheckVASANvmeSupport: ArrayId:com.storagevendor:12345678-abcd-ef00-fecd-1a2b3c4d5e6f does not supports NVMe.

Environment

VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

  • Network misconfiguration.
  • Support for NVMe namespaces is not configured or incorrectly configured on the SAN.

Resolution

  • Rescan the Storage on the cluster level (from Inventory view in vSphere Client:  (Right-click Cluster -> Storage -> Rescan Storage)
  • Verify the network driver/firmware versions (see link below) with the Broadcom Compatibility Guide 
  • Validate basic network and port connectivity between hosts and SAN (see link below)
  • In additional to basic network connectivity checks, also verify the following:
    • If jumbo frames are configured on the storage network, verify MTU size consistency:

vmkping -d -s 8972 -I <vmkernel_port> <SAN_IP>   (for MTU 9000)

    • Validate TCP connectivity to the VASA port on the SAN:

nc -z <SAN_IP> <vasa_port> 

NOTE: VASA is typically 8443, but can vary by vendor. Check vendor documentation for correct port.

  • Consult SAN documentation for correct steps to enable NVMe namespace support on SAN.

Additional Information

Powered by Wolken Software