Skip to main content
NetApp Knowledge Base

What does the Solidfire VASA Provider do?

Last Updated:

Applies to

  • Solidfire Element OS 
  • VASA Provider (VP)


  • The VASA Provider  runs on all SF cluster nodes and logs to /var/log/ The VP is responsible for translating VASA requests into zero or more SF API calls to perform various actions like creating and deleting virtual volumes. Only the VP on the CM node actively processes VASA requests from vSphere.
  • VASA requests are sent by ESX hosts and vCenter servers to the VP on the CM using SOAP protocol. The VASA requests and responses are logged to An ESX host or vCenter server must create a VASA session with the VP before making VVol-related requests. VASA sessions are created using the setContext VASA request.

Additional Information

The Service: sfvasa Provider provides monitoring and management of vVols from VMware, vVols will continue to work even without it.  If the sfvasa provider is not working you will not be able to manage (add, delete or modify) vVols from v-Center.  


NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device