Hi Ron,
What you observe is correct and matches the SNMP standard requirements.
In SNMP, the trap receiver is authoritative. That is, the sender must use the
SNMP(v3) user name and password the receiver knows and accepts.
Hope this helps anyway ;-)
Best regards,
Frank
> On 2 Feb 2017, at 22:06, Ronald Braswell wrote:
>
> I have a device that hard codes a UsmUser name nameB and sends it with
> SNMPv3 notifications noAuthNoPriv (can't change the level). I did
> configure the device for SNMPv3 with a different user name nameA and the
> passphrases for priv and auth. I can poll the device using nameA. But I
> cannot send a notification from the device using SNMPv3. which uses nameB.
> Is this because with SNMPv3 notifications there must be a UsmUser for
> nameB registered in the USM UsmUserTable associated with the snmp instance
> (I have one instance for traps and polls)? Of course I can send a V1 trap
> using a trap community string of anything and it is delivered. But the
> SNMP4J library will not deliver the SNMPv3 notification with nameB to
> processPdu(CommandResponderEvent evt).
>
> I configured the SNMP manager (my code) with nameB using the same authPriv
> as for nameA and set up the same user on the target device with the same
> security parameters. Now when the device sends an SNMPv3 notification USM,
> name=nameB, noAuthNoPriv the SNMP4J software forwards the notification to
> me whereas it did not before.
>
> Do I need to add a nameB UsmUser noAuthNoPriv to the UsmUserTable just to
> receive SNMPv3 traps from the device which hard codes the nameB for the
> UsmUser name?
>
> Ron
> ___
> SNMP4J mailing list
> SNMP4J@agentpp.org
> https://oosnmp.net/mailman/listinfo/snmp4j
___
SNMP4J mailing list
SNMP4J@agentpp.org
https://oosnmp.net/mailman/listinfo/snmp4j
