On Tue, 22 Nov 2011 12:33:23 +0000 Dave wrote: DS> On 22 November 2011 11:39, <[email protected]> wrote: DS> > Forget my application and consider a standalone netsnmp app. DS> > Say, i am issuing an SNMPGET for "sysDescr.0" on a CISCO switch using SNMPv3. DS> DS> I suspect that it is the use of SNMPv3 that is the issue here. DS> DS> Before the app can send an SNMPv3 request, it needs to know the engineID DS> of the remote agent. It does this by querying the agent to discover its ID DS> (either as part of opening the session, or sending the query) DS> DS> That query is done synchronously, so will hang if the agent is not DS> responding.
A synchronous request during an asyn call is obviously a bug. I've created a bug report for this: https://sourceforge.net/tracker/?func=detail&aid=3446148&group_id=12694&atid=112694 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
