>>>>> On Wed, 22 Jun 2011 11:45:23 +0100, "Lewis Adam-VNQM87" >>>>> <[email protected]> said:
LA> In our agent [based on 5.4.2.1 in an embedded environment] we have the LA> ability to change the ip address without rebooting the unit. As a LA> general question, are there any issues with updating the SNMPEngineID LA> (and subsequently snmpEngineBoots and snmpEngineTime) dynamically? I LA> know that snmpEngineBoots and snmpEngineTime get used in timeliness LA> calculations and I was concerned we might break this mechanism if we LA> don't force a reboot. The SNMPv3/USM user table, if you're using USM, bases all the keys and data off of the engineID. So you really don't want to change the engineID if it can be avoided. Thus, we actually recommend that you not base the engineID off of an IP address, which can change. The default Net-SNMP installation basis the engineID off of time and a random value, which is generally suitable for most implementations except boxes that will always first-boot with the same time/random-seed. Actually, the best thing to do would be to base it off of a serial number you can get programatically, but we have no way of doing that generically in the code in the base package. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
