Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • "Unknown" error when selecting an aggregate in the Virtual Storage Console provisioning wizard
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/Unknown_error_when_selecting_an_aggregate_in_the_Virtual_Storage_Console_provisioning_wizard
      Applies to Virtual Storage Console (VSC) Issue When selecting an aggregate in the NetApp Datastore Provisioning Wizard, an Unknown error is reported: The VSC kamino.log file includes (or similar): Err...Applies to Virtual Storage Console (VSC) Issue When selecting an aggregate in the NetApp Datastore Provisioning Wizard, an Unknown error is reported: The VSC kamino.log file includes (or similar): Error getting volumes mounted as datastores. java.lang.IllegalArgumentException: 'filer01-lif01' is not an IP string literal. Unable to get IP for host01 java.net.UnknownHostException: host01: Name or service not known
    • Virtual Storage Console (VSC): Aggregate missing in Provision Datastore wizard
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/Aggregate_missing_in_Provision_Datastore_wizard
      Applies to Virtual Storage Console (VSC) Issue In the VSC Provision Datastore wizard, the Aggregate dropdown is missing one or more desired aggregates.
    • Trident creates a new economy ONTAP volume despite space in existing ones
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_creates_a_new_economy_ONTAP_volume_despite_space_in_existing_ones
      Applies to Trident for Openshift/Kubernetes When setting up a POD with a new PVC using the ontap-nas-economy or ontap-san-economy backends, Trident creates a new ONTAP Volume despite the existing econ...Applies to Trident for Openshift/Kubernetes When setting up a POD with a new PVC using the ontap-nas-economy or ontap-san-economy backends, Trident creates a new ONTAP Volume despite the existing economy (qtree/LUN) volumes having space for the new volume on the aggregate. Instead of creating the volume, this can also cause the following error when the SVM's volume limit is reached: Cannot create volume. Reason: Maximum volume count for Vserver <SVM> reached. Maximum volume count is <VOL_LIMIT>.
    • Incorrect drive letter assigned when provisioning new disk
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Incorrect_drive_letter_assigned_when_provisioning_new_disk
      Applies to SnapCenter Plug-In for Windows (SCW) Issue When provisioning a new disk with SnapCenter, the wrong drive letter is assigned to the disk when the operation completes For example: The S:\ is ...Applies to SnapCenter Plug-In for Windows (SCW) Issue When provisioning a new disk with SnapCenter, the wrong drive letter is assigned to the disk when the operation completes For example: The S:\ is specified during the create disk wizard but the disk is created as F:\
    • SolidFire GUI shows incorrect volume capacity utilization
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/SolidFire_GUI_shows_incorrect_volume_capacity_utilization
      Applies to Element Software NetApp SolidFire NetApp HCI Issue Both SolidFire GUI and Active IQ show incorrect (non-updated) volume capacity utilization after data migration from one volume to another ...Applies to Element Software NetApp SolidFire NetApp HCI Issue Both SolidFire GUI and Active IQ show incorrect (non-updated) volume capacity utilization after data migration from one volume to another using Storage vMotion