It means that you have so many devices in your network sending traps in, at
such a rate, that snmpCollect cannot process them quickly enough to keep
his queue in trapd's storage below the maximum. When this happens to any
daemon, trapd forces him off, his queue of traps is flushed, and he has to
re-connect. Some daemons will, some won't, and those that don't may die.
I don't know off hand what snmpCollect does.
But to fix it, you need to either reconfigure your agents to send fewer
traps or you can increase the default buffer queue size for trapd (this is
the -B option). You can do this from the Framework context menu (right
click on the NetView box icon and select Configure --> Set options for
daemons --> event and trap processing daemons).
You want to increase the Application queue buffer size. The default is
500; you try say 2000, as a starter. This increases everybody's queue so
trapd's memory requirement goes up.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Wouter de_Bruin <W.M.de.Bruin@DNB.NL> on 03/18/99 02:01:25 AM
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: snmpCollect
Hi all,
What exactly does the following message in the Netview Events log mean:
snmpCollect reached maximum number of outstanding events. Disconnecting
from trapd.
removing outstanding events from snmpCollect event queue.
I do quite a lot of data collections, and am concerned that something is
going wrong somewhere, and I might lose data. Don
´t want that...;-)
Thanks
Wouter de Bruin
Network Consultant
De Nederlandsche Bank
Externe E-Mail wordt door DNB niet gebruikt voor het aangaan van
verplichtingen
Any e-mail messages from The Nederlandsche Bank are given in good faith but
shall not be binding nor shall they be construed as constituting any
obligation on the part of the Bank
|