436452:  Snmptrap sent to port 161 instead of port 162

Author: Jan Safranek <jsafrane@redhat.com>

Emphasize that 'trapsess' host argument should explicitly include port 
number, otherwise the agent uses wrong port 161 (it should be 162) - the
agent can't distinguish when to use 161 and 162 as default ports. This
feature was added to net-snmp-5.4.1 and cannot be easily ported back to
5.3.2.2.

diff -up net-snmp-5.3.2.2/man/snmpd.conf.5.def.trapsess-port net-snmp-5.3.2.2/man/snmpd.conf.5.def
--- net-snmp-5.3.2.2/man/snmpd.conf.5.def.trapsess-port	2008-08-06 12:40:00.000000000 +0200
+++ net-snmp-5.3.2.2/man/snmpd.conf.5.def	2008-08-06 12:38:21.000000000 +0200
@@ -618,6 +618,13 @@ should be the command-line options requi
 The option \fI-Ci\fR can be used (with \fI-v2c\fR or \fI-v3\fR) to generate
 an INFORM notification rather than an unacknowledged TRAP.
 .IP
+\fIHOST\fR must follow transport specification as described in section
+.B LISTENING ADDRESSES
+in the
+.I snmpd(8)
+manual page. In addition, it should explicitly contain port number, otherwise
+the agent will send the traps to port 161.
+.IP
 This is the appropriate directive for defining SNMPv3 trap receivers.
 See
 http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html