Message autosupport :
Sun Nov 4 01:00:32 CET [FILERXXX: asup.smtp.sent:notice]: Cluster Notification mail sent: Cluster Notification from FILERXXX (BATTERY_LOW) WARNING
Sun Nov 4 01:00:45 CET [FILERXXX: asup.post.sent:notice]: Cluster Notification message posted to NetApp: Cluster Notification from FILERXXX (BATTERY_LOW) WARNING
Sysconfig -M :
!NVMEM Battery (bq20z80)!0x0a2d!27100027!0x0000:0x0210:0x00d1!
Bug ref : http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=536445
Battery status :
FILERXXX> environment status chassis list-sensors battery
Sensor Name State Current Critical Warning Warning Critical
Reading Low Low High High
————————————————————————————————-
Bat_1.8V normal 1806 mV 1612 mV 1625 mV 1973 mV 1999 mV
Bat_8.0V normal 7200 mV — — 8900 mV 9000 mV
Bat_Curr normal 0 mA — — 2048 mA 2304 mA
Bat_Run_Time warning low 80 72 80 — —
Bat_Temp normal 21 C -40 C 1 C 70 C 75 C
Charger_Curr normal 0 mA — — 2200 mA 2300 mA
Charger_Volt normal 0 mV — — 8900 mV 9000 mV
SP firmware version : 1.2.1
KB article states that a battery firmware upgrade is required. This causes a filer downtime !
SOLUTION
=========
The 1.3.1 SP firmware contains the new battery firmware, which is not affect by the bug.
An upgrade of the SP firmware from 1.2.1 to 1.3.1 fix the problem. This upgrade can be done safely on a production controller as this not required a takeover.
15 minutes after the end of the upgrade, the battery status is back to normal, as shown bellow :
Sensor Name State Current Critical Warning Warning Critical
Reading Low Low High High
————————————————————————————————-
Bat_1.8V normal 1806 mV 1612 mV 1625 mV 1973 mV 1999 mV
Bat_8.0V normal 7300 mV — — 8900 mV 9000 mV
Bat_Curr normal 0 mA — — 2048 mA 2304 mA
Bat_Run_Time normal 82 72 80 — —
Bat_Temp normal 16 C -40 C 1 C 70 C 75 C
Charger_Curr normal 2000 mA — — 2200 mA 2300 mA
Charger_Volt normal 8200 mV — — 8900 mV 9000 mV