topic Re: RE: One hard disk failed at Eva3000 but couldn't notify by ISEE in Insight Remote Support

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

Charles Ooi Chia Lun — Sun, 04 Dec 2005 00:05:52 GMT

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.

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

Liem Nguyen — Wed, 07 Dec 2005 07:51:59 GMT

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.

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

R.KrishnaKumar — Sat, 10 Dec 2005 01:09:33 GMT

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

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

Charles Ooi Chia Lun — Sat, 10 Dec 2005 05:14:12 GMT

how to check the filtering rules ? mind to share with me the steps? thank you.

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

Maurice Skubski_1 — Fri, 16 Dec 2005 04:28:25 GMT

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!

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

R.KrishnaKumar — Thu, 22 Dec 2005 17:09:23 GMT

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