Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 17 results
    • VASA vVol expansion fails
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/VASA_vVol_expansion_fails
      Applies to vSphere APIs for Storage Awareness (VASA) 9.6 vSphere APIs for Storage Awareness (VASA) 9.7 VMware Virtual Volumes (vVols) Issue VASA vVol expansion fails with misleading error: Failed to r...Applies to vSphere APIs for Storage Awareness (VASA) 9.6 vSphere APIs for Storage Awareness (VASA) 9.7 VMware Virtual Volumes (vVols) Issue VASA vVol expansion fails with misleading error: Failed to retrieve storage details for a given vVols datastore with moref: datastore-n
    • vVOLs show 0B in size
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/vVOLs_show_0B_in_size
      Applies to vSphere APIs for Storage Awareness (VASA) 9.7, 9.7P1 Virtual volumes (vVOL) Issue VASA Provider workflows might fail with error: VP: Out of memory Exception :unable to create native thread:...Applies to vSphere APIs for Storage Awareness (VASA) 9.7, 9.7P1 Virtual volumes (vVOL) Issue VASA Provider workflows might fail with error: VP: Out of memory Exception :unable to create native thread: possibly out of memory or process/resource limits This causes vVOLs to show 0B in size from host size and be inaccessible
    • Storage added at SVM level shows as 'Unknown' model
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/Storage_added_at_SVM_level_shows_as_Unknown_model
      Applies to NetApp VASA Provider NetApp ONTAP tools for VMware vSphere(OTV) NetApp ONTAP Storage Virtual Machine(SVM) Issue Adding storage to OTV at SVM level shows as 'Unknown' and is not compatible w...Applies to NetApp VASA Provider NetApp ONTAP tools for VMware vSphere(OTV) NetApp ONTAP Storage Virtual Machine(SVM) Issue Adding storage to OTV at SVM level shows as 'Unknown' and is not compatible with VASA Storage Capability Profiles
    • How to view OTV/VSC operations in-flight
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/How_to_view_OTV_VSC_operations_in_flight
      Applies to Virtual Storage Console (VSC) ONTAP Tools for VMware (OTV) Description VSC has the ability to show in flight operations in real time: VMware API calls ONTAP ZAPI calls Background Discovery ...Applies to Virtual Storage Console (VSC) ONTAP Tools for VMware (OTV) Description VSC has the ability to show in flight operations in real time: VMware API calls ONTAP ZAPI calls Background Discovery Rediscovery Manager Background Threads
    • Unable to delete Datastore with VSC
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/Unable_to_delete_Datastore_with_VSC
      Applies to When trying to delete a datastore with VSC, the below error appears: Could not access HTTP invoker remote service at [https://localhost:8143/kamino/remoting/kaminoRmiExporter?sessionId= <ss...Applies to When trying to delete a datastore with VSC, the below error appears: Could not access HTTP invoker remote service at [https://localhost:8143/kamino/remoting/kaminoRmiExporter?sessionId= <ssession-id>&serviceUrl=https://<vcenter-ip>:443/sdk]; nested exception is java.io.WriteAbortedException: WARN [RemoteInvocationTraceInterceptor] - Processing of HttpInvokerServiceExporter remote call resulted in VASA Provider credential object contains invalid credentials.
    • VASA Provider raises alert "SAN PE is not operational"
      https://kb.netapp.com/data-mgmt/OTV/OTV_Issues/VASA_Provider_raises_alert_SAN_PE_is_not_operational
      Applies to VASA (vSphere APIs for Storage Awareness) vVols (Virtual Volumes) Issue VASA raises the following alert for protocol endpoints (PE's) that are missing on the host: Storage provider [NetApp-...Applies to VASA (vSphere APIs for Storage Awareness) vVols (Virtual Volumes) Issue VASA raises the following alert for protocol endpoints (PE's) that are missing on the host: Storage provider [NetApp-VP] raised an alert type 'Object' on vvol:<vvol-uuid>: SAN PE is not operational: PE with naa id naa.<naa-id> on ESXi host <host-fqdn> has a non "ok" operational state: inaccessible. Screenshot of error:
    • VASA raised an alert FileSystem Capacity crossed full threshold
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/VASA_raised_an_alert_FileSystem_Capacity_crossed_full_threshold
      Applies to vSphere APIs for Storage Awareness (VASA) Virtual volumes (vVOL) Issue VASA Provider reports error: Storage provider [Netapp-VP] raised an alert type 'Object' on vvol:uuid: FileSystem Capac...Applies to vSphere APIs for Storage Awareness (VASA) Virtual volumes (vVOL) Issue VASA Provider reports error: Storage provider [Netapp-VP] raised an alert type 'Object' on vvol:uuid: FileSystem Capacity crossed full threshold for volumes and/or aggregate on volumes: [vol-name]
    • VASA appliance CPU consumption increases when ESXi host is down
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/VASA_appliance_CPU_consumption_increases_when_ESXi_host_is_down
      Applies to vSphere APIs for Storage Awareness (VASA) ONTAP Tools for VMware vSphere (OTV) Virtual Volumes (vVOL) Issue VASA appliance CPU usage increases when ESXi host is down or unresponsive. This i...Applies to vSphere APIs for Storage Awareness (VASA) ONTAP Tools for VMware vSphere (OTV) Virtual Volumes (vVOL) Issue VASA appliance CPU usage increases when ESXi host is down or unresponsive. This is resulting in vVOL access loss for connected hosts. Issue can be confirmed in VASA rightnow page (https://<VASA-IP>/rightnow). API calls such as these will be seen stuck for a long time:
    • What are the settings included in each default Storage Capability Profile?
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/What_are_the_settings_included_in_each_default_Storage_Capability_Profile
      ONTAP tools for VMware vSphere NetApp VASA Provider Storage Capability Profiles There are 11 predefined Storage Capability Profiles in ONTAP tools for VMware: Space reserve:Thick Tiering policy (Fabri...ONTAP tools for VMware vSphere NetApp VASA Provider Storage Capability Profiles There are 11 predefined Storage Capability Profiles in ONTAP tools for VMware: Space reserve:Thick Tiering policy (FabricPool):Snapshot Platform:All Flash FAS (AFF) Min IOPS:50 IOPS Max IOPS:Unlimited Compression:Yes Performance:None Description:Predefined profile Platform:Fabric Attached Storage (FAS) Protocol:Any Max IOPS:20 IOPS Deduplication:Yes Space reserve:Thin Encryption:No Tiering policy (FabricPool):None
    • VVOL provisioning with VSC: Error on SCP selection
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/VVOL_provisioning_with_VSC__Error_on_SCP_selection
      Applies to VASA Provider 7.x, 9.6, 9.7 Issue When provisioning a new VVOL datastore, the following "There are no matching storage systems found for the selected SCP" warning is seen:
    • vVOL VMDK deletion fails with error "volume of naa.xyz was still bound to X handles and cannot be deleted."
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/vVOL_VMDK_deletion_fails_with_error_volume_of_naa_xyz_was_still_bound_to_X_handles_and_cannot_be_deleted
      Applies to vSphere APIs for Storage Awareness (VASA) Virtual Volumes (vVOL) Issue When in use vVOL VMDK's are bound to a host. Under certain circumstances it is possible that the host never releases t...Applies to vSphere APIs for Storage Awareness (VASA) Virtual Volumes (vVOL) Issue When in use vVOL VMDK's are bound to a host. Under certain circumstances it is possible that the host never releases the active binds, for example, if the host fails due to a hardware error. In this case a deletion of the vVOL VMDK will fail with error: FINAL FAILURE deleteVirtualVolume, error (RESOURCE_BUSY / Caused by: volume of naa.xyz was still bound to X handles and cannot be deleted.