An enclosure was found on Fibre Channel, but not on the CAB bus DP-1A

[Bob Firek]

Shortly after upgrading our EVA6100 from XCS 6110 to XCS 6220 I received the following alert from SIM:
Problem Found: Failure diagnosis needed: EVA01: An enclosure was found on Fibre Channel, but not on the CAB bus DP-1A at Mon 19 Oct 2009 15:38:33 GMT-04:00

I checked Command View and all systems are showing OK. I logged into the loop switches and do not see any errors. Has anyone seen this error before? The full alert is pasted below. Any help will be greatly appreciated.

Problem Found: Failure diagnosis needed: EVA01: An enclosure was found on Fibre Channel, but not on the CAB bus DP-1A at Mon 19 Oct 2009 15:38:33 GMT-04:00
Problem Report Times:
Event Time: Mon 19 Oct 2009 15:14:57 GMT-04:00
Report Time: Mon 19 Oct 2009 15:38:33 GMT-04:00
Expiration Time: Tue 20 Oct 2009 15:14:57 GMT-04:00


Managed Entity:
SANworks Management Appliance Name: 732-mgmt-30333
Controller Type: HSV200
Firmware Version: CR1363 6220
WWN & Storage System Name: 5000-1FF1-500D-5C00 EVA01
Entitlement Information:
Product ID: AD556C
Serial Number: 2SXXXX14FY

Service Obligation Data:
Service Obligation: Valid
Service Obligation Number: 2SXXXX14FY
System Serial Number: 2SXXXX14FY
Service Provider Company Name: Hewlett-Packard Company


Device Type:
EVA
Brief Description:
Failure diagnosis needed: EVA01: An enclosure was found on Fibre Channel, but not on the CAB bus DP-1A
Rule ID:
HSV_FCS_Rule -- V 1.14 Event Code: (06 3E C5 13)
Rule Severity:
Warning
Reporting Node:
EVA01
Full Description:
The HSV200 controller has detected one or more enclosures
on the Fibre Channel but is unable to communicate with the EMUs
on the CAB bus. Or, the EMUs are reporting invalid enclosure
numbers. The Storage System and device port loop are reported
in the FRU list. A summary of the events is reported in the
Evidence section.


ELC: If ISEE is enabled, an Event Log Collection (ELC) was sent
with this report.

Failed Component Type:
EAB
Recommended Action:
Investigate further - see evidence in Problem Report.


FRU List:
System Identification --
Storage System Name: EVA01
Storage System World Wide ID: 5000-1FF1-500D-5C00
OS Version: Windows 5.2 Service Pack 2 build 3790
Device Type: HSV Controller
Logging Controller Serial Number: PBA24F19SVL0AC
CommandView Version: 8.00.02.080909
Is Storage System RoHs: YES (replace w/ RoHs parts)
The XCS controller is a CR2 type


Device Location:

Device Port Loop: DP-1A

FRU Location(s):
Device Location:
Storage System Name: EVA01
Storage System World Wide ID: 5000-1FF1-500D-5C00
Device Port Loop: DP-1A

Evidence:
Local Event Time : Mon 19 Oct 2009 15:14:57 GMT-04:00
Controller Report Time: 19-Oct-2009 14:13:35.068
EVA Log Description:
063ec513: CAC=c5 - Fibre Channel Services Physical
Disk Drive/Mirror Port/Drive Enclosure Environmental
Monitoring Unit Error summary. Summary of errors encountered
while attempting to access a physical disk drive, the
mirror port, or a Drive Enclosure Environmental Monitoring
Unit. The HSV200 controller has detected an enclosure
on the Fibre Channel but is unable to communicate with
the Drive Enclosure Environmental Monitoring Unit on
the enclosure address bus or the Drive Enclosure Environmental

Sequence Number: 87
Rule#: HSV_FCS_Rule -- V 1.14 Event Code: (06 3E C5 13)

Full Corrective Action Statement:
Check enclosure address bus cable connections between Drive
Enclosure EMU and nodes. If cabling is not the problem, the
node or Drive Enclosure EMU may need to be replaced.

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

Loop Switch: A Loop Switch has been detected.
NOTE: The back end switch is a 30-10022-01 loop switch.
# like events in last 24 hrs: 16
Contributing Events:

Seq # Controller Report Time Local Event Time
~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-2
Enclosure WWN: 5005-08B3-006A-85C6

57 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-3
Enclosure WWN: 5005-08B3-006A-8870

58 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-4
Enclosure WWN: 5005-08B3-006A-861D

