>>>>> On Mon, 8 Feb 2010 17:12:02 +0530, "Hemanth Raju" >>>>> <[email protected]> said:
HR> I agree with u, now does the snmp agent store this engine-ID for HR> future informs or every time it will discover to send inform. I want HR> to avoid re-discover for every inform, am trying to simulate this, HR> if u already know kindly help me. The engineID discovery happens by sending an unauthenticated, unencrypted message to the trap receiver (or agent) with a blank (0-length) engineID value. It's the job of the daemon to send back a message containing the engineID so that applications can "discover" it. Dave's right, the library handles this for you if you're using our code (it's unclear from your messages if you are). We have routines to fetch the engineID once it's been discovered, and it is cached after it's discovered so it doesn't need to be "rediscovered" (I've seen other implementations that don't cache the information and re-discover it for every outgoing trap, which is obviously wasteful). You should note, though, that there are security implications involved with using engineID discovery. For further details, you can read my article on the subject: http://pontifications.hardakers.net/computers/limitations-of-snmpv3usm-when-combined-with-engineid-discovery/ -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
