R: Re: help on snmpd.conf and monitor instruction

I've tried to do it doesn't work.
I wrote in snmpd.conf:

 agentSecName 
internal
 rouser internal
 monitor -r 1 -u internal -o timeX  "warning" 
time > 10 (that's to say that when the value of time goes beyond 10, 
snmpd has to send a notification (trap)

I've started snmptrapd,and 
then i've started snmpd.

It prints :

NET-SNMP version 5.4 AgentX 
subagent connected
NET-SNMP version 5.4
2007-07-20 15:34:45 <UNKNOWN> 
[UDP: [127.0.0.1]:32821]:
DISMAN-EVENT-MIB::sysUpTimeInstance = 
Timeticks: (2915) 0:00:29.15      SNMPv2-MIB::snmpTrapOID.0 = OID: NET-
SNMP-AGENT-MIB::nsNotifyShutdown
2007-07-20 15:34:45 <UNKNOWN> [UDP: 
[127.0.0.1]:32822]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: 
(2915) 0:00:29.15      SNMPv2-MIB::snmpTrapOID.0 = OID: NET-SNMP-AGENT-
MIB::nsNotifyShutdown
2007-07-20 15:34:45 <UNKNOWN> [UDP: [127.0.0.1]:
32822]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17) 0:00:
00.17        SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::
coldStart        SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::
netSnmpAgentOIDs.10
2007-07-20 15:34:45 <UNKNOWN> [UDP: [127.0.0.1]:
32823]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17) 0:00:
00.17        SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::
coldStart        SNMPv2-MIB::snmpTrapEnterprise.0 = OID: NET-SNMP-MIB::
netSnmpAgentOIDs.10
2007-07-20 15:34:45 <UNKNOWN> [UDP: [127.0.0.1]:
32822]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (18) 0:00:
00.18        SNMPv2-MIB::snmpTrapOID.0 = OID: DISMAN-EVENT-MIB::
mteTriggerFired    DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: 
warning   DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:  DISMAN-EVENT-
MIB::mteHotContextName.0 = STRING:       DISMAN-EVENT-MIB::mteHotOID.0 
= OID: DISMAN-EVENT-MIB::sysUpTimeInstance     DISMAN-EVENT-MIB::
mteHotValue.0 = Wrong Type (should be INTEGER): Timeticks: (18) 0:00:
00.18  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (18) 0:00:00.18
2007-07-20 15:34:45 <UNKNOWN> [UDP: [127.0.0.1]:32823]:
DISMAN-EVENT-
MIB::sysUpTimeInstance = Timeticks: (18) 0:00:00.18        SNMPv2-MIB::
snmpTrapOID.0 = OID: DISMAN-EVENT-MIB::mteTriggerFired    DISMAN-EVENT-
MIB::mteHotTrigger.0 = STRING: warning   DISMAN-EVENT-MIB::
mteHotTargetName.0 = STRING:  DISMAN-EVENT-MIB::mteHotContextName.0 = 
STRING:       DISMAN-EVENT-MIB::mteHotOID.0 = OID: DISMAN-EVENT-MIB::
sysUpTimeInstance     DISMAN-EVENT-MIB::mteHotValue.0 = Wrong Type 
(should be INTEGER): Timeticks: (18) 0:00:00.18  DISMAN-EVENT-MIB::
sysUpTimeInstance = Timeticks: (18) 0:00:00.18


In my case, the 
condition is met, but i'havent got a trap from snmpd.

Why?







----
Messaggio originale----
Da: [email protected]
Data: 20-lug-2007 
2.50 PM
A: "[email protected]"<[email protected]>
Cc: <net-
[email protected]>
Ogg: Re: help on snmpd.conf and 
monitor instruction

On 20/07/07, [email protected] 
<[email protected]> wrote:
> I want to know if is it possible to 
use the "monitor"
> instruction in snmpd.conf to monitor custiomized 
OID?

Yes.

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. 
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.
com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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





-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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