59 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-1
Enclosure WWN: 5005-08B3-006A-8591

84 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-3
Enclosure WWN: 5005-08B3-006A-8870

85 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-4
Enclosure WWN: 5005-08B3-006A-861D

86 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-2
Enclosure WWN: 5005-08B3-006A-85C6

87 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:12:48 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-1
Enclosure WWN: 5005-08B3-006A-8591

56 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:14:56 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-2
Enclosure WWN: 5005-08B3-006A-85C6

57 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:14:56 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-3
Enclosure WWN: 5005-08B3-006A-8870

58 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:14:56 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-4
Enclosure WWN: 5005-08B3-006A-861D

59 19-Oct-2009 14:07:35.467 Mon 19 Oct 2009 15:14:56 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-1
Enclosure WWN: 5005-08B3-006A-8591

84 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:14:57 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-3
Enclosure WWN: 5005-08B3-006A-8870

85 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:14:57 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-4
Enclosure WWN: 5005-08B3-006A-861D

86 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:14:57 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-2
Enclosure WWN: 5005-08B3-006A-85C6

87 19-Oct-2009 14:13:35.068 Mon 19 Oct 2009 15:14:57 GMT-04:00
Device Port Loop: DP-1A Location (R-E): 0-1
Enclosure WWN: 5005-08B3-006A-8591


Notifications:
All

Analysis Mode:
Automatic

SEA Version:
System Event Analyzer for Windows V5.5 Patch1 (Build
61)

WCC Version:
Web-Based Enterprise Services Common Components for
Windows V5.5 Patch1 (Build 61), member of Web-Based
Enterprise Services Suite for Windows V5.5 Patch1
(Build 61)

[Uwe Zessin · Accepted solution]

> Shortly after upgrading our EVA6100 from XCS 6110 to XCS 6220

... the controllers start loading new firmware into each disk drive enclosure's EMU. You can watch the process on the 7-segment display: it shows "ld" and the current progress in percent.

Give the EVA some time to settle, even after the load has finished.

[Viveki]

Hi

Check whether the CAB cable is properly attached to the disk enclosures EMU properly.
Also check the Disk Enclosure EMU's LCD (rear side)and ensure every enclosure got a valid ID. If any enclosure ID is not proper, remove and re-attach that EMU module online and check.

[Víctor Cespón]

Events 063ec513 after updating to XCS 6220 are a known issue. Cannot provide you many details since the advisories are not public, but it's documented inside HP and the support people on your country should be able to locate the advisories.

These events do not indicate any failure and there are some workarounds that can be tried.

[ALCS]

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01914371&dimid=1006920700&dicid=alr_oct09&jumpid=em_alerts/us/oct09/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts

It's public advisory as of yesterady...

Whart did you do so far?

NB:I need to do such update next week - I'm reluctant now.

Regards,
Farid

[AWilliams_1]

I've upgraded 7 8000/8100 in the last few weeks and everyone has shown that error in the event log immediately after the upgrade. Not one of them continues to show the error, so I think it is just a transitory error as the firmware on the shelves is updated.
FYI: Another problem that I have had on a number of the upgrades is that the events stop logging. To fix you have to stop CV, rename the Programfiles\sanworks\hsv...\cache\ folder to ....WWN.old then restart CV.

[Bob Firek]

Farid,

Uwe Zessin, vcespon, and Allan Williams are correct. I believe the EMUs were still updating when I tried to run the disk dirve update. Even thought the upgrade came back as completeted I when right into runing the disk dirve update instead of letting the array sit and spin for awhile. Actually I had ran the disk drive update prior to running the XCS upgrade so none of the drives needed updating anyway. (Got my pre and post to-dos crossed. D'oh!)

This error has not reoccured since the XCS upgrade. This is the first time I read the Customer Advisory you posted in the link above. I did not perform any of the mentioned workarounds and my array has not thrown any alerts since then.

I'm not sure what to think about this advisory but I have to admit that the workarounds suggested by HP is a little disconcerting. I'm glad I didn't see this advisory before my upgrade or I would have second thoughts too. Ignorance is bliss they say.

[Javier Dominguez]

Hi,

I am getting the same issue. I am not upgraded to XCS 6.220 yet.

May I follow this process on-line, with the controllers having I/Os requests?

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01914371&dimid=1006920700&dicid=alr_oct09&jumpid=em_alerts/us/oct09/all/xbu/emailsubid/mrm/mcc/loc/rbu_category/alerts

Thanks.
Best regards,
Javier.