Avamar: Gen4s Hardware: Battery Temperature is High
Summary: This article addresses the issue of: Symptom Code 52620 - Controller ID: 0 Battery temperature is high on Avamar Gen4S Hardware.
Symptoms
The following error appears in the Avamar UI or the logs:
<MRMON145> Controller ID: 0 Battery temperature is high
A Dial Home Service Request may also be sent.
Cause
The controller battery on the node fails because the temperature is too high.
The root cause is unknown.
Resolution
1. Log in to the Avamar server as admin, elevate to root, and load the SSH keys.
For instructions on loading keys, see article Avamar: How to Log in to an Avamar Server and Load Various Keys.
2. Using the information from the UI event or the Dial Home Service Request:
a. Determine the node that produced the error message.
b. Connect to that node as root:
ssn 0.# --user=root
Where 0.# is the physical node number.
3. Extract /var/log/messages files using the applicable command below:
bunzip2 /var/log/messages*
gunzip /var/log/messages*
xz --decompress /var/log/messages*
4. Confirm that the logs show that the battery temperature is too high:
grep -i battery /var/log/messages*
Example output:
Nov 22 10:50:20 localhost MR_MONITOR[5385]: Controller ID: 0 Battery Not Present
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery charge complete
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery relearn pending: Battery is under charge
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery Present
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery started charging
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery charge complete
Nov 22 12:02:15 localhost MR_MONITOR[5543]: Controller ID: 0 Battery temperature is normal
Nov 22 12:02:28 localhost MR_MONITOR[5543]: Controller ID: 0 Battery relearn pending: Battery is under charge
Nov 22 12:05:43 localhost MR_MONITOR[5543]: Controller ID: 0 Battery relearn started
Nov 22 12:09:41 localhost MR_MONITOR[5454]: Controller ID: 0 Battery has been replaced
Nov 22 12:09:41 localhost MR_MONITOR[5454]: Controller ID: 0 Battery temperature is high
Nov 22 12:09:44 localhost MR_MONITOR[5454]: Controller ID: 0 Battery relearn pending: Battery is under charge
Jan 16 10:14:15 localhost MR_MONITOR[5497]: Controller ID: 0 Battery Present
Jan 16 10:14:15 localhost MR_MONITOR[5497]: Controller ID: 0 Battery temperature is high
Jan 16 10:14:27 localhost MR_MONITOR[5497]: Controller ID: 0 Battery relearn pending: Battery is under charge
5. Confirm using CmdTool2 that both voltage and current as 0:
CmdTool2 -AdpBbuCmd -GetBbuStatus -a0
BBU status for Adapter: 0
BatteryType:
Voltage: 0 mV
Current: 0 mA
Temperature: 28 C
BBU Firmware Status:
Charging Status : None
Voltage : Low
Temperature : High
Learn Cycle Requested : Yes
Learn Cycle Active : No
Learn Cycle Status : OK
Learn Cycle Timeout : No
I2c Errors Detected : No
Battery Pack Missing : No
Battery Replacement required : No
Remaining Capacity Low : No
Periodic Learn Required : No
Transparent Learn : No
No space to cache offload : No
Pack is about to fail & should be replaced : No
Cache Offload premium feature required : No
Module microcode update required : No
GasGuageStatus:
Fully Discharged : No
Fully Charged : No
Discharging : No
Initialized : No
Remaining Time Alarm : No
Remaining Capacity Alarm: No
Discharge Terminated : No
Over Temperature : No
Charging Terminated : No
Over Charged : No
Pack energy : 0 J
Capacitance : 0
Remaining reserve space : 156
Exit Code: 0x00
6. Check if the battery also reports 0 V:
CmdTool2 -AdpBbuCmd -GetBbuDesignInfo -a0
BBU Design Info for Adapter: 0
Date of Manufacture: 00/00, 0000
Design Capacity: 0 J
Design Voltage: 0 mV
Serial Number: 0
Manufacture Name:
Device Name:
Device Chemistry:
Battery FRU: N/A
TMM FRU: N/A
Module Version:
Transparent Learn = 1
App Data = 0
Exit Code: 0x00
CmdTool2 -AdpBbuCmd -GetBbuProperties -a0
BBU Properties for Adapter: 0
Auto Learn Period: 2419200 Sec
Next Learn time: 0 Sec
Learn Delay Interval:0 Hours
Auto-Learn Mode: Enabled
Exit Code: 0x00
7. If the criteria above is matched, Create a Service Request providing the output above to determine if a node replacement is required.
-- Or --
If the criteria above are not met and the battery is operating as expected, no further action is required.