Re: DisMan Event MIB Problem

"Uday Sorte" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Logs. for 
monitor -r 60 -u root -S -I "DisMan Event Testing" ntc2223DevTemp.0 == 10

[root@NTC-2223-DEV ~]# 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 container (95b4c18)
disman:event:init: init trigger container
disman:event:init: Trigger Table
disman:event:init: init trigger container
disman:event:init: Trigger Delta Table
disman:event:init: init trigger container
disman:event:init: Trigger Exist Table
disman:event:init: init trigger container
disman:event:init: Trigger Bool Table
disman:event:init: init trigger container
disman:event:init: Trigger Threshold Table
disman:event:init: init trigger container
disman:event:init: init event container
disman:event:init: create event container (95b7c30)
disman:event:table: Create event entry (_snmpd, _mteTriggerFired)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerRising)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerFalling)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerFailure)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _linkDown)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _linkUp)
disman:event:table: Event entry created
disman:event:init: init event container
disman:event:init: Event Table container (95b7c30)
disman:event:init: init event container
disman:event:init: Event Set Table container (95b7c30)
disman:event:init: init event container
disman:event:init: Event Notify Table container (95b7c30)
disman:event:init: init event container
Turning on AgentX master support.
disman:event:conf: Parsing disman monitor config (-r 60 -u root -S -I "DisMan Event Testing" ntc2223DevTemp.0 == 10)
disman:event:conf: _BDisMan Event Testing: Bool (ntc2223DevTemp.0, 2, 10)
disman:event:table: Create trigger entry (snmpd.conf, DisMan Event Testing)
disman:event:table: Trigger entry created
disman:event:conf: Storing mteTriggerTable config:
disman:event:conf:   done.
disman:event:conf: Storing mteEventTable config:
disman:event:conf:   done.
disman:event:conf: Storing mteObjectTable config:
disman:event:conf:   done.
NET-SNMP version 5.3.1
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
disman:event:trigger:monitor: Running trigger (DisMan Event Testing)
disman:event:trigger:monitor: Trigger query (get) failed: -2
failed to run mteTrigger query



>>> "Dave Shield" <[email protected]> 3/2/2007 10:36:02 AM >>>
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 see if I can reproduce the problem.


> I also tried
> monitor -r 60 -u root -S -I  ""DisMan Event Testing"  ntc2223DevTemp.0  == 10
> but did not help

What was the -Ddisman:event output from this run?

Dave



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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.