Insight Remote Support
1752353 Members
5394 Online
108787 Solutions
New Discussion юеВ

RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

 
SOLVED
Go to solution
Charles Ooi Chia Lun
Occasional Advisor

RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

Dear all,
We got installed ISEE,WEbes & Osem. 2-3 weeks ago, 1 hard disk spoilt at the Eva3000 enclosure 4 but it couldn't trigger the ISEE to send out any alert to the intended person that the disk is down. We went to ISEE site and see the open incident, all the simulated test is there. That's means tested working but 3 das ago, the same eva3000 enclosure 0 emu down but it sent an email from isee@hp.com to the intended person that the eva3000 got problems. Please advise your idea / suggestions. Thank you very much.
5 REPLIES 5
Liem Nguyen
Honored Contributor

Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE


Hi,

This issue would require intensive troubleshooting to find out which application (ISEE, OSEM, WEBES) failed within the process. I would reccommend you to call HP Support Center to work on the issue.
R.KrishnaKumar
Frequent Advisor
Solution

Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

Hi Charles,

In the WEBES, might be a filter is set to supress the events related to disks. So please check the filtering rules set in the WEBES.

regards,
Krishna
Charles Ooi Chia Lun
Occasional Advisor

Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

how to check the filtering rules ? mind to share with me the steps? thank you.
Maurice Skubski_1
Valued Contributor

Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

we had the same issue here for one cu. it seams that if he stopps and start commandview again, webes crashed. after reboot it worked again. there is a open case for this but till now no sollution!
R.KrishnaKumar
Frequent Advisor

Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE

Hi Charles,

If you are using webes 4.4.1 or 4.4.2 it is better to upgrade to 4.4.3. As 4.4.1 has known issue,

1.where it doesnot report the failure of disk.

Regards,
Krishna