Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • Fault LED is lit for no apparent reason on a FAS or AFF HA storage system with internal-only SAS storage
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Fault_LED_is_lit_for_no_apparent_reason_on_a_FAS_or_AFF_HA_storage_system_with_internal-only_SAS_storage
      C, SAS, <UP>) Firmware rev: 01.11.06.00 Base WWN: 5:00a098:00361ff:74 Phy State: [4] Enabled, 6.0 Gb/s [5] Enabled, 6.0 Gb/s [6] Enabled, 6.0 Gb/s [7] Enabled, 6.0 Gb/s QSFP Vendor: Amphenol QSFP Part...C, SAS, <UP>) Firmware rev: 01.11.06.00 Base WWN: 5:00a098:00361ff:74 Phy State: [4] Enabled, 6.0 Gb/s [5] Enabled, 6.0 Gb/s [6] Enabled, 6.0 Gb/s [7] Enabled, 6.0 Gb/s QSFP Vendor: Amphenol QSFP Part Number: 112-00176+A0 QSFP Type: Passive Copper 0.5m ID:01 QSFP Serial Number: APF14131767EDC
    • FAS2xxx ports e0a, e0b, e0M, e0P missing with "Invalid PCIe device detected"
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FAS2xxx_ports_e0a_e0b_e0M_e0P_missing_with_Invalid_PCIe_device_detected
      Node remains up but stops responding on the network via ports e0a, e0b, and e0M. Invalid PCIe device detected below PCIe Root Port(Bus/Dev/Func): 00/1C/00 <== the BIOS is not able to recognize some co...Node remains up but stops responding on the network via ports e0a, e0b, and e0M. Invalid PCIe device detected below PCIe Root Port(Bus/Dev/Func): 00/1C/00 <== the BIOS is not able to recognize some components If node can boot, ports e0a, e0b, e0M, and e0P will either be missing entirely, or report Hardware Initialization Failed in sysconfig output: e0a MAC Address: 00:00:00:00:00:00 (Hardware Initialization Failed: IGB: 3)
    • INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/INVALID_CHASSIS_CONFIGURATION_Incompatible_Partner_PCM
      Applies to FAS2500 series FAS2620 FAS2650 Issue The system might report something similar to: System Alert from SP of netapp02-01 (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) In the SP-S...Applies to FAS2500 series FAS2620 FAS2650 Issue The system might report something similar to: System Alert from SP of netapp02-01 (INVALID CHASSIS CONFIGURATION (Incompatible Partner PCM)) In the SP-SYSTEM-EVENT-LOG, you might also see: [SP.critical]: Rebooting SP due to loss of ACP comms
    • PANIC : SINAI device driver fatal error detected in wake-up. in SK process sinai_cleanup_thread on release x.x.x
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/PANIC___SINAI_device_driver_fatal_error_detected_in_wake_up_in_SK_process_sinai_cleanup_threa_on_release_x_x_x
      Applies to FAS20xx FAS22xx FAS25xx Issue Controller panics and reboots with the following message: PANIC: SINAI device driver fatal error detected in wake-up. in SK process sinai_cleanup_thread on rel...Applies to FAS20xx FAS22xx FAS25xx Issue Controller panics and reboots with the following message: PANIC: SINAI device driver fatal error detected in wake-up. in SK process sinai_cleanup_thread on release X.XPX (C)
    • FAS2552 or FAS2554 Ignoring unsupported device boot_i attached to the default bootdevice port
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FAS2552_or_FAS2554_Ignoring_unsupported_device_boot_i_attached_to_the_default_bootdevice_port
      Ignoring unsupported device boot_i attached to the default bootdevice port. Any attempt to restore the image file to a boot device using netboot fails. INSTALL running in check-only mode: the image wi...Ignoring unsupported device boot_i attached to the default bootdevice port. Any attempt to restore the image file to a boot device using netboot fails. INSTALL running in check-only mode: the image will be validated only Mode of operation is INSTALL Current image is image1 Alternate image is image2 Using device /dev/da0 for install Package MD5 checksums pass Versions are compatible Install Validation Failed.
    • Fans are running at high speed and are loud
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Fans_are_running_at_high_speed_and_are_loud
      "environment status" shows fans are running at very high speed even though the temperature is normal in the server room. [1] 14 C (57 F) (ambient) Normal temperature range [2] 33 C (91 F) Normal tempe..."environment status" shows fans are running at very high speed even though the temperature is normal in the server room. [1] 14 C (57 F) (ambient) Normal temperature range [2] 33 C (91 F) Normal temperature range [3] 36 C (96 F) Normal temperature range [4] 57 C (134 F) Normal temperature range [5] 37 C (98 F) Normal temperature range [6] 47 C (116 F) Normal temperature range [7] 59 C (138 F) Normal temperature range [8] 56 C (132 F) Normal temperature range