That depends on what is going on.  The message means that netmon is not
processing the traps that trapd is sending to him, probably because he is
busy doing something else.  When his queue gets full, trapd terminates his
connection, so that he himself does not wind up in an out-of-memory
condition.  If you have just restarted netmon then this may be entirely
normal, because he has to do all of his initialization and config checks
before he can process traps.  When he is done with his init stuff, he will
re-connect to trapd and start paying attention to the incoming trap flow.
If you have not just restarted netmon, then you may have a trap storm
problem or a netmon hang of some kind to investigate.  I would start with
the netmon trace and see what netmon is doing in that case, and call
Support if you need help.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



"Treptow, Craig" <Treptow.Craig AT principal DOT com>@tkg.com on 04/02/2001
10:04:51 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "NetView List (E-mail)" <nv-l AT tkg DOT com>
cc:
Subject:  [NV-L] Maximum number of events?





Hi.  We are running Netview 6.0.2 on AIX 4.3.3.  I just saw an event scroll
by with this message:

"netmon reached maximum number of outstanding events, disconnecting from
trapd"

The processes are still running, and things still appear ok.  Should I be
concerned?

Craig Treptow
Principal Financial Group
I/S Network Administration
(515) 247-6207