From the Help docs:
The snmptd probe has the following known issues:
(From version 3.30) The probe does not process any SNMP v3 trap that includes the engine boot and engine time. You must create a set_Engine_Time key and set to yes in the Raw Configure > setup section. The probe now matches the engine time of the trap and successfully processes it.
(Also related to the wrong engineID being used)...
The SNMPTD probe requires a unique Engine ID for each SNMPv3 device that is sending traps to the probe. The EngineID in SNMPv3 traps are necessary to identify unique network devices. A wildcard engineid cannot be used and is per SNMP standard.
See the following link for more information on SNMP standards; https://tools.ietf.org/html/rfc5343
“To retrieve or manipulate management information using the third version of the Simple Network Management Protocol (SNMPv3) [RFC3410],it is necessary to know the identifier of the remote SNMP protocol engine, the so-called snmpEngineID”
See the following statement in the SNMPTD documentation:
https://docops.ca.com/ca-unified-infrastructure-management-probes/en/alphabetical-probe-articles/snmptd-simple-network-management-protocol-trap-daemon-monitoring/snmptd-im-configuration
“User: This tab applies to SNMP v3 only. If there is a SNMPv3 trap, the message is rejected unless the SNMPv3 user sending the trap is defined. You can refer the user using a combination of the name of the user and an identifier for the given SNMP application that you are talking to (called an "EngineID").”