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-1012692.1
Update Date:2011-06-10
Keywords:

Solution Type  Problem Resolution Sure

Solution  1012692.1 :   Sun StorEdge [TM] 351x Array: How to Resolve Devices Missing from The Se3kxtr "show_frus" and "show_ses-devices" Output  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
217449
This article explains how to resolve devices missing from se3kxtr show_frus and show_ses-devices files due to Duplicate Box Id's.

Applies to:

Sun Storage 3310 Array
Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
All Platforms

Symptoms

{SYMPTOM}

Symptoms

In the se3kxtr's show_frus.out output, the fru instances for the primary and secondary "FC_RAID_IOM " and "BATTERY_BOARD" are missing.
Only the 3510 JBOD chassis's FRUs are reported in the "show frus" output.

Additional Symptoms:

1. The output for the command "show battery-status" reports that "sccli: retrieving battery status: error: not an existing target."

2. The "show_loopmaps [ch2/ch3]" report the 3510FC RAID Chassis's SES Devices with a SEL_ID of 125.

3. The se3kxtr output for show_ses-devices.out file reports only the 3510 JBOD's SES devices for CH (2/3)loops (a/b) respectively.



Changes

{CHANGE}

Cause

{CAUSE}

The symptoms described in the problem statement, were a result of two separate
problems seen on a 3510 FC Array. Similar symptoms and resolution could occur
on a 3511 SATA array.

1) Duplicate Chassis/Box IDs.
Note: After removing the plastic bezels on both chassis it was discovered that indeed both the 3510FC RAID Chassis and the JBOD chassis Box ID's were set to "1"

This was certainly confusing considering the loop map outputs from both ch2/ch3 reported the RAID device FRUs with a ENCL_ID of "0" and the JBOD device FRUs with a ENCL_ID of "1." It is uncertain whether this is a reporting bug or consequence of SCCLI's inability to properly communicate with the RAID Chassis. It was visibly proven that the Box ID's were indeed both set to "1" so one can conclude for this instance that sccli only assumes the ID's were unique when it could not communicate to the RAID Chassis and assigned unique ENCL_ID's in the channel loop maps.

*Please also note that there are other documented symptoms associated with having duplicate Chassis/Box IDs that are not mentioned in this document.

2) SES Mismatch discovered between the Primary/Secondary RAID I/O MODULES.


Solution



Corrective Actions:

1) Changed the ID switch of the RAID Chassis Box ID to "0".

2) Power-cycled the 3510FC in the following order: First powered  OFF the RAID head, then the JBOD. Then powered ON the JBOD followed by the RAID head.

3) Then the RAID Chassis came up with and audible alarm and an amber maintenance LED was blinking, uncovering an SES firmware mismatch which apparently existed in the RAID I/O MODULE SES devices. Possibly introduced on a prior RAID I/O MODULE replacement or maintenance activity.

4) The RAID Chassis SES on the primary controller that previously had a SEL_ID 125 instead of 12 had to be manually upgraded using sccli from SES-FW 1046 to 1080 to match that of the secondary's SES and another shutdown, reset was initiated. After the reset the SEL_ID for primary controller's SES then was identified correctly as SEL_ID 12.


Note: SEL_ID 125 has also been known to be a result of having a faulty component i.e. I/O Module or cable 

5) A new se3k-extractor was collected and all was reported correctly.



Additional Information:

Problem/Symptom Analysis Reference:

Array Configuration:
3510FC + 1 JBOD Configuration (cabled correctly)

se3kextractor symptom output: (Note: comments inline ending with !!)
show_frus.out -->Notice only JBOD FRUs reporting status!!

sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN
StorEdge 3510 SN#0856XX]
5 FRUs found in chassis SN#098BBO at ch 2 id 28
Name: FC_CHASSIS_BKPLN
Description: SE3510 FC Chassis/backplane
Part Number: 370-5535
Serial Number: 098BB0
Revision: 02
Initial Hardware Dash Level: 02
FRU Shortname: 370-5535-02
Manufacturing Date: Fri Nov 4 10:18:18 2005
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: FC MIDPLANE SLOT
Chassis Serial Number: 098BB0
FRU Status: OK
Name: FC_JBOD_IOM
Description: SE3510 I/O w/SES JBOD FC 2U
Part Number: 370-5538
Serial Number: HG11SA
Revision: 06
Initial Hardware Dash Level: 06
FRU Shortname:
Manufacturing Date: Mon Nov 28 20:56:50 2005
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER FC JBOD IOM SLOT
Chassis Serial Number: 098BB0
FRU Status: OK
Name: AC_POWER_SUPPLY
Description: AC PWR SPLY FAN MOD 2U FC/SATA
Part Number: 370-6776
Serial Number: GM2AV5
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: FC/SATA AC PS
Manufacturing Date: Mon Aug 29 11:08:51 2005
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: RIGHT AC PSU SLOT #1 (RIGHT)
Chassis Serial Number: 098BB0
FRU Status: OK
Name: AC_POWER_SUPPLY
Description: AC PWR SPLY FAN MOD 2U FC/SATA
Part Number: 370-6776
Serial Number: GM2CAH
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: FC/SATA AC PS
Manufacturing Date: Tue Aug 30 10:55:57 2005
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: AC PSU SLOT #0 (LEFT)
Chassis Serial Number: 098BB0
FRU Status: OK
Name: FC_JBOD_IOM
Description: SE3510 I/O w/SES JBOD FC 2U
Part Number: 370-5538
Serial Number: HG11TD
Revision: 06
Initial Hardware Dash Level: 06
FRU Shortname:
Manufacturing Date: Mon Nov 28 21:05:39 2005
Manufacturing Location: Suzhou,China
Manufacturer JEDEC ID: 0x0301
FRU Location: LOWER FC JBOD IOM SLOT
Chassis Serial Number: 098BB0
FRU Status: OK
show_battery-status.out
sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN
StorEdge 3510 SN#085681]
sccli: retrieving battery status: error: not an existing target
sccli: retrieving battery status: error: not an existing target

