Troubleshooting Sun Storage[TM] Array non-SMART Battery Faults

Asset ID:	1-75-1392919.1
Update Date:	2012-02-27
Keywords:

Solution Type Troubleshooting Sure

Solution 1392919.1 : Troubleshooting Sun Storage[TM] Array non-SMART Battery Faults

Applies to:

Sun Storage 6130 Array - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Sun Storage 6540 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage 6140 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage Flexline 280 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Sun Storage Flexline 210 Array - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Information in this document applies to any platform.

Purpose

The purpose of this document is to help users identify common problems with batteries in the Sun Storage Flexline 210, 240, 280, 380, StorageTek 6130, StorageTek 6140 or StorageTek 6540 arrays. These batteries provide power to the controller's data cache in the event of a power outage. If you have a StorageTek 2500, Sun Storage 2500-M2, 6x80 array, please refer to <Document 1021054.1> Troubleshooting Sun Storage[TM] Array SMART Battery Faults.

Symptoms Include

The following table contains the most common faults seen by Common Array Manager (CAM) or SANtricity:

Grid ID
CAM Critical Fault
SANtricity Critical Fault
xx.66.1005
Battery Near Expiration
BATTERY_NEAR_EXPIRATION
xx.66.1006
Critical Fault for a Cache Backup Battery has Failed
FAILED_BATTERY
xx.66.1039
Controller Cache Battery Near Expiration
NON_FRU_BATTERY_NEAR_EXPIRATION INTEGRATED_BATTERY_NEAR_EXPIRATION
xx.66.1040
A Controller Cache Backup Battery has Failed
NON_FRU_FAILED_BATTERY or FAILED_INTEGRATED_BATTERY
xx.66.1091
Battery Tray.xx.Battery.xx has transitioned to an Unknown State
BATTERY_UNKNOWN_STATE
xx.66.1101
There has been a failure in the ICC Battery pack
FAILED_BATTERY_SYSTEM
xx.66.1254
Critical Fault for Battery has expired
EXPIRED_BATTERY
xx.66.1255
Critical Fault for Battery has expired
EXPIRED_INTEGRATED_BATTERY

Other possible conditions include:

You just replaced the battery, but it still shows failed.
Amber LED lit on battery.
Amber LED lit on array.

Batteries are monitored by two methods, an Expiration Timer and SMART (Self-Monitoring, Analysis and Reporting Technology) battery technology. Within the scope of this document only the Expiration Timer is used.

The Expiration Timer is a simple counter whereas the newer SMART battery technology internally tests the ability of the batteries to hold a charge. Both are used to determine battery replacement but the Expiration Timer is also susceptible to outside conditions which can lead to reports of premature failures.

Last Review Date

January 10, 2012

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Verify the Array Type, Firmware Version and Fault.

Since the steps to resolve battery issues will differ based on the Hardware and Firmware involved, it is necessary to gather this information in order to determine the proper troubleshooting steps.

To determine the Array type, see <Document 1021066.1> Verify Sun Storage [TM] Array Array type via the User Interface.
To determine the Firmware version, see <Document 1021067.1> Verify Storage[TM] Array Firmware via the user Interface.
To determine the faults, see <Document 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] Critical Faults via the User Interface.

If there are no faults, go to step 5.

The following table lists the most common faults associated with batteries. If you have an array with redundant batteries and both batteries have a fault, each fault should be evaluated on it's own. Sometimes a single remedy will fix multiple faults. If you have a single battery with multiple faults, go to step 6, contact Oracle support.

Critical Fault	Array Type	Firmware Version	Remedy
Battery Near Expiration	6130/FLXxx0/6x40	Any	Go to step 2.
Battery Expired	6130/FLXxx0/6x40	Any	Go to step 2.
Over Temperature	6130/FLXxx0/6x40	Any	Go to step 6.
Replacement Required	6130/FLXxx0/6x40	Any	Go to step 6.
Battery Failed	6130/FLXxx0/6x40	Any	Go to step 2.
Unknown	6130/FLXxx0/6x40	Any	Go to step 6.

Confirm Array System Time is correct.

Batteries that have the Expiration Timer active are subject to premature failures if the array system time gets improperly set. Typically this is the result of a rogue NTP server. Use <Document 1021108.1> Verifying and Setting Sun Storage[TM] Array System Time, to verify the array system time. If the system time is incorrect, search the majorEventLog.txt file (from supportdata bundle) to see if a rogue NTP server is the cause.

Example: # grep NTP majorEventLog.txt Description: Controller clocks set via NTP or SNTP Description: Controller clocks set via NTP or SNTP #

If you find any instances of the above, you can reset the array system time but the problem is likely to return unless the rogue NTP server is addressed. Isolating the array(s) and management host on their own private network is the best way to avoid a rogue NTP server. Reset the array system time and wait 5 minutes.
- If the critical fault clears, no further action is needed.
- If the critical fault remains and you recently replaced the battery, go to step 3.
- If the critical fault remains, the array system time is correct and the battery has not been recently replaced, it is likely time to replace the battery. Go to step 6.
Reset the Battery Age.

Go to <Document 1021695.1> Resetting the Battery Age for a StorageTek[TM] 2500 and Sun Storage[TM] 6000 Array. If after resetting the battery age the problem is still unresolved, it may be necessary to reseat the battery to clear the failed state. Proceed to step 4.
Reseating the Battery.

The 6x40 and FLXx80 arrays have batteries that are externally accessible and this can be done without any impact to data access. Flexline 210, 240 and 6130 arrays will require a controller reboot which means a temporary loss of a data path. Users may want to schedule an outage for this but it is not a requirement.

To reseat the battery follow the service steps for battery replacement to remove and reinsert the battery.
- For CAM users see Service Advisor
- For SANtricity users see Recovery Guru
If you have to reboot the controller
- For CAM users select the array from the Storage System Summary page, then expand the Physical Devices and select Controllers in the Navigation Tree. Scroll down to the proper controller and select Reset Controller. Confirm to execute the reboot.
- For SANtricity users select the Logical/Physical View tab in the Array Management Window and highlight/select the controller in the Physical window. From the menu bar, select Advanced then Recovery, then Reset and finally Controller. Confirm to execute the reboot.
If the problem still is not resolved, go to step 6.
Battery in an Unknown State.

Go to <Document 1283914.1> Troubleshooting Sun Storage[TM] Array Unknown Battery Status for further troubleshooting.
Contact Oracle Support.

Collect a supportdata:
- For CAM users, reference <Document 1002514.1> Collection Support Data for Arrays Using Sun StorageTek[TM] Common Array Manager.
- For SANtricity users, reference <Document 1014074.1> Collecting Support Data for Arrays Using Sun StorageTek[TM] SANtricity Storage Manager.
Log a Service Request

Attachments

This solution has no attachment