---
oid: "1.3.6.1.4.1.1206.4.2.6.4.4.1.5"
short-description: "eventLogValue OBJECT-TYPE"
last-modified: "2025-07-02"
parent-oid: "1.3.6.1.4.1.1206.4.2.6.4.4.1"
---

## OID: `1.3.6.1.4.1.1206.4.2.6.4.4.1.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1206 transportation(4) devices(2) global(6) globalReport(4) eventLogTable(4) eventLogEntry(1) eventLogValue(5)}
```

### Description

```asn1
eventLogValue OBJECT-TYPE
SYNTAX OpaqueACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>The value of this object is set to the BER encodingof the value referenced by the eventConfigLogOID of the associatedeventLogID when the event was logged. Its length is variable.
The value shall not contain any padding characters either beforeor after the values.
NOTE: Opaque objects are doubly wrapped. For SNMP operations,
which use BER, this would be {type, length, {type, length,
value}}. For example, a zero-length octet string, would beencoded in BER as 0x44 02 04 00. For STMP or SFMP operations,
which use OER, this would be {length, {type, length, value}}.
For example, the same example would be encoded in OER as 0x02 0400.
<DescriptiveName>Event.logValue:frame
<DataConceptType>Data Element"
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

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

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.