Weetos wrote: > 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 (along 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 > displays 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 these events to whatever alerts I want, but imho this would > be more of a workaround than a real solution.
Hmmmm.... I can duplicate the issue if I'm using v1 traps: [EMAIL PROTECTED] ~]# snmptrap -v 1 -c public localhost 1.3.6.1.2.1.14.16.2 localhost 6 1 '' 1.3.6.1.2.1.14.16.2.2.0 s "test trap" but not when using v2c traps: [EMAIL PROTECTED] ~]# snmptrap -v 2c -c public localhost '' 1.3.6.1.2.1.14.16.2.2 1.3.6.1.2.1.14.16.2.2.0 s "yet another test trap" If possible switch to using version 2c traps which doesn't seem to have this issue. I've opened up http://dev.zenoss.com/trac/ticket/3965 on your behalf. It should be noted that the events will come in and be placed into /Unknown unless you've set up event mappings to do something different with them. kells -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=26874#26874 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
