Feroz writes:
> For a given MIB, our container_load function takes 2 seconds, but
> still the snmpwalk (v2) command times out with default values (5
> retries with 1 sec delay between each retry).
The others have stated this already, but one additional point: it's not
just the port and address t
Hi Patrik,
My response has two parts.
*Part 1:*
In the following tcpdump I see the same source port being used by the
client i.e 39813 for all the get-next requests.
Moreover the agent has responded approximately at the 4th second i.e at
12:10:25.862408.
So, the 6th GetNextRequest should have wor
Hi,
The default setup with 5 retries and 1 second delay would work if the
function works across requests. My guess is that the third request cannot
use the data from the first request.
The timeline would be something like (with a second gap between each line)
T0 - Request #1 - function #1 starts
Hi,
We are using net-snmp 5.8.
We have Agent-SubAgent model.
For a given MIB, our container_load function takes 2 seconds, but still the
snmpwalk (v2) command times out with default values (5 retries with 1 sec
delay between each retry).
My question is, why does it time out, though the container_
On 20 October 2011 08:15, Franco, Battista
wrote:
> I want to get info from my UPS.
> I copied XUPS-mib.txt (file attached) into folder C:\usr\share\snmp\mibs
> But when I ran snmpget or snmpwalk (see attached error.jpg) there’s timeout
> error.
Have you tried specifying the version/community exp
