DX Infrastructure Manager

Expand all | Collapse all

Engine_id in snmptd

Jump to Best Answer
  • 1.  Engine_id in snmptd

    Posted 02-22-2018 09:25 AM

    #engine_id in #snmptd

    what is engine_id in snmptd, How can i create this.

  • 2.  Re: Engine_id in snmptd
    Best Answer

    Posted 02-22-2018 09:45 AM

    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:




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

  • 3.  Re: Engine_id in snmptd

    Posted 02-22-2018 08:56 PM

    engine id is controlled by SNMP device side, not snmptd probe side.

  • 4.  Re: Engine_id in snmptd

    Posted 08-24-2018 05:34 AM

    One of the things that you will encounter with engine_id when you use SNMPv3 is that if you use a system for keeping a track of router (or other network device) configurations then you may end up with duplicate engine_ids due to common configuration being pushed out. The engine_id should be unique for every SNMPv3 agent that is on the system. Spectrum (and others) do respect this and will display errors when encountering duplicates.