On 20 May 2010 16:46, Ron Rader <ron.ra...@cipheroptics.com> wrote: > If you wish to use > INFORMs instead of TRAPs, your agent needs to include the remote > target's engineID.
That's strictly accurate, but slightly misleading. SNMPv3 requests will always include _some_ engine ID. Which engine ID this is, depends on the style of request. With traps, this will typically be the engineID of the sending application, so the notification receiver needs to be configured with SNMPv3 users that specify this engine ID explicitly. With INFORM notifications (as with the other GET* and SET requests), this will typically be the engineID of the notification receiver. and the sending application will probe to discover this automatically. So it's *not* necessary to specify this explicitly in the "snmpinform" or "trapsess" directive. (Or in the snmptrapd.conf createUser directive either, since this is the natural engine ID of the trap receiver anyway) Of course, it's always possible to explicitly specify a different engineID for both the sending application and the notification receiver. The vital thing is that the same value should be used for both sides. Dave ------------------------------------------------------------------------------ _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
