problem getting monitor command in snmpd.conf to work with 5.4.1

Mike Harless <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
I'm trying to get active monitor working and wondered if someone could 
give me a push in the right direction.  

What I'm seeing, is a request into my agentx sub-agent for the given 
oid I want to watch, but the trigger times out after 30 seconds saying 
that the query failed with a return code of -2.  After another 30 seconds 
(my monitor period is 60 seconds), the trigger runs again, but with the 
same result.

I tried 'linkUpDownNotifications yes' and that works, so I'm probably
messing up my monitor syntax, or forgetting something in my agentx sub-agent,
or missing some setup for notifications in the disman event mib, or ...?

Any suggestions on where to look?  Thanks!

--Mike

------------------------------------------

my monitor commands look like:

  monitor -I -S -r 60 "<name>" <oid> != 0

and what I'm seeing (when I run snmpd with -Ddisman) is:

  - snmpd: disman:event:trigger:monitor: Running trigger (<oid>)

  - my agentx process sees the request for the <oid> being monitored
    and is returning SNMP_ERR_NOERROR;

   (30 seconds go by)

  - snmpd: disman:event:trigger:monitor: Trigger query (get) failed: -2
  - failed to run mteTrigger query

  (30 seconds go by)

  - snmpd runs the trigger again and it fails again in the same way.

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.