I don’t have one handy, but keep in mind that the engineID used to encode the usmUser credentials, for both snmptrapd and the agent, is the one for snmptrapd itself, not the agent sending the INFORM:
With SNMPv3 informs, the authoritative engine ID is the engine that receives the inform, unlike SNMPv3 traps, where the agent's engine ID is authoritative. So when you create the usmUser for the SNMP agent, you use the snmptrapd engineID. Since the usmUser must exist in the agent configuration before it can send the INFORM, engineID discovery is useless for INFORMs (unlike queries like GET, GET-NEXT). Hope this helps, Brian From: Feroz <feroz.afs...@gmail.com> Sent: Wednesday, January 6, 2021 10:11 AM To: net-snmp-users@lists.sourceforge.net Subject: snmptrapd for V3 informs NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. Anyone tried forwarding V3 informs with snmptrapd? Can some one share the snmptrapd.conf file? -Feroz
_______________________________________________ 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
