RE: setEvent

> 2009/8/26 Michal Filka <[email protected]>:
> > I repeat monitor and event definition, to be clear.
> > setEvent                setActive       <MIB>::test = 4321
> > monitor -e setActive    -r 60 "SetMonitor"   <MIB>::test2 >= 1234
> 
> That's actually the opposite of the config fragment you posted originally.
> (But makes more sense).
... it's possible. I edited the code a bit to make it shorter, possibly I swapped these names.
> 
> I can't immediately spot what might be going wrong.
> I suspect you may need to run the agent under a debugger,
> set a breakpoint in the routine "netsnmp_query_set",
> and check exactly what assignment is being made
> and why it is failing.
... I have a last note. I defined my own handler. It sees requests with mode code 0 (possibly derived from SNMP_MSG_GET ?) and 4 (possibly derived from SNMP_MSG_TRAP ?). I can see correct value (4321) in val list in both cases. The only thing which can cause these requests is setEvent (value is never queried) Last question is: Is it possible that setEvent generates some kind of that *_TRAP request (instead of a *_SET request) which is not processed by default handler?
> 
Thanks for your time.
Michal Filka

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users