[
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 f{{{}lowfile{}}} is created and nothing is
written to the logs.
Checking the SNMP RFCs, there is no mention of uniqueness constraints for the
OIDs:
* [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.
Given this, we think that even if a trap contains duplicated OIDs, a
{{flowfile}} should still be created. Attributes in that {{flowfile}} should be
filled with the value of the latest occurrence of the corresponding OID.
was:
When sending a SNMP trap with duplicated OID, {{ListenSNMPTrap}} processor
silently discards the trap: no f{{{}lowfile{}}} is created and nothing is
written to the logs.
Checking the SNMP RFCs, there is no mention of uniqueness constraints for the
OIDs:
* [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.
Given this, we think that even if a trap contains duplicated OIDs, a {{flowfile
}}should still be created. Attributes in that {{flowfile }}should be filled
with the value of the latest occurrence of the corresponding OID.
> 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
> Affects Versions: 1.28.1
> Reporter: Antonio Sousa
> Priority: Major
>
> When sending a SNMP trap with duplicated OID, {{ListenSNMPTrap}} processor
> silently discards the trap: no f{{{}lowfile{}}} is created and nothing is
> written to the logs.
> Checking the SNMP RFCs, there is no mention of uniqueness constraints for the
> OIDs:
> * [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.
> Given this, we think that even if a trap contains duplicated OIDs, a
> {{flowfile}} should still be created. Attributes in that {{flowfile}} should
> be filled with the value of the latest occurrence of the corresponding OID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
