Let me guess...are you using HPOV 6.x? Since OV 6.x provides event correlation services, the trapd.log is disabled unless you manually enable it. To enable trapd.log in 6.x, edit the pmd.lrf file to read as follows:<br>
<br>
OVs_YES_START::-SOV_EVENT;t:OVs_WELL_BEHAVED:15

AUSE::<br>
<br>
The change is between the second and third colons, add:<br>
<br>
-SOV_EVENT;t<br>
<br>
----------------------------------------------------------<br>
Here is HP's explanation of this, found on page 25 of the OV 6.0 for UNIX Migration Guide:<br>
<br>
3.3 trapd.log Event Log<br>
<br>
NNM 6.0 provides a new binary event database that stores full ASN.1 SNMP trap notations (including all variable binding information). This new binary event database replaces the trapd.log file; however, NNM 6.0<br>
provides two methods to enable backward compatibility with trapd.log. A command line utility, ovdumpevents, allows you to take a snapshot of the binary event database and write the output to a file in trapd.log format.See the ovdumpevents(1M) reference page in NNM’s online help on Windows NT or the UNIX manpage for more information. If continuous output to trapd.log is required, you may modify the PMD Local Registration File (LRF) so that it contains the following line (changes in bold):<br>
<br>
OVs_YES_START::-SOV_EVENT;t:OVs_WELL_BEHAVED:15

AUSE::<br>
<br>
The trapd.log file will then be generated in addition to (not instead of) the event database. See the ov_event reference page in NNM’s online help on Windows NT or the UNIX manpage for more information. Generating the trapd.log file in addition to the event database requires space on your management station’s hard drive.<br>
----------------------------------------------------------<br>
<br>
After you enable trapd.log, you will be able to see if OV is even receiving the INFORMS you are sending. Also, since you have already imported the MIBs, you could configure those OIDs in the event configuration. If the events are getting into trapd.log but not displaying in the event browser, I would think the events are setup to "Don't Log or Display" in the event config. Take a look at that and let me know what you find. Hope this helps.<br>
<br>
Dave sends...