On 22 November 2011 14:43, prashant n <prashant.n...@gmail.com> wrote: > Before i move to the problem with running sub-agent, i wanted to know > what is the main advantage of using sub-agent in comparison with compiling > MIB modules with the SNMP agent snmpd
The main advantage is with regard to deployment. If you have a sub-agent that implements a new MIB module, then you can install this sub-agent onto an existing system, and connect this to an already-running master agent. If the new MIB module is compiled directly into the snmpd agent, then you would need to stop the previously running agent, install the new agent binary/libraries, and then start the new agent. On a running system, this is significantly more disruptive. > Which one i need to follow compiling MIB modules with the SNMP agent? > or sub-agent creation? Please suggest me on this. When you are developing, it doesn't really matter. The MIB module code is the same for both cases. Personally, I tend to work with the new MIB module compiled into the agent binary itself, and then run that agent on a temporary, non-standard port. This doesn't touch the main active agent at all, which can continue serving information about the system, regardless of my testing/development/etc. It's only when the new MIB needs to be brought into service that I'd consider using a subagent. The other advantage of the subagent approach is that you can use this with *any* SNMP (master) agent - not just the Net-SNMP binary. 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 Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
