The number one cause of this symptom is a name resolution problem.  It
usually means that the nameserver for your NetView box has poor timeout
parameters or is handing off to another server, which hands off to another
and so on before timeout.  Every NetView trap conatins at least two IP
addresses to resolve into hostnames, and this resolution is repeated by
each daemon which handles the trap on its way to your event window.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Mogamat Kahaar <mogamat AT SNSCON.CO DOT ZA> on 11/25/98 02:29:11 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  Problems with Events





Note: Some recipients have been dropped due to syntax errors.
Please refer to the "$AdditionalHeaders" item for the complete headers.



Hi,

We are experiencing a few strange problems with the "events" in our
trapd.log as well as "events browser". When I simulate an event using the
snmptrap command it takes about 1/2 hour before it is visible in the
trapd.log. The simulation is run on the same box. When I unmanage an object
on the ipmap for example, an event is immediately visible in the trapd.log.
I have tested the same  snmptrap command to another Netview 5.0 box and it
almost immediately appeared in the trapd.log as well as the events browser.
It also takes a awhile before the events in the trapd.log appear in the
events browser.

The machine is running Netview 5.0, Framework 3.6 and AIX 4.2.1. It also
has Ciscoworks and Optivity installed.

Any ideas are welcome ???? Do I need to load a patch or are there a few
configuration parameters I need to change ???

Thanks a million in advance.

Regards

Mogamat