|Subject:||RE: [nv-l] Status Polling|
|From:||"Evans, Bill" <Bill.Evans@hq.doe.gov>|
|Date:||Fri, 24 Jun 2005 16:49:45 -0400|
|Delivery-date:||Fri, 24 Jun 2005 21:50:51 +0100|
Your description was much clearer than mine.
"NetView compensates by its geometrically increasing waits on retries"
Translation: "Every retry doubles the timeout value" = "a geometric progression".
The NetView for Administrators class also used to warn attendees not to set the retries and wait time so high that the total exceeded the polling cycle. Your example of 7 retries with 1 second timeout would exceed a two minute polling cycle. NetView Administration is not for the arithmetically challenged or those who don't appreciate the relationships among the tuning values.
Thanks for clearing up my muddy wording.
One warning about retries.
Each time you retry, the SNMP or ping, netmon appears to double the
If you have a lot of nodes this way, that can cause more issues than it
One caveat, I've been doing TEC/Framework/ITM for a while so the way
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||RE: [nv-l] Status Polling, Barr, Scott|
|Next by Date:||Re: [nv-l] Managing Layer-3 Switches with Switch Analyzer, Michael Webb|
|Previous by Thread:||RE: [nv-l] Status Polling, Barr, Scott|
|Next by Thread:||RE: [nv-l] Status Polling myth, Leslie Clark|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web