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 .
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 <[EMAIL PROTECTED]> 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 A PI (AgentX).
Dave
Yahoo! Mail
Stay connected, organized, and protected. Take the tour
