Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 8 results
    • CRC errors due to incorrect type of SFP used AFBR-57F5MZ-NA1
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CRC_errors_due_to_incorrect_type_of_SFP_used_AFBR-57F5MZ-NA1
      RECEIVE Total frames: 87552k | Frames/second: 6 | Total bytes: 16679m Bytes/second: 1066 | Total errors: 11430 | Errors/minute: 0 Total discards: 0 | Discards/minute: 0 | Multi/broadcast: 2567k Non-pr...RECEIVE Total frames: 87552k | Frames/second: 6 | Total bytes: 16679m Bytes/second: 1066 | Total errors: 11430 | Errors/minute: 0 Total discards: 0 | Discards/minute: 0 | Multi/broadcast: 2567k Non-primary u/c: 0 | CRC errors: 11352 | Runt frames: 0 Fragment: 0 | Long frames: 0 | Jabber: 16 Length errors: 62 | No buffer: 0 | Xon: 0 Xoff: 0 | Pause: 0 | Jumbo: 419k Noproto: 0 | Error symbol: 2300 | Illegal symbol: 1300 Bus overruns: 0 | Queue drops: 0 | LRO segments: 55499k LRO bytes: 12918m | L…
    • e0a/e0b link flaps on A300/FAS8200, A200/FAS2600, A220/FAS2700,C190 may cause a Takeover
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/e0a_e0b_link_flaps_on_A300_FAS8200_A200_FAS2600_A220_FAS2700_C190_may_cause_a_Takeover
      Cluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the a...Cluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the affected node and resolve the issue.
    • "(CHASSIS POWER DEGRADED: Power Supply Status Critical: PSU1, PSU2.) ERROR" AutoSupport message occurs
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CHASSIS_POWER_DEGRADED__Power_Supply_Status_Critical__PSU1_PSU2_ERROR_AutoSupport_message_occurs
      AutoSupport is triggered that the chassis power supply are degraded. HA Group Notification from node-02 (CHASSIS POWER DEGRADED: Power Supply Status Critical: PSU1, PSU2.) ERROR [node-02: monitor: mon...AutoSupport is triggered that the chassis power supply are degraded. HA Group Notification from node-02 (CHASSIS POWER DEGRADED: Power Supply Status Critical: PSU1, PSU2.) ERROR [node-02: monitor: monitor.globalStatus.critical:EMERGENCY]: Power Supply Status Critical: PSU1, PSU2. [node-02: power_low_monitor: monitor.chassisPowerSupplies.ok:info]: Chassis power supplies OK [node-02: monitor: monitor.globalStatus.ok:info]: The system's global status is normal
    • ONTAP Upgrade got paused, as the new BIOS firmware was unable to load with "mSATA Read Error"
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ONTAP_Upgrade_got_paused_as_the_new_BIOS_firmware_was_unable_to_load_with_mSATA_Read_Error
      SP logs showed: during upgrade the new BIOS firmware failed to load from boot device for Update and system landed at Loader prompt: mSATA Read Error: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) Faile...SP logs showed: during upgrade the new BIOS firmware failed to load from boot device for Update and system landed at Loader prompt: mSATA Read Error: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) Failed to load flash image: Error Record 77: Thu Feb 25 03:07:31.000000 2021 [SysFW.critical]: mSATA Read Error: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) Record 80: Thu Feb 25 03:07:33.000000 2021 [SysFW.notice]: Failed to update flash: Failed to load flash image.
    • DIMM mapped out with error 0x30 during boot on A300, A220, A200, FAS8200, FAS27xx, FAS26xx
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/DIMM_mapped_out_with_error_0x30_during_boot_on_A300_A220_A200_FAS8200_FAS27xx_FAS26xx
      Applies to AFF A300 AFF A220 AFF A200 FAS8200 After a reboot, the system fails to boot with the error DIMM:x mapped out with the error code 0x30. Error on boot: System DIMM configuration is not suppor...Applies to AFF A300 AFF A220 AFF A200 FAS8200 After a reboot, the system fails to boot with the error DIMM:x mapped out with the error code 0x30. Error on boot: System DIMM configuration is not supported on FAS2650 Please check the DIMM placement on SLOT-2 ... BIOS Version: 11.2.1 Portions Copyright (C) 2014-2018 NetApp, Inc. All Rights Reserved. Initializing System Memory ... DIMM:2 mapped out. BIOS MRC HW R/W test error. Major / Minor Error Code: 0x30 / 0x1C Complete channel mapped out.
    • Service Processor is not functioning
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Service_Processor_is_not_functioning
      Applies to NetApp AFF and FAS systems ONTAP 9 Service Processor - SP Baseboard Management Controller - BMC Management port - e0M Issue Unable to connect to the service processor via SSH, firmware imag...Applies to NetApp AFF and FAS systems ONTAP 9 Service Processor - SP Baseboard Management Controller - BMC Management port - e0M Issue Unable to connect to the service processor via SSH, firmware image and version is seen as "unknown". Refer to the additional information section for more details.
    • System disruption occurs after temporarily unable to read or write to boot device X3320A
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/System_disruption_occurs_after_temporarily_unable_to_read_or_write_to_boot_device_X3320A
      The node with the boot device experiencing the issue will panic or fail to reboot with errors referencing CPU hung, mgwd unresponsive or boot device not found
    • AFF A300 data port is down
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/AFF_A300_data_port_is_down
      Applies to AFF A300 ONTAP 9 Onboard data ports (a0a, a0b, e0c, e0d) Issue Data ports are down (sysconfig -a) slot 0: 1/10 Gigabit Ethernet Controller IX4-T e0c MAC Address: xx:xx:xx:xx:xx:xx (auto-unk...Applies to AFF A300 ONTAP 9 Onboard data ports (a0a, a0b, e0c, e0d) Issue Data ports are down (sysconfig -a) slot 0: 1/10 Gigabit Ethernet Controller IX4-T e0c MAC Address: xx:xx:xx:xx:xx:xx (auto-unknown-fd-down) e0d MAC Address: xx:xx:xx:xx:xx:xx(auto-1000t-fd-up) In some cases, the port may be up but going down very often: ::> network port show -health -node node-01 Node Port Link Status Degraded Reasons node-01 a0a up degraded link_flapping a0b up degraded link_flapping