Skip to main content
NetApp Knowledge Base

Adding a VM disk fails on NetApp SolidFire storage in vCenter

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
solidfire
Last Updated:

Applies to

  • NetApp Element software 12.8 & 12.9
  • NetApp SolidFire VASA provider for VMware vSphere

Issue

  • Adding a new virtual disk to a VM that uses NetApp SolidFire-backed storage (vVol or VMFS datastore on SolidFire) fails in VMware vCenter during storage policy validation.
  • vmware-sps.log shows an error similar to:

PBM error occurred during PreReconfigureCallback: pbm.fault.PBMFaultNo VASA Provider for schema namespace (com.solidfire.vasa.capabilities) found

  • NetApp SolidFire VASA provider log on the vCenter appliance may show the underlying Element API error:

com.solidfire.core.client.ApiServerException: Slice IOPS for slice ID <N> does not exist mapped to vasa.vim.vmware.com._2.StorageFault

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.