jeopardyracing wrote: > I do see the drive when I run that command on localhost. The relevant line is: > > HOST-RESOURCES-MIB::hrStorageDescr.12 = STRING: /volumes/SATA1 > > Is any of the data there helpful to me getting it into the Zenoss tracking > (ie does that number go into the snmp Index field if I add the storage device > manually?
Unfortunately, I'm not very familiar with adding volumes manually...I've never done. Zenoss has always done a good job of picking it up during the modeling process. Your device should remodel at a set interval and pick up the change automatically. If you run the modeling process manually from a terminal on the zenoss server, as the user "zenoss", it should either pick up the changes or give you some more info as to what is going on with this device. So login to the zenoss server as root. Then Code: su - zenoss zenmodeler run -v 10 --force -d DEVICE zenmodeler is the process that looks for changes on the device (stuff that's added or removed). It maps out what zenoss will monitor. The "run" option tells it to run in the foreground and output everything to the console...as opposed to running it as a daemon. The "-v" is the log severity...assigning it a value of 10 tells it to output as much debug info as possible. The "-d" just specifies the device to model. Can you please run that and copy the output to this thread? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=24993#24993 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
