Changchun Zhao wrote:
I tried to use different engineIDs on the trapsess line and snmptrap command, also add a 'createUser' line with the same user but different engineID in snmptrapd. That seems work. But this won't be a good solution for our problem.
The command-line utilities (like snmptrap) don't preserve state while the agent (snmpd) does, so their engineBoots/engineTime values differ. Using the same engineID for both thus creates problems.
Either use different engineIDs or manage to let snmpd itself send all notifications, w/o using an external snmptrap command.
+Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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
