I do a lot of trap processing with Zenoss, and it look like you're missing the mib needed to decode those OID's.
This numeric OID's you posted seem to be from the HP enterprises section. In order to make these traps useful to you, you'll need to find and install the mibs. Once you do, they will start showing up as a name. At that point you'll need to map them to an event class assign severity and apply any transform rules. Traps can be 'chatty' and depending on their nature you might be setting their severity to informational and stick them in the history table, or drop them all together. You indicate that your switch is fine, but in my experience traps don't lie. Traps are sent because the device, in this case a switch, has had a trappable event happen. Link up/down events happen because a port changed state. If link state changes are happening and you're not sure why (ie no ones unplugging cables etc...) it's something that should be looked in to. It could be a failing nic or a loose cable or something else. I was curious so I looked up some of the OID's and 1.3.6.1.4.1.11.2.14.12.1.0.5 is hpicfFaultFinderTrap. The trap details should provide more information, but it doesn't sound good. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17573#17573 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
