Ok, When i send Inform without discovery ( i.e the NULL EngineID ), the net-snmp internally send snmp GET to the secondary Manager. This SNMP get is also blocking. The idea behind sending an explicit GET request is to know the EngineID in advance before sending the inform. In my application i dont want the snmp thread to be blocked for the response coming from the secondary Manager.
Dave Shield wrote: > On 31 March 2010 05:49, Manjit <[email protected]> wrote: > >> I am running snmpd agent as a thread with some primary manager. >> As a result of some actions agent gets a list of secondary managers IP >> Address( But we dont know the engineID), >> and we need to send informs to these managers. >> > > I believe that the Net-SNMP library should attempt to discover the engineID > automatically. You shouldn't need to prime this by sending GET requests > explicitly. > > What happens if you suppress sending the GET requests to the secondary > managers? > > Dave > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
