Almost. DataFabric Manager uses the file system name as its key, rather than the SNMP OID index. I'm not aware of any way to trick MRTG into doing it that way.
- Brian Hackworth
When asked how Data Fabric Manager can handle this, the answer was that since it relies on a database, DFM is clever enough to update the index to check.
Quoting message received from Hackworth, Brian:
Almost. DataFabric Manager uses the file system name as its key, rather than the SNMP OID index. I'm not aware of any way to trick MRTG into doing it that way.
Start feeding MRTG or better RRD by your own - e.g. write a perl script that collects .1.3.6.1.4.1.789.1.5.4.1.2.* and make a mapping <name>:<id> (match !~ /snapshot/). I use RRD for it since it is more comfortable for that, can draw more graphs in one chart and you can define where in which db-field the data will go. You'll find all relevant OIDs in(/filer/vol/<rootvol>)/etc/mib/traps.dat:
dfKBytesTotal snmp.1.3.6.1.4.1.789.1.5.4.1.3.<vol id> dfKBytesUsed snmp.1.3.6.1.4.1.789.1.5.4.1.4.<vol id> dfKBytesAvail snmp.1.3.6.1.4.1.789.1.5.4.1.5.<vol id>
I've added a (edited) output example.
Greetings,
-
Hackworth, Brian -
Stefan Funke