---
oid: "1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
short-description: "eventLogNumber 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.2`

```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) eventLogNumber(2)}
```

### Description

```asn1
eventLogNumber OBJECT-TYPE
SYNTAX INTEGER(1..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>The event number within this class for this event.
Event numbers shall be assigned starting at 1 and shall increaseto the value specified by the associated eventClassLimit for theclass associated with the rows. Events shall maintain a
chronological ordering in the table with the oldest event of aclass occupying the row with eventNumber = 1, and subsequentevents filling subsequent rows. This ordering shall be maintainedfor those rows still remaining when events are cleared.
<DescriptiveName>Event.number:identifier
<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.