The two notes below got me asking questions about this more rapid netmon -y
function which was reported. The fact is that nothing in that code path was
changed. The Level 3 folks who work on netmon are mystified as to what could be
causing this much improved result. All we can suggest is that this is an
unintended result of fixing some other bug, but we don't even know what that one
might be. As far as we know, it was not noticed in Verification. Are you
sure you just didn't get your DNS or IP routing problems fixed and that caused
this improvement?
Puzzled,
James Shanks
Tivoli (NetView for UNIX) L3 Support
Stefan.Beck AT HVBINFO DOT COM on 10/26/99 03:25:17 AM
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: James Shanks/Tivoli Systems)
Subject: AW: 5.1.2 and netmon -y improved
I've also been astonished, that netmon -y is so fast in discovering new
nodes (in V5.1.2).
We're using several NetViews, and all show up the same improvement. Our
seedfiles contain about 8000 nodes ...
Regards
Stefan Beck
> -----Urspr
üngliche Nachricht-----
> Von: Leslie Clark [SMTP:lclark AT US.IBM DOT COM]
> Gesendet am: Dienstag, 26. Oktober 1999 04:36
> An: NV-L AT UCSBVM.UCSB DOT EDU
> Betreff: 5.1.2 and netmon -y improved
>
> For those of you who have heard me express the opinion that netmon -y
> was good for getting netmon to reconsider the rules in a seedfile, but not
> real good at forcing the discovery of explicitly listed new nodes; that
> that
> usually took a stop/start.... I've put 5.1.2 on at 4 different customer
> sites
> so far, and it sure looks like it is working a lot better! Just add the
> list,
> netmon -y, and within seconds it starts finding those nodes. Either I have
> been doing something wrong all along, or something got fixed. I take it
> all back. How nice not to wait through that startup configuration poll!
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
|
