SNMPv3 informs

[Frank Fock]

Mike,

I think a year or more ago, we had a similar
discussion on this list with detailed examples.
May be you can find it in the archive.

To send an inform from an AGENT++ agent:

1. Add a parameter row in snmpTargetParamsTable
2. Add an "inform" tag to the snmpNotifyTable
3. Add a target address in the snmpTargetAddrTable
    that refers to the parameter row created in (1)
    and the tag row created in (2).
4. Add a user with the engine ID, user name, and
    password of the *target* system to the AGENT++
    agent's usmUserTable. This can be easily done
    by MIB Explorer's Edit/Create Modiy SNMPv3 User
    function. Alternatively, this can also be done
    from within the agent or by other command line
    tools.
[5.] Add the user created in (4) to your target
    system, with the local engine ID of course.

Hope this helps.

Best regards,
Frank Fock


Buchan, Mike wrote:
> Last week I sent a message about having problems getting the engine ID
> discovery to happen when trying to do informs and got a quick response which
> sounded promising.  As it turned out we were using the
> NotificationOriginator method to send the inform and were still having
> problems.  I looked for an example to see where else we might be making a
> mistake.  The only example that I could find related to
> informs/notifications was the atm_mib example.  It sends an SNMPv1 trap.  I
> tested that against SilverCreek and it worked just fine.  I also changed it
> to send an SNMPv2c trap which also worked just fine.  In both of these
> cases, authentication was not used (as expected and verified by using bogus
> data in SilverCreek for expected authentication request from the agent).  
> 
> Is there an example somewhere where an SNMPv3 inform works so I can compare
> the setup and see what I'm missing or doing wrong?  I don't see it.  I think
> I'm setting up all of the appropriate table and using the correct method
> from NotificationOriginator.
> 
> Thank you in advance for your help.
> 
> Mike Buchan
>