linkUpDownNotifications not working
Helen McManus <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Organization | Genexis BV |
| Message-ID | <[email protected]> |
Hello, I'm having trouble getting linkUpDownNotifications to work. I'll try to describe the problem below and what I've found out so far. It seems that the "monitor" directive *has* to have -u SECNAME supplied, even though according to the doc at http://www.net-snmp.net/docs/man/snmpd.conf.html you only need to use -u if you want to use a different name than that specified by iquerySecName. The problem with this of course is that the linkUpDownNotifications has no facility to specify a -u. (Yes I do realise I can manually add the monitor and notificationevent lines that linkUpDownNotifications is equivalent to, but I would like to try and resolve the issue). Below is the log file generated when I start the smmpd. # cat /var/log/snmp registered debug token trap, 1 2006-09-28 16:02:27 trap: adding callback trap sink 2006-09-28 16:02:27 trapsess: adding to trap table 2006-09-28 16:02:27 /etc/snmp/snmpd.conf: line 94: Error: You must specify a default user name using the agentSecName token 2006-09-28 16:02:27 /etc/snmp/snmpd.conf: line 94: Error: You must specify a default user name using the agentSecName token 2006-09-28 16:02:27 net-snmp: 2 error(s) in config file(s) 2006-09-28 16:02:27 trap: send_trap 0 0 NET-SNMP-MIB::netSnmpAgentOIDs.10 2006-09-28 16:02:27 trap: sending trap type=167, version=1 2006-09-28 16:02:27 NET-SNMP version 5.3.1 # Here is a portion of my snmpd.conf file. 87 # Need to create an snmp3 user for the disman stuff to work. 88 createUser dismanUser MD5 "noli me tangere" 89 rouser dismanUser 90 iquerySecName dismanUser 91 92 # Built in trap to monitor the network interfaces 93 #defaultMonitors yes 94 linkUpDownNotifications yes 95 96 # Monitor lines 97 98 ## PROC ## 99 # proc, check every 60s 100 # oid is .iso.org.dod.internet.private.enterprises.ucdavis.prTable.prEntry.prErrorFlag 101 monitor -u dismanUser -r 60 -S -e procMon -o prNames -o prErrMessage "proc monitor" .1.3.6.1.4.1.2021.2.1.100 > 0 102 If I remove the -u in line 101, then the log file will contain an additional copy of the error message, but for line 101 as well. Also, using the directive agentSecName instead of iquerySecName makes no difference. I'm running snmpd with the options '-Lf /var/log/snmp -p /var/run/snmpd.pid -Dtrap' on version net-snmp 5.3.1. Are the error message I'm seeing my fault? Thanks. H. ------------------------------------------------------------------------- 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