Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1272612.1
Update Date:2017-07-28
Keywords:

Solution Type  Technical Instruction Sure

Solution  1272612.1 :   How to Remove and Replace a Sun Storage 3510/3511 FC Array Battery [VCAP]  


Related Items
  • Sun Storage 3510 FC Array
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
  •  
  • Microlearning>Video>ML-VID-VCAP
  •  
  • _KM>Content>Video
  •  




In this Document
Goal
Solution
References


Applies to:

Sun Storage 3510 FC Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

How to Remove and Replace a Sun Storage 3510/3511 FC Array Battery

Solution

PROBLEM OVERVIEW
Defective Battery

TIME ESTIMATE:  15 minutes

TASK COMPLEXITY: 0

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?

Write cache should be disabled prior to replacing battery to prevent data loss if power event occurs before replacement battery is charged

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE

Check for amber LED on battery, check CLI battery status and location (upper or lower slot). From SCCLI:

sccli> show battery


Prepare array for battery replacement

1. To determine status of write cache on array, access array Main Menu from telnet or via serial port access.

2. Select appropriate mode and press <enter>

3. Clear any pop-up messages with <CTL> + < C> Select Disable pop-ups
   On upper right of Main Menu, Cache Status is displayed. Value to right indicates percentage of controller cache that differs from what is saved to disk. 'Clean' means all cache has been saved to disk.

4. Ensure the Storage controller time/date and timezone are correct. Change if needed

       a) Via the Serial port, or via telnet access or sccli command line - Check the time/date on the top line of the Serial port access menu

       Either using the command line sccli from a host or via Serial port access

       From Main Menu: view and edit Configuration parameters  ->  Controller Parameters ->  Set Controller Date and Time
                  Select as needed  -> Time Zone  and/or  -> Date and Time

       b) Via sccli

                 sccli> show controller-date :

                      To change use the command "sccli set controller-date month day hh:mm:ss year time-zone"

                       For example: # sccli c2t0d0 set controller-date Sep 22 13:43:00 gmt -7

5. Disable Cache:

  From telnet Main Menu, Disable cache:
   a. Select View and edit Configuration parameters
   b. Select Caching Parameters . Note cache state (enabled or disabled).
   c. Select Write-Back Cache Enable ? > No
   d. Disable Write-back cache? >Yes

   OR

   From sccli, Disable Cache:
   e. sccli -o <ip>(out-of-band) or sccli /dev/dsk/c#t#d#s2(in-band)
   f. Check cache parameters. From sccli> show cache-parameters
   g. Disable cache. sccli> set cache-parameters write-through

6. Verify write-through cache status.

sccli> show cache-parameters


Note: Verify "cache" status led on Raid controller is off

7. Remove ethernet and serial cable from battery module

8. Unscrew and disengage thumbscrews and cables on battery module and use thumbscrews to pull out the battery module

9. Insert new battery module and tighten thumbscrews until finger tight

WARNING: Do not force or apply excessive pressure when inserting battery module


10. Re-attach cables

11. Using CLI (sccli), check battery status and set in service date

sccli> show battery-status
sccli> show battery-status -u
sccli> show battery-status


If second battery needs to be replaced, repeat steps 7-11

12. Confirm controller redundancy.

sccli > show redundancy


13. Restore write cache to original settings. To Enable Write-Back Cache
   a. Select View and edit Configuration parameters
   b. Select Caching Parameters
   c. Select Write-Back Cache Disabled
   d. Enable Write-Back Cache?--> YES

sccli> set cache-parameters write-back



Note: Write cache will enable once battery can protect on-board cache. Verify battery is charging by blinking green light on battery. Battery status LED may remain amber for up to 30 minutes.


14. Verify host access

15. Restart Configuration Services agent to prevent expired battery related messages from recurring. From host, type

 Note: This task has no impact on storage access from the host.

 

/etc/init.d/ssagent stop     # The command will advise when the service has been stopped

/etc/init.d/ssagent start


ADDITIONAL COMMENTS:

  • 1002220.1 Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged"
  • 1008188.1 Sun Storage 3000 Arrays: Troubleshooting Battery Problems


If you are using Sun Storedge Configuration Service (SSCS) , you may need to manually perform a rescan of the array to get the new battery in-service date and correct age. Execute the steps in Chapter 4.5 of the Sun StorEdge 3000 Family FRU Installation Guide.

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE: Batteries 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 service personnel for additional instructions.


PARTS NOTE:

REFERENCE INFORMATION:

References

<NOTE:1008188.1> - Sun Storage 3000 Arrays: Troubleshooting Battery Problems
<NOTE:1002220.1> - Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged"

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback