SNMPv3 trap problem with snmp++v3.1.4a
Lukasz Szczepankowski
lukasz____nnu.com
Thu Nov 29 18:33:29 CET 2001
Frank,
I have just upgraded to the latest versions of snmp++ and agent++ and I have
a problem with SNMPv3 traps (my agent which used to work just fine with
agent++ v3.4.7 and snmp++ v3.1.3 quit sending v3 traps - or rather it keeps
sending them, but they are not received by my trap receiver any more).
I compiled the new snmp++ and tried to use the consoleExamples. I got
receive_trap running, and I tried the following command:
[lukasz at aveta consoleExamples]$ ./snmpInform localhost -p10162 -v3 -snMD5DES
-md5 -uaMD5DESUserAuthPassword -des -upMD5DESUserPrivPassword
SNMP++ Trap to localhost SNMPV3
securityName= MD5DES, securityLevel= 3, securityModel= 3
contextName= , contextEngineID=
Oid = 1.3.6.1.4.1.11.2.16.2
Value = SNMP++ Trap Send Test
This worked just fine. Next, I tried:
[lukasz at aveta consoleExamples]$ ./snmpTraps localhost -p10162 -v3 -snMD5DES
-md5 -uaMD5DESUserAuthPassword -des -upMD5DESUserPrivPassword
SNMP++ Trap to localhost SNMPV3
securityName= MD5DES, securityLevel= 3, securityModel= 3
contextName= , contextEngineID=
SNMP++ Trap Send Status = Success
This command returned success, but the trap never showed as received by
receive_trap. I compiled snmp++ with debugging, and this is what
receive_trap reported:
usmCheckTime: TimeWindowCheck for engine_id (TrapSender), boot (6), time(1)
usmCheckTime: time ok
apDESDecryptData: Data to decrypt:
<data>
apDESDecryptData: decrypted Data:
<data>
ErrorCode is 0
Parsing contextEngineID with length = 0x0
Parsing contextName with length = 0x0
mp: received request message with zero length contextEngineID ->
unknownPduHandlers.
What's going on here?
Thanks,
Lukasz Szczepankowski
More information about the AGENTPP
mailing list