What i did in this situation is to use an event transform. In my case we have load balancers that send traps every time the real server service goes down or up.
The key idea is to map the device "component" attribute to a unique identifier in the trap (one of the OID variables in the "details" tab of the event). That way the event is unique to the component (in your case the interface). mine looks like this: evt.component=str(evt.snL4TrapRealServerName) + ":" + str(evt.snL4TrapRealServerPort) In your case you'll want to replace the variables with something that will work for you. Hope this helps, -Joseph -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36611#36611 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
