On 17.02.21 15:48, Wes Hardaker wrote:
Harald Krammer <h...@hkr.at> writes:
If an SNMPv3 node is missing, the function is blocked.
What function is getting blocked? Anything in our library should return
with a timeout error just like v1/v2. Yes, the engineID won't be
retrievable but it shouldn't cause anything to hang indefinitely.
snmpv3_engineID_probe works synchronously. It takes approx. 6 seconds
per query on missing node (6 repetitions after waiting 1 s). This now
delays the query interval for snmpv3. The problem is now, if I query 150
nodes and e.g. 100 nodes are missing, then the query interval increases
to 600 seconds. The interval should stay at e.g. 60 seconds.
Unfortunately, this behavior is not accepted.
Running snmpv3_engineID_probe asynchronously is a solution, but it's not
that easy for me.
Nice greetings
Harald
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
