Abhishek Singh <abhisheksingh.rohit...@gmail.com> writes: > I have a question on the format how oldEngineID is stored in snmpd.conf. > After configuring an engine ID, I observed the oldEngineID in snmpd.conf saved > as > engineBoots 1 > oldEngineID 0x80001f880438303030623835633033653030373162633735333532 > > The question is why the oldEngineID is stored in ASCII format when engine-id > input is actually Hex.
The oldEngineID basically stores what was used in the last run, for if the engineID changes (in the current run) then boots needs to be reset. I'm not sure I understand the ascii question -- how are you setting the engineID? If you're using a "string", the encode engineid still has some leading binary information to indicate it was set as a string. IE, the engineID consists of more than just the string itself (per the SNMPv3 RFCs). -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
