#2033 SNMP Trap PDU agent-addr is different from agentaddress
# software version number
# snmpd -v
NET-SNMP version: 5.3.1
Web: http://www.net-snmp.org/
Email: net-snmp-coders@lists.sourceforge.net
# the operating system you are using
# uname -a
Linux LO_RADIUS_1 2.6.18-53.el5PAE #1 SMP Wed Oct 10 16:48:18 EDT 2007 i686 i686 i386 GNU/Linux
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Problem/feature:
This has been reported previously on 1156545 but maybe it wasn't explained correctly.
In 5.3.1 if the agentaddress IP address configured on the snmpd.conf the trap is not sent in the agent-addr field of the SNMP PDU although is sent on the destination IP address. I notice that the usual is that snmpd uses the eth0 (first kernel interface) as the IP address to send on the SNMP PDU agent-addr field.
If the eth0 matches the snmpd.conf:agentaddress config it works but if the agentaddress is eth1 the HP Openview inserts on the alarm DB the source as the SNMP PDU agent-addr field. It supose this is the correct behavior.
Although the integrator can match the eth0 to be the snmpd.conf:agentaddress configured it is not the best way to do it.
The man of snmp.conf says the following:
clientaddr [<transport-specifier>:]<transport-address>
specifies the source address to be used by command-line applications when sending SNMP requests. See snmpcmd(1) for more information about the format of addresses.
This value is also used by snmpd when generating notifications.
Since this doesn't work it seems to be a bug.
Thanks for the bug report!
We've fixed the problem in the main development
tree (SVN trunk), so it should be fixed in the next major
release of the Net-SNMP package.
Ok, I've made some search and there is a patch 1916840 that solves this problem in 5.5 release.
I change to version 2c and it works fine. trapsink -> trap2sink