Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1002220.1
Update Date:2017-08-01
Keywords:

Solution Type  Problem Resolution Sure

Solution  1002220.1 :   Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged"  


Related Items
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
  •  

PreviouslyPublishedAs
203139


Applies to:

Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
All Platforms

Symptoms

Sun Storage 3000 Arrays will at times have the following sequence of messages contained within the RAID controller event log:


[0125] #6: StorEdge Array SN#123456 Peripheral Device ALERT: primary battery board not fully charged
[01a5] #7: StorEdge Array SN#123456 Peripheral Device NOTICE: primary battery board fully charged
[0125] #13: StorEdge Array SN#123456 Peripheral Device ALERT: secondary battery board not fully charged
[01a5] #14: StorEdge Array SN#123456 Peripheral Device NOTICE: secondary battery board fully charged

These messages are referencing the cache battery backup unit (BBU) of the primary and secondary RAID controllers. Moreover, the following message is logged for both RAID controllers on the management host (or loghost) reported by Sun Storage Diagnostic Reporter:

Nov  9 15:37:48 Testhost SUNWscsdMonitor[315]: [ID 863683 daemon.error][SUNWscsd 0x10B1D0E: Critical] <rctrl5007> Controller Event, Battery Primary Not-fully-charged. Likely battery module error. If error persists, replace defective battery module.  (Secondary, Sat Nov  6 01:07:05 2004) {SN#123456}

 

Cause

These events are not necessarily an indication of a problem with the array. They are the result of a drop in battery charge below 3.9V. These events are logged upon controller insertion, array reset and/or array power ON. The below event was logged when the voltage of the BBU on the primary controller has dropped below 3.9V and the system has turned ON the charging circuit for that battery:

[0125] #6: StorEdge Array SN#123456 Peripheral Device ALERT: primary battery board not fully charged

Subsequently, the below event follows which indicates that the primary BBU has charged fully and the charging circuit has been turned OFF.  A fully charged battery holds a charge of greater than 4.2V.

[01a5] #7: StorEdge Array SN#123456 Peripheral Device NOTICE: primary battery board fully charged

The following table describes the relationship between the firmware menu display, battery voltage, and capacity:

Battery Display      Battery Voltage       Battery Capacity
--------------------------------------------------------------
+++++               > 4.2V                   100%
++++-               < 4.20V                < 100%
+++--               < 4.05V                < 80%
++---               < 3.96V                < 60%
+----               < 3.84V                < 40%
-----               < 3.76V                < 20%

Solution

If the battery charge time is relatively short, then replacement should be considered. Also replacement may be needed if the "fully charged" event never appears in the RAID controller event logs, or if a new charge cycle is immediately started within minutes of completion.

 

  • A 60% battery capacity is sufficient to safely provide backup for 512 Mbyte cache module if the array is powered down for 72+ hours.

  • Unlike the Sun Storage 6000 Arrays, there is no periodic discharge for the BBU. The enclosure relies on the voltage sensor within the controller board, which turns ON the charging circuit when the battery voltage drops below 3.9V.


Your lithium ion battery should be changed every two years if the unit is continuously operated at 25 degrees C. If the unit is continuously operated at 35 degrees C or higher, it should be changed every year. The shelf life of the battery is three years.

In the event of a power failure, the battery maintains power to the cache for 72 hours. When power is restored, the data in cache is destaged to disk. The following example shows a good upper battery and a lower battery that is set to expire within the next week. Note that the command show battery-status applies only to Sun Storage 3510 and 3511 arrays.

sccli> show battery-status
Upper Battery Type: 1
Upper Battery Manufacturing Date: Sat Jan 04 00:00:00 2003
Upper Battery Placed In Service:  Thu Jan 22 10:59:58 2004
Upper Battery Expiration Date:    Tue Jan 03 06:00:00 2006
Upper Battery Status: good


Lower Battery Type: 1
Lower Battery Manufacturing Date: Tue Jan 02 00:00:00 2001
Lower Battery Placed In Service: Sat Dec 29 00:00:00 2001
Lower Battery Expiration Date: Mon Dec 29 00:00:00 2003
Lower Battery Status: warning

 

NOTE: For information on "Battery Expiration" reference Technical Instruction < Document: 1009069.1 > Sun StorEdge[TM] 351x Array: Battery Expiration and Status Monitoring.
3310, 3320, 3511, 3510, battery, charged, StorEdge, Array, Minnow, SE3000, 3000, audited, normalized
Previously Published As
78711

Change History
Date: 2009-12-22
User Name: sue.copeland@sun.com
Action: Currency & Update

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback