---
oid: "1.3.6.1.4.1.838.1.6.1"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 838 agentConfig(1) agentConfiguration(6) agentEngineID(1)}"
description: "agentEngineID OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2019-01-10"
---

## OID : `1.3.6.1.4.1.838.1.6.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 838 agentConfig(1) agentConfiguration(6) agentEngineID(1)}
```

### Description

```asn1
agentEngineID OBJECT-TYPE
SYNTAX DisplayString(SIZE(0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The configured SNMP EngineID used for SNMPv3 packets. This
object can be used to override automatic engine id assignment.
If this object is set, care must be taken to ensure its
uniqueness within the SNMP Domain. Additionally, setting this
object may result in the initialization of snmpEngineBoots.
Normally, this has the desired affect, but if the engine ID is
reset to an old value, previously captured PDUs may again apear
to be valid, since the number of restarts has been reset.

Setting this value results in the following:

> a null EngineID results in the normal 'MAC address'
of the SNMP EngineID encoding as per rfc2271.

> an ASCII string results in the normal 'Text'
administratively assigned value.

> an ASCII string beginning with a '-' results in a
straight, display string implementation of only
readable/printable bytes. This does NOT abide by
the recommendation in rfc2271. Typically, this is
only needed with primative manager stations that have
trouble with non-ascii data."
DEFVAL { "" }
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
