On 10 March 2010 10:23, Alexander King <chenyapu1...@qq.com> wrote:
> But I can hardly got you "use the DisMan Event MIB" exactly meaning,
>How do I implement this? Write the config info into the snmptrapd.conf file?
Yes.
> Just like:
> monitor -o prNames -o prErrMessage "process table" prErrorFlag != 0
> and I do this:
> monitor -o uitUPSNames -o uitUPSErrMessage " UPS failed! "
> uitUPSErrorStatus != 1
That looks about right, yes.
> Whether one trap object can send the different information? Such as,one
> value get from the sensor higher or lower than the set value,then the trap
> can notify the difference(that is to say one trap identifier,but send
> different information.).
Monitoring values using the DisMan Event MIB will generate the same basic trap
(mteTriggerFired) containing a standard set of values. These including:
- the name of the trigger entry (" UPS failed! )
- the OID instance that triggered the notification (uitUPSErrorStatus.{N})
- and the value of this instance
The trap can also include additional varbinds, such as uitUPSNames.{N}
and uitUPSErrMessage.{N} shown above.
I'm not sure whether that answers your question.
Dave
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
