Skip to main content
NetApp Knowledge Base

E-Series Controller cache battery failed - AutoSupport Message

Last Updated:

Applies to

NetApp E-Series

Event Summary

SANtricity error in the Recovery GURU: FAILED_BATTERY-Recovery Failure Type Code: 6 


  • RECOVERY-GURU-PROCEDURES file shows failure entry of FAILED_BATTERY-Recovery Failure Type Code: 6.

E-Series Controller cache battery failed - AutoSupport Message

  • MAJOR-EVENT-LOG file shows Controller cache battery failed, Event Type 210C.

E-Series Controller cache battery failed

  • SHELVES section in STORAGE-ARRAY-PROFILE file shows Battery status as Failed.


         Battery status:              Failed              
         Location:                    Controller B        
         Age:                         1,825 days          
         Days until replacement:      Not applicable      
         Last learn cycle:            2021/01/21          
         Next learn cycle:            2021/03/18          
         Weeks between learn cycles:  8                   
         Part number:                 PN 36540-06         
         Serial number:               <SERIAL NUMBER>     
         Vendor:                      VN LSI              
         Date of manufacture:         2015/07/01    

  • bidShow(255,0,0,0,0,0,0,0,0,0) command output in STATE-CAPTURE-DATA file provides additional details about the battery failure including its safety status. Example below shows the battery under voltage safety status was triggered leading to its failure.
    • CUV: Cell Under voltage
    • CUVC: Cell Under voltage
    • COV: Cell Overvoltage
    • OCC#: Overcurrent In Charge #
    • OCC: Overcurrent In Charge Recovery
    • OCD#: Overcurrent In Discharge #
    • OCD: Overcurrent In Discharge Recovery
    • AOLD: Overload in Discharge 
    • ASCC: Short Circuit In Charge 
    • ASCD: Short Circuit in Discharge 
    • OTC: Over temperature in Charge
    • OTD: Over temperature in Discharge
    • UTC: Under Temperature in Charge
    • UTD: Under Temperature in Discharge

SafetyStatus:          0x00000001 [ CUV ]


  1. Any BBU failure must first be evaluated to ensure the current controller code is running before replacement.​​​​​ The system must be running or greater.
  2. If the controller firmware is not current as listed above, the firmware must be updated first.
  3. After the firmware is updated, a new manual learn cycle must be run - How to manually start a battery learn cycle using SANtricity
    1. On rare occasions, this may need to be run twice to fully recover a battery affected by previous downrev code issues.
  4. If none of above solved the issue, please contact NetApp Technical Support as a replacement may be necessary. 

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.