SNMPv3 informs

[Frank Fock]

Mike,

the "unknown engine ID" report is normal behaviour.
After having received it, AGENT++ should try a time
synchronization (which I am pretty sure it does -
Jochen and me have tested this while looking for
interoperability problems). May be SilverCreek does
not properly respond to the time synchronization?

You could use the Ethereal sniffer to see what's
going on. It does on-the-fly decoding of the
SNMP packets which helps a lot.

Best regards,
Frank

Buchan, Mike wrote:
> Thank you for your quick response.  I thought you had pointed out my error
> in my first read through.  We were not using one of the
> UsmUserTable::addNewRow forms which included the engine ID.  
> For a test case, I altered the atm_mib example to do an SNMPv3 inform
> following the steps you outlined in your reply.  I tried both forms of
> UsmUserTable::addNewRow which include the engine ID as a parameter.  I am
> still failing.  
> As stated in a previous message I am using the SilverCreek tool to test the
> interfaces.  In this case, I'm using there Notification Manager and looking
> at the log entries.  The inform never makes it to the Notification Manger.
> When in detailed mode, the log shows a set of 68 octets received and
> indicates that it returns an UnknownEngineID report.  I am having no luck
> deciphering the octets received in relation to what I think should be sent.
> Just for information, the octets dump follows:
> 
>