Summary
Question
Answer
1.If the trap is coming as a v1 trap you can use the following property so that NNMi uses the UDP header IP instead of the agent_addr SNMP header field (I am assuming agent_addr is set to 0.0.0.0 by the SNMP agent when sending the trap). This is a global parameter that will affect all traps.
# Use the IP address in an SNMPv1 trap's UDP header instead of the contents
# of the SNMPv1 trap PDU's agent_addr field. This option is useful in
# Duplicate IP address environments that use NAT (Network Address Translation).
# This flag ignores the value of the agent_addr field from the SNMPv1 PDU and
# instead relies on the UDP header to determine the source of the trap. This
# option will not allow an SNMP agent to proxy for another device because the
# agent_addr value is not utilized.
# (default = false)
#!com.hp.nnm.trapd.useUdpHeaderIpAddress=false
You can find this information in the nms-jboss.properties file.
UNIX:
/var/opt/OV/shared/nnm/conf/props/nms-jboss.properties
Windows:
ProgramData\HP\HP BTO Software\shared\nnm\conf\prop\nms-jboss.properties
2.If the trap is coming as v2 then probably the SNMP agent is setting the following varbind to 0.0.0.0 snmpV2TrapAddress .1.3.6.1.6.3.18.1.3.0 NMMi administrator should contact the Vendor.