Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1283914.1
Update Date:2011-06-08
Keywords:
Solution Type  Problem Resolution Sure

Solution  1283914.1 :   Troubleshooting Sun Storage[TM] Array Unknown Battery Status  

Related Items 
    

  • Sun Storage 6180 Array
    •  
  • Sun Storage 6580 Array
    •  
  • Sun Storage 2510 Array
    •  
  • Sun Storage 2540 Array
    •  
  • Sun Storage 6780 Array
    •  
  • Sun Storage 2540-M2 Array
    •  
  • Sun Storage 6140 Array
    •  
  • Sun Storage 2530 Array
    •  
  • Sun Storage 2530-M2 Array
    •  
  • Sun Storage 6540 Array
    •  
  • Sun Storage 6130 Array
    •  
Related Categories 
    

  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
    •  
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 2xxx Arrays
    •  
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - Flexline FLX FLA FLC Arrays
    •  






In this Document

  Symptoms

  Cause

  Solution






Applies to: 
 
Sun Storage 2530 Array - Version: Not Applicable and later   [Release: N/A and later ]
Sun Storage 2510 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 6180 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 6540 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 6130 Array - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.



Symptoms

Critical Faults of:


    

  • Common Array Manager alarm code xx.66.1091:  Battery Tray.xx.Battery.x has transitioned to an unknown state 
    • 

  • SANtricity Storage Manager fault of BATTERY_UNKNOWN_STAT
Reference:  <Document: 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 Critical Faults via the User Interface

Cause

A possible controller offline/failure has caused a problem in getting the battery status, or, possibly, a failure in the cache battery handling system of the array has lost track of the battery status.

Solution


1.  Verify the Critical Faults on the system and make sure that there is a critical fault for one or both batteries as follows.



Reference:  <Document: 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 Critical Faults via the User Interface.




  • Common Array Manager alarm code xx.66.1091:  Battery Tray.xx.Battery.x has transitioned to an unknown state.
    
  
  • SANtricity Storage Manager fault of BATTERY_UNKNOWN_STAT.


If the faults are listed, continue to Step 2.

Otherwise, reference <Document: 1021054.1> Troubleshooting Storage[TM] Array Battery Faults.


2. Verify Critical Fault List for a Controller Fault.

You have identified that your array is one that has a battery integrated or installed on the RAID controller of the system. If the RAID controller is transitioned to an offline state, the surviving controller will no longer be able to get the battery status.  As such, the controller fault should be fixed prior to any work performed on the battery.  


Reference:  <Document: 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 Critical Faults via the User Interface.

If there are any of the following faults listed:
  • Common Array Manager alarm code xx.66.1028: Controller Tray.xx.Controller.x is offline.
  • Common Array Manager alarm code xx.66.1041: RPA Memory Error.
  • SANtricity Storage Manager fault for OFFLINE_CTL.
  • SANtricity Storage Manager fault for RPA_ERR_CTL.
you will need to resolve the controller issue prior to addressing the battery status.   

Reference:  <Document: 1021054.1> Troubleshooting Sun Storage[TM] RAID Controller Failures.

If none of the faults for controllers exist, continue to Step 3.

3.  Verify Array Model and Remove and Insert the Battery then Check the status.

Reference <Document: 1021066.1> Verify Sun Storage[TM] Array Array Type via the User Interface.

The batteries in these units:  

  • 2510
  • 2530
  • 2540
  • 2530-M2
  • 2540-M2
  • 6140
  • 6180
  • Flexline 380
  • 6540
  • 6580
  • 6780
are customer replaceable and hot pluggable. You can remove and reseat these batteries without any impact to the system. The write caching that the batteries protect has already been disabled by the fault(s) in the symptoms list.

Note: For the 2500 arrays, the controller 
needs to be offlined and pulled before removing its battery. In a dual 
controller configuration, this requires a multipathing environment to be
 configured to allow the IO access through the surviving controller.



Note: Follow carefully the instructions in Service Advisor, under Battery Removal and Replacement procedures.  Depending on the model you may require a static mat and screwdriver to remove the battery, as is the case with any 2500 array.

a) Remove the battery listed in the fault.  Battery A or Battery 1 is on the left.  Battery B or Battery 2 is on the right.  Diagrams of the battery is located in the Service Advisor procedure for Battery Removal and Replacement in Common Array Manager.

b) Wait about 1-2 minutes then insert back the battery.

c) Wait about 5 minutes, then evaluate the list of faults again.

If this step has been completed without change, contact support for further troubleshooting.
If the array is not in the list of customer replaceable batteries, contact support for further troubleshooting.



Attachments

This solution has no attachment


















       

Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.

 Feedback