6120 Controller VPD Reporting

Was wondering if anyone has seen this.

We recently took over responsibility for several 6120 arrays and one of them seems to have a problem with the secondary controller reporting VPD. As a side note: All volumes are intact and can be accessed by the host. We can fail over to the secondary controller and fail back without incident. There appears to be no other symptoms that the lack of VPD reporting in the <fru list> out put shown below. We replaced the controller with a spare we had on hand, but the symptoms persist.

6120 Release 3.2.6

Copyright (C) 1997-2006 Sun Microsystems, Inc.

All Rights Reserved.

/:<1>fru list

IDTYPEVENDORMODELREVISIONSERIAL

-- -- -- - --

u1ctrcontroller card0x301540555950 004312

u2ctrcontroller cardunknownunknownunknownunknown

u1d01disk drive FUJITSUMAP3735F SUN 140105Q07V3V

u1d02disk drive FUJITSUMAP3735F SUN 140104Q07RWL

u1d14disk drive FUJITSUMAP3735F SUN 140104Q07RVS

u2d01disk drive FUJITSUMAP3735F SUN 140104Q07RW4

u2d02disk drive unknownunknownunknownunknown

u2d03disk drive unknownunknownunknownunknown

u2d04disk drive unknownunknownunknownunknown

u2d05disk drive unknownunknownunknownunknown

u2d06disk drive unknownunknownunknownunknown

u2d07disk drive unknownunknownunknownunknown

u2d08disk drive unknownunknownunknownunknown

u2d09disk drive unknownunknownunknownunknown

u2d10disk drive unknownunknownunknownunknown

u2d11disk drive unknownunknownunknownunknown

u2d12disk drive unknownunknownunknownunknown

u2d13disk drive unknownunknownunknownunknown

u2d14disk drive FUJITSUMAP3735F SUN 140104Q07RVN

/:<2>fru stat

CTLRSTATUSSTATEROLEPARTNERPORT1PORT2TEMP

- - - ----

u1ctrreadyenabledmasteru2ctrreadyready31

u2ctrreadyenabledalt master u1ctrreadyready30

DISKSTATUSSTATEROLEPORT1PORT2TEMP VOLUME

- - --

u1d01readyenableddata diskreadyready23v0

u1d02readyenableddata diskreadyready26v0

u1d14readyenabledstandbyreadyready23v0

u2d01readyenableddata diskreadyready18v1

u2d02readyenableddata diskreadyready19v1

u2d03readyenableddata diskreadyready20v1

u2d04readyenableddata diskreadyready18v1

u2d05readyenableddata diskreadyready22v1

u2d06readyenableddata diskreadyready23v1

u2d07readyenableddata diskreadyready21v1

u2d08readyenableddata diskreadyready20v1

u2d09readyenableddata diskreadyready20v1

u2d10readyenableddata diskreadyready17v1

u2d11readyenableddata diskreadyready19v1

u2d12readyenableddata diskreadyready20v1

u2d13readyenableddata diskreadyready19v1

u2d14readyenabledstandbyreadyready24v1

[2764 byte] By [flogia] at [2007-11-27 11:04:48]
# 1

What state are the loop cards in?

The FRU stat information comes over the loop card interface and this can affect the information provided.

Have you tried disabling u1 to make u2 run as the active controller (remember to reenable u1 once u2 has managed the takeover :-)

I wouldn't recommend running this with the arrays in use...

--A.

andrew-nessa at 2007-7-29 13:04:18 > top of Java-index,Storage Forums,Storage General Discussion...
# 2

Andrew,

Thanks for your reply. The information on the loop cards is very helpful. Below is an output from the same data collection as above. As you can see the loop cards appear to be OK.

OOPSTATUSSTATEMODECABLE1HLB CABLE2HLB TEMP

- - --

u1l1readyenabledmaster-- installed110 33

u1l2readyenabledslave-- installed110 30

u2l1readyenabledmasterinstalled110 --32

u2l2readyenabledslave installed110 --30

We did try disabling and re-enabling the controllers as you suggested. We also powered down the array and reseated the controllers, but were unable to get the controller in tray 2 to report in. I suspect we may need to order a new controller.

K

flogia at 2007-7-29 13:04:18 > top of Java-index,Storage Forums,Storage General Discussion...