Netbotz Devices host Template

[lmorair]

Hello again,
To complete my former post (Uptime Devices Host Template) , we also have a Netbotz 300B in one of our locations.
Thanks to that device, we monitor the air flow, humidity, temperature and have a camera there. The problem is that the device has a very good interface but a poor SNMP implementation (MIBs are included) allowing us to monitor it, but not through an indexed SNMP query .
As we have only three things to monitor, it is not a big deal, so here you will find the host template, exported with "dependencies".
Please feel free to send me any feedback or comments!
Regards,
Lmorair

[kurgoth]

I keep getting an error when trying to look at this template. Any suggestions?

[JBs]

Not 100% sure but this template has been designed for cacti 0.8.6b. Maybe this is a version connflict?

[TheWitness]

Templates are not currently version portable. To import a Template from a 0.8.6c system, it must have been exported on one.

TheWitness

[jtnfoley]

What are the odds that somebody's already got this ported to Version 0.8.6h?

[shanekennedy]

this query should work for version H

snmpget -v1 -c adllc <hostname> .1.3.6.1.4.1.5528.30.10.1.0 .1.3.6.1.4.1.5528.30.10.2.0 | awk 'BEGIN{ RS = "" }{print "temp:"$4" humd:"$8}'

[mrjibbles]

HI,
Has anyone got this working on i release?
Getting XML parse errors on importing.
Cheers

[yetdog]

Anyone have this for the i version of Cacti?

[aleto]

Anyone got this working for latest cacti yet?

[Splash]

I have a NetBotz 520 and using Cacti 0.8.7 I was able to import the NetBotz templates with no problem. To get it to graph however I had to change the OID strings in the Data Templates with the data below. I still can't find the threshold values, once I do I will post them. I also picked up that even though I specified a RO SNMP community, it stuck to the default "public".


Temp: .1.3.6.1.4.1.5528.100.4.1.1.1.8.21604919
Humidity: .1.3.6.1.4.1.5528.100.4.1.2.1.7.20490798
AirFlow: .1.3.6.1.4.1.5528.100.4.1.5.1.8.18717296

[ebjers]

you may need to remove the degree symbol ° from the xml code before inporting into Cacti

[guanno]

Here is an updated template for a Netbotz 420 using (F) Degrees.
The OID's are different than the 520.
Using 8.7a

[surferboy]

I'm getting "-nan" on my graphs. I have a Netbotz 550 appliance. How do I find my OID that I'm meant to use and where do I have to place the value once I've found it? I don't know what to look for with SNMPWalk.

[eschoeller]

@surferboy, et al.

I hate to break it to you but the updated templates will not work for anyone but guanno. In their sheer brilliance it looks like netbotz decided to use the sensor unique identifier as the index value. Take the following example:

Code: Select all

$ snmpwalk -v2c -c public 192.X.X.X .1.3.6.1.4.1.5528.100.4.1.1.1.9 -m  ALL
NETBOTZ320-MIB::tempSensorValueIntF.242089423 = INTEGER: 71
NETBOTZ320-MIB::tempSensorValueIntF.636159851 = INTEGER: 74
NETBOTZ320-MIB::tempSensorValueIntF.882181375 = INTEGER: 87
NETBOTZ320-MIB::tempSensorValueIntF.1619732064 = INTEGER: 106
NETBOTZ320-MIB::tempSensorValueIntF.1665932156 = INTEGER: 74
NETBOTZ320-MIB::tempSensorValueIntF.1751899818 = INTEGER: 71
NETBOTZ320-MIB::tempSensorValueIntF.2628357572 = INTEGER: 71
NETBOTZ320-MIB::tempSensorValueIntF.2716713264 = INTEGER: 109
NETBOTZ320-MIB::tempSensorValueIntF.3103062985 = INTEGER: 75
NETBOTZ320-MIB::tempSensorValueIntF.3406802758 = INTEGER: 74

Code: Select all

snmpwalk -v2c -c public 192.X.X.X NETBOTZ320-MIB::tempSensorLabel -m  ALL
NETBOTZ320-MIB::tempSensorLabel.242089423 = STRING: A-07 Temperature  (2)
NETBOTZ320-MIB::tempSensorLabel.636159851 = STRING: A-04 Temperature  (4)
NETBOTZ320-MIB::tempSensorLabel.882181375 = STRING: A-13 Back Temperature  (1)
NETBOTZ320-MIB::tempSensorLabel.1619732064 = STRING: A-04 Back Temperature  (2)
NETBOTZ320-MIB::tempSensorLabel.1665932156 = STRING: A-09 Temperature  (4)
NETBOTZ320-MIB::tempSensorLabel.1751899818 = STRING: A-11 Temperature  (2)
NETBOTZ320-MIB::tempSensorLabel.2628357572 = STRING: A-05 Temperature  (1)
NETBOTZ320-MIB::tempSensorLabel.2716713264 = STRING: A-09 Back Temperature  (1)
NETBOTZ320-MIB::tempSensorLabel.3103062985 = STRING: A-13 Temperature  (4)
NETBOTZ320-MIB::tempSensorLabel.3406802758 = STRING: A-02 Temperature  (3)

From a developer's standpoint I can certainly understand the desire to do this. But it wreaks total havoc for Cacti, Nagios, or anything else that would need to have some sort of standard. Plus, if you have a sensor fail, the IDs will all change when you swap it out. Perhaps this is part of the desired behaviour.

Either way, a more complex approach needs to be taken to accurately handle the newer netbotz appliances .. most likely a script data query. One of these days I'm going to tackle this but if someone beats me to it ... please let me know