Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: Virtualization Integration > VASA provider
vSphere APIs for Storage Awareness (VASA) are VMware-defined and vendor-neutral APIs that enable vSphere to determine the capabilities of a storage system. The API requests basic storage information from PowerStore and uses it for monitoring and reporting storage details to the user in vSphere.
PowerStore includes a native VASA 3.0 and VASA 4.0 provider, which enables the vVols storage framework. The VASA provider must be registered in vSphere in order to use vVols. On PowerStore X models, the storage provider is registered in vSphere automatically as part of the initial configuration process.
On PowerStore T models, starting with PowerStoreOS 2.0, the storage provider can be optionally registered during the initial configuration process. After initial configuration is completed, this registration can be done as part of the vCenter server connection process in PowerStore Manager or manually registered in vSphere.
After a storage provider is successfully registered, additional details about the provider are displayed, as shown in the following figure:
Starting with PowerStoreOS 3.5, you can implement a third-party certificate for the PowerStore VASA provider. You can replace the system’s self-signed certificate with the third-party certificate, or you can retain the system’s self-signed certificate and also add a third-party certificate. Implementing a third-party certificate for the PowerStore VASA provider allows for support of multiple standalone vCenter instances to leverage a single PowerStore VASA provider.
Under VASA Certificate, you have the option to retain the current VASA certificate, whether it is a self-signed PowerStore certificate, a third-party signed certificate, or a vCenter certificate. If enabled, the retain option prevents the VASA server certificate on the PowerStore system from being overwritten by the vCenter server.
To implement a third-party certificate for VASA, follow these steps:
Note: Ensure that the vCenter server trusts the CA of the certificate being imported; otherwise, VASA functionality, including the management of a vVol VM, will be unavailable.