---
oid: "1.3.6.1.4.1.4491.2.2.3.5.1.1.8"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4491 clabProject(2) clabProjPacketCable(2) pktcEventMib(3) pktcDevEventLog(5) pktcDevEventLogTable(1) pktcDevEventLogEntry(1) pktcDevEvLogTargetInfo(8)}"
description: "pktcDevEvLogTargetInfo OBJECT-TYPE"
last-modified: "2020-09-03"
tags: [oid-repository]
---

## OID: `1.3.6.1.4.1.4491.2.2.3.5.1.1.8`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4491 clabProject(2) clabProjPacketCable(2) pktcEventMib(3) pktcDevEventLog(5) pktcDevEventLogTable(1) pktcDevEventLogEntry(1) pktcDevEvLogTargetInfo(8)}
```

### Description

```asn1
pktcDevEvLogTargetInfo OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB Object contains a comma separated list of the
actions taken, along with the target IP address for the
generated event.
The syntax is as:
<action-1/IP:port>,<action-2/IP:port>,<action-3/IP:port>
Where <action-n/IP> is to be denoted as follows:
For Syslog events:
syslog/<IP address of the Syslog Server:port>
For SNMP traps:
snmpTrap/<IP address of the SNMP Server:port>
For SNMP INFORMS:
snmpInform/<IP address of the SNMP Server:port>
If there are multiple targets for the same type (SNMP
Traps sent to multiple IP addresses) or if there are
multiple messages sent to the same IP (Syslog and SNMP
sent to the same IP address) they need to be reported
individually."

**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 and J.169 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)