On 28 November 2011 09:15, prashant n <[email protected]> wrote:
> I created a new snmpv3 user using following command
> net-snmp-config --create-snmpv3-user -a "my_password" myuser
> After that i queried using SNMPv3 options using following commands:
> $ snmpget -v 3 -u myuser -l authNoPriv -a MD5 -A my_password localhost
> sysUpTime.0
OK - all that looks good.
In which case, the next thing you should do is add the line
iquerySecName myuser
to the snmpd.conf file.
This tells the agent to run any internal queries as this user.
There's no need to specify the password here - the agent can
pick this up from the 'createUser' line that you already have in place.
> Actually i have to monitor an object in the table but before to that i want
> to test the scalar object( That i defined in MIB file and able to access
> using GET request) for simplicity. I want to trigger the trap when integer
> scalar object is within this range i,e 1 to 3 (value = 1 to value = 3).
Hmmmm... that might be tricky.
It would be more common to monitor an object, and trigger a trap
when the value moves *outside* a particular range.
(Or simply exceeds a specific threshold value)
Try adding the following to the snmpd.conf file
monitor -r 10 myScalarTest myScalar > 3
and restart the agent
That should trigger a trap when the value of myScalar.0
becomes greater than 3 (checking every 10 seconds).
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
