I'm not an NT wizard, but I understand what is happening to ovtopmd and to
snmpCollect. But I don't understand what is happening to trapd. Trapd
maintains a queue of events for every application which connects to him.
Ovtopmd, snmpCollect, and netmon are some of those that do. As traps come
in they are put on the each application's queue. If the application cannot
keep up with the processing -- traps are coming in too fast -- the queue
builds up. When it is full, traps will force off the laggard. The
messages here indicate that he has done so to ovtopmd and to netmon. But
trapd should still stay running. So why he is falling over, I don't know.
The application queue limit is configurable, at least in UNIX. Sorry, but
my NT box is unavailable at the moment, so I cannot verify that it is
configurable there also, but it should be. However, since you say that
server setup is not working for you, that may not matter. Apparently, you
have a large number of external traps flowing into your NT NetView. Can
you reduce that number by cutting back what your agents are sending? Your
event browser probably shows may agents sending you the same trap over and
over again.
I also note that you are on NT 5.0a. Since server setup is not working for
you at the level you have, why not migrate to NT 5.1? I know it works
there.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Deborah Stephenson <debbie_stephenson@UK.IBM.COM> on 12/02/98 12:06:40 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: t
Hi
We have a problem, in that every day (almost) trapd falls over.
We are on NetView 5.0a/NT, the error code in nv.log reads:
[ovtopmd] get socket error 10054: the other end of a socket was reset; an
application probably disconnected.
[ovtopmd] Lost connection to trapd.
[ovtopmd] gt socket error 10054: the other end of a socket was reset; an
application probably disconnected.
[snmpcollect] snmpcollect.exe.
we have looked up code 10054 on Microsoft TechNet, it's:
Windows socket error 10054, WASECONNRESET - connection reset by peer.
This is all the info. we can find. Has anybody seen this before?
What makes this worse is that the start the server option on NetView
5.0a/NT is
not working for some reason, and therefore we have to keep re-booting.
Any help would be appreciated.
|