Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_troubleshoot_Metadata_drive_moves_to_available_as_soon_as_adding_it
      Applies to NetApp Element software Storage Node Description Metadata drive moves to available a few minutes later after adding it.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/How_to_change_the_IOPs_on_a_Virtual_Volume_vVOL_that_has_already_been_created
      This guide will show you how to change QOS settings for vVols by modifying the associated Storage Policy. By monitoring vVols statistics from the cluster WebUI (Active IQ currently does not report on ...This guide will show you how to change QOS settings for vVols by modifying the associated Storage Policy. By monitoring vVols statistics from the cluster WebUI (Active IQ currently does not report on vVols) you may find that you need to change the vVols IOPs that are defined for better performance. Virtual Volumes are controlled by Storage Policies (SPBM) that can be edited within the vSphere Web client. Changes made to the SPBM will be reflected in Element on the related vVols.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/SF_Series_Hardware_Fault__RTFI_HARDWARE_FAILURES_RADIAN_TIME_TO_CHARGE_or_timeToChargeCapacitors__150_in_cluster_UI
      In Storage cluster UI, a node fault: warning={timeToChargeCapacitors: [>150] Seconds} error={derivedCapacitanceOfThePack: 0.000 F} During RTFI: Example screenshot during RTFI: If this occurs during RT...In Storage cluster UI, a node fault: warning={timeToChargeCapacitors: [>150] Seconds} error={derivedCapacitanceOfThePack: 0.000 F} During RTFI: Example screenshot during RTFI: If this occurs during RTFI, accept the message Ignore errors and continue (ALT-F8 to display, ALT-F7 to return) (Yes,No) Finish the RTFI and add the node to the cluster, but do not add any drives Cluster UI should show a node fault similar to: NVRAM device problems detected, metadata drive will be removed.
    • https://kb.netapp.com/Legacy/NetApp_HCI/OS/Element_OS_12.0__MVIP_cannot_login_due_to_NTP_sync
      Applies to Element 12.0 and above Issue When incorrect NTP configuration is applied users cannot login to the cluster MVIP and cannot update NTP server, an error is raised: Sign in is blocked because ...Applies to Element 12.0 and above Issue When incorrect NTP configuration is applied users cannot login to the cluster MVIP and cannot update NTP server, an error is raised: Sign in is blocked because your client's clock is more than 5 minutes out of sync with the storage cluster's clock. Adjust the clocks, then refresh the page to try again.