Rafael Garabato wrote:
I increased the tcpdump's snaplen as you asked. This time I didn't get
the same problem as the time before. Only 2 packets are transmited each
time the session is opened.
That's exactly how the engineID discovery is supposed to work.
So what happens now if you actually perform a GET before and after the
changeover?
However I noticed that there is a parameter
called "usmStatsUnknownEngineIDs.0" that always increments its value
untill the Change over. Could this be the problem?
That's just a counter of the received packets with unknown engineIDs
(most-if-not-all of them being the engineID probes). Don't worry.
What you *should* worry about, again, is that you will need to increment
the engineBoots value when the "new" agent becomes active after the
changeover (compared to the "old" agent). *How* you pass that
information between the two systems is *your* problem and will depend on
your failover setup. For the testing just manually tweak the
"engineBoots" value in your persistent config file (usually
/var/net-snmp/snmpd.conf) on the "new" system *before* starting the new
agent.
+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-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
