---
oid: "1.3.6.1.4.1.644.2.4.3.6"
short-description: "trapType OBJECT-TYPE"
last-modified: "2026-04-16"
parent-oid: "1.3.6.1.4.1.644.2.4.3"
---

## OID: `1.3.6.1.4.1.644.2.4.3.6`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 644 eriProducts(2) dnx(4) traps(3) trapType(6)}
```

### Description

```asn1
trapType OBJECT-TYPE
SYNTAX -- Long list deleted.
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This is the specific Trap Code that represents the type of alarm or event that occurred. Each alarm type has a code that sets the trap as active and a corresponding code that clears the trap to simulate an alarm. The event type codes have the prefix 'evnt' but also occur at the start of and end of the event. Each Type code has a base number that represents the resource type followed by the bit number from the resource extended device state. Each event or alarm will have a trap for the start equal to the bit number plus the base number and then a trap at the end of the event/alarm equal to the bit number plus the base number plus 40.
For example, clearSlotMissing(142) represents a SLOT resource which has a base 100, bit 2 for slot missing, plus 40 to signify the end of the alarm. The exception to this is General Events such as evntColdStart(1)."
```

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