AFF A320 shuts down after nvmem.battery.wrongCharge
Applies to
- AFF A320
- ONTAP 9
Issue
Node shuts down after nvmem.battery.wrongCharge:alert
- EMS messages for one node in the cluster:
Sat Dec 19 16:23:27 +0100 [CLUSTERBA-CTRLA: env_mgr: callhome.battery.warning:alert]: Call home for BATTERY (wrong charge) WARNING.
... (repeated hourly)
Sun Dec 20 15:23:38 +0100 [CLUSTERBA-CTRLA: env_mgr: nvmem.battery.wrongCharge:alert]: The NVMEM battery charger is charging the battery even though the battery is not requesting to be charged. To prevent data loss, the system will shut down in 60 minutes.
Sun Dec 20 15:24:18 +0100 [CLUSTERBA-CTRLA: env_mgr: callhome.battery.warning:alert]: Call home for BATTERY (wrong charge) WARNING.
Sun Dec 20 16:22:30 +0100 [CLUSTERBA-CTRLA: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Battery charging current failed)
- Platform sensors output for the NVMEM Battery:
Battery Charge Failed? discrete fault normal TRUE
Battery Capacity Message discrete failed failed
Bat Curr current normal -40 mA
Bat Charging State discrete fault normal WRONG_CHARGE
- The Service Processor firmware and internal switch firmware are updated to the latest version available.
- BMC System log output:
Jan 7 14:17:14 (none) env_mgr[1035]: Payload EMS: EMS_nvmem_battery_wrongCharge(in 24 hours)
Jan 7 14:17:46 (none) env_mgr[1035]: Payload EMS: EMS_callhome_battery_warning(BATTERY (wrong charge))
Jan 7 15:17:20 (none) env_mgr[1035]: Payload EMS: EMS_nvmem_battery_wrongCharge(in 23 hours)
Jan 7 15:17:47 (none) env_mgr[1035]: Payload EMS: EMS_callhome_battery_warning(BATTERY (wrong charge))
...
- Node shutsdown once counter reaches 24 hours