Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 18 results
    • VVOL Provisioning: Issues with NDMP node-scope-mode
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/VVOL_Provisioning__Issues_with_NDMP_node_scope_mode
      When provisioning a new VVOL datastore, the following "There are no matching storage systems found for the selected SCP" warning is seen: <vserverReasons>Did not match profile Storage system platform ...When provisioning a new VVOL datastore, the following "There are no matching storage systems found for the selected SCP" warning is seen: <vserverReasons>Did not match profile Storage system platform type does not match profile platform type..</vserverReasons> <failedReason>NDMP Daemon needs to be configured in vServer Aware Mode, Did not match profile Storage system platform type does not match profile platform type..</failedReason>
    • 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
    • ESXi host is not able to discover Element vVOLs via iSCSI - Target returned login error of: 0204
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/ESXi_host_is_not_able_to_discover_Element_vVOLs_via_iSCSI_Target_returned_login_error_of__0204
      The ESXi host is newly added to the vCenter server The ESXi host is not able to discover the iSCSI target for Element vVOLs <date>: [iscsiCorrelator] <id>: [esx.problem.storage.iscsi.target.login.erro...The ESXi host is newly added to the vCenter server The ESXi host is not able to discover the iSCSI target for Element vVOLs <date>: [iscsiCorrelator] <id>: [esx.problem.storage.iscsi.target.login.error] Login to iSCSI target <iqn> on vmhba68 @ vmk3 failed. <date> error vvold[2100193] [Originator@6876 sub=Default] Initialize: Unable to init session to VP SolidFire HCI state: 0
    • ONTAP Tools: The container could not be deleted - still contains 1 vVols out of which 1 are vSphere HA Datastore Heartbeat vVols
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/Unable_to_delete_vVol_datastore_error__still_contains_1_vVols_out_of_which_1_are_vSphere_HA_Datastore_Heartbeat_vVols
      Applies to VMware vSphere High Availability (HA) VMware vSphere APIs for Storage Awareness (VASA provider) Virtual volumes (vVol) ONTAP Tools for VMware vSphere (OTV) 9.13P1 Issue When attempting to d...Applies to VMware vSphere High Availability (HA) VMware vSphere APIs for Storage Awareness (VASA provider) Virtual volumes (vVol) ONTAP Tools for VMware vSphere (OTV) 9.13P1 Issue When attempting to delete a vVol datastore through ONTAP Tools (OTV) the following error is seen: The container could not be deleted- still contains 1 vVols out of which 1 are vSphere HA Datastore Heartbeat vVols. Disable vSphere HA and retry
    • VASA raises alert "PE on ESXi host has a non "ok" operational state: inaccessible"
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/VASA_raises_alert_PE_on_ESXi_host_operational_state__inaccessible
      Applies to VASA (vSphere APIs for Storage Awareness) vVOL (virtual volumes) PE (protocol endpoint) Issue VASA raises the following alert for PE's that are inaccessible for the host: Storage provider [...Applies to VASA (vSphere APIs for Storage Awareness) vVOL (virtual volumes) PE (protocol endpoint) Issue VASA raises the following alert for PE's that are inaccessible for the host: Storage provider [NetApp-VP] raised an alert type 'Object' on vvol:<vvol-uuid> PE with naa id <naa-id> on ESXi host <host-name> has a non "ok" operational state: inaccessible.
    • AutoSupport Message: VASA provider certificate expiration alarm
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/AutoSupport_Message__VASA_provider_certificate_expiration_alarm
      Applies to NetApp HCI VMware vCenter 6.x or 7.x VMware ESXi 6.x or 7.x vSphere 6.x or 7.x Issue Host VASA provider certificate expiration alarm reported in NetApp SolidFire Active IQ: Alert name: VASA...Applies to NetApp HCI VMware vCenter 6.x or 7.x VMware ESXi 6.x or 7.x vSphere 6.x or 7.x Issue Host VASA provider certificate expiration alarm reported in NetApp SolidFire Active IQ: Alert name: VASA provider certificate expiration alarm Description: Monitors whether VASA provider certificates are getting close to their expiry date
    • 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]
    • 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:
    • What is the procedure to rename flexvolumes that are backing vVol datastores
      https://kb.netapp.com/data-mgmt/OTV/VASA_Provider_Kbs/What_is_the_procedure_to_rename_flexvolumes_that_are_backing_vVol_datastores
      It is recommended to have a VMware snapshot of the powered off OTV / VSC appliance in place before starting this procedure As a general rule, however, it is not recommended to make changes to storage ...It is recommended to have a VMware snapshot of the powered off OTV / VSC appliance in place before starting this procedure As a general rule, however, it is not recommended to make changes to storage outside of VASA Provider. The procedure to rename Flexvols that are backing vVol datastores is as follows: In the vSphere client select the vVol datastore in question > Configure > ONTAP storage. If the volume is not showing the new name, then rescan storage in vSphere
    • Virtual machine freezes during cloning on VVOL datastore
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/Virtual_machine_freezes_during_cloning_on_VVOL_datastore
      Applies to NetApp HCI Virtual Volumes (vVols) vSphere NetApp Element software 11.3 Cisco UCS UCSB-B200-M5 Issue Cloning a virtual machine residing on a VVOL datastore halts at 95% and freezes the virt...Applies to NetApp HCI Virtual Volumes (vVols) vSphere NetApp Element software 11.3 Cisco UCS UCSB-B200-M5 Issue Cloning a virtual machine residing on a VVOL datastore halts at 95% and freezes the virtual machine for 30 seconds. Please see Additional Information