Red Hat Bugzilla – Bug 880945
When send SNMP Trap notifications from JON, using incorrect port
Last modified: 2014-01-02 15:34:47 EST
Created attachment 653363 [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
see the attachement, it is the customer case 00745614 https://c.na7.visual.force.com/apex/Case_View?id=500A000000BerX9&sfdc.override=1
This was fixed in master c5539a4
on Jan 18th, 2013 in Bug 880960
Verified on Version : 3.2.0.GA Build Number : df41432:804f1e9
Created an alert definition using snmp trap notification on default port.
The trap notification is sent on 162 port. Verified with starting snmptrapd listening to 162 port.
When snmptrapd is started listening on 161 port, the snmptrapd o/p does not show the trap notification after firing alert.