as i see the only thing you have to do for snmp traps is importing the right enterprise mibs for the devices.
i alreadty do it for nortel passport devices and for enterasys swithces. Now i can interpret the snmp traps operat0r wrote: > I posted on http://forums.zenoss.com/viewtopic.php?p=32374#32374 > > Basically ANY trap I get does not resolve fully .. I don't know why. It > would be one thing if I did not have the mibs loaded or if it was one or two > not resolving but ANY ... > > > > snmp trap vmwProductSpecific.3.201 > > * what logs should I be looking at > * if I imported all the right mib using the import tool via CLI that is all I > need to do right ? > * what other info do you need to help resolve this ? > > * running: > > Zenoss Zenoss 2.3.3 > OS Linux (i686) 2.6.24 (Linux lupe 2.6.24-19-server #1 SMP Wed Aug 20 > 23:54:28 UTC 2008 i686) > Zope Zope 2.8.8 > Python Python 2.4.4 > Database MySQL 0.0.0 (Ver 0) > RRD RRDtool 1.2.26 > Twisted Twisted 2.5.0 > NetSnmp NetSnmp 5.4.1 > PyNetSnmp PyNetSnmp 0.28.12 > WMI Wmi 1.1.8 > > I am going to try 2.4 today .. > [Image: http://rmccurdy.com/public_images/zenoss/Clipboard01.jpg ] > [Image: http://rmccurdy.com/public_images/zenoss/Clipboard02.jpg ] > [Image: http://rmccurdy.com/public_images/zenoss/Clipboard03.jpg ] -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=34585#34585 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
