Asset ID: |
1-71-1207186.1 |
Update Date: | 2012-04-17 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1207186.1
:
SMART Battery Functionality in Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 Arrays
Related Items |
- Sun Storage 6580 Array
- Sun Storage 2540 Array
- Sun Storage 2540-M2 Array
- Sun Storage 2510 Array
- Sun Storage 6180 Array
- Sun Storage 6780 Array
- Sun Storage 2530-M2 Array
- Sun Storage 2530 Array
|
Related Categories |
- PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
|
In this Document
Applies to:
Sun Storage 2510 Array - Version Not Applicable and later
Sun Storage 6180 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 2540 Array - Version Not Applicable and later
Sun Storage 2530-M2 Array - Version Not Applicable and later
Information in this document applies to any platform.
Goal
This document is intended to explain how SMART Batteries function in the Oracle Storage Arrays that have them.
Fix
This 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. 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. Arrays with 7.77.13.11 or later firmware have the expiration timer disabled.
For 25x0 arrays running at least 7.35 firmware it is possible to edit the NVSRAM to negate the Expiration Timer. This edit will be permanent unless the array's NVSRAM is reloaded or upgraded. The procedure is below:
/* `service` is under:
/* Solaris: /opt/SUNWsefms/bin/
/* Linux: /opt/sun/cam/private/fms/bin/
/* Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin\
# service -d <arrayname> -c read -q nvsram region=0xEE
# service -d <arrayname> -c set -q nvsram region=0xEE offset=0x2D value=0xFF
# service -d <arrayname> -c set -q nvsram region=0xEE offset=0x2E value=0xFF
# service -d <arrayname> -c read -q nvsram region=0xEE
Example:
# service -d myarray -c read -q nvsram region=0xEE
Executing the read command on myarray
Controller A Region Id = (238) REGION_USER_CONFIG_DATA
0000: 0000 c220 0000 0000 0050 0600 0000 0000 ... .....P......
0010: 0000 0000 0000 0000 f001 0000 8080 0000 ................
0020: 0000 0000 0000 0000 8c86 008a 0000 0000 ................
0030: 80be 9f41 1300 2000 0f00 1400 0000 0000 ...A.. .........
Controller B Region Id = (238) REGION_USER_CONFIG_DATA
0000: 0000 c220 0000 0000 0050 0600 0000 0000 ... .....P......
0010: 0000 0000 0000 0000 f001 0000 8080 0000 ................
0020: 0000 0000 0000 0000 8c86 008a 0000 0000 ................
0030: 80be 9f41 1300 2000 0f00 1400 0000 0000 ...A.. .........
Completion Status: Success
#
# service -d myarray -c set -q nvsram region=0xEE offset=0x2D value=0xFF
Executing the set command on myarray
Completion Status: Success
#
# service -d myarray -c set -q nvsram region=0xEE offset=0x2E value=0xFF
Executing the set command on myarray
Completion Status: Success
#
# service -d myarray -c read -q nvsram region=0xEE
Executing the read command on myarray
Controller A Region Id = (238) REGION_USER_CONFIG_DATA
0000: 0000 c220 0000 0000 0050 0600 0000 0000 ... .....P......
0010: 0000 0000 0000 0000 f001 0000 8080 0000 ................
0020: 0000 0000 0000 0000 8c86 008a 00ff ff00 ................
0030: 80be 9f41 1300 2000 0f00 1400 0000 0000 ...A.. .........
Controller B Region Id = (238) REGION_USER_CONFIG_DATA
0000: 0000 c220 0000 0000 0050 0600 0000 0000 ... .....P......
0010: 0000 0000 0000 0000 f001 0000 8080 0000 ................
0020: 0000 0000 0000 0000 8c86 008a 00ff ff00 ................
0030: 80be 9f41 1300 2000 0f00 1400 0000 0000 ...A.. .........
Completion Status: Success
#
SMART or 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 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 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.
This learn cycle will disable write caching on 2500 arrays, however the learn cycle will not affect the 6180, 6580, or 6780 array. For 2500-M2 arrays, write caching will only be disabled if the battery capacity falls below the minimum application capacity level.
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.
This system of using the SMART technology to monitor the batteries, replaces the expiration timer that was seen in previous products of this line. 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 isn't the result of the expiration timer.
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 .
Attachments
This solution has no attachment