Sun Storage 6540 Array
 
Sun Storage 6130 Array
 
Sun Storage 6140 Array
 

GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
 
GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
 

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.

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.

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:

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

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

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

CSM100-F tray output:

    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:

  [email protected]
and CC the following persons:
  Internal Contributor/Submitter
  Internal Eng Responsible Enginee

This solution has no attachment