On Wed, 2006-03-15 at 15:51 -0600, Billington, David wrote: > Hi! I have a Redhat 9 server with net-snmp 5.0.9 installed.
I'd strongly suggest that you upgrade to 5.2.2, or 5.3.0.1. The 5.0.x line is extremely old code now, and things have moved on a lot since then. > # Trap Configuration > > authtrapenable 1 > trapcommunity public > trapsink <ip_addr1> > trapsink <ip_addr2> > trapsink <ip_addr3> > informsink <ip_addr1> > informsink <ip_addr2> > informsink <ip_addr3> Why do you want to send *two* copies of each trap to each of these destinations? Please use *EITHER* "trapsink" *OR* "informsink" for any given host receiver. Not both. > # Trap Generation > > agentSecName internal > rouser internal > defaultMonitors yes That looks good. Presumably you also have a "createUser internal ..." entry somewhere? What do you see if you walk the usmUserSecurityName object? > Cold start traps are received if the snmpd service is restarted, > but if I kill a monitored process (e.g. ntpd), nothing happens. What do you see if you walk the prTable? Has the corresponding prErrorFlag been set? Try running the agent with '-Dmte' - what debug output do you see? Dave ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
