Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1009069.1
Update Date:2010-06-30
Keywords:

Solution Type  Technical Instruction Sure

Solution  1009069.1 :   Sun StorEdge[TM] 351x Array: Battery Expiration and Status Monitoring  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
212505


Applies to:

Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
All Platforms

Goal

Description:

The battery expiration monitoring feature is available for the Sun Storage  351x Arrays. This feature, which reports the expiration date and status of battery modules has been available since release 1.5 of the sscs software. The minimum Battery module revision is PN: 370-5545-02 (date code 050 or later),
and the minimum Controller PN: 370-5537-06 (Revision 50 or later).

This document describes the theory of operation for battery expiration monitoring for the Sun Storage 3510 and 3511 Arrays.

Solution

Theory of Operation:

The battery manufacture date, the in-service date, and the battery
shelf life are used to determine the expiration date.

Only the manufacturing date is set for a battery CRU during the
manufacturing process. The in-service date will be set when the Battery
Module is installed in a system as per the CRU replacement procedure.


The serial eeprom on the Battery Module will contain the following information:

1. Battery Type
2. Manufacture Date
3. In-service date
4. Checksum values

During the manufacturing process, an in-circuit tester reads the barcode from the battery and stores this value, known as the manufacturing date, into the Battery Modules serial eeprom. The Battery Type is also programmed into the serial eeprom during manufacturing.

The end use date, also known as the in-service date, is the date the battery is put into service. During in-circuit testing, the in-service date will be set to zero and stored in the Battery Modules serial eeprom.

The in-circuit tester also generates a checksum which also gets stored in the serial eeprom. This value is used to validate the stored data by the sscs software.

When a Battery Board is installed as part of a Controller FRU,if you do not reset and verify the in-service date, Sun StorEdge Configuration Service and the Sun StorEdge CLI cannot accurately calculate the battery expiration date.

If you run the show battery-status command and the battery in-service date is not set, run the "sccli> show battery-status -u" command. The "sccli>show battery-status -u" command sets the in-service date to the battery board manufacturing date and prompts the user to verify the date. The sscs software will establish the new in-service date and store this value into the serial eeprom based on the current system time.

It is only possible to set the in-service date once. The user is prompted to ensure that the system date and time are correct before proceeding to set the in-service date. The warning is very clear as there is no way to clear or reset this value.

Follow latest Sun StorEdge 3000 Family FRU Installation Guide 816-7326-xx for Battery replacement procedures.

The sscs software upon startup, and during periodic polling, and the sccli when explicitly invoked will check the battery information by issuing a scsi read buffer command to the SES firmware to obtain the battery type. The SES firmware will verify the checksum information in the serial eeprom. If incorrect/invalid checksum (as with older Battery Modules) a zero battery type will be returned to the software, and a
message indicating the following will be displayed:

sccli> show battery-status
Upper Battery : battery board type not supported for expiration monitoring

If a correct checksum is calculated, a battery type is returned in the range of 1 to 255. The sscs software will recognize the battery type, and calculate/display the expiration date:

sccli> show battery-status
Lower Battery Manufacturing Date: Thu Jan 1 01:00:00 2004
Lower Battery Placed In Service: Mon Feb 2 01:00:00 2004
Lower Battery Expiration Date: Wed Feb 1 01:00:00 2006
Lower Battery Status: good

The sscs software uses a battery expiration algorithm to calculate the expiration date from the following values:

1. The battery manufacture date (MfgDate).
2. The in-service date (InServiceDate).
3. The battery shelf life is calculated to be three years by the battery manufacturer (ShelfLife).
4. BatteryExpirationDate (calculated battery expiration value).

The following algorithm is used to calculate battery expiration by the sccli or sscs software:

Total life of battery is three years from the date of Manufacturing.

/* If on-shelf for less than one year */
If (InServiceDate - MfgDate) < 1 year.
BatteryExpirationDate = InServiceDate + 2years.
Else
/* Unused for more than one year.*/

 BatteryExpirationDate =  Will be three years from the MfgDate which will be less than two years from date of InServiceDate.

If the battery has been on the shelf for less than one year,the user will obtain a full two years of life from the battery. If the battery has been on the shelf for more than one year, then expiration date is three years from the Manufacturing date which is less than two years from the date the battery was placed in service.

For older versions of the battery module that don't support this monitoring feature, the following message appears:

sccli> show battery-status
Upper Battery : battery board type not supported for expiration
monitoring
Lower Battery : battery board type not supported for expiration
monitoring

In Diagnostic Reporter, you might see the following trap generated:

 A Trap was received from the 3510 the trap was [SUNWscsd
0x03080409:0x03000000 Informational] \<\>\
Battery Expiration Monitoring of \(Ch:2,Id:12\) is not available.

Use the "sccli> show frus" command in the Command Line Interface to determine the revision of the battery module:

 sccli> show frus
...
Name: BATTERY_BOARD
Description: SE3510 Hot Swap Battery Module
Part Number: 370-5545
Serial Number: 001955
Revision: 01
Manufacturing Date: Wed Mar 19 08:40:05 2003
Manufacturing Location: Milpitas,CA,USA
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER BATTRY BOARD SLOT
Chassis Serial Number: 001D2B

In the preceding example, the battery module is at Revision 01, and was manufactured over a year before the April 5, 2004 shipment that included the battery monitoring feature.




Change History
Date: 2010-06-30
User Name: susan.copeland@oracle.com
Action: Currency & Update

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback