Sun Storage[TM] 6000 Arrays and Sun StorageTek[TM] 2500 Arrays: Troubleshooting Power Supply and Fan Failures

Asset ID:	1-75-1021103.1
Update Date:	2011-06-08
Keywords:

Solution Type Troubleshooting Sure

Solution 1021103.1 : Sun Storage[TM] 6000 Arrays and Sun StorageTek[TM] 2500 Arrays: Troubleshooting Power Supply and Fan Failures

Applies to:

Sun Storage 2510 Array - Version: Not Applicable and later   [Release: N/A and later ]
Sun Storage 2530 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 2540 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]
Sun Storage 6780 Array - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Purpose

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - 6000 and 2500 Series RAID Arrays

Description
The purpose of this document is to help troubleshoot Power Supply Unit (PSU) fault symptoms on StorageTek[TM], Sun StorEdge[TM], Sun StorageTek[TM], and Sun Storage[TM] arrays.

Symptoms:

Failed Power Supply (66.1002)
Failed Power Supply / Failed Support CRU (66.1090)
Power Supply Unknown Status (66.1059)
Removed Power Supply (66.1085)
Failed Fan (66.1001)
Fan Unknown Stat (66.1058)
Removed Fan (66.1084)
Support CRU No Input (66.1097)
Power Supply, Fan, or Power Cooling Unit status as Failed, Removed, or Unknown
Array event log entries similar to:

Jan 14 00:58:54 db_storage Tray.01.PowerSupply.A:[ID 0x280D] NOTICE Drive tray component failed or removed

Jan 14 00:59:04 db_storage Tray.01.PowerSupply.A:[ID 0x280C] NOTICE Drive tray component changed to optimal

Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions via a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Last Review Date

June 8, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

1. Verify the Critical Fault seen by the array.

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

If there are no critical faults, or you are receiving fault notification and find no critical faults, continue to Step 3

If the faults are for

Power Supply Unknown Status (66.1059)
Fan Unknown Stat (66.1058)

contact support for further troubleshooting.

If the faults are for

Support CRU No Input (66.1097)

continue to Step 2.

If the faults are for

Failed Power Supply (66.1002)
Failed Power Supply/ Failed Support CRU (66.1090)
Failed Fan (66.1001)

The power supply, fan, or power cooling unit should be replaced.

If the faults are for

Removed Power Supply (66.1085)
Removed Fan (66.1084)

This is normal if the power supply has been removed from the system for maintenance. Re-seat the power supply in the location annotated by the fault. A is on the left. B is on the right. If the status does not change, contact support for further troubleshooting.

2. Verify the power cord is plugged in and firmly seated in the Power Supply and power strip in the cabinet and that the switch is in the on position. Also ensure Power Supply Unit is firmly seated in tray.

If the cord is plugged in and seated firmly, contact support for further troubleshooting.

3. Verify the tray type that is showing the fault

Reference <Document: 1021104.1> How to verify Sun Storage[TM] Array Tray Type via the User Interface

if the Tray Type is a CSM200, continue to Step 4.
otherwise, contact Oracle for further support.

4. Verify the existence of 0x280D component failed or removed messages for the power supply, fan, or power cooling unit.

Browser:

    1.    Expand Storage Arrays in the left menu pane.
    2.    Expand your storage array name in the left menu pane.
    3.    Expand Troubleshooting in the left menu pane.
    4.    Click on Events.
    5.    In the right pane, click on the -|-> icon. If you mouse over it it will state Advanced Filter.
    6.    Set Event to Log Events.
    7.    Set Event Type to Component.
    8.    Set Read the last X Kbytes From Log File to 100.
    9.    Set String Filter to "Fan" or "PowerSupply".
    10.    Click on the Details of any alarm that is shown.
    11.    Review the Description Field.
    12.    Get the value of the array log event ID from the description.

Example:

Description : Apr 08 21:31:31 6780-array Tray.01.PowerSupply.A: [ID 0x280D] NOTICE
Drive tray component failed or removed

SSCS CLI:

Get the list of events:

sscs list -d <array_name> -t LogEvent -f PowerSupply event

sscs list -d <array_name> -t LogEvent -f Fan event

Get the event details:

sscs list -d <array_name> event event_id

Get the value of the array log event ID from the description:

Example:

Description : Apr 08 21:31:31 6780-array Tray.01.PowerSupply.A: [ID 0x280D] NOTICE
Drive tray component failed or removed

SANtricity Storage Manager:

GUI:
    1.    Launch SANtricity.
    2.    Double Click on your array name to open the Array Management Window.
    3.    Click on the Advanced Menu.
    4.    Click on the Troubleshooting Sub-Menu.
    5.    Click on View Event Log.
    6.    Un-Check View Only Critical Events.
    7.    Click on the Component Type field header to sort the events.
    8.    Look for Fan or Power Supply in the list of events.
    9.    For any Fan or Power Supply event, highlight it, and check the View Details box.
    10.    Get the value of the Event type field for each Fan or Power Supply event.

SMcli:

Get the list of events by saving off the event log:

SMcli -n array_name -c "save storageArray allEvents file=\"some/file/path/log.txt\";"

Open a text viewing application to look at the individual events.
Get the value of the Event type field for each DIMM event.

Example Event

Date/Time: Mon Aug 03 02:15:04 EAT 2009
Sequence number: 9747
Event type: 280D
Event category: Notification
Priority: Critical
Description: Drive tray component failed or removed
Event specific codes: 0/0/0
Component type: PowerSupply
Component location: Tray.0 (Power Supply)
Logged by: Controller in slot A

â¢ If there is the existence of an Event ID of 0x280D, go to Step 5.
â¢ If there are no 0x280D Event ID's, and your power supplies are Optimal/OK, contact support for further troubleshooting.

5. Verify the existence of a corresponding 0x280C event using the method above.

CAM Event:

Description : Apr 08 21:31:31 6780-array Tray.01.PowerSupply.A: [ID 0x280C] NOTICE
Drive tray component changed to optimal

SANtricity Event:

Date/Time: Mon May 25 06:40:23 EAT 2009
Sequence number: 7722
Event type: 280C
Event category: Notification
Priority: Informational
Description: Drive tray component changed to optimal
Event specific codes: 0/0/0
Component type: PowerSupply
Component location: Tray.0 (Power Supply)
Logged by: Controller in slot A

If there is a corresponding 0x280C event on the system after a 0x280D event, then you may be running into Defect 6755247, which is caused by a problem in the expansion tray firmware. Please update to IOM firmware 98D3 or later, which is bundled with CAM 6.7 or later.

Internal Comments
This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap
contained in this document, and/or prior to updating this document, please
add a comment to the document.

Attachments

This solution has no attachment