1 step forward and 1 step back! Having compiled in the disman/event module I get a new error about the agentSecName token which I didn't get before:
D:\netSNMPMisc>snmpd -f -Ddisman:event:conf No log handling enabled - turning on stderr logging registered debug token disman:event:conf, 1 disman:event:conf: Parsing disman monitor config (-r 10 -e scisysNotification -o scisysString "Generate scisysNotification" scisysInteger == 2) disman:event:conf: _BGenerate scisysNotification: Bool (scisysInteger, 2, 2) d:/netSNMP/etc/snmp/snmpd.conf: line 21: Error: You must specify a default user name using the agentSecName token disman:event:conf: Parsing mteTriggerTable config... (snmpd.conf, Generate scisysNotification) net-snmp: 1 error(s) in config file(s) disman:event:conf: Storing mteEventTable config: disman:event:conf: done. disman:event:conf: Storing mteObjectTable config: disman:event:conf: done. disman:event:conf: Storing mteTriggerTable config: disman:event:conf: Storing (snmpd.conf Generate scisysNotification) disman:event:conf: done. NET-SNMP version 5.3.1 My snmpd.conf file is: # Community settings rocommunity public rwcommunity private # User settings - required for sending traps via monitors createUser myuser MD5 mypassword DES myotherpassword rouser myuser # Table rows add_row scisysTable 1 "Test1a" "Test1b" add_row scisysTable 2 "Test2a" "Test2b" add_row scisysTable 3 "Test3a" "Test3b" # Trap settings trapcommunity trap trap2sink localhost # Monitors iquerySecName myuser agentSecName myuser monitor -r 10 -e scisysNotification -o scisysString "Generate scisysNotification" scisysInteger == 2 Any ideas??? Thanks, Emlyn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: 01 March 2007 13:00 To: Emlyn Purvis Cc: [email protected] Subject: Re: Monitor using !=OID On 01/03/07, Emlyn Purvis <[EMAIL PROTECTED]> wrote: > registered debug token disman:event:conf, 1 > snmpd.conf: line 21: Error: unable to parse oid:!=scisysInteger Hmmm.... I'd expect to see a bit more than that. Something of the form "Parsing disman monitor config (....)", at the very least. <tap, tap, tap> Aha! You're using the older Event MIB implementation. No - that code does *not* support the !=OID test. You'll need to recompile the agent to use the newer 'disman/event' module, rather than the 'disman/event-mib' (or 'disman/old-event-mib') module. I'm a little surprised, since I thought the newer version was the default for the 5.3.x line. But the error message above is definitely coming from the older code. 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
