On 22 June 2011 09:54, Giuseppe Modugno <[email protected]> wrote:
> I think DisMan Event MIB has the purpose to allow the user to completely
> customize the OIDs to monitor and the conditional expressions that trigger
> notifications.
> In my case, I don't want to give the user this flexibility.
Then don't.
It would be perfectly possible to hardcode a suitable "monitor" entry,
that would provide the necessary monitoring, without allowing the final
user to change this.
I'm suggesting that you use the *functionality* of the Event MIB support,
rather than re-implementing this yourself. You might as well start with
what's already in place - experiment with this yourself.
> Moreover the conditional expressions are very complex so the facility of
> DisMan Event would be too limiting.
Can you expand on this, please.
> I have the following objects defined in myMIB:
> myV1 OBJECT-TYPE
> SYNTAX Integer32
> UNITS "V"
> MAX-ACCESS read-only
> STATUS current
> DESCRIPTION "First voltage"
> ::= { myMIB 1 }
> myV2 OBJECT-TYPE
> SYNTAX Integer32
> UNITS "V"
> MAX-ACCESS read-only
> STATUS current
> DESCRIPTION "Second voltage"
> ::= { myMIB 2 }
> ...and so on.
First question - how many voltages will there be?
Could this ever change? (Perhaps with different hardware)
Why are you using individual scalar objects rather than a table?
Dave
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
