This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How to uniquely identify the IP address of a node within a MoM for traps received from NPM?

When Orion NPM sends an SNMP trap to a north bound SNMP trap receiver or MoM (Manager of Managers) such as HP OM in our case, the source address of the packet is populated with the IP of the Solarwinds Orion server. As such the MoM cannot uniqely identify the end node that generated the trap. Has anyone come across this scenario and have a solution or workaround?

One work around we are pursuing is to have the trap re-issued to the MoM using Kiwi tools which will form a SNMP Trap packet with the source address from the IP address varbind that was in the trap from NPM.

  • Hi,

    if I understand you correctly you would like to change the source address of trap when going out from NPM correct? If so this is a spoofing and most of firewalls will block such packet because source destination will be different than subnet from where it is coming from.

    What would be possible is to re-package the trap and include "origin IP" as part of a new outgoing package so it could be reassembled on receiver side and you can get the origin.

  • In Cisco devices, you can embed the IP address in the syslog message text.

    Not sure about other device types though.

    Also an idea is to use the syslog viewer to modify the message by adding the source IP. (assuming you can use some kind of a variable for the source IP)

    pastedImage_0.png