Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FAQ__NVMe_Flash_Cache_module_firmware_update
      Unlike previous iterations of Flash Cache where FW was available with system firmware, the NVMe Flash Cache FW is available on the NetApp Support Site Drive Firmware Page as part of the All FW package...Unlike previous iterations of Flash Cache where FW was available with system firmware, the NVMe Flash Cache FW is available on the NetApp Support Site Drive Firmware Page as part of the All FW package or as individual downloads. Unlike storage HDD or SSD firmware, there are no messages indicating that "firmware will now be updated". However, there are three EMS events that are logged in ONTAP 9.1 or later that track completion of the firmware update:
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ic_HAInterconnectLinkDown_occurring_frequently
      [?] Thu Apr 28 02:00:00 +0000 [node-1: statd: ic.HAInterconnectLinkDown:error]: HA interconnect: External link #0 has been down for 73387 minutes. [?] Thu Apr 28 03:00:00 +0000 [node-1: statd: ic.HAIn...[?] Thu Apr 28 02:00:00 +0000 [node-1: statd: ic.HAInterconnectLinkDown:error]: HA interconnect: External link #0 has been down for 73387 minutes. [?] Thu Apr 28 03:00:00 +0000 [node-1: statd: ic.HAInterconnectLinkDown:error]: HA interconnect: External link #0 has been down for 73447 minutes. [?] Thu Apr 28 04:00:00 +0000 [node-1: statd: ic.HAInterconnectLinkDown:error]: HA interconnect: External link #0 has been down for 73507 minutes.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Physical_connectivity_is_unstable_between_cluster_network_cable_and_cluster_ports
      Applies to FAS8700 Issue Physical connectivity is unstable between cluster network cable and cluster ports Cable replacement could not resolve this onboard cluster port physical problem
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/A400_FAS8300_FAS8700_PSU_missing_even_after_replacement
      Tue May 14 13:05:57 -0700 [scc57n13b: env_mgr: callhome.chassis.ps.rm:error]: Call home for CHASSIS POWER SUPPLY REMOVED: PS 1 Health alert for missing FRU is present on the cluster: Probable Cause: P...Tue May 14 13:05:57 -0700 [scc57n13b: env_mgr: callhome.chassis.ps.rm:error]: Call home for CHASSIS POWER SUPPLY REMOVED: PS 1 Health alert for missing FRU is present on the cluster: Probable Cause: PSU1 is not present in the chassis XXXXXXXXXX. Possible Effect: The nodes in the chassis might not function effectively or redundancy might be lost. Refer to the Hardware specification guide for more information on the position of the field-replaceable unit (FRU) and ways to check or replace it.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Some_controllers_might_fail_to_boot_after_inserting_into_chassis
      After inserting a motherboard (listed above) into the chassis and closing the levers, the motherboard may not fully engage the backplane and will fail to boot up. After maintenance, such as a replacem...After inserting a motherboard (listed above) into the chassis and closing the levers, the motherboard may not fully engage the backplane and will fail to boot up. After maintenance, such as a replacement of a FRU (NVRAM card, NVRAM battery, RTC battery, DIMM, fan, boot device or PCIe adapter card) on the known-good motherboard, or a replacement of the motherboard itself, you could misinterpret the symptoms as a failed motherboard.