Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/AFF_A400_FAS8300_BATTERY_wrong_charge_WARNING
      System generates the AutoSupport alert, ‘Call home for BATTERY (wrong charge) WARNING’, in FAS8300, FAS8700, AFF-A400. KB article explains the steps to resolve this issue, based on the BMC firmware ve...System generates the AutoSupport alert, ‘Call home for BATTERY (wrong charge) WARNING’, in FAS8300, FAS8700, AFF-A400. KB article explains the steps to resolve this issue, based on the BMC firmware version.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Why_raid_timeout_option_doesn_t_avoid_a_environmental_shutdown
      Bug 1466540 - ONTAP ignores the "raid.timeout" option for NV battery events that trigger a shutdown Environmental NVRAM battery full-charge capacity errors are not controlled by the raid.timeout optio...Bug 1466540 - ONTAP ignores the "raid.timeout" option for NV battery events that trigger a shutdown Environmental NVRAM battery full-charge capacity errors are not controlled by the raid.timeout option. [node_name: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Battery PCT capacity low) Bug 1226107 Feature request: SP/BMC support for system environmental shutdown configuration in ONTAP
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/The_NVMEM_battery_charge_FET_is_off_on_AFF-A250___FAS500f
      Repeating The NVMEM battery charge FET events in EMS logs followed immediate by A valid NVMEM battery pack is present. [NODE1: env_mgr: nvmem.battery.packValid:notice]: A valid NVMEM battery pack is p...Repeating The NVMEM battery charge FET events in EMS logs followed immediate by A valid NVMEM battery pack is present. [NODE1: env_mgr: nvmem.battery.packValid:notice]: A valid NVMEM battery pack is present.[ [NODE1: env_mgr: nvmem.battery.FET.off:alert]: The NVMEM battery charge FET is off. [NODE1: env_mgr: nvmem.battery.packValid:notice]: A valid NVMEM battery pack is present. [NODE1: env_mgr: nvmem.battery.normalCharge:notice]: The NVMEM battery charging status is normal.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Controller_Fault_LED_ON_and_Sensor_234_Fault_is_reported_on_NV_Battery
      Controller LED on Controller fault LED is on and the NV Battery is reporting a Sensor 234 Fault. Cluster::> system controller service-event show -instance Location: NV Battery on Controller A Descript...Controller LED on Controller fault LED is on and the NV Battery is reporting a Sensor 234 Fault. Cluster::> system controller service-event show -instance Location: NV Battery on Controller A Description: Sensor 234 Fault Record 328: Sat Jul 23 12:00:13 2022 [IPMI.notice]: 6701 | 02 | EVT: 0301ffff | Bat_Lrn_Active | Assertion Event, "State Asserted" Record 329: Sat Jul 23 18:47:41 2022 [IPMI.notice]: 6801 | 02 | EVT: 0300ffff | Bat_Lrn_Active | Assertion Event, "State Deasserted"
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/nvmem_battery_wrongCharge_for_13_seconds_and_recovers
      FAS2650, FAS8200, AFF A200, and AFF A300 systems report an occasional EMS message 'nvmem.battery.wrongCharge' for several seconds and recovers. KB article provides the reason for this issue and the SP...FAS2650, FAS8200, AFF A200, and AFF A300 systems report an occasional EMS message 'nvmem.battery.wrongCharge' for several seconds and recovers. KB article provides the reason for this issue and the SP firmware versions in which this issue has been resolved.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Call_home_for_BATTERY_Bat_Initial_FCC_unreadable_CRITICAL
      After motherboard replacement, ONTAP reports the following error messages during the boot process: [Node01:nvram.battery.sensor.unreadable:EMERGENCY]: The NVRAM battery state cannot be determined beca...After motherboard replacement, ONTAP reports the following error messages during the boot process: [Node01:nvram.battery.sensor.unreadable:EMERGENCY]: The NVRAM battery state cannot be determined because the 'Bat Initial FCC' sensor is unreadable. [Node01:callhome.battery.failure:EMERGENCY]: Call home for BATTERY ('Bat Initial FCC' unreadable) CRITICAL. [nvram.hw.initFail:CRITICAL]: NVRAM hardware initialization failed: DDR DIMM is not present or failed to train.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FAS9000_NVRAM_battery_capacity_critically_low_0_cycles_warning
      The NVRAM battery capacity is critically low (0 cycles) warning and recover soon. Sun Sep 06 00:00:31 CST [host1: env_mgr: nvram.battery.capacity.low.critical:EMERGENCY]: The NVRAM battery capacity is...The NVRAM battery capacity is critically low (0 cycles) warning and recover soon. Sun Sep 06 00:00:31 CST [host1: env_mgr: nvram.battery.capacity.low.critical:EMERGENCY]: The NVRAM battery capacity is critically low (0 cycles). Sun Sep 06 00:01:12 CST [host1: env_mgr: nvram.battery.capacity.normal:info]: The NVRAM battery capacity is normal. Sun Sep 06 00:01:32 CST [host1: env_mgr: callhome.battery.failure:EMERGENCY]: Call home for BATTERY (capacity low) CRITICAL.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/monitor_shutdown_emergency_Battery_not_present_alert_messages_in_a_powered_down_cluster
      Record 342: Mon Jun 01 15:48:26.930000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not charging Record 402: Mon Jun 22 11:43:49.530000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Batte...Record 342: Mon Jun 01 15:48:26.930000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not charging Record 402: Mon Jun 22 11:43:49.530000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present Record 427: Mon Jun 22 12:01:30.780000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present Record 538: Mon Jun 22 14:19:46.300000 2020 [IPMI.emergency]: env_mgr triggers OS halt:Battery not present
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E_Series_Notification_Write_back_caching_forcibly_disabled_CRITICAL_due_to_faulty_battery
      E-Series notification received: “Write-back caching forcibly disabled”. This could be caused due to battery issue. KB article provides solution to resolve this issue.