Using snmpdget with the -d option I found that Netview 6.0.3 follows the
same algorithm for increasing the timeout value as Netview 5.1.3. It
doubles the timeout with each retry.

--- Begin Message ---

Subject:	[nv-l] ovsnmp.conf timeoutInterval
From:	Robin James <robin.james AT thalesatm DOT com>
To:	NetView Discussion <nv-l AT lists.tivoli DOT com>
Date:	Thu, 02 May 2002 13:39:01 +0100

I am looking at the differences between Netview 5.1.3 and 6.0.3 for
ovsnmp.conf and the setting for timeoutInterval in particular.

In 5.0.3 when timeoutInterval is set to 4 the timeout is 0.4 seconds.
The timeout for the first retry is 0.8 seconds and for the second retry
is 1.6 seconds. The man page for ovsnmp.conf does not describe this
behaviour of doubling the timeout value with each retry but I know I
have read it somewhere.

In 6.0.3 the man page says:

       timeoutInterval The timeoutInterval field specifies the
(positive)
       number of one-tenth of a second before a first retry. The
timeoutIn-
       terval is calculated based on the response from the node. The
       timeoutInterval is increased if the node does not respond within
the
       time specified, or it is decremented if the node responds before
the
       timeoutInterval is reached.

What I would like to know is how the timeoutInterval is increased for
6.0.3. Is it the same as 5.1.3?

Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)

--- End Message ---