---
oid: "1.3.6.1.4.1.164.6.5.2.1.1"
short-description: "alarmEventLogEntry OBJECT-TYPE"
last-modified: "2024-05-03"
parent-oid: "1.3.6.1.4.1.164.6.5.2.1"
---

## OID: `1.3.6.1.4.1.164.6.5.2.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 164 radGen(6) fmObjects(5) alarmEventLog(2) alarmEventLogTable(1) alarmEventLogEntry(1)}
```

### Description

```asn1
alarmEventLogEntry OBJECT-TYPE
SYNTAX AlarmEventLogEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in the table holds either a raised alarm,
either a cleared alarm, or, an event."
INDEX {alarmEventLogIndex}
```

**Classification:** MIB object for network management

### Child OIDs

- `1.3.6.1.4.1.164.6.5.2.1.1.1`: `alarmEventLogIndex(1)`
- `1.3.6.1.4.1.164.6.5.2.1.1.2`: `alarmEventLogDateAndTime(2)`
- `1.3.6.1.4.1.164.6.5.2.1.1.3`: `alarmEventLogAlarmOrEventId(3)`
- `1.3.6.1.4.1.164.6.5.2.1.1.4`: `alarmEventLogDescription(4)`
- `1.3.6.1.4.1.164.6.5.2.1.1.5`: `alarmEventLogSourceId(5)`
- `1.3.6.1.4.1.164.6.5.2.1.1.6`: `alarmEventLogSourceType(6)`
- `1.3.6.1.4.1.164.6.5.2.1.1.7`: `alarmEventLogSeverity(7)`
- `1.3.6.1.4.1.164.6.5.2.1.1.8`: `alarmEventProperties(8)`
- `1.3.6.1.4.1.164.6.5.2.1.1.9`: `alarmEventReason(9)`
- `1.3.6.1.4.1.164.6.5.2.1.1.10`: `alarmEventLogSourceName(10)`

### 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.
