Call home for BATTERY (voltage low) CRITICAL
This knowledge base was generated through a script and may contain formatting issues. For the accurate content, please refer to the WIP editor. WIP editor.
Applies to
- ONTAP 9
- AFF systems
- ASA systems
- FAS systems
Issue
- Call home event for NVMEM battery:
env_mgr: nvmem.battery.voltageLow:EMERGENCY]: The NVMEM battery voltage is critically low (0 mV). To prevent data loss, the system will shut down in 5 minutes.
env_mgr: callhome.battery.failure:EMERGENCY]: Call home for BATTERY (voltage low) CRITICAL.
- Alert is cleared and battery reading normal shortly after:
env_mgr: nvmem.battery.voltage.normal:info]: The NVMEM battery voltage is normal.
- Following events can be seen in BMC event logs:
| Bat_Temp | Assertion Event, "Lower Non-critical going low " | Reading: -18.000 | Threshold: 5.000
| Bat_Temp | Assertion Event, "Lower Critical going low " | Reading: -18.000 | Threshold: 0.000
| Bat_Temp | Deassertion Event, "Lower Critical going low " | Reading: 30.000 | Threshold: 0.000
| Bat_Temp | Deassertion Event, "Lower Non-critical going low " | Reading: 30.000 | Threshold: 5.000
| Bat_Volt | Assertion Event, "Lower Non-critical going low " | Reading: 0.000 | Threshold: 5.600
| Bat_Volt | Assertion Event, "Lower Critical going low " | Reading: 0.000 | Threshold: 5.500
| Bat_Volt | Deassertion Event, "Lower Critical going low " | Reading: 7.900 | Threshold: 5.500
| Bat_Volt | Deassertion Event, "Lower Non-critical going low " | Reading: 7.900 | Threshold: 5.600
- Alerts are seen outside of a learning cycle
- BMC is on latest firmware