On Wed, Jul 20, 2022 at 2:46 AM Feroz wrote:
> What I configured in snmpd.conf file
>
> *engineID 8000b85c03d0672649a01e*
>
This configured net-snmp to use the string " 8000b85c03d0672649a01e" to
generate an engineID.
If you want to configure the engine-id with a hex string, please use the
"ex
What I configured in snmpd.conf file
*engineID 8000b85c03d0672649a01e*
NetSNMP converted the above engineID in to equivalent Hex value for each
character, i.e (8000b85c03d0672649a01e => 38 30 30 30 62 38 35 63 30 33 64
30 36 37 32 36 34 39 61 30 31 65) with some prefix *0x80001f8804*
*snippet:*
Abhishek Singh 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 t
Hello,
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 1oldEngineID
0x80001f880438303030623835633033653030373162633735333532*
The question is why the oldEngineID is stored in A
