Sun Storage 3511 SATA Array
 
Sun Storage 3510 FC Array
 
Sun Storage 3310 Array
 
Sun Storage 3320 SCSI Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
 

Troubleshooting Battery Problems.

In this Document

Purpose

Troubleshooting Steps

References

Applies to:

Purpose

This document presents steps to troubleshoot battery problems for the following arrays:

• Sun Storage 3310 Array
• Sun Storage 3320 Array
• Sun Storage 3510 Array
• Sun Storage 3511 Array

Symptoms may include:

• Failed or absent battery
• Not fully charged battery
• Expired or expiring battery
• BBU Failures
• Battery not charging or Bad

Troubleshooting Steps

Step 1: Verify the battery hardware status is OK by any of the following methods.

Use sccli > show battery-status:

Use sccli > show peripheral-device-status:

Use the firmware menu. Follow the steps in "Battery Status on the Initial Firmware Screen" in the Sun StorEdge 3000 Family FRU Installation Guide.

Step 2: Verify the battery LED is solid green (fully charged) or blinking green (charging).

The location of the battery LEDs is shown in the Systems LED Descriptions portion of the Sun System Handbook.

The batteries in controller FRUs experience discharge during shipment and might require an extended charging cycle upon initial power-up. Nominal battery operation is achieved when the battery status LED changes from amber to flashing green within 25 minutes after the initial power cycle. If the battery status LED remains amber for more than 25 minutes after the initial power-up, then the unit must be power cycled to initiate the extended charging cycle. If the battery status LED remains amber for more than 30 minutes after initiating the extended charging cycle, contact Oracle Support for additional assistance.

Step 3: Verify the battery FRU status is OK.

Issue the sccli> show frus command and examine the portion of the output for the battery module.

Step 4: Verify normal frequency and completion of battery charging.

Examine the eventlog or persistent eventlog by issuing the sccli> show events or sccli>show persistent-events command.

• For irregular battery charging events, refer to <Document 1009803.1> Sun Storage 3510 and 3511 Arrays: Irregular Battery Charging Cycles.

• For battery not fully charged events, refer to <Document 1002220.1> Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged".

• For BBU thermal shutdown messages, review the "Battery Operation" section in the Sun StorEdge 3000 Family FRU Installation Guide and ensure temperatures are within normal range.

• For the Sun Storage 3510 and 3511 arrays, battery failures shortly after upgrading to 4.1x from 3.2x may be caused by a bug which was addressed in Patch 113723-14. It is recommended that arrays experiencing this problem be updated to the most current <Patch 113723-21>.

Step 5: Verify battery expiration status.

Batteries for the Sun Storage 3000 arrays expire in 1 year if battery temperature is above 35 degrees Celsius and in 2 years if the temperature is at or below 25 degrees Celsius.

For additional informtion for the Sun Storage 3510 and 3511 arrays, refer to <Document 1009069.1> Sun StorEdge SE351x Array: Battery Expiration and Status Monitoring.

For battery expiring events immediately after replacement on Sun Storage 3510 and 3511 arrays, refer to "Refreshing the Battery Status With Sun StorEdge Configuration Service" in the  Sun StorEdge 3000 Family FRU Installation Guide.

Step 6: Ensure there are no false battery failure messages.

Refer to <Document 1006414.1> Sun StorEdge 351x/33x0 Arrays: Mute Button Held During Reset of Array Will Cause False Battery Failure Messages.

Step 7: Check for a controller over-temperature condition.

Ensure that a controller over-temperature condition is not causing battery charging to shutoff and battery status to be reported as BAD. Use the sccli> show peripheral device-status command to verify the temperature sensor values are within safety range. Refer to "Section 4.1: Battery Operations" in the Sun StorEdge 3000 Family FRU Installation Guide for details.

Step 8: Replace the battery for the following conditions:

• Battery hardware status is BAD or Missing and there are no other hardware components reporting the same status.

• For Sun Storage 3510 and 3511 arrays, battery status is Expired or Warning (will expire within 21 days).

• For Sun Storage 3310 and 3320 arrays, battery lifecycle is expired.

• Battery LED is solid amber (after battery module reseat has failed,) indicating battery is bad or missing.

• Battery charge cycle events occur too frequently.

• Battery fully charged message is absent in the eventlogs.

For replacement instructions, refer to "Replacing a Battery or Battery Module" in the Sun StorEdge 3000 Family FRU Installation Guide.

Additionally, refer to <Document 1002426.1> Battery Replacement Procedure for Sun StorEdge 3310SCSI/3510FC/3511FC Arrays.

Step 9: For Sun Storage 3510 and 3511 arrays, ensure the in-service date is set.

1. Set the in-service date by following the steps in "FC Battery Status and In-Service Date Procedures" in the  Sun StorEdge 3000 Family FRU Installation Guide.
   
   
2. Rescan the battery in the Sun StorEdge Configuration Service. Refer to "Refreshing the Battery Status With Sun StorEdge Configuration Service" in the Sun StorEdge 3000 Family FRU Installation Guide.

Step 10: If battery problems persist after replacement, or if additional hardware components are faulted or missing, refer to <Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series Hardware.

Product Documentation

The full set of documentation for the Sun Storage 3000 Arrays is located on the Oracle Disk Storage Systems Documentation page.

Documentation is available in HTML or PDF. For the Sun StorEdge 3000 Family FRU Installation Guide in particular, you may find it useful to download the PDF version.
 

References

This solution has no attachment