Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_reboot_an_Element_storage_nodeThis article outlines the procedure to reboot a storage node that is running Element Software. In rare instances, it may be necessary to reboot a storage node that is running Element software. This s...This article outlines the procedure to reboot a storage node that is running Element Software. In rare instances, it may be necessary to reboot a storage node that is running Element software. This should be done only when needed and under the direction of NetApp Support.
- https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/How_to_check__NTP_status_without_connecting_to_SolidFire_storage_nodeApplies to Solidfire Element HCI Storage Element OS Description How to check Network Time Protocol (NTP) status without connecting to SolidFire storage node.
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Adding_storage_node_fails_with_error_Failed_to_initiate_auto_install_on_pending_nodeApplies to SolidFire Element OS HCI Storage Element OS Issue Adding storage node via cluster Web UI fails and the event log(cluster Web UI > Reporting > Event Log) indicates below installEvent. Event ...Applies to SolidFire Element OS HCI Storage Element OS Issue Adding storage node via cluster Web UI fails and the event log(cluster Web UI > Reporting > Event Log) indicates below installEvent. Event Type: installEvent Event Time: 8/7/2020 5:42:23 AM Message: Failed to initiate auto install on pending node
- https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Metadata_drive_of_one_node_is_kicked_out_from_the_clusterApplies to NetApp Element software Storage Node Issue The metadata drive of one node is kicked out from the cluster. No NVRAM related errors are reported on Active IQ. ex=xFileWriteFailed error is det...Applies to NetApp Element software Storage Node Issue The metadata drive of one node is kicked out from the cluster. No NVRAM related errors are reported on Active IQ. ex=xFileWriteFailed error is detected on the event log of Active IQ.
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/Temperature_sensor_Inlet_Temp_is_over_temperature_on_NetApp_HCI_AFAApplies to Element Software SolidFire AFA NetApp HCI Issue The following alert is raised on ActiveIQ / cluster management UI: Temperature sensor Inlet Temp is over temperature The node may be shutdown...Applies to Element Software SolidFire AFA NetApp HCI Issue The following alert is raised on ActiveIQ / cluster management UI: Temperature sensor Inlet Temp is over temperature The node may be shutdown due to high temperature. nodeOffline The SolidFire Application cannot communicate with node ID X. From BMC the following alert appears. Temperature (Inlet Temp) - Upper Critical - going high - Assertion
- Drives unavailable when all nodes of an Element cluster with EAR enabled are rebooted simultaneouslyhttps://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Drives_unavailable_when_all_nodes_of_an_Element_cluster_with_EAR_enabled_are_rebooted_simultaneouslyApplies to Element Software versions 10.0 through 11.1 NetApp HCI SolidFire AFA Encryption At Rest (EAR) Issue On a cluster with Encryption At Rest enabled, one or more drives become unavailable after...Applies to Element Software versions 10.0 through 11.1 NetApp HCI SolidFire AFA Encryption At Rest (EAR) Issue On a cluster with Encryption At Rest enabled, one or more drives become unavailable after all nodes of a cluster are rebooted simultaneously and/or after entire cluster power off and subsequent power up event. In some instances, this may be accompanied by multiple blockServiceUnhealthy alerts in a cluster UI which require assistance from NetApp support to resolve.
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Network_firmware_version_mismatch_warning_appears_after_upgrade_to_Element_10.5Applies to Element 10.5 NetApp SolidFire SF-Series Issue Network firmware version mismatch warning appears in the Active IQ after upgrade to Element 10.5: NETWORK_FIRMWARE_VERSION_ETH0 should be == 7....Applies to Element 10.5 NetApp SolidFire SF-Series Issue Network firmware version mismatch warning appears in the Active IQ after upgrade to Element 10.5: NETWORK_FIRMWARE_VERSION_ETH0 should be == 7.10.18-solidfire-5f3ccbc781d53 but is FFV7.10.18 bc 7.10.11
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/How_to_create_an_RTFI_key_to_re-image_a_SolidFire_storage_nodeApplies to NetApp Element software Restore To Factory Image (RTFI) The steps required for creating an RTFI key and for using the key to re-image a NetApp SolidFire storage node SolidFire uses the Rest...Applies to NetApp Element software Restore To Factory Image (RTFI) The steps required for creating an RTFI key and for using the key to re-image a NetApp SolidFire storage node SolidFire uses the Restore To Factory Image (RTFI) process to image a node as a required part of the node replacement procedure. The node is imaged to ensure the Element software is running at the same version as the other nodes in the cluster. In order to image a node, you first need to create a bootable RTFI USB key.
- https://kb.netapp.com/Legacy/NetApp_HCI/OS/How_to_power_off_and_power_on_a_NetApp_HCI_systemApplies to NetApp HCI H series storage nodes H series compute nodes Description This article describes the procedure to power off and power on a NetApp HCI cluster.
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_disable_DPM_in_VMware_vCenterApplies to HCI Compute Boot OS HCI Storage Element OS Distributed Power Management (DPM) Description This article describes how to disable DPM in VMware vCenter.
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/H610S_Node_goes_into_reboot_loop_during_Node_AdditionApplies to NetApp H610S storage nodes Element Software Releases: 10.4 , 11.0 , 11.1 , 11.3, 11.5, 11.8 Issue While adding H610S nodes to a cluster, the node reboots 5 times before being successfully a...Applies to NetApp H610S storage nodes Element Software Releases: 10.4 , 11.0 , 11.1 , 11.3, 11.5, 11.8 Issue While adding H610S nodes to a cluster, the node reboots 5 times before being successfully added to the cluster.