You and I are in the same boat...I asked practically the same question yesterday.
http://community.zenoss.com/forums/viewtopic.php?t=3919 Zenoss is not automatically aware of MIBs/OIDs even if you import them. Importing MIBs gives Zenoss a way to translate the SNMP traps it receives (match a human readable description to a number i.e. sysDescr.0 = 1.3.6.1.2.1.1.1.0) To make Zenoss aware, you'd have to write a plugin. So until I write a plugin or find one I need...this is what I do. 1. Import the MIBs to Zenoss (looking to the future and gives me a quick lookup rather than having to do snmpwalk all the time/ it's easier to read in Zenoss than it is in the console) 2. Create a template for my device 3. Add a datasource with an OID equal to the value I want to track 4. Graph the datasource's datapoint If you can snmpget the OID from the device then you should be able to graph it. Right now I am having trouble getting the graph to appear the way I want and I think it has to do with choosing COUNTER, GAUGE, DERIVE, or ABSOLUTE. The descriptions of each are pretty clear I am just having trouble deciding which I need. One thing I've seen all over the forums is "don't forget to add .0 to a scalar OID". If you do an snmpget of an OID with and without the .0 you'll notice different results. Sometimes it returns different values, but more importantly Zenoss doesn't interpret the scalar OID without the .0. Hope this helps...I am working through the same issue right now and having some success so let me know if you have more questions. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13010#13010 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
