Asset ID: |
1-72-1486413.1 |
Update Date: | 2014-06-26 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1486413.1
:
Sun Storage 2500-M2 or 6x80 Arrays Reporting "insufficient cache backup capacity" after a controller replacement or firmware upgrade
Related Items |
- Sun Storage 6580 Array
- Sun Storage 2540-M2 Array
- Sun Storage 6180 Array
- Sun Storage 6780 Array
- Sun Storage 2530-M2 Array
|
Related Categories |
- PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
|
In this Document
Applies to:
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6180 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6580 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6780 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
Symptoms
Sun Storage Common Array Manager (CAM) reports the following alarm for your array:
Alarm ID : alarm173
Description: Controller Tray.X.Controller.Y is reporting insufficient cache backup capacity.
Severity : Critical
Element : tXctrlY
GridCode : 90.66.1253
Date : <date and time>
This document covers the following situations:
- The alarm is raised after a controller replacement. Make sure the correct replacement controller was installed. Refer to <Document 1546658.1> Sun Storage 2500 Arrays: Controller Replacement Requires Verifying Cache Size.
- The alarm is raised after a firmware upgrade from 07.77 or lower, to 07.80 or higher.
Cause
Error reporting for the USB cache backup device was changed in the 07.80 firmware to provide better notification.
If you are receiving error reports as described above after upgrading to 07.80, it is likely the error condition existed prior to the upgrade and is only being reported now due to the change in error reporting in 07.80.
Solution
Oracle support needs to determine when the alarm was raised and analyze array logs.
- Collect a supportdata, refer to <document 1002514.1>.
- Contact Oracle support to open a SR.
Internal Only - To be used by TSC engineers.
Instructions for the TSC L1 engineers:
- Open a collaboration with TSC L2 to request the solution.
Instructions for the TSC L2 engineers:
- Collect the output of the following shell command from both controllers:
pstorShow
- If you meet any of the following condition in the "pstorShow" output:
IsUsable....................: FALSE
or
HeaderStaus.................: INVALID
or
The NumBlocks or NumberOfDataBlock values do not match for a device between the two controllers
then you need to proceed with step 3. Otherwise replace the USB cache device.
Note: For the 2500-M2 and 6180, the USB cache device replacement requires to replace the controller. For the 6580 and 6780, you can replace the USB cache device individually.
- Execute the following commands on the controller which matches one or more of the above conditions:
pstorWipe
bucWipe
Note: This requires a controller reboot.
- If the alarm has not been cleared after 5 minutes, please replace the USB cache device.
Note: For the 2500-M2 and 6180, the USB cache device replacement requires to replace the controller. For the 6580 and 6780, you can replace the USB cache device individually.
References
<NOTE:1002514.1> - Collecting Sun Storage Common Array Manager Support Data for Arrays
Attachments
This solution has no attachment