---------------------------------------------------------------
Upper Battery Hardware Status: OK
Lower Battery Hardware Status: OK

show_loop-map_channel_2.out
sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN
StorEdge 3510 SN#085681]
28 devices found in loop map

Channel Loop Map retrieved from CH 2 ID 28

AL_PA   SEL_ID  SEL_ID  TYPE    ENCL_ID SLOT
(hex) (hex) (dec)
----- ----- ----- ---- ------ ----
CE 0F 15 RAID N/A N/A
B9 1B 27 DISK 1 11
C6 16 22 DISK 1 6
BA 1A 26 DISK 1 10
C5 17 23 DISK 1 7
B6 1C 28 SES 1 N/A
CC 11 17 DISK 1 1
C9 14 20 DISK 1 4
CB 12 18 DISK 1 2
CA 13 19 DISK 1 3
C7 15 21 DISK 1 5
CD 10 16 DISK 1 0
C3 18 24 DISK 1 8
BC 19 25 DISK 1 9
D9 08 8 DISK 0 8
D6 09 9 DISK 0 9
D5 0A 10 DISK 0 10
D4 0B 11 DISK 0 11
01 7D 125 RAID N/A N/A <---SEL_ID 125 !!
D1 0E 14 RAID N/A N/A
EF 00 0 DISK 0 0
E8 01 1 DISK 0 1
E4 02 2 DISK 0 2
E2 03 3 DISK 0 3
E1 04 4 DISK 0 4
E0 05 5 DISK 0 5
DC 06 6 DISK 0 6
DA 07 7 DISK 0 7
show_loop-map_channel_3.out
sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN
StorEdge 3510 SN#085681]
28 devices found in loop map
=== Channel Loop Map retrieved from CH 3 ID 28 ===
AL_PA   SEL_ID  SEL_ID  TYPE    ENCL_ID SLOT
(hex) (hex) (dec)
----- ----- ----- ---- ------ ----
CE 0F 15 RAID N/A N/A
CC 11 17 DISK 1 1
C9 14 20 DISK 1 4
CB 12 18 DISK 1 2
CA 13 19 DISK 1 3
C7 15 21 DISK 1 5
CD 10 16 DISK 1 0
C3 18 24 DISK 1 8
BC 19 25 DISK 1 9
B9 1B 27 DISK 1 11
C6 16 22 DISK 1 6
BA 1A 26 DISK 1 10
C5 17 23 DISK 1 7
B6 1C 28 SES 1 N/A
E1 04 4 DISK 0 4
E0 05 5 DISK 0 5
DC 06 6 DISK 0 6
DA 07 7 DISK 0 7
D9 08 8 DISK 0 8
D6 09 9 DISK 0 9
D5 0A 10 DISK 0 10
D4 0B 11 DISK 0 11
D1 0E 14 RAID N/A N/A
EF 00 0 DISK 0 0
E8 01 1 DISK 0 1
E4 02 2 DISK 0 2
E2 03 3 DISK 0 3
01 7D 125 RAID N/A N/A<---SEL_ID 125 !!
show_ses-devices.out --->Notice only displays JBOD SES Devices !!
sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN
StorEdge 3510 SN#085681]
Ch Id Chassis Vendor/Product ID Rev PLD WWNN WWPN
-------------------------------------------------------------------------------
2 28 098BB0 SUN StorEdge 3510F D 1080 1000 205000C0FF098BB0
215000C0FF098BB0
Topology: loop(a)
3 28 098BB0 SUN StorEdge 3510F D 1080 1000 205000C0FF098BB0
225000C0FF098BB0
Topology: loop(b)



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 contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-os-disk-low-domain@sun.com

The Knowledge Work Queue for this article is KNO-STO-VOLUME_DISK.


SEL_ID, 125, SES, show_frus.out, show_ses.out, FRU, missing, box id, show_battery-status.out, audited, retrieving, chassis id, se3kxtr, se3k, extractor, 3510, 3511
Previously Published As
86947

Change History
Date: 2009-12-23
User Name: sue.copeland@sun.com
Action: Currency & Update
Date: 2007-06-29
User Name: 7058
Action: Approved

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback