I'm using NPM 10.1.3 and have some alets configured for email - they seem to work fine. We have recently installed another tool to receive traps from the existing monitoring tools for high level event correlation. I configured new alerts in Solarwinds to send traps to the new system if nodes are down, interfaces are down, or if a node reboots. most of the traps come through fine, but some are traps are formatted inconsistently. While we receive them all on the correlation tool, some of the traps come through fine and others come through with the event description in hex. This screws up the parsing of the trap and presents garbage in the correlation console. I've set the trap receiver on the correlation tool to a degugging level and the trap is received with what apears to be line breaks in the event text. The hex of a "bad" event is displayed like this:
53 37 33 34 57 4d 41 30 30 31 2d 47 69 67 61\n62 69 74.....and so on.
How can this be corrected? Please help?