Sun Storage 6580 Array
 
Sun Storage 2510 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage 6180 Array
 
Sun Storage 2540 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530 Array
 
Sun Storage 2530-M2 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
 

In this Document

Goal

Solution

References

Applies to:

Goal

This document is intended to explain how SMART Batteries function in the Oracle Storage Arrays that have them.

Solution

SMART (Self-Monitoring, Analysis, and Reporting Technology) was developed originally for disk drives to alert the owner to a predictive failure of a component.  It has also been applied to the battery backup units.

A SMART battery backup unit (BBU) contains battery cells, thermal cells, a charger, a battery gas gauge, a discharge load and control logic. With SMART battery, the controller must periodically perform learn cycles (in 7.x firmware revisions) to determine how much capacity is left in the battery. This information allows the controller firmware to determine exactly how long the BBU can hold the cache "up" and take action as needed.

The battery has two SMART flags that indicate that the battery requires replacement:

• Over Temperature - Indicates whether the battery temperature has reached a threshold
• Below Charge Capacity - Indicates that the battery cannot maintain a minimum level of charge

Periodically, the battery must calibrate the sensors on the battery during a learn cycle (see Appendix A below). The 2500 and 6000 products that have SMART batteries will only be replaced if they are faulted due to the above two flags being set, or if the firmware detects a fault that is not the result of the expiration timer. Hence this system of using the SMART technology to monitor the batteries replaces the expiration timer that was seen in previous products of this line. Arrays with 7.77.13.11 or later firmware have the expiration timer disabled. Batteries that have SMART technology in systems that still have the expiration timer active on them will NOT be replaced if the timer fails or expires the battery. For 2500 arrays, it is possible to edit the NVSRAM to negate the Expiration Timer(see Appendix B below).

For more information on troubleshooting battery faults, reference:
<Document: 1021054.1>  Troubleshooting Storage[TM] Array SMART Battery Faults.
<Document: 1392919.1> Troubleshooting Sun Storage[TM] Array non-SMART Battery Faults .

This SMART functionality is limited to the models 2510, 2530, 2540, 2530-M2, 2540-M2, 6180, 6580, and 6780 arrays.  All other models do not have SMART technology built into them, and require the use of an expiration timer to identify when the battery may need replacement. 

Appendix A : Cache mode during Learn cycle

For more information on the behavior of the cache and the learning cycle, reference  <Document: 1205345.1> Write back cache disabled during SMART battery learn cycles.

Appendix B: Procedure to edit the NVSRAM to negate the Expiration Timer in 2500 arrays

This edit will be permanent unless the array's NVSRAM is reloaded or upgraded. The procedure is below:

This solution has no attachment