Disk Enclosures
1752807 Members
5805 Online
108789 Solutions
New Discussion юеВ

Re: EVA 8000 Warning

 
SOLVED
Go to solution
Hasan_9
Regular Advisor

EVA 8000 Warning

Hello,
I have got the following warning on the first Enclosure of my 2C18D. I disconnected the EVA cab cable and connect it aggain and problem solved but after 24 hours the warnng came back. What should I do?

Sincerely,
Alireza Naderi

Event Code: 0d828e11 Severity: Warning
-- not failed but attention recommended or required.
A drive enclosure's address is incorrect or the enclosure has no address.
5 REPLIES 5
Steven Clementi
Honored Contributor
Solution

Re: EVA 8000 Warning

What version of XCS are you running?

Last I was told, there is a know issue with this in the current XCS and that it is NOT critical. To fix (more like eliviate), you simply reseat the cable or the I/O card.


I would still call HP if it keeps happening and have them replace the I/O module just to be safe.


Steven


Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
Hasan_9
Regular Advisor

Re: EVA 8000 Warning

XCS version is 5.1

I have 12 Enclousre on this array, but just Enclosure #1 has this problem.
Steven Clementi
Honored Contributor

Re: EVA 8000 Warning

Right. The issue, as confirmed by HP several months ago was ONLY with Enclosure 1. I have seen this issue at 3 of my customers so far.

Some live with it, some call for replacements.



Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
Hasan_9
Regular Advisor

Re: EVA 8000 Warning

Thank you Steven,
Could you please let me know where can I read about this bug? Does HP offer a fix for the bug? Is there any document for this issue?


Steven Clementi
Honored Contributor

Re: EVA 8000 Warning

Currently, I do not think there is a Customer Advisory though I could be mistaken. Last I talked with HP about this it was a new issue they were working on.

The issue stems from the XCS and only an XCS update would fix it. Whether or not it was fixed in 5.110 or 6.x, I am not sure. I do know that I have 1 customer at 5.110 and was experiencing the problem so it probably not fixexd in 5.110.


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)