---
oid: "1.3.6.1.4.1.4491.2.2.3.4.1.1.5"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4491 clabProject(2) clabProjPacketCable(2) pktcEventMib(3) pktcDevEventDescr(4) pktcDevEventDescrTable(1) pktcDevEventDescrEntry(1) pktcDevEventDescrReporting(5)}"
description: "pktcDevEventDescrReporting OBJECT-TYPE "
last-modified: "2020-09-03"
tags: [oid-repository]
---

## OID: `1.3.6.1.4.1.4491.2.2.3.4.1.1.5` (last updated: 2020-09-03)

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4491 clabProject(2) clabProjPacketCable(2) pktcEventMib(3) pktcDevEventDescr(4) pktcDevEventDescrTable(1) pktcDevEventDescrEntry(1) pktcDevEventDescrReporting(5)}
```

### Description

```asn1
pktcDevEventDescrReporting OBJECT-TYPE 
SYNTAX BITS \{ 
local(0), 
syslog(1), 
snmpTrap(2), 
snmpInform(3)\} 
MAX-ACCESS read-write 
STATUS current 
DESCRIPTION 
"This MIB Object defines the action to be taken on 
occurrence of this event class. 
Setting a bit to a value of '1' indicates that the 
corresponding action will be taken upon occurrence of 
this event, provided the required parameters are present. 
(e.g.,: Syslog Server for Syslog messages, SNMP targets for 
SNMP traps and SNMP INFORMs etc). If none of the bits 
is set, then no action is taken upon occurrence of the 
event. 
The default value of this MIB OBject is dependent on the 
value of the MIB Object 'pktcDevEventDescrLevel', for the 
corresponding event. 
For the following values of 'pktcDevEventDescrLevel': 
emergency(0), alert(1), critical(2) and error(3), 
the PacketCable device MUST set the bits for local(0), 
syslog(1) and snmpInform(3) to a value of '1' and the rest 
to a value of '0'. 
For all the remaining values of 'pktcDevEventDescrLevel', 
the PacketCable device MUST set the bits for local(0) and 
syslog(1) to a value of '1' and the rest to a value of 
'0'."

**Classification**: MIB object for network management

### Supplementary information

Automatically extracted from [Rec. ITU-T J.166](http://itu.int/ITU-T/J.166) (note: Recs ITU-T J.168, J.169 and J.176 were withdrawn in 2006 after their content were updated and incorporated in Rec. ITU-T J.166 (2015)).

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