[
https://issues.apache.org/jira/browse/NIFI-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sousa updated NIFI-14466:
---------------------------------
Description:
When sending a SNMP trap with duplicated OID, {{ListenSNMPTrap}} processor
silently discards the trap: no {{FlowFile}} is created and nothing is written
to the logs.
No mention of uniqueness constraints on the OIDs on SNMP RFCs:
* [RFC 1157 (SNMPv1)|https://www.rfc-editor.org/rfc/rfc1157#page-19] defines a
{{VarBindList}} as:
A sequence of variable bindings, each of which contains an object identifier
and its value.
* [RFC 3416 (SNMPv2)|https://www.rfc-editor.org/rfc/rfc3416#page-8] similarly
defines a {{VarBindList}} as:
A list of one or more variable bindings. The order of variable bindings in the
list is preserved.
So no mention of uniqueness constraints on the OIDs.
was:
Add attribute corresponding to peer address of SNMP traps that are received.
This is useful to determine where a trap originated from, as not all SNMPv2
traps include an OID that identifies the sender.
The information is placed in the attribute with name snmp$peerAddress
> ListenSNMPTrap does not support duplicated varbinds
> ----------------------------------------------------
>
> Key: NIFI-14466
> URL: https://issues.apache.org/jira/browse/NIFI-14466
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Antonio Sousa
> Priority: Major
> Fix For: 1.28.1
>
>
> When sending a SNMP trap with duplicated OID, {{ListenSNMPTrap}} processor
> silently discards the trap: no {{FlowFile}} is created and nothing is written
> to the logs.
> No mention of uniqueness constraints on the OIDs on SNMP RFCs:
> * [RFC 1157 (SNMPv1)|https://www.rfc-editor.org/rfc/rfc1157#page-19] defines
> a {{VarBindList}} as:
> A sequence of variable bindings, each of which contains an object identifier
> and its value.
> * [RFC 3416 (SNMPv2)|https://www.rfc-editor.org/rfc/rfc3416#page-8]
> similarly defines a {{VarBindList}} as:
> A list of one or more variable bindings. The order of variable bindings in
> the list is preserved.
> So no mention of uniqueness constraints on the OIDs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
