Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 17 results
    • FAQ: NVMe Flash Cache module firmware update
      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:
    • 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
    • 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.
    • Chassis Power Supply Need To Be Replaced - AutoSupport message
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CHASSIS_POWER_SUPPLY_NEED_TO_BE_REPLACED_-_Autosupport_message
      This article describes the procedure on how to handle AutoSupport message - CHASSIS POWER SUPPLY NEEDS TO BE REPLACED. This message indicates that one or more of the power supplies on the Controller C...This article describes the procedure on how to handle AutoSupport message - CHASSIS POWER SUPPLY NEEDS TO BE REPLACED. This message indicates that one or more of the power supplies on the Controller Chassis is not working correctly. If the source power is not the issue and the issue is not resolved, a part replacement may be required. Bug 1417161 - System might send "CHASSIS POWER SUPPLY NEED TO BE REPLACED" AutoSupport message during power maintenance
    • SP in rebooting status after ONTAP upgrade or maintenance activity
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SP_in_rebooting_status_after_ONTAP_upgrade_or_maintenance_activity
      ONTAP 9 Service processor (SP) Baseboard Management Controller (BMC) The status of SP/BMC shows as rebooting after a maintenance activity: Cluster::> system service-processor show Node Type Status IP ...ONTAP 9 Service processor (SP) Baseboard Management Controller (BMC) The status of SP/BMC shows as rebooting after a maintenance activity: Cluster::> system service-processor show Node Type Status IP Configured FirmwareVersion IP Address FAS8200-01 BMC rebooting true 13.4P2 1.2.3.4 FAS8200-02 BMC online true 13.4P2 1.2.3.5 The same status is observed from sysconfig -a output as well: ::> system node run -node <node> -command sysconfig -a Service Processor Status: Rebooting
    • ONTAP Service Processor output "Error: command failed: Database is not open."
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ONTAP_Service_Processor_output_Error__command_failed__Database_is_not_open
      Applies to FAS8200 ONTAP version: 9.5P13 Service Processor (SP) version: 5.6P2 Issue Controller replacement running SP fw. version 5.6P2. No SSH to the SP of that node SP status on that node not visib...Applies to FAS8200 ONTAP version: 9.5P13 Service Processor (SP) version: 5.6P2 Issue Controller replacement running SP fw. version 5.6P2. No SSH to the SP of that node SP status on that node not visible in the ONTAP command line interface (CLI). Example: ::> system service-processor show IP Firmware Node Type Status Configured Version IP Address Node_name1 SP online true 5.6P2 xxx.yyy.zzz.ttt Error: show failed: Database is not open.
    • Both the nodes are indicating Chassis power supply x is degraded: PSUx sensorName is Unreadable
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Both_the_nodes_are_indicating_Chassis_power_supply_x_is_degraded__PSUx_sensorName_is_Unreadable
      [?] Mon Jul 29 13:07:07 [node-a: env_mgr: monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan1 Fault is Unreadable [?] Mon Jul 29 13:07:07 [node-a: env_mgr: monit...[?] Mon Jul 29 13:07:07 [node-a: env_mgr: monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan1 Fault is Unreadable [?] Mon Jul 29 13:07:07 [node-a: env_mgr: monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan2 Fault is Unreadable [?] Mon Jul 29 13:07:06 [node-b: env_mgr: monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan1 Fault is Unreadable
    • Boot loop PANIC during ONTAP upgrade on FAS8200
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Boot_loop_PANIC_during_ONTAP_upgrade_on_FAS8200
      One node in s boot loop PANIC after ONTAP upgrade. Tue Dec 21 08:54:32 2021 [nv2flash.restage.progress:NOTICE]: ReStage is not needed because the flash hasno data. PANIC : Sanity check failed, armed: ...One node in s boot loop PANIC after ONTAP upgrade. Tue Dec 21 08:54:32 2021 [nv2flash.restage.progress:NOTICE]: ReStage is not needed because the flash hasno data. PANIC : Sanity check failed, armed: 1, disarmed: 0, is_armed: 0 coredump: primary dumper is not yet registeredthis early during system initialization. coredump: secondary dumper is not yetregistered this early during system initialization. A coredump will not be available at this time.
    • LUNs missing on HP UX Host with Error “Evpd inquiry page 83h/80h failed” generated on host end
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/LUNs_missing_on_HP_UX_Host_with_Error_Evpd_inquiry_page_83h_80h_failed_generated_on_host_end
      Applies to HP-UX 11.31 Ontap 9 FAS 8200 Issue LUNs went missing on host end with error: “Evpd inquiry page 83h/80h failed” generated on host end
    • IO interrupted during takeover
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/IO_interrupted_during_takeover
      Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node1 (on virtual server 3), IP address xx.xxx.xx.81, is now hosted on node node-01, port a2a. Tue Nov 19 19:12...Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node1 (on virtual server 3), IP address xx.xxx.xx.81, is now hosted on node node-01, port a2a. Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node2 (on virtual server 3), IP address xx.xxx.xx.82, is now hosted on node node-01, port a2a.