Interesting numbers. I wonder how much of the traffic increase has to do
with
the big changes in discovery and seedfile processing. I know one cause for
netmon failures is fixed in 5.1.1, the kind you get when you try to do
multiple
demand polls. I'm still seeing occasional failures, though I have not taken
the
time to investigate them. There is a trap generated when it dies, however,
if you want to just automate the restart of it in Event Configuration..

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager


---------------------- Forwarded by Leslie Clark/Southfield/IBM on 03-18-99
11:18 PM ---------------------------


Schiffinger Ralph 2100 <Ralph.Schiffinger AT ERSTEBANK DOT AT> on 03-12-99
12:07:00 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: Leslie Clark/Southfield/IBM)
Subject:  NV 5.1 netmon observations





Dear netmon-colleagues,
since migration from NV4 to NV5.1 my netmon-life has changed.
Fact: network-load produced by netmon has increased (NV4 avg. 30
packets/sec,
NV5.1 avg. 50 packets/sec)
Fact: network-load produced by netmon more often peaks out (150 packets/sec
and more) under NV5.1
Fact: ovsnmp.conf has become a highly delicate playground
Fact: netmon under NV5.1 dies more often than under NV4 (especially if
stopped and restarted with hundreds of nodes down)
Fact: running a script every 10 minutes and (besides other stuff) checking
if
netmon is still alive (and restarting it if necessary) was just a neat idea
under NV4, but has become a necessity under NV5.1
Any kind of consolation and/or advice welcome.
Thanks for listening, Ralph.
iT-AUSTRIA / OE2100 / TK-NET
Tel.    +43 1   21717   58948
FAX     +43 1   21717   58979
Mobil           0664    1908469
Mailto:Ralph.Schiffinger AT erstebank DOT at