I am using a RA11 and the server setup from my previous tutorial. I am not a big fan of the RA11 as you can tell from my review.
First check if you device has SNMP settings you need to enter before starting the tutorial. My RA11 requires I place the IP of the SNMP server in its web interface (not the Zenoss web interface). Here are the Dell Poweredge MIB, Cisco MIB and a large list of MIB files if you need to download them.
Download the MIB from your manufacture and copy them to your /opt/zenoss/share/mibs/NeWfOlDeRnAmE
My file name is ROOMALERT11E.MIB
The folder name I chose is ra11
Check the group and owner of the MIB file ls -l
Change the group and owner to zenoss wheel
Change to the zenoss user and import the MIB file.
su - zenoss
zenmib run ROOMALERT11E.MIB
INFO:zen.zenmib:Skipping file /opt/zenoss/share/mibs/irtf/IRTF-NMRG-SMING-TYPES
INFO:zen.zenmib:Skipping file /opt/zenoss/share/mibs/irtf/IRTF-NMRG-SMING-EXTENSIONS
INFO:zen.zenmib:Skipping file /opt/zenoss/share/mibs/irtf/IRTF-NMRG-SMING
INFO:zen.zenmib:Loaded mib ROOMALERT11E-MIB
It will should show up in the web interface under "Main View" "Mibs"
Now lets add the device.
Login to Zenoss via http://example.com:8080
Under "Management" select "Add Device"
For the "Device Name" use the ip or host name of the environmental monitor. In my case it is 192.168.30.73
The remainder of the information is optional, but fill out as much as you can.
Now select "Add Device"
You will see the Zenoss try and model the device via SNMP.
You might see some errors and warnings, that does not mean you where not successful.
Select the "Navigate to device 192.168.30.73" at the bottom of the "Collection Log"
Your device has been added and up-time is being monitored. At this point if your device sends a alert it will show on the main dashboard.
We need to find out what OID has the data we are looking for.
If you are on a windows machine you can use http://www.ireasoning.com/mibbrowser.shtml for free.
In linux use snmpwalk -v1 -c <community> <env. monitor host/IP> <OID>
You can get the OID from the "Mibs" location from the beginning of the tutorial.
You may need to try the OID with a .0 at the end. Even if you get the correct response without the .0 you will need to enter the .0 for the "DataSource"
snmpwalk -v1 -c public 192.168.30.73 18.104.22.168.4.1.20922.214.171.124.2.2.0
This is the response I get
SNMPv2-SMI::enterprises.209126.96.36.199.2.2.0 = INTEGER: 8384
That means 83.84 degrees Fahrenheit.
We have added a MIB file.
Added a new device.
Found out the OID number we want to use.
Lets make them work together and so something real important, make a cool temperature graph.
Select the device and go to "PerfConf" tab.
Select "Local Copy" of the RRD template
Add a "DataSource" where the data is coming from.
Add a "DataPoint"
I changed the RPN to convert the 8384 to 83.84
I also made the graph color blue, it is the same color as the sensor hardware.
Go back to the "PerfConf" tab for your device. This is not required for the graph.
Add a Threshold such as hightemp.
IMPORTANT THE MAX VALUE IS THE INTEGER VALUE NOT THE CONVERTED RPN VALUE.
For example my "Max Value" is 9000 NOT 90.00
Finally we can make a graph.
At the bottom of "PerfConf" add a "Graph"
Now if you select "Perf" you will see your graph, it can take some time before it starts so do not worry. Check back in a hour.
If you do not get a graph here are some things to try (as su - zenoss):
zenperfsnmp run 192.168.30.73 -v -10
zenperfsnmp run 192.168.30.73
One of the problems I had is snmpwalk would give the value I wanted but zenperfsnmp said the OID was bad unless I added the .0
This is my graph, you see the spike where someone thought the server room fan was to loud and unplugged it.
This is my new graph, I added another temp sensor. Now one is red and one is blue.
That's all for now, my next how to will cover running commands based on events. We will be doing graceful server shutdowns based on high temperatures.
I would like to thank Steve Huston with Princeton University for helping with this How-to.