StorEdge[TM] 3510FC Array Controller LED Amber,"show fru" Missing FRUs

Asset ID:	1-72-1004958.1
Update Date:	2012-07-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1004958.1 : StorEdge[TM] 3510FC Array Controller LED Amber,"show fru" Missing FRUs

Applies to:

Sun Storage 3510 FC Array
All Platforms

Symptoms

When we did a health check for a customer's Sun[TM] StorEdge 3510 FC array
we found that this array's controller amber LED was
abnormally flashing in the following order:
Green flashes --> Amber flashes --> Off --> Green flashes --> Amber flashes

And CLI checking command " sccli > show fru " reported:

-------------------------------------------------------------

4 FRUs found in chassis SN#003455 at ch 2 id 12
Name: FC_CHASSIS_BKPLN
Description: SE3510 FC Chassis/backplane
Part Number: 370-5535
Serial Number: 003455
...
Name: AC_POWER_SUPPLY
Description: SE3310/SE3510 AC PWR SUPPLY w/FAN
Part Number: 370-5398
Serial Number: 021525
...
Name: AC_POWER_SUPPLY
Description: SE3310/SE3510 AC PWR SUPPLY w/FAN
Part Number: 370-5398
Serial Number: 021550
...
Name: FC_JBOD_IOM
Description: SE3510 I/O w/SES JBOD FC 2U
Part Number: 370-5538
Serial Number: 004014
...

It seems that system could not get following TWO FRUs statuses:

Name: FC_RAID_IOM
Description: SE3510 I/O w/SES + RAID Cont 1GB
Part Number: 370-5537

Name: BATTERY_BOARD
Description: SE3510 Hot Swap Battery Module
Part Number: 370-5545

----------------------------------------------------------------

Array configurations are:

Firmware: 327R
Single controller
single hosts connected
Array S/N: 000451-0327003455
Controller P/N: 370-5537-02 with S/N: 003488

The system administrator complains that I/O performance is not as
good as they expected.

Reseating or resetting the controller did not fix the symptoms described as above.

Changes

{CHANGE}

Cause

{CAUSE}

Solution

Resolution

The solution was to order a controller FRU 370-5537, and take actions to replace the original faulty one.

As there is no way to confirm the health of NVRAM in the array, it is advised that the setting be manually recovered using the output from the se3k extractor data captured before any work is carried out - also manually make a note of the sector, heads and cylinder data by accessing the array via the network or serial port and then select view and edit Configuration Parameters then Host-side Parameters and then Host Cylinder/Head/Sector Mapping Configuration.

Open a tip session to access the new controller, because the new controller does not know the original controller configurations, such as network configurations LUN mapping information etc. then check the setting of the new controller with those in the se3k extractor data and set those that don't match.

Set "Controller Unique identifier" to 0.
Do not input the new Controller S/N here, the "Controller Unique
identifier" points to the array chassis S/N, once the new controller
is auto reset and up again, all original configuration comes back again !

$ tip -38400 /dev/term/a
--> Select "View and edit Configuration parameters"
--> Select "Controller parameters"
--> Select "Controller Unique Identifier(Hex) - 3455"
--> change "3455" to "0"

Now, it is time to reset controller for setting to take effect.
Wait sometime until array startup completed !

At this time, check the controller LED, No amber LED flashes,
the green LED flashes periodically as expected :

Green flashes --> Off --> Green flashes --> Off

At the hosts side, recognizes the SE3510 LUNs, mount the user file system
All okay !

check the array configurations as:

$ sccli
sccli > show fru
system now shows the two MISSING FRUs information as follows;
(We omited the other four FRUs which can always be detected)

...

Name: FC_RAID_IOM
Description: SE3510 I/O w/SES + RAID Cont 1GB
Part Number: 370-5537

Name: BATTERY_BOARD
Description: SE3510 Hot Swap Battery Module
Part Number: 370-5545

...

Now,SE3510FC array becomes normal completely.

Product
Sun StorageTek 3510 FC Array

SE3510FC, Controller Amber, show fru
Previously Published As
77561

Change History
Date: 2004-09-07
User Name: 36642
Action: Approved
Comment: This document is ready for SunSolve. It is trademarked and there appear to be no duplicates.
Version: 4
Date: 2004-09-01
User Name: 125432
Action: Approved

Attachments

This solution has no attachment