On 22 November 2011 11:39, <[email protected]> wrote: > Forget my application and consider a standalone netsnmp app. > Say, i am issuing an SNMPGET for "sysDescr.0" on a CISCO switch using SNMPv3.
I suspect that it is the use of SNMPv3 that is the issue here. Before the app can send an SNMPv3 request, it needs to know the engineID of the remote agent. It does this by querying the agent to discover its ID (either as part of opening the session, or sending the query) That query is done synchronously, so will hang if the agent is not responding. If the switch is configured to work with SNMPv1 or SNMPv2c, then consider using this instead. Those versions don't require the engineID, so won't do this preliminary query. Dave ------------------------------------------------------------------------------ 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
