That's very helpful and it certainly gives me something to get started with.
If I'm being honest I was kind of hoping that I'd missed some option somewhere which, when clicked on, did exactly what I wanted. But the fact that you've felt need to write your own tool like that suggests that I haven't. The frustration stems from the fact that SNMP OID 1.2.3.4.5.6.7.8.9.10 may refer to hdBlocksFree on sda4 on one host and hdBlocksFree on sda2 on another - and the only way to find out which partition it refers to on a particular host is to walk the tree for that host. Generally speaking, some other OID at a parallel point in the tree enumerates which index refers to which item - for instance: 1.2.3.4.5.6.7.8.9.10 : STRING: sda2 1.2.3.4.5.6.7.8.9.11 : STRING: sda3 1.2.3.4.5.6.7.8.9.12 : STRING: sda4 1.2.3.4.5.6.7.8.9.13 : STRING: sda5 1.2.3.4.5.6.7.8.10.10 : INTEGER: 12345 1.2.3.4.5.6.7.8.10.11 : INTEGER: 34567 1.2.3.4.5.6.7.8.10.12 : INTEGER: 56789 1.2.3.4.5.6.7.8.10.13 : INTEGER: 78901 allows us to deduce that sda2 has 12345 blocks free, sda3 has 34567 blocks free etc. Looks like the only way I'm going to know how it was done is to dig in the source code. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17243#17243 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
