Skip to main content
NetApp Knowledge Base

Call home for BATTERY (charge FET off) WARNING

Views:
1,388
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS8040
  • ONTAP 9.7P8
  • Service Processor (SP) 3.10

Issue

  • ONTAP hourly reports "BATTERY (charge FET off)" warning in the EMS logs.

​​​​Example:

2/20/2021 08:28:44 node02 ALERT callhome.battery.warning: Call home for BATTERY (charge FET off) WARNING.
2/20/2021 08:28:14 node02 ERROR nvram.battery.chargeFET.off: The NVRAM battery charge FET is off. To prevent data loss, the system will shut down in 20 hours.
2/20/2021 07:28:44 node02 ALERT callhome.battery.warning: Call home for BATTERY (charge FET off) WARNING.
2/20/2021 07:28:14 node02 ERROR nvram.battery.chargeFET.off: The NVRAM battery charge FET is off. To prevent data loss, the system will shut down in 21 hours.
2/20/2021 06:28:44 node02 ALERT callhome.battery.warning: Call home for BATTERY (charge FET off) WARNING.
2/20/2021 06:28:14 node02 ERROR nvram.battery.chargeFET.off: The NVRAM battery charge FET is off. To prevent data loss, the system will shut down in 22 hours.
2/20/2021 05:28:44 node02 ALERT callhome.battery.warning: Call home for BATTERY (charge FET off) WARNING.
2/20/2021 05:28:14 node02 ERROR nvram.battery.chargeFET.off: The NVRAM battery charge FET is off. To prevent data loss, the system will shut down in 23 hours.
2/20/2021 04:28:44 node02 ALERT callhome.battery.warning: Call home for BATTERY (charge FET off) WARNING.
2/20/2021 04:28:14 node02 ERROR nvram.battery.chargeFET.off: The NVRAM battery charge FET is off. To prevent data loss, the system will shut down in 24 hours.

  • SP log "system sensors" show "Charge FET" off.

Example:

Bat_Present      | 0x0        | discrete   | Present    | na        | na        | na        | na        
Bat_Temp         | 20.000     | degrees C  | ok         | 0.000     | 5.000     | 53.000    | 58.000    
Bat_Volt         | 8.000      | Volts      | ok         | 5.500     | 5.600     | 8.500     | 8.600     
Bat_Curr         | 0.000      | Amps       | ok         | -4.000    | -0.040    | 1.200     | 1.520     
Bat_Rem_Cap      | 3.072      | Amps * hour | ok         | na        | na        | na        | na        
Bat_Full_Cap     | 3.072      | Amps * hour | ok         | na        | na        | na        | na        
Bat_Charge_Curr  | 0.000      | Amps       | ok         | na        | na        | 2.200     | 2.300     
Bat_Charge_Volt  | 0.000      | Volts      | ok         | na        | na        | 8.900     | 9.000     
Bat_Design_Cap   | 5.500      | Amps * hour | ok         | na        | na        | na        | na        
Bat_Initial_Fcc  | 4.200      | Amps * hour | ok         | na        | na        | na        | na        
Bat_Dstg_Cycles  | 45.000     | cycles     | ok         | 2.000     | 5.000     | na        | na        
Bat_Power_Fault  | 0x0        | discrete   | Deasserted | na        | na        | na        | na        
Bat_Tca_Status   | 0x0        | discrete   | Asserted   | na        | na        | na        | na        
Bat_Dcharge_FET  | 0x0        | discrete   | Deasserted | na        | na        | na        | na        
Bat_Charge_FET   | 0x0        | discrete   | Asserted   | na        | na        | na        | na        
Bat_Pack_Invalid | 0x0        | discrete   | Deasserted | na        | na        | na        | na     

  • SP log "events all" also shows "charge FET" off and does not automatically recover.
Example:
Fri Feb 19 19:22:06.182655 2021 [IPMI.notice]: c601 | 02 | EVT: 0300ffff | Bat_Tca_Status | Assertion Event, "State Deasserted"
Fri Feb 19 19:28:13.791368 2021 [IPMI.notice]: c701 | 02 | EVT: 0301ffff | Bat_Tca_Status | Assertion Event, "State Asserted"
Fri Feb 19 19:28:13.876524 2021 [IPMI.notice]: c801 | 02 | EVT: 0301ffff | Bat_Charge_FET | Assertion Event, "State Asserted"
Fri Feb 19 19:28:14.081617 2021 [Agent.notice]: 727.659: 11 : Controller Attention LED asserted 
Fri Feb 19 19:28:14.081784 2021 [Agent.notice]: 727.659: 14 : Attention LED (at Midplane) asserted
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.