---
oid: "1.3.6.1.6.3.2.1.2.2.1.2"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpM2M(2) snmpM2MObjects(1) snmpEvent(2) snmpEventTable(2) snmpEventEntry(1) snmpEventID(2)}"
description: "snmpEventID OBJECT-TYPE "
last-modified: "2020-06-02"
tags: [oid-repository]
---

## OID: `1.3.6.1.6.3.2.1.2.2.1.2` (last updated: 2020-06-02)

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpM2M(2) snmpM2MObjects(1) snmpEvent(2) snmpEventTable(2) snmpEventEntry(1) snmpEventID(2)}
```

### Description

```asn1
snmpEventID OBJECT-TYPE 
SYNTAX OBJECT IDENTIFIER 
MAX-ACCESS read-create 
STATUS current 
DESCRIPTION 
"The authoritative identification of the event 
type generated by this entry. This variable 
occurs as the second varbind of an InformRequest- 
PDU. If this OBJECT IDENTIFIER maps to a 
NOTIFICATION-TYPE the sender will place the 
objects listed in the NOTIFICATION-TYPE in the 
varbind list."

**Classification**: MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 1451](https://www.rfc-editor.org/rfc/rfc1451.html).

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