Red Hat Bugzilla – Bug 880960
SNMP Trap notifications sent from JON using incorrect port
Last modified: 2013-09-03 10:44:23 EDT
Created attachment 653392 [details]
default snmap trap port
Description of problem:
- A trap notification is created with the default port
- the trap appears to have been created to use the default port of 162
However, the trap is not sent on port 162, it uses port 161.
If a trap is created to explicitly use port 162, the trap is sent as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The snmp trap notification is sent on port 161
I did not set the port, it will use the default port, you can see from the attachement that the default port is set to 162, so the snmp trap notification should be sent on port 162
JON bug : https://bugzilla.redhat.com/show_bug.cgi?id=880945
see the attachement, it is the customer case 00745614 https://c.na7.visual.force.com/apex/Case_View?id=500A000000BerX9&sfdc.override=1
fixed in master
time: Fri Jan 18 14:50:07 2013 +0100
author: Jirka Kremser - email@example.com
message: [BZ 880960 - SNMP Trap notifications sent from JON using incorrect port] typo: default port for snmptrapd has been set to 162
note for QA: for verifying the bug, the wireshark (filtering communication on ports 161/162) can be used (no need for actuall installing of snmpd/snmptrapd)
Bulk closing of issues in old RHQ releases that are in production for a while now.
Please open a new issue when running into an issue.