G'day,
Just as a note... I noticed some suspicious behaviour when the agent is
trying to run the behaviour. A strace on snmpd with -Ddisman and -f
shows that almost immediately following the "Running trigger
(triggername)" message, we start seeing select(2) calls with timeout set
to 1 usec.
G'day all,
I followed the discussion between Uday Sorte and Dave Shield on the
archives and wanted to chime in. I am experiencing the same behaviour
as Uday with a trigger on an OID that is delegated to another agent
(failed to run mteTrigger query with Trigger query (get) failed: -2).
(In m
Thanks Dave for all the hard work you have done.
I think if I try compiling the subagent code as a part of master agent,
using the "configure --with-mib-modules" this problem will not show up.
I will try to explore more features down the line and will report you if
I encounter any new problems.
On 02/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> I tried with the master agent object sysServices and it is working fine.
> Means I have problems with the subagent and not with the snmpd.conf file
> or anything else.
>
> What could be the possibility. My subagent is not linked properly with the
On 02/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> disman:event:trigger:monitor: Running trigger (DisMan Event Testing)
> disman:event:trigger:fire: Returned non-integer result(s):
NTC-2223-MIB::ntc2223DevTemp.0 (boolean/threshold) 5
Hmmm that looks like the master agent is getting a
Logs. for
monitor -r 60 -u root -S -I "DisMan Event Testing" ntc2223DevTemp.0 == 10
[EMAIL PROTECTED] ~]# snmpd -f -Ddisman:event
No log handling enabled - turning on stderr logging
registered debug token disman:event, 1
disman:event:init: init trigger container
disman:event:init: create trigger
Thanks a lot Dave.. for your help.
Here is the update..
I tried with the master agent object sysServices and it is working fine.
I could see the traps coming. I tried the following things and all of them
are working fine.
monitor -r 60 -u root -S -I "DisMan Event Testing" sysServices.0 = 79
mon
On 02/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> I tried with the master agent object sysServices and it is working fine.
> I could see the traps coming.
Right - so the problem is somewhere in the interaction between
DisMan monitoring, and AgentX subagents.
That's useful information. I'll
The difference is I get a failure in GET now
disman:event:trigger:monitor: Running trigger (DisMan Event Testing)
disman:event:trigger:monitor: Trigger query (get) failed: -2
failed to run mteTrigger query
Without -I option is was walk.
Good .. Something has changed.
Thanks,
Uday
>>> "Dave
monitor -r 60 -u root -S -I "DisMan Event Testing" ntc2223DevTemp == 10
No... did not help either.
I am just giving my test MIB, if in case something is wrong.
NTC-2223-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, NOTIFICATION-TYPE
FROM SNMPv
Hi Dave,
I also tried with 5.3.1, same problem.. Looks like I am missing some
configuration.
Looked at the code in
net-snmp-5.3.1/agent/mibgroup/disman/event/mteTrigger.c
I think there is a timeout in either netsnmp_query_walk or
netsnmp_query_get which
are returning with -2. It is most probably
On 01/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> monitor -r 60 -u root -S -I "DisMan Event Testing" ntc2223DevTemp == 10
> No... did not help either.
But that's not what I said.
Please try
monitor -r 60 -u root -S -I test ntc2223DevTemp.0 == 10
with the *full* instance OID.
Note "ntc
On 01/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> monitor -r 60 -u root -S "DisMan Event Testing" ntc2223DevTemp == 10
OK - another thing to try:
monitor -r 60 -u root -S -I test ntc2223DevTemp.0 == 10
(that's minus-capital-i).
This will configure the test with a single instance (and a
The object is in Integer object and it is implemented as a part of subagent.
ntc2223DevTemp OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"ntc2223 Device Temperature"
::= { ntc2223DevConfig 1 }
snmpwalk gives correct value.
[EMAIL
On 01/03/07, Uday Sorte <[EMAIL PROTECTED]> wrote:
> The log which I get after running snmpd
> *-
> disman:event:trigger:fire: Returned non-integer result(s):
>NTC-2223-MIB::ntc2223DevTemp (boolean/threshold) 0
That looks like a problem.
What syntax
The log which I get after running snmpd
*-
[EMAIL PROTECTED] subagent]# snmpd -f -Ddisman
No log handling enabled - turning on stderr logging
registered debug token disman, 1
disman:event:init: init trigger container
disman:event:init: create trigger con
Hi,
I am trying to use DisMan Event MIB for generating notifications but keep
getting "failed to run mteTrigger query" error.
Debugging with snmpd -DdismanEventMIB or snmpd -f -Le -d or
/var/log/snmpd.log did not helped much.
This is what I did
Created a SNMPV3 user as "root" and assigned
17 matches
Mail list logo
