ulrich berl
2018-07-12 06:52:45 UTC
Hi!
During tests with snmp v3 i get little confused about contextEngineID and securityEngineID.
For sending snmp v3 request i use net-snmp tool snmpget:
There are two options available for specifying an engineId:
-e ENGINE-ID set security engine ID (e.g. 800000020109840301)
-E ENGINE-ID set context engine ID (e.g. 800000020109840301)
The snmpget request works without specifying an engineId - it will do a discovery first.
Specifying e or E or both of them with correct snmp4j-agent engineId will work too.
Specifying -e with wrong engineId will result in: 'Timeout: No Response from 127.0.0.1.'
Specifying -E with wrong engineId will result in: 'snmpget: Unknown Report message'
Actually if specifying -e or -E i have to use the same engineId ...
What about contextEngineID/securityEngineID in snmp4j ?
How can i configure different values for them ?
br, Ulrich
During tests with snmp v3 i get little confused about contextEngineID and securityEngineID.
For sending snmp v3 request i use net-snmp tool snmpget:
There are two options available for specifying an engineId:
-e ENGINE-ID set security engine ID (e.g. 800000020109840301)
-E ENGINE-ID set context engine ID (e.g. 800000020109840301)
The snmpget request works without specifying an engineId - it will do a discovery first.
Specifying e or E or both of them with correct snmp4j-agent engineId will work too.
Specifying -e with wrong engineId will result in: 'Timeout: No Response from 127.0.0.1.'
Specifying -E with wrong engineId will result in: 'snmpget: Unknown Report message'
Actually if specifying -e or -E i have to use the same engineId ...
What about contextEngineID/securityEngineID in snmp4j ?
How can i configure different values for them ?
br, Ulrich