Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
I have been working to get different kinds of hardware monitoring working in a consistent manner. This is the SuperMicro SuperoDoctor sensors package.
Here is what the final result looks like for one of my systems, and shows the fan speeds, thermal probe temperatures, and voltage levels for all of the available sensors on that server:
There are some caveats here. Obviously, you must have the Superodoctor SNMP extensions installed and working. I have tested this with SuperoDoctor III running on Windows Server 2003 (using native SNMP extensions) and SuperoDoctor II on Linux (using net-snmp extensions) and both seem to work fine.
Which SuperMicro model is this template for?
From my experience (with MRTG and supermicro superodoctors) OID-s vary from model to model (as some have 10 fans, other 2, etc).
Edit: Ignore my incompetence - I am new to cacti
I saw it reads and determinates available monitoring items - very nice!
The posted update contains a fix that converts the SNMP timeout value from Cacti's millisecond format to PHP/Net-SNMP microsecond format. The lack of conversion in the earlier script would sometimes result in excessive retries or complete failure.
THanks for these great scripts, I have a little problem though. I copied the XML from Script_queries to the script_queries folder, the scripts to the scripts folder, and i imported the templates into Cacti, but one of the templates (cacti_graph_template_sensors_supermicro_fan_sensors_8x.xml) gave me some errors: Unmet Dependencies (See Pic). I assume that it is because of this that my fan and termal sensor graphs are not working.
Any thoughts?
Thanks for the help
app
Attachments
unmet dependency.PNG (100.47 KiB) Viewed 32940 times
Cacti does not seem to export GPRINT definitions, so you will need to manually create the missing GPRINT preset.
Click on the Graph Management cacti menu item, and then click on the (new) GPRINT Presets sub-menu underneath. Create a GPRINT Preset with the exact name of "Exact Numbers" and the GPRINT Text value of "%8.0lf". That should allow the graph templates to be imported successfully.
hmmm, that GPRINT Preset was already there. Any other thoughts? In looking at what happens on the import, the GPRINT shows good, but the unmet dependencies appear to be on Data Template Items. Am i doing this right? I just import the 7 XML templates, correct?
I noticed the tarball did not have the default 1X graph templates so I rebuilt the tarball. This shouldn't have been the cause of your problem but who knows.
I am having the same problem as apperrault from above post with the screenshot when importing. I tried both cacti 0.8.6i and 0.8.6j versions - no difference.
Single graphs work just fine for me, but I can't get the 8x versions to work. I am thinking I am doing something incorrectly. Here is what I do:
uppon 'devices' I select the desired host, then at "associated graph templates" I add the supermicro (8x) templates (fan/voltage/thermal), then "create graphs for this host" highlight the new "sensors - supermicro ..." graph templates, click create button at the bottom.
However I always get broken image for that graph.
I have a win 2008 server x64 box and when i enable the snmp support with supero doctor III I am unable to query/snmpwalk to the box at ALL now. I uninstall supero and its all fine
ehall wrote:I uploaded a new version that should work with both Cacti 0.8.6 and 0.8.7 and should also support the SNMPv3 stuff in 0.8.7.
Thanks for posting this. We now encourage contributors to publish their work at the central cacti repository at http://docs.cacti.net/templates
Reinhard
john_d13 wrote:have you got it working with windows ?
I have a win 2008 server x64 box and when i enable the snmp support with supero doctor III I am unable to query/snmpwalk to the box at ALL now. I uninstall supero and its all fine
I had it working with superodoctor III on Windows to make sure the OIDs were the same, but I haven't tried again in the past couple of years. I'd email Supermicro support about the conflict you are having, they have always been nice to me.
