Re: is it possible to integrate an Net SNMP sub agent(.dll) with Microsoft SNMP service ?

--0-901479625-1118832529=:91783
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

So in that case , You are saying if we can implement MS-specific) SNMP
Extension API functions to develop the Sub agent DLL , even though it is using mib2c generated code, it should work .
is it right ?
Thanks
Mamon


Dave Shield <D.T.Shield@csc.liv.ac.uk> wrote:
On Wed, 2005-06-15 at 11:11, mahua dutta wrote:
> But Dave, All the SNMP data is in TLV(ASN.1) format. That is why third
> party clients(like snmpwalk, getif) are able to connect to snmp
> service and able to read those datas.-- If I am not wrong.

You are not wrong.
But that covers the management-client-to-agent interface.
You were asking about the agent-to-MIB-module interface,
which is not standardised, and doesn't typically use ASN.1.


> So If we use mib2c tool to generate the code template(which uses
> Net-snmp api's) and to integrate with the Snmp service if we
> implement SNMP Extension API Functions, It should work.
> Do you forsee any issue?

Yes.
The Net-SNMP agent does *NOT* implement the (MS-specific) SNMP
Extension API functions. It implements the industry standard
Agent Extensibility API (AgentX).

Dave



---------------------------------
Yahoo! Mail
Stay connected, organized, and protected. Take the tour
--0-901479625-1118832529=:91783
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>So in that case , You are saying if we can implement MS-specific) SNMP<BR>Extension API functions&nbsp; to develop the Sub agent DLL , even though it is using mib2c generated code, it should work .</DIV>
<DIV>is it right ?</DIV>
<DIV>Thanks </DIV>
<DIV>Mamon</DIV>
<DIV><BR><BR><B><I>Dave Shield &lt;D.T.Shield@csc.liv.ac.uk&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">On Wed, 2005-06-15 at 11:11, mahua dutta wrote:<BR>&gt; But Dave, All the SNMP data is in TLV(ASN.1) format. That is why third<BR>&gt; party clients(like snmpwalk, getif) are able to connect to snmp<BR>&gt; service and able to read those datas.-- If I am not wrong.<BR><BR>You are not wrong.<BR>But that covers the management-client-to-agent interface.<BR>You were asking about the agent-to-MIB-module interface,<BR>which is not standardised, and doesn't typically use ASN.1.<BR><BR><BR>&gt; So If we use mib2c tool to generate the code template(which uses<BR>&gt; Net-snmp api's) and to integrate with the Snmp service if we<BR>&gt; implement SNMP Extension API Functions, It should work.<BR>&gt; Do you forsee any issue?<BR><BR>Yes.<BR>The Net-SNMP agent does *NOT* implement the (MS-specific) SNMP<BR>Extension API functions. It implements the industry standard<BR>Agent Extensibility A
PI
(AgentX).<BR><BR>Dave<BR><BR></BLOCKQUOTE><p>
<hr size=1>Yahoo! Mail<br>
Stay connected, organized, and protected. <a href="http://tour.mail.yahoo.com/mailtour.html">Take the tour</a>
--0-901479625-1118832529=:91783--


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders