On Jun 5, 2008, at 12:41 PM, Patrick Landry wrote: > I am currently monitoring tempSensorValueIntF.1095346743 directly, for > instance, with this entry in datacollection-config.xml: > > <mibObj oid=".1.3.6.1.4.1.5528.100.4.1.1.1.9" instance="1095346743" > alias="netBotz2-temp" type="INTEGER" /> > > I assume that this works because the instance value happens to fit > into an integer. > > I would like to be able to monitor all of these sets of sensors using > Indexes rather than monitoring them directly. The leads me to the > problem of what MIB variable to use as an index. It seems that > tempSensorEntry.10 would be the correct Index variable for the > temperature sensors but how do I enter that into > datacollection-config.xml? > > My feeling is that this NetBotz MIB is broken. Is there any hope for > me?
The new Netbotz mib is the suck (the version one stuff was amazing). I usually use generic indices to get this working. I can't remember which client I did this for recently (so I don't have an easy example) but by using the generics you can set the instance for everything (check the configs for the Net-SNMP disk stuff for an example). -T _______________________________________________________________________ Tarus Balog, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 503 961 7746 Email: [EMAIL PROTECTED] URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
