Sun StorEdge 351x Array: How to Resolve Devices Missing from the se3kxtr "show_frus" and "show

Asset ID:	1-72-1012692.1
Update Date:	2013-08-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1012692.1 : Sun StorEdge 351x Array: How to Resolve Devices Missing from the se3kxtr "show_frus" and "show_ses-devices" Output

Applies to:

Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
All Platforms

Symptoms

Given a 3510 raid array with one expansion jbod attached. The se3kxtr's show_frus.out output, is missing the instances for the primary and secondary FC_RAID_IOM and BATTERY_BOARD. You would expect to see 5 more FRU's found in chassis SN#098BB0 at ch 2 id XX. Instead, only the jbod hardware is listed.

sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUNStorEdge 3510 SN#0856XX] (parsed output for clarity) 
sccli> show frus
5 FRUs found in chassis SN#098BBO at ch 2 id 28

Name: FC_CHASSIS_BKPLN
Description: SE3510 FC Chassis/backplane
FRU Status: OK

Name: FC_JBOD_IOM
Description: SE3510 I/O w/SES JBOD FC 2U
FRU Status: OK

Name: FC_JBOD_IOM
Description: SE3510 I/O w/SES JBOD FC 2U
FRU Status: OK

Name: AC_POWER_SUPPLY
Description: AC PWR SPLY FAN MOD 2U FC/SATA
FRU Status: OK

Name: AC_POWER_SUPPLY
Description: AC PWR SPLY FAN MOD 2U FC/SATA
FRU Status: OK

Similarly, show-ses output is missing everything for the Raid Chassis. Only the jbod chassis shows up. (There should be 2 more devices, typically at chan 2/3 id 12)

sccli> show_ses-devices.out
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)

Other anomalies in se3xtr include errors for the batteries.

sccli> 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

Lastly, sccli output for the loop maps reports the RAID Chassis's SES Devices with a SEL_ID of 125. A more typical value for the device would be 12.

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
B6      1C      28      SES     1       N/A
01      7D      125     RAID    N/A     N/A
D1      0E      14      RAID    N/A     N/A

show_loop-map_channel_3.out
sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN StorEdge 3510 SN#085681]
28 devices found in loop map (DISKS omitted for clarity)
=== 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
B6      1C      28      SES     1       N/A
D1      0E      14      RAID    N/A     N/A
01      7D      125     RAID    N/A     N/A

Note: SEL_ID 125 has also been linked to hardware problems with I/O Module or cabling.

Changes

There have been no changes to the array.

Cause

This problem will occur if the box ID of any two chassis are the same. Remove the plastic bezel from the front (left and right side) of the array to view the ID.
In our above example, the ID was set to one on both chassis.

Solution

Stop all I/O to the array
Power off the Raid Head First. Wait 30 seconds. Power off all expansion jbods (any order)
Make the Box ID's unique. It does not matter what values you choose so long as they are all different.
Power on all expansion jbods. Wait a minute
Power on raid chassis.
Start I/O

Attachments

This solution has no attachment