Re: Max # of Outstanding Pings in netmon

1999-06-07 23:18:32
Subject: Re: Max # of Outstanding Pings in netmon
From: Leslie Clark <lclark AT US.IBM DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 7 Jun 1999 23:18:32 -0400
That's news to me. I've always told customers it's 10 and not
to worry about it. Inflation?

 Regarding detailed documentation of netmon, I am of the opinion
that it has gotten so complex that no one really knows for sure any
more how it works. It has evolved into behaviors that you can observe
and make use of. Only partly kidding. The Diagnostics manual
is pretty good, but is aimed at telling you how to gather trace data
to send in to support. The trace data is not documented, but you
can get good clues from it.


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

Hello everyone,

It appears that the outstanding ping limit (undocumented "-q") parameter
is now defaulting to 16 at NV5.1.  Years ago the release notes stated it
had been increased from 3 to 10, but I haven't seen any mention of it
since then. Can anyone confirm or deny this (ie: Leslie Clark :-)?
I am seeing this by running netmon -a5 and seeing the # elements on
pingWait maxing at 16 (half the net was down at the time).

Aside - anyone know of any good reference material on detailed
functioning/debugging of netmon that you could point me to?

Thanks a lot.

Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada

<Prev in Thread] Current Thread [Next in Thread>