You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jonathan Barber (JIRA)" <ji...@apache.org> on 2012/05/11 01:02:47 UTC
[jira] [Created] (CAMEL-5270) Add community and peer address of
SNMP TRAP PDUs to camel-snmp header
Jonathan Barber created CAMEL-5270:
--------------------------------------
Summary: Add community and peer address of SNMP TRAP PDUs to camel-snmp header
Key: CAMEL-5270
URL: https://issues.apache.org/jira/browse/CAMEL-5270
Project: Camel
Issue Type: Improvement
Components: camel-snmp
Affects Versions: 2.10.0
Reporter: Jonathan Barber
Attachments: snmp-peer-and-community.patch
A patch is included to add the community and peer address of SNMP traps that are received by camel. 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 message header as strings with names:
securityName
peerAddress
These names correspond to the accessor names in the snmp4j API for the CommandResponderEvent class. securityName is not the correct name for SNMP v1/2 traps, but it's probably better to stick with a name that can be consistant between SNMP versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-5270) Add community and peer address of
SNMP TRAP PDUs to camel-snmp header
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-5270:
-----------------------------------
Assignee: Willem Jiang
> Add community and peer address of SNMP TRAP PDUs to camel-snmp header
> ---------------------------------------------------------------------
>
> Key: CAMEL-5270
> URL: https://issues.apache.org/jira/browse/CAMEL-5270
> Project: Camel
> Issue Type: Improvement
> Components: camel-snmp
> Affects Versions: 2.10.0
> Reporter: Jonathan Barber
> Assignee: Willem Jiang
> Attachments: snmp-peer-and-community.patch
>
>
> A patch is included to add the community and peer address of SNMP traps that are received by camel. 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 message header as strings with names:
> securityName
> peerAddress
> These names correspond to the accessor names in the snmp4j API for the CommandResponderEvent class. securityName is not the correct name for SNMP v1/2 traps, but it's probably better to stick with a name that can be consistant between SNMP versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5270) Add community and peer address of
SNMP TRAP PDUs to camel-snmp header
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5270.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
> Add community and peer address of SNMP TRAP PDUs to camel-snmp header
> ---------------------------------------------------------------------
>
> Key: CAMEL-5270
> URL: https://issues.apache.org/jira/browse/CAMEL-5270
> Project: Camel
> Issue Type: Improvement
> Components: camel-snmp
> Affects Versions: 2.10.0
> Reporter: Jonathan Barber
> Assignee: Willem Jiang
> Fix For: 2.10.0
>
> Attachments: snmp-peer-and-community.patch
>
>
> A patch is included to add the community and peer address of SNMP traps that are received by camel. 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 message header as strings with names:
> securityName
> peerAddress
> These names correspond to the accessor names in the snmp4j API for the CommandResponderEvent class. securityName is not the correct name for SNMP v1/2 traps, but it's probably better to stick with a name that can be consistant between SNMP versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5270) Add community and peer address of
SNMP TRAP PDUs to camel-snmp header
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273084#comment-13273084 ]
Willem Jiang commented on CAMEL-5270:
-------------------------------------
Applied patch with thanks to Jonathan, I also updated the camel SNMP wiki page for new enhancement.
> Add community and peer address of SNMP TRAP PDUs to camel-snmp header
> ---------------------------------------------------------------------
>
> Key: CAMEL-5270
> URL: https://issues.apache.org/jira/browse/CAMEL-5270
> Project: Camel
> Issue Type: Improvement
> Components: camel-snmp
> Affects Versions: 2.10.0
> Reporter: Jonathan Barber
> Assignee: Willem Jiang
> Attachments: snmp-peer-and-community.patch
>
>
> A patch is included to add the community and peer address of SNMP traps that are received by camel. 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 message header as strings with names:
> securityName
> peerAddress
> These names correspond to the accessor names in the snmp4j API for the CommandResponderEvent class. securityName is not the correct name for SNMP v1/2 traps, but it's probably better to stick with a name that can be consistant between SNMP versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5270) Add community and peer address of
SNMP TRAP PDUs to camel-snmp header
Posted by "Jonathan Barber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Barber updated CAMEL-5270:
-----------------------------------
Attachment: snmp-peer-and-community.patch
> Add community and peer address of SNMP TRAP PDUs to camel-snmp header
> ---------------------------------------------------------------------
>
> Key: CAMEL-5270
> URL: https://issues.apache.org/jira/browse/CAMEL-5270
> Project: Camel
> Issue Type: Improvement
> Components: camel-snmp
> Affects Versions: 2.10.0
> Reporter: Jonathan Barber
> Attachments: snmp-peer-and-community.patch
>
>
> A patch is included to add the community and peer address of SNMP traps that are received by camel. 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 message header as strings with names:
> securityName
> peerAddress
> These names correspond to the accessor names in the snmp4j API for the CommandResponderEvent class. securityName is not the correct name for SNMP v1/2 traps, but it's probably better to stick with a name that can be consistant between SNMP versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira