I don't have code to set the engine ID explicitly, what my observation was during SNMP V3 communication, the cache maintained with engine ID and engine boot time etc... for the first device the communication work fine but for the second device which is having same engID as previous it always reports error (USM Time not in window) . Is there any way to tell always probe for engine ID discovery.
Thanks. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield Sent: Thursday, June 09, 2011 3:56 PM To: Mygapula, Sudheer IN BLR SISL Cc: [email protected] Subject: Re: SNMPV3 problems. On 9 June 2011 10:32, Mygapula, Sudheer IN BLR SISL <[email protected]> wrote: > I have problem with SNMP V3 Communication. > The devices in network are having same engine ID. Yes - that would be a problem. Each device should have a unique engine ID. > How this problems can be resolved. How are the engineIDs being set? By default, the Net-SNMP agent generate a random engineID, so the chances of them all being the same are infinitesimal. So you must be doing something to set the engine IDs explicitly, If you stop doing that, then things should work better. Dave Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank You. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
