False alarm?

 
easynet
Advisor

False alarm?

someone knows if the message of following error could be a false alarm like marked to this link?

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 a lot



message:

Problem Found: Failure diagnosis needed: NWI-SAN: An enclosure was found on Fibre Channel, but not on the CAB bus DP-1A at Fri 13 Nov 2009 14:42:24 GMT+01:00 ----------

Problem Report Times:
Event Time: Fri 13 Nov 2009 14:17:01 GMT+01:00
Report Time: Fri 13 Nov 2009 14:42:24 GMT+01:00
Expiration Time: Sat 14 Nov 2009 14:17:01 GMT+01:00

Managed Entity:
SANworks Management Appliance Name: xxxxxx
Controller Type: HSV100
Firmware Version: CR0A3E 3028
WWN & Storage System Name: xxxxxxxxx
Entitlement Information:
Product ID: xxxxxxxxxx
Serial Number: xxxxx


Service Obligation Data:

Service Obligation: Valid
Service Obligation Number: silent
System Serial Number: silent
Service Provider Company Name: Hewlett-Packard Company


Device Type:
EVA

Brief Description:
Failure diagnosis needed: xxxxxx: 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:
NWI-SAN

Full Description:
The HSV100 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.


BL ELC: If ISEE is enabled, an Event Log Collection (ELC) would
have been sent with this report. However, in this case it was
black listed. The date of the last ELC sent for this array was:
Fri 13 Nov 2009 12:20:39 GMT+01:00


Failed Component Type:
EAB

Recommended Action:
Investigate further - see evidence in Problem Report.


EMU in disk enclosure spare part:
EMU spare part = 375393-005



FRU List:
System Identification --
Storage System Name: xxxxxxxx
Storage System World Wide ID: xxxxxxxxxxx
OS Version: Windows 5.2 Service Pack 2 build 3790
Device Type: HSV
Logging Controller Serial Number: - NA - Requires CommandView V7.0 or higher
CommandView Version: - NA - Requires CommandView V7.0 or higher


Device Location:

Device Port Loop: DP-1A


FRU Location(s):
Device Location:
Storage System Name: xxxxxxxxxx
Storage System World Wide ID: 5000-1FE1-5002-5A50
Device Port Loop: DP-1A


Evidence:
Local Event Time : Fri 13 Nov 2009 14:17:01 GMT+01:00
Controller Report Time: 13-Nov-2009 15:07:58.576
EVA Log Description:
6 3e c5 13: 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 HSV100 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
Monitoring Unit is reporting an invalid enclosure number.

Sequence Number: 7629
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.


EMU in disk enclosure spare part:
EMU spare part = 375393-005

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

Loop Switch: No Loop Switch has been detected at this time
# like events in last 24 hrs: 4
Contributing Events:

Seq # Controller Report Time Local Event Time
~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7626 13-Nov-2009 15:07:58.576 Fri 13 Nov 2009 14:17:01 GMT+01:00
Device Port Loop: DP-1A Location (R-E): 0-5
Enclosure WWN: xxxxxxxxxx

7627 13-Nov-2009 15:07:58.576 Fri 13 Nov 2009 14:17:01 GMT+01:00
Device Port Loop: DP-1A Location (R-E): 0-3
Enclosure WWN: xxxxxxxxxx

7628 13-Nov-2009 15:07:58.576 Fri 13 Nov 2009 14:17:01 GMT+01:00
Device Port Loop: DP-1A Location (R-E): 0-6
Enclosure WWN: xxxxxxxxxxx

7629 13-Nov-2009 15:07:58.576 Fri 13 Nov 2009 14:17:01 GMT+01:00
Device Port Loop: DP-1A Location (R-E): 0-1
Enclosure WWN: xxxxxxxxxxxxxxxxxx



Notifications:
All


Analysis Mode:
Automatic


SEA Version:
System Event Analyzer for Windows V5.6 (Build 128)


WCC Version:
Web-Based Enterprise Services Common Components for
Windows V5.6 (Build 128), member of Web-Based
Enterprise Services Suite for Windows V5.6 (Build
128)
2 REPLIES 2
Rob Leadbeater
Honored Contributor

Re: False alarm?

Hi,

Have you done any VCS upgrades on the EVA recently ?

That advisory is applicable to the EVA4/6/8000 machines, not the EVA3000 which you have, however the same thing can happen during a VCS upgrade...

Cheers,

Rob
Víctor Cespón
Honored Contributor

Re: False alarm?

1) Firmware 3028 has been out of support for years, please update to 3110

2) Enclosures 1, 3, 5 and 6? In an EVA3000? That's not well set-up on the rack. No consequences probably, but the usual set-up is using 1, 2, 4 and 5.

3) The messages could indicate a short interruption on the loop, so the communication with all EMUs got interrupted. If you're doing a firmware update, as said above, that could explain it. If not, we'll need the full controller event log to see what happened around that time.