PKTC-IETF-EVENT-MIB :: pktcEventReporting

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PKTC-IETF-EVENT-MIB › pktcEventReporting

pktcEventReporting

Module: PKTC-IETF-EVENT-MIB

OID (symbolic): PKTC-IETF-EVENT-MIB::pktcEventReporting

OID (numeric): 1.3.6.1.2.1.182.1.4.1.1.5

Node type: OBJECT-TYPE

Type: Bits

Access: read-write

Description: This MIB object defines the action to be taken on occurrence of this event. Bit local(0) refers to local logging of events; bit sylog(1) refers to the transmission of events using syslog; bit snmpTrap(2) refers to the transmission of events using SNMP Traps (SNMPv2-Trap-PDU); and bit snmpInform(3) refers to the transmission of events using SNMP INFORMs.

Setting a bit to a value of '1' indicates that the corresponding action will be taken upon occurrence of this event. If none of the bits are set, then no action is taken upon occurrence of the event. The success of transmission using syslog and SNMP depends on the MTA configuration. For example, a valid syslog server address is required for syslog message transmission.

Specification of a management event does not necessarily include the actions to be taken upon its generation, i.e., it does not need to specify if a generated event needs to be transmitted via SNMP or syslog, or stored locally. Thus, certain default values are specified, based on the event's severity level specified by the MIB object pktcEventSeverityLevel, as follows: - If the severity level of an event is emerg(0), alert(1), crit(2), or err(3), set the bits for local(0), syslog(1), and snmpInform(3) to a value of '1' and set the remaining bits to a value of '0'.

- For an event with any other severity level, set the bits for local(0) and syslog(1) to a value of '1' and set the rest of the bits to a value of '0'.

What is pktcEventReporting?

A bitmask controlling how this event, when it occurs, is reported: locally logged, sent via syslog, sent as an SNMP trap, and/or sent as an SNMP inform; if no bits are set, the event produces no output at all beyond whatever default the MTA applies based on severity.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.182.1.4.1.1.5
snmpwalk -v2c -c public <target> PKTC-IETF-EVENT-MIB::pktcEventReporting

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.182.1.4.1.1.5.1
snmpget -v2c -c public <target> PKTC-IETF-EVENT-MIB::pktcEventReporting.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.182.1.4.1.1.5.1 s <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> pktcEventReporting.1

Start monitoring PacketCable/IPCablecom Multimedia Terminal Adapter (MTA), cable VoIP eMTA device (event/logging) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PKTC-IETF-EVENT-MIB::pktcEventReporting OID value, configure state conditions and alerts, and monitor any PacketCable/IPCablecom Multimedia Terminal Adapter (MTA), cable VoIP eMTA device (event/logging) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.182pktcIetfEventMibPKTC-IETF-EVENT-MIB
1.3.6.1.2.1.182.1pktcEventMibObjectsPKTC-IETF-EVENT-MIB
1.3.6.1.2.1.182.1.4pktcEventsPKTC-IETF-EVENT-MIB
1.3.6.1.2.1.182.1.4.1pktcEventTablePKTC-IETF-EVENT-MIB
1.3.6.1.2.1.182.1.4.1.1pktcEventEntryPKTC-IETF-EVENT-MIB
1.3.6.1.2.1.182.1.4.1.1.5pktcEventReportingPKTC-IETF-EVENT-MIB