Friday, June 15, 2012

Accessing SNMP Temperature information on a NetBotz 200 + NetBotz 150

Right, so a delivery of shiny new toys just arrived for me to play with^W^W set up and do work with.

The NetBotz 200 is the modern, new version of the AP9340 EMU. It has the ability to chain up to a dozen NetBotz 150 sensor pods off of it, effectively adding 6 additional sensor ports per pod. This uses some goofy proprietary PoE-ish type thing to connect them, over your run-of-the-mill cat 5/RJ45 cable (don't forget the included terminators on the unused ports).

I picked up a pair of the 200's and a pair of the 150's. The 200's arrived first, so I fired one up at my desk to start poking around. It's very similar to the AP9340's, and actually uses the same OIDs.

Both the AP9340 and the NetBotz 200 use the following OIDs for the temperature and humidity, as well as naming:

1.3.6.1.4.1.318.1.1.10.4.2.3.1.3.0.1  - Sensor Name
1.3.6.1.4.1.318.1.1.10.4.2.3.1.4.0.1  - Sensor Location
1.3.6.1.4.1.318.1.1.10.4.2.3.1.5.0.1  - Temperature
1.3.6.1.4.1.318.1.1.10.4.2.3.1.6.0.1  - Humidity

Like before, if you increment the last digit you'll get the different ports (.1 is for port 1, .2 is port 2, .6 is port 6, etc). Since the NetBotz 150 pods are dumb units, and just add additional port capacity to the 200, my first inclination was that port 1 on the 150 would show up as port 7, giving it an OID of
1.3.6.1.4.1.318.1.1.10.4.2.3.1.4.0.7
This turned out to not be the case. A simple snmpwalk against  1.3.6.1.4.1.318.1.1.10.4.2.3.1
turned up that the second to last digit is significant for the device that the sensor is connected to. Thus, for the first 150 in the chain, you use the following OIDs:

1.3.6.1.4.1.318.1.1.10.4.2.3.1.3.1.1  - Sensor Name
1.3.6.1.4.1.318.1.1.10.4.2.3.1.4.1.1  - Sensor Location
1.3.6.1.4.1.318.1.1.10.4.2.3.1.5.1.1  - Temperature
1.3.6.1.4.1.318.1.1.10.4.2.3.1.6.1.1  - Humidity

My assumption is that the first port on the second 150 in the chain would be .2.1, third 150 would be .3.1, etc.

Now, to get these online in the DC, and to get a more serious way of monitoring them and the AP8941 PDUs than a cron job and a mad script.


No comments:

Post a Comment