> -----Original Message----- > From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On > Behalf Of Dave Shield > Sent: Thursday, March 18, 2010 12:55 PM > To: Martz, Peter > Cc: net-snmp-users@lists.sourceforge.net > Subject: Re: snmpd.conf configuration issue > > On 18 March 2010 16:02, Martz, Peter <peter_ma...@cable.comcast.com> wrote: > > monitor -r 60 -o hrSWRunName "pjm: high cpu is WAY too high" > hrSWRunPerfCPU > 1 > > OK - That makes sense. > "Send a trap if the CPU usage of a process is too high, > and include the name of the offending process. > Repeat this check every 60 s" > > > > > monitor -r 60 -o hrSWRunName "pjm: memorysize" hrMemorySize > 100 > > That doesn't. > "Send a trap if the amount of installed memory is > 100Kb > and include the name of the offending process. (???) > Repeat this check every 60s (????)" > > How often are you installing new memory in your kit?!
Fair enough, I was using the wrong token. I meant to use this (and the other 2 working monitor lines) only as an example of what formats were working. > > > monitor -r 60 -o hrSWRunName "pjm: high process memory" > > 1.3.6.1.2.1.25.5.1.1.2 > 10 > > That makes sense again > "Send a trap if the memory usage of a process is too high, > and include the name of the offending process. > Repeat this check every 60 s" > > > > > ## This monitor trap gives me an error: failed to run mteTrigger query > > > > monitor -r 60 -o hrSWRunName "Martz: CheckPoint CPU" > > 1.3.6.1.4.1.2620.1.6.7.2.4 > 1 > > > > monitor -r 60 -o hrSWRunName "Martz: CheckPoint Connections" > > 1.3.6.1.4.1.2620.1.1.25.3 > 1 > > Again, these two probably don't make sense, unless the (private) MIB > objects you are querying use the same indexing as the hrSWRunTable. > In general, the additional payload objects you specify in a monitor > line should typically belong to the same table as the object being > monitored, since the agent will append the relevant index subidentifier. > OK. Based on that, could this be why I am getting the trigger error?: disman:event:trigger:monitor: Trigger query (walk) failed: -2 I am not sure I fully understand which additional OIDs I can supply with an alert (not a smart man jenny). How can I add "custom" information to the traps, once I get them working? > It's also worth checking whether this agent actually implements these > two MIB objects. What happens if you run "snmpgetnext" on these > two OIDs? > Running snmpgetnext on 1.3.6.1.4.1.2620.1.1.25.3 gives the following: /usr/local/bin/snmpgetnext -Of -On -v 2c -c <community> <ip> 1.3.6.1.4.1.2620.1.1.25.3 .1.3.6.1.4.1.2620.1.1.25.3.0 = INTEGER: 19 ------------------------------------------------------------------------------ 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