[AGENT++] SNMPv3 requests problem
Jochen Katz
katz at agentpp.com
Mon Apr 25 00:02:37 CEST 2016
Hi,
> I'm not being able to make SNMPv3 requests using the SNMP++ api. The
> two subsequent requests are all receiving usmStatsUnknownEngineIDs
> errors. I don't think that this error is the real problem because
> when I'm using the snmpWalk it also happens, but the application/api
> remakes the request to move forward instead.
just to be sure, I assume: The log output of your mail is from _one_
call of the snmp++ API.
For the first request the expected report is received:
> 20160424.05:15:27: 0: (1)DEBUG : *** Receiving a ReportPDU ***
> 20160424.05:15:27: 0: (1)DEBUG : mp finished (OK)
> 20160424.05:15:27: 0: (1)DEBUG : receive_snmp_response: engine_id
> ( 80 00 1F 88 80 95 F4 55 69 62 75 B9 55 00 00 00 .......Uibu.U...
> 00 .), security_name (), security_model (3), security_level (1)
> 20160424.05:15:27: 0: (1)DEBUG : addtoengineidtable:
> (192.168.147.244/161)
After this has been executed, the v3MP::EngineIdTable must contain the
discovered engine id. So...
> 20160424.05:15:27: 0: (4)INFO : v3MP::EngineIdTable: Dont know
> engine id for (host) (port): (192.168.147.244), (161)
... this line from the get_entry() function should not happen.
If you set the log profile "all" (or log levels higher than 10, if log
profiles are disabled), you should get more output of the
v3MP::EngineIdTable class.
If you call v3MP::get_from_engine_id_table() in your code after the
failed request, does it return the engineId?
If you manually add it with v3MP::add_to_engine_id_table(), can you
retrieve it afterwards? Does the SNMP request then succeed?
Regards,
Jochen
More information about the AGENTPP
mailing list