Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 18 results
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/What_is_the_upgrade_matrix_for_storage_clusters_running_NetApp_Element_software
      Find the version that your storage cluster is currently running in the first column to know the target Element versions the cluster can be upgraded to. If you are upgrading form Element 11.0 or 11.1, ...Find the version that your storage cluster is currently running in the first column to know the target Element versions the cluster can be upgraded to. If you are upgrading form Element 11.0 or 11.1, you must first upgrade to Element 12.3 using HealthTools and then upgrade to Element 12.5 using NetApp Hybrid Cloud Control. 10.4.x †^, 10.5.x †^ , 10.6.x †^ , 11.0.x †^ , 11.1.x^, 11.3P1, 11.3.2, 11.5.x^, 11.7, 11.8.x ^
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/SolidFire_network_ports_show_up_with_incorrect_current_status
      Applies to SolidFire Issue When performing network checks with querying the network.json files, sometimes the network ports status show up as incorrect to the current state of the port, for example po...Applies to SolidFire Issue When performing network checks with querying the network.json files, sometimes the network ports status show up as incorrect to the current state of the port, for example port ethX shows as "Up" and not "UpAndRunning," as shown in the node UI (https://nodeMIP:442) An alert can be raised in AIQ for "Detected network configuration mismatch on Bond1G/Bond10G" with "status" : "Up", + "status" : "UpAndRunning" information
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/When_is_in_order_delivery_IOD_required_and_how_is_it_set
      If one switch in the fabric delivers out-of-order exchanges, the exchanges are delivered to the target out-of-order, regardless of the policy configured on other switches in the fabric. Out of order d...If one switch in the fabric delivers out-of-order exchanges, the exchanges are delivered to the target out-of-order, regardless of the policy configured on other switches in the fabric. Out of order delivery in these environments should not occur if the switches are configured according to the “Switch Configuration for Fabric MetroCluster” which is posted on the NOW site.
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Why_do_not_all_SolidFire_nodes_have_a_role
      Not every node in a cluster will have a role, only the Cluster Master and either 3 or 5 Ensemble nodes, and these roles can and do often overlap Log in to Active IQ, select the cluster you wish to vie...Not every node in a cluster will have a role, only the Cluster Master and either 3 or 5 Ensemble nodes, and these roles can and do often overlap Log in to Active IQ, select the cluster you wish to view and click on Nodes in the left hand menu Also listed in the output will be "ensemble": followed by a list of IP addresses of the nodes acting as Ensemble members
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/What_are_the_SolidFire_FC_cluster_limits
      It is necessary to determine the total IOPS capability of the FC hardware installed in a cluster, and the total storage IOPS capability, to ensure that FC capabilities are always sufficient to serve t...It is necessary to determine the total IOPS capability of the FC hardware installed in a cluster, and the total storage IOPS capability, to ensure that FC capabilities are always sufficient to serve the storage. Failure to take care of number of zone Initiator access to specific FC Target ports results in "Path Explosion" - where a single host might have far more paths to a LUN than intended and so unintentionally consumes many resources on the FC node.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/How_to_calculate_volume_usage__on_SolidFire_cluster_using_APIs
      Applies to SolidFire NetApp Element software Description This article explains how to obtain volume usage via APIs
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/What_are_the_SolidFire_FC_cluster_best_practices
      Frames that arrive out of order are “dropped”, this forces the initiator to restart the transaction which consumes Initiator, Target, and, possibly, switch resources (very broadly, this adds to the fa...Frames that arrive out of order are “dropped”, this forces the initiator to restart the transaction which consumes Initiator, Target, and, possibly, switch resources (very broadly, this adds to the fabric latency and ESXi Path Down Discovery (PDL)). Above recommendation keeps State Change notifications constrained to just the Initiator and Target in the zone and they do not need to process the rest of the fabric.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Failed_drive_on_Element_cluster
      Alert for driveFailed on Element cluster in NetApp SolidFire Active IQ and in cluster alerts tab
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_migrate_SolidFire_vCenter_API_for_Storage_Awareness_VASA_from_one_vSphere_instance_to_another
      When attempting to migrate to a new vCenter, VASA may issues with the old vCenter keystore being persistent, leading to inaccessible VVol containers and a data unavailable situation. The SolidFire VAS...When attempting to migrate to a new vCenter, VASA may issues with the old vCenter keystore being persistent, leading to inaccessible VVol containers and a data unavailable situation. The SolidFire VASA provider can only be registered to a single vCenter due to limitations with how vCenter handles SSL. A single vCenter can have multiple SolidFire clusters, but a SolidFire cluster cannot be shared between two instance of vCenter.
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/AutoSupport_Message__driveFailed_on_Element_cluster
      AutoSupport Message: driveFailed on Element cluster in NetApp SolidFire Active IQ and in cluster alerts tab
    • https://kb.netapp.com/Legacy/NetApp_HCI/Hardware/H610S__erroneous_NVRAM_error_messages
      This article covers sporadic logging of NVRAM faults on H610S nodes, which often results in eviction of a node's slice (metadata) drive. The node logs a variation of one of the NVRAM (NVDIMM) faults m...This article covers sporadic logging of NVRAM faults on H610S nodes, which often results in eviction of a node's slice (metadata) drive. The node logs a variation of one of the NVRAM (NVDIMM) faults mentioned in the issue section.