Sun StorageTek 6000 Arrays May Report "Trays Not Grouped by Type" Message

Asset ID:	1-77-1017338.1
Update Date:	2013-04-17
Keywords:

Solution Type Sun Alert Sure

Solution 1017338.1 : Sun StorageTek 6000 Arrays May Report "Trays Not Grouped by Type" Message

Related Items


Sun Storage 6540 Array
 Sun Storage CSM100 Array
 Sun Storage Flexline 280 Array
 Sun Storage Flexline FLA300 Drive Module
 Sun Storage CSM200 Array
 Sun Storage 6130 Array
 Sun Storage 6140 Array
 Sun Storage Flexline 240 Array
 Sun Storage Flexline 380 Array

Related Categories


PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun Alert
 _Old GCS Categories>Sun Microsystems>Sun Alert>Release Phase>Resolved

PreviouslyPublishedAs
228392

Bug Id
<BUG: 15408580>

Product
Sun StorageTek 6130 Array
Sun StorageTek 6140 Array
Sun StorageTek 6540 Array

Date of Workaround Release
23-AUG-2007

Date of Resolved Release
16-Dec-2008

***Checked for relevance 17-Apr-2013***

Impact

Sun StorageTek 6000 Arrays may report "Trays Not Grouped by Type" message. In most cases, the message is superficial, and causes no system degradation, other than an alert or alarm notification that the condition exists. In rare cases, the user may experience some performance degradation, but no loss of data access or failure of a component.

Contributing Factors

This issue can occur on the following platforms:

Sun StorageTek 6130 with array firmware 06.19.25.10
Sun StorageTek 6140 with array firmware 06.19.25.10
Sun StorageTek 6540 with array firmware 06.19.25.10
StorageTek FLX240 with array firmware 06.19.25.00
StorageTek FLX280 with array firmware 06.19.25.00
StorageTek FLX380 with array firmware 06.19.25.00
StorageTek FLA300 Fibre Channel Array Expansion Trays without ESM firmware 9681
Sun StorageTek CSM100 Fibre Channel Array Expansion Trays without IOM firmware 9681
Sun StorageTek CSM200 Fibre Channel Array Expansion Trays without IOM firmware 98C1

Note: The addition of an expansion, re-cabling, replacement of an IOM, or even a power on sequence could lead to this issue.

Symptoms

Should the described issue occur, the event presents itself as an alarm issued via Common Array Manager(CAM) as follows:

    -------------------------------------------------------
    Property      Value      Severity: Critical     Date: 03.03.2007 17:02:17     State: Open     Reopened By: Bob
    Auto Clear  Yes     Description: Drive trays not grouped by type: Tray.11 Tray.15 Tray.14 Tray.17
    Tray.5     Info:         Device:     ARRAY01
    Component:     Tray.02     Event Code:     48.66.1092     Aggregated Count:     0

or via SANtricity Storage Manager:

    Failure Entry X:  DRIVE_TRAYS_NOT_GROUPED_TOGETHER
    Details
    Storage array: ARRAY01
    Affected trays: 11, 15, 14, 17
    End of Failure Entry X

Workaround

For cases where performance is not impacted, the message may be ignored until a resolution is provided. Otherwise, the following workarounds exist, and are listed in order of preference (from least to greatest impact to production level services):

Option 1:

Reseat the cables between all affected trays first on the A controller side, then repeat on the B controller side. This can be done without taking the into a maintenance outage, if managed properly.

Option 2:

Unplug and plug the IOM on the A controller, then the B controller for each tray. This can be down without a maintenance outage, if managed properly.

Option 3:

Power cycle the array. This requires a maintenance outage of all servers accessing the array, and should be done in the following order:

Stop IO access to the array.
Power off the RAID head.
Power off all trays.
Power on all trays.
Power on RAID head.
Verify by using CAM or SANtricity that the array is optimal, and the alarm has cleared.
Start IO access.

Resolution

This issue is addressed in the following releases:

StorageTek FLA300 Fibre Channel Array Expansion Trays with ESM firmware 9681 or later
Sun StorageTek CSM100 Fibre Channel Array Expansion Trays with IOM firmware 9681 or later
Sun StorageTek CSM200 Fibre Channel Array Expansion Trays with IOM firmware 98C1 or later

Note 1: Firmware 9681 is provided in the Sun StorageTek Common Array Manager (CAM) 6.2 release.
Note 2: Firmware 98C1 is provided in the Sun StorageTek Common Array Manager 6.2 release.
Note 3: Common Array Manager (CAM) download information is available at:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1296274.1

Modification History
16-Dec-2008: Updated Contributing Factors and Resolution sections. Resolved.
11-Apr-2013: Corrected CAM download link
17-Apr-2013: Updated for currency, relevance, corrections to format

Previously Published As
103050
Internal Comments
The following is an example of the corresponding MEL entry to the alarm/event raised by the management host:

Date/Time: 04/07/07 20:33:53
Sequence number: 133829
Event type: 2835
Event category: Internal
Priority: Critical
Description: Drive trays cabled incorrectly
Event specific codes: 0/0/0
Component type: Tray Component (ESM, SFP, Power Supply, or Fan)
Component location: Tray 17, Slot 0
Logged by: Controller in slot B

For customers making a complaint about performance, check the
"stateCaptureData.dmp" file generated from the affected array. The
"HubMode" or "socInHubMode" field of "showEnclosuresPage81" will tell
you if the IOM is operating in HUB mode.

    Tray ID 1

    page 0x81 info
    ENCL_IO
    op_code    0x81
    IO_size    648
    IO flags:  0x00000000
    Page 0x81  slot-A  socInHubMode 0  sfpTreeModeMap 1  cleared 0  length 644  duration(s) 11898229
    NOTE:  "socInHubMode 1" indicates the tray is operating in HUB mode

CSM200 tray output:

    Tray 0 page 0x81 info

    ESM Type: Wrigley
    PageCode: SOC DIAGNOSTICS
    ESM Slot: B
    HubMode : NO
    NonSEOC : 0 0 0 1
    NOTE:  "HubMode: YES" indicates the tray is operating in HUB mode

If HubMode is not active for either IOM/ESM type, array performance is not impacted by this issue.

If possible we would need to
collect from the array controller a dump or "stateCapture" of the
IOM/ESM on each tray, as well as a full "dqprint" from each array
controller. Please escalate to PTS/Backline to get a procedure on
collecting this output.

Please send technical questions to the following email:
sunalertpublication_us_grp@oracle.com
and CC the
Internal Eng Responsible Engineer
Internal Contributor/submitter: Curtis.DeCotis@sun.com
Internal Eng Responsible Engineer: Curtis.DeCotis@sun.com
Internal Services Knowledge Engineer: jeff.folla@oracle.com
Internal Eng Business Unit Group: NWS (Network Storage)
Internal Escalation IDs:
65591551, 37903176, 1-334933606, 1-338162602

Attachments

This solution has no attachment