>>>>> On Mon, 21 Feb 2011 10:49:42 +0530, Manjit >>>>> <[email protected]> said:
M> A row which is volatile(2) is lost upon reboot. A row which M> is either nonVolatile(3), permanent(4) or readOnly(5), is M> backed up by stable storage. First, for the keywords make sure you read the StorageType definition in mibs/SNMPv2-TC.txt as well. It discusses what each of those keywords is supposed to mean. But... your problem really has nothing to do with 'permanent' or any other type because this: M> But the issue is whenever the system reboots we are also changing the M> SnmpEngineID. Means you're going to completely lose the point of having the row persistent in the first place. If the EngineID is always changing then the old users will not be useful so there is really no point in keeping them around in the first place! Why are you generating a new engineID on every boot? This is really something that isn't recommended (in fact, highly discouraged). -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
