[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-coders
Subject:    Net-snmp Version 5.5 DISMAN-EVENT Errors
From:       Charles Liu <cliu () stonewatercontrols ! com>
Date:       2009-10-07 1:21:26
Message-ID: 3a6f0eb40910061821h7832c11fl495dc255950c8f90 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I have some Net-snmp Version 5.5 DISMAN-EVENT Errors.

The steps are:

(1) Inside the snmpd.conf, I have the following lines:


authtrapenable 1
trapcommunity  public
trap2sink      localhost
createUser    user1 MD5 "pass1" DES
iquerySecName user1
rouser        user1


(2) After I ran snmpd as "snmpd -Ddisman -c /etc/snmpd/snmpd.conf"

I started DISMAN-Event setting as:

snmpset -v 2c -c private localhost
mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 6
snmpset -v 2c -c private localhost
mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 5
snmpset -v 2c -c private localhost
mteTriggerValueID.6.107.97.106.116.122.117.3.65.66.67 = ifInOctets.1
snmpset -v 2c -c private localhost
mteTriggerValueIDWildcard.6.107.97.106.116.122.117.3.65.66.67 = 2
snmpset -v 2c -c private localhost
mteTriggerFrequency.6.107.97.106.116.122.117.3.65.66.67 = 5
snmpset -v 2c -c private localhost
mteTriggerTest.6.107.97.106.116.122.117.3.65.66.67 = 2
snmpset -v 2c -c private localhost
mteTriggerSampleType.6.107.97.106.116.122.117.3.65.66.67 = 2
snmpset -v 2c -c private localhost
mteTriggerObjects.6.107.97.106.116.122.117.3.65.66.67 = 'TEST EVENT'
snmpset -v 2c -c private localhost
mteTriggerThresholdStartup.6.107.97.106.116.122.117.3.65.66.67 = 1
snmpset -v 2c -c private localhost
mteTriggerThresholdDeltaRising.6.107.97.106.116.122.117.3.65.66.67 = 100
snmpset -v 2c -c private localhost
mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 6
snmpset -v 2c -c private localhost
mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 5
snmpset -v 2c -c private localhost
mteEventActions.6.107.97.106.116.122.117.3.65.66.67 = 1
snmpset -v 2c -c private localhost
mteTriggerEnabled.6.107.97.106.116.122.117.3.65.66.67 = 1
snmpset -v 2c -c private localhost
mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 1
snmpset -v 2c -c private localhost
mteEventEnabled.6.107.97.106.116.122.117.3.65.66.67 = 1
snmpset -v 2c -c private localhost
mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 1


(4)I set the mteTriggerFrequency as 5 seconds. For each 5 second, I kept
getting errors of:

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


Any suggestions on how to solve this problem will be highly appreciated.

Charles Liu

[Attachment #5 (text/html)]

I have some Net-snmp Version 5.5 DISMAN-EVENT Errors.<br><br>The steps are:  \
<br><br>(1) Inside the snmpd.conf, I have the following \
lines:<br><br><br>authtrapenable 1<br>trapcommunity  public<br>trap2sink      \
localhost<br> createUser    user1 MD5 &quot;pass1&quot; DES<br>iquerySecName \
user1<br>rouser        user1<br><br><br>(2) After I ran snmpd as &quot;snmpd -Ddisman \
-c /etc/snmpd/snmpd.conf&quot;<br><br>I started DISMAN-Event setting as:<br> \
<br>snmpset -v 2c -c private localhost \
mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 6<br>snmpset -v 2c -c \
private localhost mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = \
5<br>snmpset -v 2c -c private localhost \
mteTriggerValueID.6.107.97.106.116.122.117.3.65.66.67 = ifInOctets.1<br> snmpset -v \
2c -c private localhost mteTriggerValueIDWildcard.6.107.97.106.116.122.117.3.65.66.67 \
= 2<br>snmpset -v 2c -c private localhost \
mteTriggerFrequency.6.107.97.106.116.122.117.3.65.66.67 = 5<br>snmpset -v 2c -c \
private localhost mteTriggerTest.6.107.97.106.116.122.117.3.65.66.67 = 2<br> snmpset \
-v 2c -c private localhost mteTriggerSampleType.6.107.97.106.116.122.117.3.65.66.67 = \
2<br>snmpset -v 2c -c private localhost \
mteTriggerObjects.6.107.97.106.116.122.117.3.65.66.67 = &#39;TEST \
EVENT&#39;<br>snmpset -v 2c -c private localhost \
mteTriggerThresholdStartup.6.107.97.106.116.122.117.3.65.66.67 = 1<br> snmpset -v 2c \
-c private localhost \
mteTriggerThresholdDeltaRising.6.107.97.106.116.122.117.3.65.66.67 = 100<br>snmpset \
-v 2c -c private localhost mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = \
6<br>snmpset -v 2c -c private localhost \
mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 5<br> snmpset -v 2c -c \
private localhost mteEventActions.6.107.97.106.116.122.117.3.65.66.67 = 1<br>snmpset \
-v 2c -c private localhost mteTriggerEnabled.6.107.97.106.116.122.117.3.65.66.67 = \
1<br>snmpset -v 2c -c private localhost \
mteTriggerEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = 1<br> snmpset -v 2c -c \
private localhost mteEventEnabled.6.107.97.106.116.122.117.3.65.66.67 = 1<br>snmpset \
-v 2c -c private localhost mteEventEntryStatus.6.107.97.106.116.122.117.3.65.66.67 = \
1<br><br><br>(4)I set the mteTriggerFrequency as 5 seconds. For each 5 second, I kept \
getting errors of:<br> <br>disman:event:trigger:monitor: Trigger query (get) failed: \
-2<br>failed to run mteTrigger query<br><br><br>Any suggestions on how to solve this \
problem will be highly appreciated.<br><br>Charles Liu<br><br><br>



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic