I've installed OSPF-MIB and OSPF-TRAP-MIB in zenoss, so I can setup alerts on ospf neighbor loss, or any critical events regarding ospf. The MIBs installed fine (long with the related dependencies), and the OIDs listed by zenoss are correct.
Now when a router sends an OSPF trap, Zenoss doesn't know the OID and display this trap in the /Unknown class - I wondered why it didn't match the OIDs I loaded, and looking closely at the trap, I realized there's a '0' that shouldn't be there : 1.3.6.1.2.1.14.16.2.0.2 should be 1.3.6.1.2.1.14.16.2.2 and 1.3.6.1.2.1.14.16.0.2 should be 1.3.6.1.2.1.14.16.2 I captured the trap using tcpdump, and the OIDs were Ok in the packets - I came to the conclusion those extra '0' have been somehow added by the zentrap daemon - Can anyone confirm this, so I can send a bugreport ? I know I can map this events to whatever alerts I want, but imho this would be more of a workaround than a real solution. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=26731#26731 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
