Can a snmpv3 profile for snmptd probe be created with a wildcard for the engineid?

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe

Issue/Introduction

The SNMPTD probe "SNMPv3 User Settings" menu displays the following fields:

Can a single SNMPv3 profile be created with a wildcard for the engineid?

Environment

- snmptd probe and devices with Simple Network Management Protocol version 3 (SNMPv3) capability.

Resolution

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”

Please refer to the following statement in the snmptd probe documentation

“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 to 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").”