Asset ID:	1-73-1171913.1
Update Date:	2011-04-20
Keywords:

---

Solution Type  FAB (standard) Sure

Solution  1171913.1 :   Battery Expiration is no longer cause for replacement on Storage 6x80 and 25x0 Arrays.  

In this Document
  Symptoms
  Cause
  Solution

---

Oracle Confidential (PARTNER). Do not distribute to customers
Reason: FABs available to Internals and Partners only

Applies to:

Sun Storage 6580 Array - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Sun Storage 6780 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 6180 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 2510 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 2530 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Information in this document applies to any platform.
This issue also affects the 2540 Array.
__________

Affected Parts: (FRU/CRU Part Number / Description)

371-4676 - Battery Pack, Sun Storage 6180
371-4374 - Battery Backup Module, Sun Storage 6580/6780
371-2482 - 2.5V 6.5Ah 400mA Li-Ion Battery Module, Sun StorageTek 2510/2530/2540

Symptoms

Subsystems may report the following critical faults, which indicate failure due to the battery timer:

Reference

CAM based faults(alarms)

    xx.66.1039   Battery Nearing Expiration
    xx.66.1005   Controller Cache Backup Battery Nearing Expiration
    xx.66.1254   Battery has Expired
    xx.66.1255   Battery has Expired

SANtricity based faults(in recovery guru)

    REC_NON_FRU_BATTERY_NEAR_EXPIRATION = 39
    REC_BATTERY_NEAR_EXPIRATION = 5
    REC_EXPIRED_BATTERY = 254
    REC_EXPIRED_INTEGRATED_BATTERY = 255

Any 2510, 2530, or 2540 subsystem that receives the following fault will require further investigation, as the SMART technology is not in use until the firmware is at 7.35.xx.xx or later:

    REC_FAILED_BATTERY = 6

Impact

Customers using the the above mentioned arrays will no longer receive replacement batteries that have been determined by the subsystem as failed or about to fail due to the battery age timer. The customer will receive instructions on how to reset the timer if it is still active on the affected system.

Cause

Root Cause

The affected arrays use SMART Battery Backup Units(BBU). The SMART BBU will monitor its current charge level, and if this cannot be maintained through a charge cycle, write caching will be disabled. The smart BBU will also monitor its Full Charge Capacity, which is expected to decrease over the life of the battery. Once this Full Charge Capacity falls below the Replacement Capacity threshold (which should be a value greater than the Minimum Application Capacity), the battery is nearing the end of its useful life and should be replaced. At this point, Battery Replacement Required event notification occurs, which is signified by the following Critical Fault:

    CAM:  xx.66.1176 Battery {0} has a full charge capacity below the replacement capacity threshold

    SANtricity:  BATTERY REPLACEMENT REQUIRED = 176

Write Caching will NOT be disabled at this point. If the battery is not replaced, at some point the Full Charge Capacity will fall below the Minimum Application Capacity, at which point caching will be disabled and an informational event will be logged in the major event log with the following critical fault:

    CAM: xx.66.1006  A battery has failed
    xx.66.1040  A controller cache backup battery has failed

    SANtricity:
    REC_FAILED_BATTERY = 6, REC_NON_FRU_FAILED_BATTERY = 40

 

Solution

Workaround


Identify the critical faults:


After identifying the critical fault, apply the appropriate workaround as shown below:

1. If the Critical Fault listed is as follows, then reset the battery age:

CAM:

    xx.66.1039    Battery Nearing Expiration
    xx.66.1005    Controller Cache Backup Battery Nearing Expiration

SANtricity:

    REC_NON_FRU_BATTERY_NEAR_EXPIRATION = 39, REC_BATTERY_NEAR_EXPIRATION = 5   

2. If the Critical fault listed is as follows, physically reseat the battery and reset its age:

CAM:

    xx.66.1254  -  Battery has Expired
    xx.66.1255     Battery has Expired

SANtricity:

    REC_EXPIRED_BATTERY = 254, REC_EXPIRED_INTEGRATED_BATTERY = 255

3. If the array is a 2500 with firmware 06.17 or 06.70, and the Critical Fault listed is:

     xx.66.1006    A battery has failed or REC_FAILED_BATTERY = 6
     xx.66.1040    A battery has failed or REC_NON_FRU_FAILED_BATTERY = 4

To check the battery age:

    # sscs list -d myarray -t Battery fru Tray.85.Battery.A

    Element Name        : Tray.85.Battery.A
    Element Status      : Optimal
    Enabled State       : Enabled
    FRU Number          : 1T71200441PS
    FRU Type            : Battery
    Firmware            : N/A
    Id                  : SUN.371-2482-01.1T71200441PS
    IdentifyingNumber   : 1T71200441PS
    *Life Remaining      : 288 Days*
    ManufactureDate     : Wed Feb 28 19:00:00 EST 2007
    Model               : 371-2482-01

If the battery life remaining is zero(0), physically reseat the battery and reset its age. If the life remaining is greater than zero(0), then the battery should be replaced.

4. If the array is a 6x80 or a 2500 with firmware 7.35.10.10 or later, and the Critical fault listed is as follows, the battery should be replaced:

CAM:

    xx.66.1006    A battery has failed
    xx.66.1040    A controller cache backup battery has failed
    xx.66.1176    Battery {0} has a full charge capacity below the replacement capacity threshold

SANtricity:

    REC_FAILED_BATTERY = 6, REC_NON_FRU_FAILED_BATTERY = 40
    BATTERY REPLACEMENT REQUIRED = 176

Resolution

Oracle will be changing the 6000 series NVSRAM in a future release so that the expiration bit, contributing to this issue, will be disabled.

Please supply the following document to customers inquiring on SMART batteries:
     Doc ID 1207186.1: SMART Battery Functionality in 2500 and 6000 Arrays,

and have them review the following document on how we are determining whether a battery is faulty or not:
     Doc ID 1021054.1: Troubleshooting Storage Array Battery Faults.

If a customer wants a replacement battery that has expired but not failed, they can purchase one through sales.

References

For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

* http://tns.central/fab

In addition to the above you may email:

* FAB-Manager_US@oracle.com


Contacts

Contributor: curtis.decotis@oracle.com
Responsible Engineer: terrance.knabe@oracle.com
Responsible Manager: brian.hanvey@oracle.com
Business Unit Group: NWS (Network Storage)

Attachments

This solution has no attachment