Learn how you can review and manage protocol endpoints that the ESXi host uses to access Virtual Volumes on storage arrays. How the protocol endpoints are represented in the vSphere Client depends on whether the host uses the SCSI and NFS protocols or the NVMe protocol to access Virtual Volumes.
Review and Manage Static Protocol Endpoints
With the SCSI or NFS protocols, the protocol endpoints represent a proxy LUN or an NFS mount point. These protocol points are called static. After you map a storage container to a Virtual Volumes datastore, these protocol endpoints become visible in the vSphere Client. The list of available static protocol endpoints looks similar to the host storage devices list. You can review properties of the protocol endpoints and modify specific settings.
Procedure
Change the Path Selection Policy for a SCSI Protocol Endpoint
If your ESXi host uses SCSI-based transport to communicate with protocol endpoints representing a storage array, you can modify default multipathing policies assigned to protocol endpoints. Use the Edit Multipathing Policies dialog box to change a path selection policy.
Procedure
Review NVMe Protocol Endpoints
Unlike the static protocol endpoint, the NVMe protocol endpoint is virtual. This protocol endpoint is a logical representation of the ANA group where the virtual volumes reside. Until a VM is powered on, the NVMe protocol point doesn’t exist. Once the VM is powered on, the NVMe protocol point is created, so that the host can access the virtual volumes in the ANA group. Use the vSphere Client to review NVMe virtual protocol endpoints.
For conceptual information that applies to Virtual Volumes with NVMe storage, see NVMe and Virtual Volumes in vSphere.