On 29 November 2011 10:22, prashant n <[email protected]> wrote: > Now suggest me on following things > > 1) What is the actual difference between generating traps by using DisMan > Event MIB and by using 'mib2c.notify.conf' configuration file ?
The code template generated by 'mib2c.notify.conf' will give you a routine that can be used to send a trap to the configured destinations. But it's then up to you to decide *when* to call this routine, and hence when to trigger the trap. i.e. this routine provides _half_ of the code needed to send the trap. It's purely concerned with how - not with when. The DisMan Event MIB handles both what trap to send, *and* when to do this. i.e. it handles both parts of the task. (It's also built into the agent, so you don't need to write any code yourself). > Only these two methods are there in net-snmp for trap generation ? The third approach (which may well be the easiest) is not to try and handle this within the agent at all. Consider writing an external client command (perhaps as a simple perl script), that queries the agent for the object(s) of interest, looks at the values returned, and issues a trap when appropriate. That's essentially what DisMan Event is doing - but embedded within the agent rather than as an external command. Writing this yourself would give you more control over exactly what conditions should trigger the trap. 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
