topic Re: Repeated EMS Event Code=199 in syslog. in Operating System - HP-UX

Repeated EMS Event Code=199 in syslog.

Rajesh SB — Thu, 06 Oct 2005 05:51:06 GMT

Hi Experts,
One of our server is started logging below messages repeatedly.

But, I didn't find any h/w connected at Address=0/9/0/0.8.0.255.6.14.0 & Hardware Address=0/0/1/1.2.0 but even getting the messages.

Any pointers on this. Also verified the health of h/w using "stm", everything seems green.

*********************************************
Oct 6 16:01:39 ismuxa24 syslog: CRITICAL Event Code=199; Description=Lost connection to host.; Unkn
own FRU Location; Hardware Address=0/9/0/0.8.0.255.6.14.0; Unknown Vendor ID; Unknown Model ID; Unkn
own Product S/N; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/Re
moteMonitor.htm#199
Oct 6 16:01:39 ismuxa24 EMS [2938]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" fo
r Resource: "/StorageAreaNetwork/events/SAN_Monitor/DiskArray" (Threshold: >= " 3") Execute
the following command to obtain event details: /opt/resmon/bin/resdata -R 192544769 -r /StorageAre
aNetwork/events/SAN_Monitor/DiskArray -n 192545163 -a
Oct 6 16:01:52 ismuxa24 syslog: CRITICAL Event Code=199; Description=Lost connection to host.; Unkn
own FRU Location; Hardware Address=0/0/1/1.2.0; Unknown Vendor ID; Unknown Model ID; Unknown Product
S/N; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor
.htm#199
Oct 6 16:01:52 ismuxa24 EMS [2938]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" fo
r Resource: "/StorageAreaNetwork/events/SAN_Monitor/DiskArray" (Threshold: >= " 3") Execute
the following command to obtain event details: /opt/resmon/bin/resdata -R 192544769 -r /StorageAre
aNetwork/events/SAN_Monitor/DiskArray -n 192545164 -a
*********************************************

Thanks in advance.

Regards,
Rajesh

Re: Repeated EMS Event Code=199 in syslog.

Luk Vandenbussche — Thu, 06 Oct 2005 05:55:04 GMT

Hi,

Do you see al the disk.
Â° ioscan -fnC disk
Â° bdf

This is the description of event 199

Event 199

Severity: Critical
Event Summary: Lost connection to host.
Event Description: No longer able to communicate with the host.
Probable Cause/ Recommended Action: Verify device is properly connected to host

Re: Repeated EMS Event Code=199 in syslog.

Rajesh SB — Thu, 06 Oct 2005 06:35:19 GMT

Hi Luk,

I verified against all the attached devices.
Strange to see this log message.

How can I stop this irrelevent envents?
Any EMS configuration can need to do?

Regards,
Rajesh

Re: Repeated EMS Event Code=199 in syslog.

saju_2 — Thu, 06 Oct 2005 08:08:34 GMT

Hi Rajesh

U can delete some monitoring requests thorugh /etc/opt/resmon/lbin/monconfig. It is a menu driven interface.

Regards
CS

Re: Repeated EMS Event Code=199 in syslog.

Arunvijai_4 — Thu, 06 Oct 2005 08:27:29 GMT

Your server might have been connected to storage some time back. Now, it is disconnected. You can ignore this message as far as you are quite sure that not connected to any storage.

-Arun

Re: Repeated EMS Event Code=199 in syslog.

Andrew Merritt_2 — Thu, 06 Oct 2005 09:28:28 GMT

The event is being generated by CommandView SDM, and is just being reported by RemoteMonitor.

One possibility is, as already suggested, that you've disconnected some hardware, but CVSDM is not aware of this for some reason.

What version of OnlineDiags and CVSDM do you have? There were some problems that should be fixed in recent versions of both (e.g. 1.06 of CVSDM or later).

Andrew