Event Forwarding loses problem server name

[Doug Koenig]

`I am going to run multiple IM-7 monitoring stations in our environment. We will be doing this to resolve some or the timeouts we get when going to Europe, Asia, and S. America. When I setup the event forwarding from one instance to send to the master, I lose the problem server name so now I can't tell what device caused the problem without going to the remote IM-7 log.

[Jadrice Toussaint]

DO you have the problem server in the IM-7 database? even if you have multiple IM7 servers, the main one where you wish to receive all events forwarded will still need to know that the problem server is on its local database. Try and see if that works out for you.

[Doug Koenig]

In my test setup I have the servers exist in both IM-7 servers list. Remote receives the event and logs it correctly in the Uncleared Event screen with the correct device name.When the master receives the event in the Uncleared Events list the device name has been replaced with the name of the remote server where IM-7 is running.

[Jadrice Toussaint]

Doug -

This seem to be an issue with the way IM7 forwards. What I did notice though is you can tell from the trap details who the problem server is.

[Doug Koenig]

On the events that I have looked at the original device name is not contained in the message.