You have a name resolution problem. One or more of the devices sending you
traps is not in your DNS and your DNS timeout is too high. I have looked
at many of these problems and the answer is always the same: Fix your DNS.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Rama, R. (Reggie)" <ReggieR@NEDCOR.CO.ZA> on 10/08/98 02:58:43 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: FW: Delay in displaying traps in nvevents
Hello Everybody
I am having this problem and I wanted to know if anybody else as had a
similar problem and how they went about resolving it.
I am receiving traps from nodes/agents and these are being logged in
trapd.log but the I have a bit of a delay before these traps are displayed
within the nvevents control desk. Within this events desk, I am using the
default ruleset (forwardall.rs). This time delay differs .i.e. sometimes it
is displayed almost immediately and at other times, there is a long delay.
Also, it seems that after some counter expires/times out, all these traps
are then forwarded to nvevents.
Thanks in advance.
Reggie Rama
Nedcor IT, S.A
|