Hi,

 

> I suspect that it is the use of SNMPv3 that is the issue here.

 

That indeed was a problem with SNMPv3.

Thanks for the reply.

 

I tried by giving the engine id as a session parameter itself and it
returned immediately.

So that solves the problem. No blocking :) 

 

But it created a new one. 

I used to understand whether the "snmp_async_send" was successful or
not, by looking at its return value.

Now it returns a "non-zero value" regardless of success or failure.

Is there any other way to understand the success/failure status of this
function?

Can this error be captured in the call-back function, by any trick?

 

And one more thing.

Can you please explain why the call-back function  is triggered twice in
the successful "snmp_async_send".

First one is shows as "SNMP_MSG_REPORT"

While second one is the correct "SNMP_MSG_RESPONSE"

 

Thanks and Regards,

Basil Joseph.

 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 

 

> 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

Reply via email to