EMS Reporting error

[Thayanidhi]

Hi,

In syslog i get this error every 15 minutes:
Apr 9 10:54:31 sapprd1 syslog: CRITICAL EventCode=199; Description=Lost
connection to host.; Unknown FRU Location; Hardware
Address=1/0/8/0/0.1.0.42.0.0.3; 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

This FCC adapter (/dev/td1) was physically connected to the HP Disk Array (VA7100)
and the assigned hardware address then was '1/0/8/0/0.1.0.42.0.0.3'. This
FCC adapter is now connected to the IBM Ultrium tape loader and has a
different hardware address (1/0/8/0/0.2.x.y.z). The system does not see
the hardware address (1/0/8/0/0.1.0.42.0.0.3) during boot up and yet it is
still logging errors in syslog. I think EMS may be still monitoring this
hardware address. the ioscan show NO_HW.
How to resolve this problem without rebooting?

Thanks in advance

T.Thayanidhi

[Stefan Farrelly]

Normally if you remove or add hardware you should reboot to stop things like this happenening, but if you really cant then you need to reconfigure ems to stop monitoring this path. You do this with the program;
/etc/opt/resmon/lbin/monconfig
and from here you can select a hardware path to not monitor, then restart the ems daemons.

[S.K. Chan · Accepted solution]

Follow the process (see my reply) in this thread and replace the hardware path accordingly.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x26265fe8b250d71190080090279cd0f9,00.html
After you've stop EMS from monitoring the path you should check if you got the latest OnlineDiag installed on your system. I've had similar issue with EMS and sometimes installing the latest OnlineDiag bundle helps. If all else fail give a call to HP.

[Steven E. Protter]

I have had similar, annoying error messages afer removing logical volumes on our disk array.

Booting doesn't even always solve the problem, and you might need to rmsf the drivers in /dev/dsk, because they just don't go away.

I'd like to see your syslog errors if different, because you may have an address conflict between the Ultrium device and the current disk setup.

SEP

[Andrew Merritt_2]

RemoteMonitor does not do much more than report events generated by CommandView, which is what is actually monitoring these devices.

Which version of CommandView do you have installed? There is a known problem where versions 1.04 and 1.05 can report this Event 199, and the answer is to install SDM CommandView 1.06.