I should update this. In the scenario where the device where the actual trap is comming from is being monitorded by zenoss, you will need to set both evt.device and evt.ipAddress or this technique will not work. Most of my NMS systems that forward traps include the ne name and the ne ipaddress where error orinated.
For example, I map the AdvaNMS events like this
# Map the base parameters
evt.device = evt.neName
evt.ipAddress = evt.neIpAddress
# And the others
evt.component = evt.entity
evt.summary = evt.description
evt.eventKey = evt.name
evt.ipAddress = evt.neIpAddress
If you cant get the ipddr you may need to use a DNS lookup inside the transform. Something like this would be equivelent to above if my event did not include the originating ip address
import socket
# Map the base parameters
evt.device = evt.neName
evt.ipAddress = socket.gethostbyname(evt.device)
# And the others
evt.component = evt.entity
evt.summary = evt.description
evt.eventKey = evt.name
evt.ipAddress = evt.neIpAddress
I hope this helps.
Rod.