I created a private MIB with many parameters. Some of them are read-only (they represent the status of the machine), other are read-write (user settings) parameters. I defined some notifications for very important events: alarms, change of core settings and so on.
Now I'd like to have an agent that sends a notification for *each* parameter: if an alarm occurs, if the user change a setting (even through SNMP SET) and so on. The only approach I know is to define in the MIB a different NOTIFICATION-TYPE for each parameter, so I'll have a MIB composed by two main trees: one for the parameters and the second for the related notifications. Is this approach good? Sincerely I don't like it: everytime I add a parameter in the MIB, I have to add a related notification. Can you suggest a better approach? Maybe defining a generic trap related to a parameter change? In this case, I can add to this generic notification a "service parameter" with an OID value: the OID will be the parameter that has changed. But how can I add the new value of the parameter in a generic way (it could be an integer, an octet string and so on). ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
