The Virtual Volumes functionality supports Fibre Channel, FCoE, iSCSI, and NFS. Storage transports expose protocol endpoints to ESXi hosts.

When the SCSI-based protocol is used, the protocol endpoint represents a LUN defined by a T10-based LUN WWN. For the NFS protocol, the protocol endpoint is a mount point, such as IP address or DNS name and a share name.

No matter what storage protocol is used, a virtual volume, like a files on other traditional datastores, is presented to a virtual machine as a SCSI disk. Virtual Volumes on disk arrays supports the same set of SCSI commands as VMFS and uses ATS as a locking mechanism.

Virtual Volumes on NAS devices supports the same NFS Remote Procedure Calls (RPCs) that are required by ESXi hosts to connect to NFS mount points.

These considerations and guidelines apply when you use different storage protocols:

With NFS, you can use version 3. Virtual Volumes does not support NFS 4.1.

IPv6 format is not supported.

For iSCSI, you must activate the software iSCSI adapter. Configure Dynamic Discovery and enter the IP address of the Virtual Volumes Storage Provider. See Configure the Software iSCSI Adapter.

You can configure multipathing on a SCSI-based protocol endpoint, but not on an NFS-based protocol endpoint. No matter which protocol you use, a storage array can provide multiple protocol endpoints for availability purposes.