StorEdge Batteries

Checking battery status

Example Error messages:

2009-06-08 10:10:14 - adm_messages on host-db01 CRITICAL - (0) Jun 8 10:08:35 host-db01 SUNWscsdServer[1245]: [ID 217491 daemon.error] [SUNWscsd 0x02060409:0x03010000 Warning] rctrl4000 The battery on (Ch:2,Id:28) is going to expire on Sun Jun 21 21:05:57 2009 (after 13 days). Please install a new battery before the current battery expires. Battery Information is (0x01, 0x46450380, 0x467B90F5, 0x4A3EA0B5). {Unique ID#: 0b1f73}

Logon to the server with the attached storage and start the Sun StorEdge CLI (sccli)

Check the battery status:

sccli> show battery-status
 
Upper Battery Type: 1
Upper Battery Manufacturing Date: Sat May 12 00:00:00 2007 Upper Battery Placed In Service: Fri Jun 22 09:05:57 2007
Upper Battery Expiration Date: Sun Jun 21 21:05:57 2009
Upper Battery Expiration Status: Warning


Lower Battery Type: 1
Lower Battery Manufacturing Date: Sat May 12 00:00:00 2007 Lower Battery Placed In Service: Fri Jun 22 09:05:57 2007
Lower Battery Expiration Date: Sun Jun 21 21:05:57 2009
Lower Battery Expiration Status: Warning

_________________________________

After replacing the battery's (sun will do this under contract)

sccli> show battery-status
sccli: Upper Battery: error: in service date not set in the battery
sccli: Lower Battery: error: in service date not set in the battery


---------------------------------------------------------------

Set the new in service date

If you run the show battery-status command and the battery in-service date is not set, run the show battery-status -u command. Early model battery boards were not programmed with an in-service date. The show battery-status -u command sets the in-service date to the battery board manufacturing date and prompts the user to verify the date.

sccli> show battery-status -u
The date 2009/ 6/ 8 will be stored as the In-Service Date of Upper Battery.
Are you sure that this date is correct? y
Upper Battery Type: 1
Upper Battery Manufacturing Date: Mon Mar 16 00:00:00 2009
Upper Battery Placed In Service: Mon Jun 8 10:17:47 2009
Upper Battery Expiration Date: Wed Jun 8 22:17:47 2011
Upper Battery Expiration Status: OK


The date 2009/ 6/ 8 will be stored as the In-Service Date of Lower Battery.
Are you sure that this date is correct? y
Lower Battery Type: 1
Lower Battery Manufacturing Date: Mon Mar 16 00:00:00 2009
Lower Battery Placed In Service: Mon Jun 8 10:17:54 2009
Lower Battery Expiration Date: Wed Jun 8 22:17:54 2011
Lower Battery Expiration Status: OK

---------------------------------------------------------------
Upper Battery Hardware Status: Charging
Lower Battery Hardware Status: Charging

Check the new status

sccli> show battery-status
Upper Battery Type: 1
Upper Battery Manufacturing Date: Mon Mar 16 00:00:00 2009
Upper Battery Placed In Service: Mon Jun 8 10:17:47 2009
Upper Battery Expiration Date: Wed Jun 8 22:17:47 2011
Upper Battery Expiration Status: OK


Lower Battery Type: 1
Lower Battery Manufacturing Date: Mon Mar 16 00:00:00 2009
Lower Battery Placed In Service: Mon Jun 8 10:17:54 2009
Lower Battery Expiration Date: Wed Jun 8 22:17:54 2011
Lower Battery Expiration Status: OK



---------------------------------------------------------------

Upper Battery Hardware Status: Charging
Lower Battery Hardware Status: Charging

Stuck Alarms

Sometimes the alerts will get stuck, and keep alerting to messages that the battery is expiring, a quick restart of the SSagent should fix this.

# /etc/rc2.d/S81ssagent stop
# /etc/rc2.d/S81ssagent start

Some note copied from sunsolve

Alarms:

 [SUNWscsdMonitor][1227]: [SUNWscsd 0x030B1D0E:0x00000000 Informational] <rctrl3044> Standard Geneal Event, NOTICE: Controller BBU Fully Charged !.[info: 16-0054A6789] Unique ID#: 0b1086

{color:#4682b4}{*}Solution  211247{*}{color}*:   Troubleshooting Sun [StorEdge][TM] 33x0/351x Battery Problems  * | {color:white}Related Categories{color} | | Home>Product>Storage>Storage Management Software | {color:#4682b4}{*}Description{*}{color} The steps below will help verify and resolve battery problems. NOTE:  This is a sub-set of  < Solution: 215672 >  : "Troubleshooting Sun [StorEdge][TM]  33x0/351x Hardware".

• Symptoms:*

-Failed or absent battery

-Not fully charged battery

-Expired or expiring battery

-BBU Failures

-Battery not charging or Bad {color:#4682b4}{*}Steps to Follow{*}{color} Troubleshooting Battery Problems

1. Verify the battery hardware status  is OK  by either using the *sccli> show battery*-*status  *command and *show peripheral-device-status,* or follow the steps in "Battery Status on the Initial Firmware Screen" in the "Sun [StorEdge] 3000 Family FRU Installation Guide".

• Example for 3510:*

sccli>show battery-status

sccli: selected device /dev/es/ses22 [SUN StorEdge 3511 SN#006975] Upper Battery Type: 1 Upper Battery Manufacturing Date: Thu Mar 31 00:00:00 2005 Upper Battery Placed In Service: Thu Jul 14 08:08:42 2005 Upper Battery Expiration Date: Sat Jul 14 08:08:42 2007 Upper Battery Expiration Status: OK

Lower Battery Type: 1 Lower Battery Manufacturing Date: Wed Jun 16 00:00:00 2004 Lower Battery Placed In Service: Tue Jun 21 16:35:39 2005

Lower Battery Expiration Date: Sat Jun 16 06:00:00 2007 Lower Battery Expiration Status: OK

---

Upper Battery Hardware Status: OK Lower Battery Hardware Status: OK

Example for 3310: sccli> show peripheral device-status

Item Value status

---

CPU Temp Sensor(primary) 96.00C over upper threshold Board1 Temp Sensor(primary) 77.50C within safety range

Board2 Temp Sensor(primary) 67.00C within safety range +3.3V Value(primary) 3.336V within safety range +5V Value(primary) 5.153V within safety range +12V Value(primary) 12.320V within safety range Battery-Backup Battery(primary) - Bad

CPU Temp Sensor(secondary) 84.00C within safety range Board1 Temp Sensor(secondary) 78.50C within safety range Board2 Temp Sensor(secondary) 70.00C within safety range +3.3V Value(secondary) 3.336V within safety range +5V Value(secondary) 5.153V within safety range +12V Value(secondary) 12.260V within safety range Battery-Backup Battery(secondary) - Bad

1. .Verify the battery LED status is green (fully charged) or blinking green (indicates charging).

• Note* - 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 Sun service personnel for additional instructions.

1. Verify the battery FRU status is OK by issuing the *sccli> show fru{*}command and examining the output for the battery module.

• Example for 3510:*

sccli>show fru

Name: BATTERY_BOARD Description: BATTERY 2U, FC/SATA Part Number: 370-6799 Serial Number: GJ02OB Revision: 01 Initial Hardware Dash Level: 01 FRU Shortname: FC/SATA Bat Manufacturing Date: Wed Apr 27 21:35:53 2005 Manufacturing Location: Milpitas,CA,USA Manufacturer JEDEC ID: 0x0301 FRU Location: UPPER BATTERY BOARD SLOT Chassis Serial Number: 00660F FRU Status: OK

sccli>show battery-status

Name: BATTERY_BOARD Description: SE3510 Hot Swap Battery Module Part Number: 370-5545 Serial Number: 008776 Revision: 01 Initial Hardware Dash Level: 01 FRU Shortname: 370-5545-01 Manufacturing Date: Fri Oct 3 23:08:57 2003 Manufacturing Location: Milpitas,CA,USA Manufacturer JEDEC ID: 0x0301 FRU Location: UPPER BATTERY BOARD SLOT Chassis Serial Number: 004B6D

FRU Status: Expired

1. Verify normal frequency and completion of battery charging  in the eventlog or persistent eventlog by issuing the *sccli> show events* or{*}sccli>show persistent*-*event* command.

• Example for 3510:*

sccli> show events

Tue Sep 5 08:54:15 2006 [Primary] Notification Controller BBU is Charging ! Tue Sep 5 08:54:19 2006 [Primary] Notification NOTICE: Controller BBU Fully Charged ! Tue Sep 5 08:55:08 2006

[Secondary] Notification NOTICE: Controller BBU Fully Charged ! -For irregular battery charging events, refer to  < Solution: 213453 >  : "Sun [StorEdge] [TM] 351x Array: Irregular Battery Charging Cycles".

-For battery not fully charged events, refer to  < Solution: 203139 >  : "Sun [StorEdge][TM] 3000 Arrays: Battery 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 battery failures shortly after upgrading to 4.11 on SE351x, review CR: 6286138 "Primary & secondary RAID controller batteries fault after 4.11 upgrade".

1.  Verify battery expiration status:

-For 33x0, refer to < Solution: 214983 > : "Sun [StorEdge][TM] Battery Life Cycle".

-For 351x,  verify battery has not expired and that  battery status is *OK* by issuing the{*}sccli>show battery-status* command. Refer to < Solution: 212505 > : "Sun [StorEdge][TM] 351x  Array: Battery Expiration and Status Monitoring" for more details.

-For battery expiring events immediately after replacement on the 351x, refer to: "Refreshing the Battery Status With Sun [StorEdge] Configuration Service" in the  Sun [StorEdge] 3000 Family FRU Installation Guide.

• Example for 3510:*

sccli> show battery-status

Upper Battery Type: 1 Upper Battery Manufacturing Date: Fri Oct 17 15:59:08 2003 Upper Battery Placed In Service: Fri Oct 17 15:59:08 2003 Upper Battery Expiration Date: Sun Oct 16 15:59:08 2005 Upper Battery Status: OK

Lower Battery Type: 1 Lower Battery Manufacturing Date: Fri Oct 17 19:29:20 2003 Lower Battery Placed In Service: Fri Oct 17 19:29:20 2003 Lower Battery Expiration Date: Sun Oct 6 19:29:20 2004 Lower Battery Status: Expired

1.  Ensure there are no false battery failure messages. Refer to < Solution: 208997 >  "Mute Button on Sun [StorEdge][TM] 351x Array held in during reset of array will cause false messages".
2. Ensure 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][TM] 3000 Family FRU Installation Guide for details.
3.  *Replace battery for the following conditions:*

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

-For 351x, Battery status is Expired or Warning (will expire within 21 days)

-For 33x0, 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 details on battery replacement refer to: "Replacing a Battery or Battery Module" in the Sun [StorEdge] 3000 Family FRU Installation Guide for replacement instructions. Additionally, refer to < Solution: 203394 > : "Battery Replacement Procedure for a Sun [StorEdge][TM] 351x/33x0" and < Solution: 203047 > : "Battery Replacement Procedure for a Sun [StorEdge][TM] 33x0".

1.  For 351x,  after battery replacement:

-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

-Rescan the battery in the Sun [StorEdge] Configuration Service: "Refreshing the Battery Status With Sun [StorEdge] Configuration Service" in the  Sun [StorEdge] 3000 Family FRU Installation Guide.

1. If battery problems persist after replacement or additional hardware components are faulted or missing refer to the Technical Instruction < Solution: 215672 > : "Troubleshooting Sun [StorEdge][TM]  33x0/351x Hardware".

{color:#4682b4}{*}Product{*}{color} Sun [StorageTek] 3511 SATA Array Sun [StorageTek] 3510 FC Array Sun [StorageTek] 3510 2U FC Array Sun [StorageTek] 3320 SCSI Array Sun [StorageTek] 3310 SCSI Array

{color:#4682b4}{*}Keywords{*}{color} 3310, normalized, 3510, 3320, 3511, battery, 351x, 33x0, BBU, thermal shutdown

{color:#4682b4}{*}Previously Published As{*}{color} 89046